How do I tell a customer how to report a problem with the completed service?
Quick answer
Tell the customer plainly which approved contact route to use, then list a few details that will help your team identify the service: for example, the service date, a reference number if one exists, and a short description of the problem. Use placeholders until you confirm the correct route and details for your process. Keep the wording courteous and do not promise a response time or outcome unless your procedures support it.
The question, the details, the next step.
I need a short message to send after a service is completed. How do I tell a customer where to report a problem without sounding defensive or promising something we cannot guarantee?
Put the action first: name the contact route the customer should actually use, then explain what information will help you identify the service. Keep the tone courteous and matter-of-fact. Clear, concise business writing puts the important information and requested action near the beginning. [S1]
Use this as a starting point, replacing each bracketed item with information confirmed for your organization:
“Questions or concerns about the completed service? Please contact us through [approved contact route]. To help us identify the service, include [service date or reference number, if available] and a brief description of the problem. You may also include [other detail your process needs].”
Do not leave the placeholder in the message you send. If you do not have an approved contact route, confirm one with the appropriate person before sending; do not guess or invent a phone number, email, portal, or response commitment.
What details should I ask the customer to include? I want enough information to find the job, but I do not want to turn this into a long form.
Start with the smallest set your team can use to locate the service. A practical draft might request a service date or reference number, if available, plus a brief description of what seems wrong. Add another item only if your actual process needs it—for example, the relevant part of the service or a useful way to follow up. These are drafting options, not universal requirements; confirm what your team can use and avoid asking for unnecessary details.
For example, if your process identifies jobs by reference number, write: “Please include your reference number, if you have it, and a short description of the problem.” If it relies on dates instead, substitute the date. The writing guidance supports including information needed for the reader’s action, but it does not establish which details a particular provider needs. [S2]
Could you show me a complete version that is warm but neutral? We use a contact route that I will insert later, and I do not want to imply when anyone will reply.
Here is a copyable version with placeholders:
“Thank you for having us complete your service. If you have a question or notice a problem, please contact us through [approved contact route]. To help us identify the service, include [reference number or service date, if available] and a brief description of the issue. [Optional: Include any other detail your team actually needs.]”
This acknowledges the completed work without arguing about the customer’s concern. It gives one clear next action and does not state a response time, resolution, or customer right. Keep the optional sentence only if the information is useful to your real process. Clear purpose and reader-focused revision help make a business message easier to act on. [S1] [S2]
How should I check the message before sending it, especially if several people on our team will reuse it?
Check it from the customer’s point of view: can they immediately see where to report the problem and what to include? Then check it against your own process: is the contact route current, are the requested details genuinely useful, and have all placeholders been replaced or removed? Purdue OWL recommends reviewing whether the purpose is clear, likely reader questions are answered, and the information needed for the intended action is present. [S2]
For a shared template, assign someone to confirm the route and any process-specific details before it is reused. The writing guidance does not verify your channel, define a complaint process, or establish response guarantees or customer rights; those must not be inferred from the wording advice.
A practical checklist
Name the approved contact route near the start; verify it rather than guessing.
Request only details your team needs to identify the service, such as a reference number or date if applicable.
Use courteous, neutral wording and avoid blame or defensive explanations.
Remove every bracketed placeholder before sending.
Check that the message makes no unsupported promise about timing, outcome, or rights.
A few more useful answers
What if I do not know which contact route the customer should use?
Do not guess. Confirm the route with the person responsible for your organization’s process, then add that verified route to the message.
Should I promise that someone will respond within a certain time?
Only include a response timeframe if your organization has confirmed that commitment and wants it stated here. Otherwise, leave it out.
Do I need to ask for a reference number?
Ask for one if your process uses it and phrase it as optional when customers may not have it. The exact identifying details depend on your organization’s process.
Sources
References used for this guide.
- [S1] General Guidelines for Business Writing owl.purdue.edu · Checked
- [S2] Revision in Business Writing owl.purdue.edu · Checked