claude skills / Customer service pack / resume-de-ticket / en français

Ticket Summary.

Thirty seconds to know what was said, promised and forgotten before you pick up a customer.

See what it produces
  • Zendesk
  • Freshdesk
  • HubSpot
  • Salesforce
  • Gmail
  • Outlook
5 linescustomer, request, history, promises, next step
8 linesof dated timeline, at most
0card number, password or code copied into the summary

orders of magnitude, depending on your volume

the problem

What gets in the way today.

  • 01The thread runs to forty messages and the agent answers the first request, not the latest one.
  • 02A callback promised by a colleague is overdue, and nobody noticed.
  • 03The manager asks "where are we on this?" and you have to reread everything.

input, output

You give this. You get this.

The email thread, pasted as is

Clair Logis, heat pump maintenance under contract.
28/10 9:12 am, customer: "My heat pump shows E4, no more heating. Contract CL-2291."
28/10 11:40 am, Samir: "A technician will come on Thursday 30th between 8 am and 12 pm."
30/10 1:05 pm, customer: "Nobody came. I took the morning off."
30/10 4:20 pm, Laura: "We will call you back tomorrow with a new slot."
03/11 8:50 am, customer: "Still no call. 15 degrees with a 4-month-old baby. I'm going to cancel."

$ claude "Summarize this ticket before I call the customer back."

Summary of ticket CL-2291example

Summary as of 3 November 2026, 10 am

Alert: promised callback overdue, home unheated with a baby, threat to cancel.

1. Customer: private individual with an annual heat pump maintenance contract.

2. Current request: a visit to get the heating working again, otherwise cancel and get a refund.

3. History: fault reported on 28/10, visit on 30/10 did not happen, promised callback not made.

4. Promised by the company: visit on 30/10 from 8 am to 12 pm (Samir, overdue), callback on 31/10 (Laura, overdue).

5. Expected next step: a fast visit, no heating since 28/10.

Tension: angry, "I'm going to cancel"

Customer chasers: 2 | Last message: 3 November, 8:50 am

Timeline

28/10 Customer: fault, code E4

28/10 Samir: visit promised on 30/10

30/10 Customer: technician did not come, morning taken off

30/10 Laura: callback promised on 31/10

03/11 Customer: no call, threat to cancel

Recommended next action

Call from the scheduling manager this morning with a firm slot, then written confirmation.

Unknown or to check

Contract cancellation terms, before any reply on this point.

the method

What Claude does, in order.

  1. step 1Put it in order

    Messages sorted by date, quoted earlier emails and identical reminders removed.

  2. step 2Extract the facts

    For each message: who, new fact, new request, new promise.

  3. step 3Set the current state

    The latest request, commitments kept, in progress or overdue, the number of times the customer chased.

  4. step 4Write the five lines

    Tension backed by a quote, short timeline, then a separate recommendation flagged as such.

demo in French / click, try it

Your turn.

An interactive demo of the skill. It is in French, the pack works in any language: ask Claude to answer in English.

the film / 44 seconds, with sound

The pack film.

the pack film

In 8 seconds.

the guardrails

What the skill never does.

  • Only what is written in the thread: an inference is marked "(inferred)", a gap becomes "unknown".
  • Absolute dates, never "three days ago".
  • Every promise with its date, its author and its status: kept, in progress, overdue.
  • Sensitive data never copied: card, IBAN, password, health beyond what is needed.

Questions

Can the summary be used to hand over to another team?

Yes, that is one of its uses: the five lines, the open commitments and the timeline are enough to take over the case without rereading the thread.

What does the skill do with a card number pasted into a message?

It never copies it. The summary only notes that bank details appear in the message of a given date, and recommends deleting them from the tool.

How is tension measured?

With an exact quote from the customer and four levels: calm, annoyed, angry, threatening. At the threatening level, the summary recommends handing over to a manager.

Does the skill write the reply too?

No, it prepares the handover. The reply is then written with the Unhappy Customer skill or an entry from the Response Library.

the pack

In the pack: Customer service pack.