The Escalation Case File
A one-page case file that turns a long, scattered complaint history into a dated timeline, a list of every promise made, and one clear next step.
When a complaint escalates, the manager inherits weeks of emails, WhatsApp messages and call notes spread across systems and agents. They either spend an hour reading it all or reply without knowing what an earlier agent already promised.
That is the gap this drop closes. It is a customer support skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
For customer support managers and team leads who take over escalated complaints.
How it works
The skill file does five things, in this order.
1. Collect every channel's history. Export the email thread, WhatsApp chat, call notes and ticket comments for this one customer. Order does not matter, but nothing should be left out.
2. Paste the policy that applies. Add the refund, warranty or service policy the case falls under. Without it the model will stop and ask for it, which is intended.
3. Fill the placeholders and run. Enter your company name and the person who owns the escalation, then run the prompt in Kimi with everything pasted in.
4. Check the promises list first. Open each quoted promise against the source message and confirm its status. Treat anything marked [inferred] as a question to verify, not a fact.
5. Decide and log the next step. Take the recommended step or the fallback and record your decision in the ticket. Attach the case file so the next person does not rebuild it.
What comes back
A one-page escalation file with a dated timeline, every promise quoted and marked kept, broken or open, a policy check, the open questions and a recommended next step with a fallback.
The mistake to avoid
Most people paste only the latest ticket and the last agent's summary, so promises made earlier on WhatsApp or by phone vanish from the file. Paste the whole history from every channel, however long, because the broken promise is usually buried in the middle.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
The prompt
You are a senior customer support lead preparing an escalation case file for {company_name}. The reader is {escalation_owner}, who has not seen this case before and must decide the next step today.
Below is the full history of one customer complaint, pasted from several channels in any order and in Arabic or English. Read every item before writing anything.
<customer_history>
{paste all emails, WhatsApp chats, call notes and ticket comments for this customer}
</customer_history>
<our_policy>
{paste the refund, warranty or service policy that applies}
</our_policy>
Do the following:
1. Build a dated timeline of every contact, oldest first: date, channel, who spoke, what was said in one line. If a date is missing, write "date unknown", place it where the content suggests and mark it [inferred].
2. List every promise our side made: who made it, when, the exact quoted words, and whether it was kept, broken or still open.
3. State the customer's current request in one sentence, using their words where possible.
4. Compare the promises and the request against the policy. Flag every conflict.
5. List the facts still unknown and who could confirm each one.
6. Recommend one next step and one fallback, each tied to a timeline entry.
Rules: use only the pasted material and never guess. Mark anything you infer as [inferred]. If the history is too incomplete to build a timeline, or the policy is missing, state exactly what is missing and stop. Write in English but keep customer quotes in their original language. Keep the file to one page.Bilingual Interview Guides That Work in Arabic
Next drop · 0123Check the Signed Copy Against the Draft
Skills that pair with this one
Extract Data Tables from Arabic PDFs
Pull structured data from Arabic research reports and keep the numbers accurate
Build a Bilingual Customer Segmentation Model
Segment your market in Arabic and English without losing nuance in either language
Negotiate in Arabic Without Losing Nuance
Preserve cultural context and technical precision when negotiating in Arabic
The daily skill, in your inbox
One email each morning with the new drop. Unsubscribe in one click.
