Shop / Prompts & Skills / How to Say No to Customers Politely — Boundary Email Prompt for Customer Success

Say no to a customer — politely, and without implying yes

For customer success leads who have to say no without starting a fight: paste your facts, get one firm, polite email audited for promises you never made. The hard part is rarely the no itself. It is the sentence after it — the softener that accidentally promises an exception, a date, or an approval nobody granted. A boundary email has to be warm in tone and exact in content at the same time.

Anatomy of a boundary email that holds

1. Acknowledge what was asked — the customer's launch timing is named, so the reply is clearly about their request, not a form letter.
2. State the boundary as a fact of the plan — 'your current plan provides support Monday through Friday' — a limit of the agreement, not a personal refusal and not an apology spiral.
3. Offer only the approved next step — an upgrade quote can be requested. Nothing about it is arranged, priced or promised.
4. Close without reopening the door — no 'let me see what I can do' that the customer will read as a maybe.

The real email, with its commitment audit

The boundary email prompt returns the draft plus an audit of what it committed to — and what it deliberately did not:

Subject: Support coverage for your launch
Email: Hi,

Thanks for sharing the timing of your launch. Your current plan provides support Monday through Friday, so we cannot include weekend coverage under that plan.

If weekend support is important for the launch, you can request a quote for an upgraded support plan. I can point you to that option, but no additional coverage is arranged at this stage.

Best,
[Name]

Commitment audit: Confirmed boundary: weekday coverage only. Approved next step: request an upgrade quote. Unverified claims withheld: availability, price, start date, or approval of upgraded coverage.

Sample data above is fictional, shown so you can judge the output before buying.

Why the audit is the point

Fights start over implied promises: availability, a price, a start date, an approval. The audit lists the confirmed boundary and the approved next step on one side, and the unverified claims withheld on the other, so a lead can check the email in seconds before it goes out. The prompt works only from the permissions you supply — it cannot approve a refund or an exception you did not grant, and it drafts for human review rather than sending.

Questions