Ticket Summarizer

Get full context on an account before you pick up the phone. Joy summarizes the open and recent tickets, the recurring issues, and the current status, so you start the call already knowing the history instead of asking the customer to repeat it.

Per Customer Success Managers Support Agents Support Leads Account Handoffs
Prompt di esempio per l'assistente Joy

Summarize the support ticket history for [account] before my call. Pull the open and recent tickets, recurring issues, current status, and what I need to know walking in, using our support records in the Knowledge Center.

Ecco come può apparire

Un esempio illustrativo: il tuo risultato dipenderà dalle tue fonti, dai tuoi dati e dalle tue richieste.

Summarize the support ticket history for Northstar Financial before my call. Pull the open and recent tickets, recurring issues, current status, and what I need to know walking in, using our support records in the Knowledge Center.

I read Northstar Financial's tickets from the last 90 days in the Knowledge Center. There's one open escalation you'll want to lead with, and a recurring theme underneath it that's worth naming on the call.

Ticket summary: Northstar Financial

Account: Northstar Financial
Window: last 90 days
Tickets: 2 open, 5 resolved

Northstar has had a rough month, and it traces back to one thing: their nightly data export keeps failing. Two of the open and recent tickets are the same root issue resurfacing. Walk in acknowledging that pattern, not treating today's ticket as a one-off, and you'll defuse most of the frustration before it starts.

Open right now.

TicketIssueStatus
#4821Nightly export failed again (3rd time)Escalated to tier 2, fix pending
#4830Report totals don't match dashboardAwaiting info from customer

Recently resolved.

  • #4795: SSO login loop for two users. Resolved in 2 days; customer confirmed.
  • #4778 and #4762: earlier export failures, both closed with a manual re-run rather than a root-cause fix, which is why it's back.

Recurring issue to name. The export has now failed three times in 90 days (#4762, #4778, #4821). Each was patched, not fixed. That's almost certainly why the account feels unheard. Every time it comes back it feels like starting over. Getting tier 2 to commit to a root-cause fix is the single thing that will change how this relationship feels.

What to know walking in. Lead with #4821 and own the pattern: three failures, and this time you're pushing for a permanent fix, not another re-run. Have a realistic date from tier 2 before the call if you can. Ticket #4830 is minor and likely a config difference. Don't let it crowd out the export conversation.

Want me to draft a status update you can read to the customer on #4821, or talking points for pushing tier 2 on a root-cause fix?

From a wall of tickets to a call-ready summary

Ticket Summarizer reads the account's support records in your Knowledge Center and gives you a single, current summary: the open tickets, the recent ones, the issues that keep coming back, and the one or two things you most need to know before you dial. You ask once and start the call informed.

  1. Connect your support records

    Add ticket history, escalation notes, and resolution logs to the Knowledge Center, or connect the helpdesk you already use. Joy reads them at ask time.

  2. Name the account and the reason for the call

    Tell Joy which account you're calling and why (a check-in, an escalation, a renewal) so the summary leads with what's relevant.

  3. Review the summary and the heads-up

    Joy returns the open and recent tickets, the recurring themes, the current status, and a short heads-up on what to watch for on the call.

  4. Use it where you work

    Copy the summary into your call notes or the account record so it's in front of you when you dial. Joy assembles the context; you run the call.

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.

Personalizzala

Open and recent tickets

The current queue and the recent history in one place, so nothing surprises you mid-call.

Recurring issues

The problems that keep coming back, flagged so you can address the pattern, not just the ticket.

Current status

Where each open item actually stands right now: pending fix, awaiting customer, escalated.

What to know walking in

A short heads-up on the one or two things most likely to shape the conversation.

Escalation prep

Focus on the escalated ticket, its timeline, and every touchpoint since it was raised.

Pre-renewal read

Summarize the support experience over the contract term to gauge renewal risk.

Account handoff

Bring a new CSM or agent up to speed on an account's full support history in one summary.

Weekly account review

Get a running summary of what changed on a key account's tickets since last week.

Frequently Asked Questions

How do I get up to speed on an account before a call?

Ask Joy to summarize the account's ticket history. It pulls the open and recent tickets, the recurring issues, and the current status from your support records, plus a short heads-up on what to watch for, so you start the call already knowing the story.

What does the summary include?

The open tickets and their current status, recently resolved ones, any issue that keeps recurring, and a brief note on the one or two things most likely to shape the conversation. Everything is grounded in your connected support records.

Can it spot recurring problems on its own?

Yes. Joy flags issues that show up more than once, like the same error patched three times, so you can address the pattern on the call rather than treating each ticket as a fresh one-off.

Where does the ticket data come from?

From the support records you connect: ticket history, escalation notes, resolution logs, and account notes in your Knowledge Center. Joy reads them at ask time and doesn't pull from anything you haven't connected.

Does Joy update or close the tickets?

No. Joy summarizes the tickets as text in chat. It doesn't open, route, or close anything. You review the summary, copy it into your call notes, and handle the tickets in your helpdesk as usual.

Ricette Correlate

Customer Success

Customer History Timeline

See a customer's full interaction history at a glance.
Customer Success

Solution Finder

Get instant, cited answers from your technical docs.
Customer Success

Auto-Response Suggester

Draft support replies grounded in your knowledge base.

Ready to start every call already caught up?

Iscriviti alla lista d'attesa e sii tra i primi a provare questo workflow quando JoySuite sarà lanciato.

Iscriviti alla Lista d'Attesa Sfoglia Tutte le Ricette