Set expectations when a customer asks for an exception review

Acknowledge the request without deciding it

Start by reflecting the request in plain language and, where appropriate, recognize why it matters to the customer. Then distinguish what you can confirm now from what still needs review. For example: “I understand you’re asking us to [requested exception] because [stated reason]. I’ve recorded the request, but I can’t confirm an outcome before it has been assessed.”

Avoid language such as “That should be fine,” “We’ll make an exception,” or “Consider it handled” unless an authorized person has actually made and communicated that decision. Even a friendly guess can be understood as a promise. Acknowledging the customer’s concern does not require agreeing with their proposed solution.

Route it to the person who can assess it

The right reviewer depends on what the customer is asking to change and how your organization assigns decision-making authority. A frontline contact can gather facts and explain the process, but should not imply they can approve an exception if that authority sits elsewhere. Route the request to the designated owner or team for the affected policy, service, or commitment; if you are unsure who that is, check internally before naming a reviewer.

Tell the customer what you can accurately say about the handoff. You might explain that the request is being sent for review, identify the team or role if it is appropriate to do so, and note that the reviewer will assess it against the relevant circumstances and requirements. Do not invent a formal process, claim a review has started before it has, or suggest that escalation itself makes approval more likely.

Ask for facts that could change the assessment

Keep information requests focused. Useful details often include the specific exception being requested, the service or decision it concerns, the relevant dates, and a concise explanation of the circumstances. Ask for supporting records only when they are relevant and can be handled through an appropriate channel. If the customer has already provided a detail, do not ask for it again without a reason.

Separate necessary facts from sensitive information. Do not request passwords, one-time codes, or unrelated personal details. If the request is unclear, ask a neutral question such as, “Which part of [decision or requirement] would you like us to review?” This helps the reviewer understand the request without steering the customer toward a particular answer.

• What exact change or exception is being requested?
• Which decision, service, or time period does it concern?
• What relevant circumstances or documentation should the reviewer consider?

Set a next-update time you can meet

Give the customer a calendar date or a clear interval for your next update, based on what you can reasonably manage. If you cannot estimate when the review will finish, say so. You can still commit to checking the status and contacting the customer by a stated time, even if the decision is not ready then.

Make clear what that update means: it may provide a decision, request more information, or explain that the assessment is still underway. Avoid implying that a particular outcome or completion date is certain unless it has been confirmed. If a delay becomes apparent, contact the customer before the promised update time where possible, explain what has changed, and give a revised time for the next communication.

Use a reply that makes the boundary clear

A useful response has four parts: acknowledge the request, state that it needs assessment, explain the next step, and set a time for an update. Keep the wording direct and avoid overly formal language. Adapt this example to your actual process and do not name a team or deadline unless it is accurate.

Subject: Update on your request

Hello [customer name],

I understand you’re asking us to [specific exception] regarding [relevant matter]. I’ve recorded the request, and [team or authorized role] needs to assess the information before we can confirm an outcome. Could you please share [specific relevant detail or document, if needed]?

I’ll update you by [date and time, including time zone], even if the review is still in progress. That update will not necessarily mean a decision has been made.

Regards,
[Your name]

Confirm the handoff and follow through

Before sending, check that the request is accurately summarized, the next step is real, and the person or team receiving it has enough context to assess it. Record the customer’s requested outcome, relevant facts, any information still needed, and the time you promised to update them according to your organization’s process. Avoid recording speculation as if it were a decision.

You can confirm the communication worked by checking that the customer knows what is under review, whether they need to provide anything, and when they will hear from you next. At that time, send the promised update—even if there is no final answer. If the request is declined, explain the decision and any available next step only when those details are confirmed. Clear follow-through does not guarantee approval; it makes the process easier to understand.