A customer asks you to change a billing record, approve an exception, or troubleshoot a system you do not manage. A vague “that’s not my department” may be accurate, but it leaves the customer to work out what to do next. A better reply names the boundary, points to the right contact or process when you know it, and makes clear whether you will pass the request along or the customer must take the next step. The goal is not to promise an outcome you cannot control; it is to keep the handoff understandable and the request from disappearing.
The useful bits
- State what is outside your role without blaming another team.
- Give a specific contact or process only when you know it is appropriate.
- Clarify who will take the next step and what the customer should expect.
Separate the request from your boundary
Begin by showing that you understand what the customer is asking for. Then state the limit in plain terms: you cannot change that record, approve that exception, or access that system. A short explanation can help, but avoid a long defense of your role or a list of internal rules the customer cannot act on.
Keep the boundary about authority or responsibility, not the customer’s worthiness. “I’m not able to approve account-credit requests” is clearer and less personal than “I can’t help you with that.” If you can still answer part of the question, separate that useful help from the part you cannot handle.
I understand you’re asking us to correct the invoice address. I can explain the information shown on the invoice, but I’m not able to change billing records.
Offer a route, not a guess
If you know the correct contact or established process, give enough detail for the customer to use it. Name the team or role, explain what channel to use, and mention any information they should include if that is known. Avoid inventing a department, email address, form, or response time just to make the handoff sound complete.
When the route is uncertain, say so and take a small verification step before redirecting. You might check an approved internal directory or ask the responsible team how requests should be sent. If you cannot verify the destination, tell the customer what you are checking rather than sending them to a likely-but-unconfirmed contact.
Choose who owns the next move
A referral is not automatically a handoff. Decide whether the customer should contact the appropriate team themselves or whether you will forward the request, introduce them, or ask someone to follow up. State that choice directly. If the customer must act, identify the action; if you are taking it, say what you will do and avoid implying that the receiving team has accepted or resolved the request.
Follow your organization’s rules for sharing customer information. Forward only what the next contact needs, use an approved channel, and tell the customer before you share details when your process requires it. If you cannot transfer the request yourself, do not describe the message as transferred.
Make the next step easy to complete
A useful redirect answers the customer’s immediate practical questions: who should they contact, how should they reach them, and what should they include? Keep the instructions focused. If the right process asks for a reference number or a description of the requested change, mention it only when you know that information is needed.
Where there is no confirmed timeline, do not invent one. You can still set a reasonable expectation about your own action, such as when you will send a handoff, if you are able to meet that commitment. Distinguish that from the other team’s response time, which may not be yours to promise.
Please send the request to the billing contact listed in your account correspondence and include the invoice number and the corrected address. I can’t update the billing record from this support channel.
Use a calm, complete reply
A reliable message usually has four parts: recognition, boundary, route, and ownership. Keep the tone courteous without over-apologizing or adding uncertainty that obscures the instruction. If the customer has already tried the recommended route, acknowledge that and avoid simply repeating it; find out whether there is another verified process or whether you can raise the routing question internally.
For example, if you are able to make a handoff, describe the action you will take and what you need from the customer, if anything. If the customer needs to contact someone directly, make that responsibility explicit. Either way, do not imply that a referral guarantees approval, a particular outcome, or a particular reply time.
I understand you need the billing address corrected. I’m not able to edit billing records here. Please contact the billing team through the address shown on your invoice and include the invoice number. I haven’t sent this request on your behalf, so the next step is yours.
Check that the request has a next step
Before sending, read the reply from the customer’s point of view. Can they tell what is outside your role, where to go, and who is expected to act now? Remove internal jargon and any directions that depend on an unverified assumption. If you promised a handoff, complete it through the appropriate channel and follow your normal process for recording or tracking the request.
Use this quick check when the request crosses a boundary:
- Did I identify the specific part I cannot handle?
- Is the contact or process confirmed and usable?
- Did I say whether I or the customer takes the next step?
- Have I avoided promises about another team’s decision or timing?
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction