OpenCode: Customer service report
Expanded web report · Related PDF snapshot: 22 October 2026 · PDF page 8
Research reviewed 22 October 2026 · Evidence and editorial planning guidance are distinguished below.
Give accurate answers and preserve customer commitments
If customers ask about AI-assisted support or delivery delays, describe the verified service effect rather than making broad claims about the tool incident. Staff should not request provider API keys or promise refunds on behalf of another vendor.
Your immediate priorities
- Direct account-specific AI billing questions to the designated account owner.
- Use a clear fallback process for support tasks that temporarily lack AI assistance.
How to work through the decision
Use one approved, dated account of what is known, what is still being checked and when the next update is expected. Avoid diagnosing compromise from a customer’s description alone. Record the minimum information needed to route a case; passwords, payment card details and recovery codes do not belong in ordinary support chat. Track unresolved orders and promised follow-ups separately from general incident questions.
Evidence to ask for
An approved service-impact message with a named escalation route for billing or privacy questions.
Are we reporting our own verified service status or repeating an unconfirmed external claim?
Work with the next person
Send the business manager a concise list of customer effects, unresolved commitments and recurring questions. Escalate new security evidence through the incident channel, preserving the original report without circulating sensitive material.
Continue with the business manager report for this topic.
A scenario to rehearse
Illustrative exercise, not an observed customer incident: A development team removes a key from a coding tool but leaves the same key active at its provider. The exercise tests whether the team recognises that removing a local configuration entry is not revocation.
What a useful outcome looks like
An approved service-impact message with a named escalation route for billing or privacy questions. Keep the decision dated and return to it if new evidence changes the scope.