SaaS support reply templates for the questions that keep coming back

1. How do I answer a pricing question?

Use this when someone asks which plan fits a specific need. Answer that need before linking to the entire pricing page. Do not add urgency or recommend the more expensive plan without a reason.

Hi [name], for [specific task], you need [plan] because it includes [relevant feature or allowance]. It costs [verified price and billing interval]. You can compare the details here: [pricing link]. If you tell me [one missing requirement], I can help you check whether that plan covers it.

Verify billing frequency, currency, and any usage cap. If the free plan meets the stated requirement, say so. A clear answer is more useful than pushing an upgrade the customer does not need.

2. How do I acknowledge a refund request?

Use a request acknowledgment until you have checked eligibility. A saved reply must not turn an uncertain refund into an automatic promise.

Hi [name], I’ve received your refund request. Please send [approved order reference] to [private support channel] so we can find the purchase and review it against our policy: [refund policy link]. Please do not send card details. We’ll confirm the outcome after checking the order.

Only say you received a request if you have. Add a review timeframe only when it reflects your actual process. If a refund has already been approved, write a separate confirmation with verified transaction details.

3. What should a setup-help reply include?

A customer who says “It doesn’t work” needs one useful next step, not every possible troubleshooting path. Start with the last step you know they completed.

Hi [name], after [completed step], the next step is [exact action and location]. You should then see [verified success state]. The steps are here: [setup guide]. If you still see [reported problem], send the exact error text and which step you reached. Please remove any private data from screenshots.

Check screen names against the current product. For a template or downloadable tool, replace settings instructions with the actual file, import, or installation step the buyer needs.

4. How do I respond to login or access trouble?

Separate access troubleshooting from identity verification. Never ask someone to send a password, one-time code, sign-in link, API key, or payment card information.

Hi [name], please check that you’re using the email address and sign-in method associated with your account. If you originally used [supported method], try that option at [official login URL]. If access still fails, contact [private support channel] with the error message and [approved non-secret account reference] so we can investigate.

Adapt the method to your product. Do not tell a Google OAuth user to reset a password if your product does not provide password login. Avoid confirming account ownership before your checks are complete.

5. How can I acknowledge a feature request without promising it?

The useful information is the customer’s intended outcome. A request for an integration may really be a request to avoid re-entering the same data.

Hi [name], [requested capability] isn’t available in the product today. What are you trying to complete with it, and what are you doing instead? That context will help us evaluate the request. I can’t promise a release date. [Include a verified workaround only if one exists.]

Do not say “coming soon” because an idea appears in your notes. If you offer to notify the customer, make sure you have a way to remember and follow through.

6. What is a clear cancellation reply?

Give the cancellation path first. Asking for feedback should not get in the way of the action the customer requested.

Hi [name], you can cancel renewal from [verified billing path] by choosing [actual action]. Your access after cancellation follows [link to your current policy]. Check for [actual confirmation shown by your product] to confirm the change. If the option is missing or does not work, contact [support channel] and we can check it with you.

Do not claim a subscription is canceled unless you have confirmed its state. Add an exact access-end date only after checking that customer’s paid period. Keep cancellation and deletion instructions separate.

7. How should I answer a data or privacy question?

Use verified policies, not reassuring guesses. Claims about encryption, data residency, retention, AI training, or certifications need evidence specific to your service.

Hi [name], our current privacy information is here: [privacy policy link]. For your question about [specific data use], the relevant detail is [verified explanation]. If you need clarification or want to make a data request, email [privacy contact]. Please avoid sending sensitive records until we confirm what information is needed.

If you do not know the answer, say you will check. A careful follow-up is better than an unsupported security claim that a customer relies on when deciding whether to use your product.

How do I reuse these templates without sounding scripted?

Read the customer’s message first. Delete instructions they already tried, acknowledge their specific problem, and leave one clear next step. On WhatsApp or in a DM, shorten the answer and offer a public help link for the longer explanation. Email can carry a little more detail.

Save the reviewed version in Ansilo, using the customer question as a searchable title and a category such as Billing or Access. AI assistance can help with wording, but you still need to check facts before applying the suggestion. Ansilo does not send these replies for you.

See the example public help center for answers worth publishing. For a routine that keeps templates current, follow how to stop rewriting customer replies. Save these in Ansilo and reuse them when the next customer asks.