How to Reply When Customers Ask for Policy Exceptions

When a customer asks for a policy exception, acknowledge their situation, check what you can authorize, and give a clear answer. Explain the relevant reason briefly, then confirm the next step or offer an alternative you can actually provide.

A useful reply follows this pattern:

Acknowledge the request → state the decision → explain the reason → confirm what happens next.

You do not need to defend your entire policy. The customer needs to know whether you can help and what your answer means for them.

Check whether it is really an exception

Before deciding how to respond, separate three situations:

• An error to correct: Your system charged the customer twice or failed to apply an agreed discount.
• An existing entitlement: The customer qualifies under your published terms, contract, or applicable law.
• A discretionary request: The customer wants something beyond those commitments, such as extra trial time.

Do not describe fixing your own billing error as a special favor.

Legal rights also deserve a separate check. For example, UK government guidance explains that consumer protections cover goods, services, and digital content. That is a UK consumer example, not a universal rule for B2B SaaS contracts. Check the customer’s status, jurisdiction, and applicable terms before treating a request as discretionary. Source: GOV.UK consumer rights guidance

For a solo founder, this can be a short review of the invoice, account history, relevant policy, and earlier promises. Ask the customer only for information you still need.

Decide using reasons you can apply consistently

For discretionary requests, consider:

• What happened? Did a product issue, unclear message, or customer mistake lead to the request?
• What would resolve it? A refund, extension, credit, or explanation may address different needs.
• What can you deliver? Check the cost, technical limits, and ongoing work involved.
• Would you make the same decision in a comparable case? Base flexibility on the circumstances, not how forcefully someone complains.

These are practical decision criteria, not a requirement to approve every sympathetic request.

A real example of explicit flexibility comes from 37signals. Its refund policy lists circumstances in which it grants full refunds, partial refunds, or credits. For Basecamp, Highrise, and other products, those examples include a recent renewal the customer meant to cancel and reviewing account usage when considering certain partial refunds. Source: 37signals refund policy

The useful lesson is to define circumstances that justify flexibility. Your business can choose different limits.

How to write the reply

Acknowledge the specific situation

Show that you understood the request without promising an outcome.

All sample replies below are hypothetical. Replace their details with verified facts and approved actions.

“Thanks for explaining that your team couldn’t finish the evaluation before the trial ended.”

That gives the customer more useful acknowledgment than a generic “We understand your frustration.”

Put the decision near the beginning

Make the answer easy to find:

“I can extend the trial through [date].”

“I’m unable to apply the expired discount to this subscription.”

“I need to check the cancellation record before confirming whether a refund is due.”

Distinguish an approval from something still under review. If you need more time, give a specific update deadline you can meet.

Explain the relevant reason

Keep the explanation short and truthful. Link to the relevant policy where it helps.

Avoid inventing a technical restriction when the decision is commercial. Likewise, do not say “I’m not allowed” if you are the founder making the decision.

For an approved exception, explain its scope: the amount, affected invoice, extension date, or duration. “One-time exception” alone leaves too much unclear.

Confirm the next step

Say whether you have completed the action or still need the customer’s agreement.

For refunds, distinguish issuing the refund from the money reaching the customer. Include a processing estimate only when you have verified it.

For trial extensions, clarify the new end date and any billing implications.

Practical policy exception reply templates

Use these hypothetical templates only when the stated decision and alternative are available.

Approving a trial extension

Hi [name],

>

Thanks for explaining that your team needs another review session. I’ve extended your trial through [date].

>

This adds [number] days to your evaluation. [Explain whether billing starts automatically or requires an upgrade.]

>

Your existing workspace is ready to use.

This makes the approval useful by explaining both access and billing.

Approving a refund outside the usual window

Hi [name],

>

I reviewed your request and the account history. Although this falls outside our usual [length] refund window, I’ve approved a refund of [amount] for invoice [number] because [specific reason].

>

[State whether the refund has been issued or when you will issue it.] [Explain the subscription status and access end date.]

Only call it an exception after confirming the refund is discretionary.

Declining a discount exception

Hi [name],

>

Thanks for asking about the expired offer. I’m unable to apply it to this subscription because it was limited to purchases completed by [date].

>

If your main concern is the monthly cost, [available plan] costs [amount] and includes [relevant features]. Moving to it would mean losing [relevant capability].

>

I haven’t changed your subscription.

An alternative should address the customer’s need and disclose meaningful tradeoffs.

Reviewing an unclear billing request

Hi [name],

>

Thanks for flagging the renewal charge. I’m checking whether your cancellation request reached us before the renewal.

>

I’ll update you by [date, time, and time zone]. If you have a cancellation confirmation, please forward it so I can compare it with our records.

Avoid asking for evidence already available in your support history.

Holding a boundary after a repeated request

Hi [name],

>

I understand that you’re asking for [requested exception]. I’ve reviewed [relevant facts], and my decision remains [decision] because [brief reason].

>

The available option is [alternative]. If there is information I have missed, I can review it.

Do not invent an escalation team if you handle support alone. Explain any genuine review route that exists.

Keep exceptions from becoming accidental promises

Record the decision in a short internal note: what was requested, why you approved or declined it, who authorized it, and exactly what you promised.

Keep customer-specific exceptions separate from general policy guidance. If you reuse replies or use AI to draft them, verify that an earlier concession has not become a standard offer.

When similar requests recur, review the underlying policy or product flow. Repeated requests about renewal timing, for example, are a reason to inspect how that timing is communicated.

References

• 37signals refund policy: A published example of circumstance-based refunds and credits.
• GOV.UK consumer rights guidance: UK consumer protections covering goods, services, and digital content.

Conclusion

A good policy exception reply makes the decision clear, explains the relevant reason, and gives an accurate next step. Check existing obligations first, apply discretion consistently, and promise only what you can deliver.