Customer Service / Customer Support Live
Post-Service Survey Dispatch
Decide which closed tickets should be surveyed and which would make things worse, then draft the invite for each one. Every draft is approved individually — nothing is sent.
- Runs on a schedule
- ~8 credits per run
- v1.0.0
What does Post-Service Survey Dispatch do?
Post-Service Survey Dispatch is a production AI agent in the customer service section of the Leverge agent store, built for the customer support process. Decide which closed tickets should be surveyed and which would make things worse, then draft the invite for each one. Every draft is approved individually — nothing is sent. It runs on a schedule (every friday at 11:00), works through 4 steps and returns 4 outputs, including this dispatch.
What it needs
-
Closed tickets
The tickets closed this period, with how they were resolved and a contact address.
-
Dispatch rules
What it does
- Reading the closed tickets
- Deciding who should be surveyed
- Drafting invite {{loop.index}} of {{loop.total}}
- Summarizing the dispatch
What you get back
- This dispatch
- Dispatch summary
- Drafted invites — approve each individually
- Deliberately not surveyed
After each run it asks: “Right people to ask?”
When it runs
Runs on a schedule — Every Friday at 11:00.
Oversight
Runs under scoped, least-privilege credentials with every action written to an audit log. Anything that moves money, alters a contract or reaches a customer requires human approval before it executes.
Customer Support
Other agents in customer support
Ticket triage, resolution drafting and feedback analysis
-
Account Change Request
Check whether the person asking for an account change is entitled to make it, then draft either the confirmation or the verification request. Nothing is changed and nothing is sent.
-
Chat Transcript Summary
Turn a live-chat log into the two things needed afterwards: a ticket record the next agent can act on, and a clean transcript the customer can be sent.
-
Complaint Tracking
Track every open complaint against the commitments made to that customer — which are past the promised date, which have gone quiet, and which were closed without the customer ever agreeing they were.
-
FAQ Gap Monitor
Check the published FAQ against what agents are actually replying, and find the entries that have quietly gone out of date as well as the questions that were never added.
-
Inquiry Self-Service Deflection
Work out how much of last month's inbound could already have been answered by the help centre, which articles were missing, and which questions should never be deflected at all.
-
Knowledge Article Drafting
Draft a publishable article from a resolved case, checked against the existing knowledge base first so it extends what is there instead of quietly contradicting it.
Next Step
Deploy Post-Service Survey Dispatch, or adapt it
It runs as-is against the inputs above. Most deployments diverge — a different source system, a different tolerance, a different approval path. A 30-minute technical call establishes which.