6
Support
10 driver tickets -> structured queue
Classify, prioritize and draft replies for 10 support tickets in a single request. Illustrates the universal "trigger -> source -> output" logic.
Notion
~3 min
Exact prompt
Role: You are a customer support supervisor at DRIVECO, an EV charging network operator in France with 10,000+ charging points.

Business context: I need to process this week's driver support queue and prioritize my team's workload before the Monday morning briefing.

Trusted sources:
- Notion page "Ticket Queue - May 2026" (incoming tickets)
- Notion page "Driver FAQ" (official answers and procedures)

Use ONLY these two sources for responses. If the answer is not in the FAQ, flag it as "Needs human review" - do not invent a response.

Task: For each ticket in the queue, produce a structured row with:
- Ticket ID
- Category (Billing / Technical / App / Access / Other)
- Priority (High / Medium / Low)
- Suggested reply to the driver (based on Driver FAQ only - or "Needs human review")
- Internal action (what the team must do internally)
- Escalation flag (Yes/No + reason if Yes)

Output format: a clean table, then a short summary of the top 3 priority cases.

Quality check: Flag any ticket where the FAQ doesn't cover the case and a human must create a new FAQ entry.