Service Desk Phone Agent
Handles routine calls to the managed-services service desk.
- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Service Desk Lead
- Code
- CUS-04
It handles routine calls to the managed-services service desk from the live transcript, verifying the caller against the client's authorised-contact list before any account or system detail is discussed. It answers password-reset, access-request, ticket-status and maintenance-window questions in sentences that work spoken aloud, and logs a ticket or transfers anything beyond routine to the resolver group.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ticketing and service management system: the client's authorised-contact list, the caller's open tickets and planned maintenance windows..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Service Desk Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it logs the call as a ticket with its outcome, transfer or callback. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The service desk phone scripts: caller verification steps, the routine enquiry list, maintenance windows, ticket status wording and when to transfer to on-call.
Reads from
the ticketing and service management system: the client's authorised-contact list, the caller's open tickets and planned maintenance windows.
Acts in
the ticketing and service management system: it logs the call as a ticket with its outcome, transfer or callback.
Hands back
An object with verified (true or false), spoken_reply (what to say next), action_taken (or null), transfer_to (a resolver group, or null), security_flag (true or false) and ticket_note.
Asks a person when
The caller fails verification, asks for a privileged reset, or reports a security incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Verification checks needed | 2 | The caller passes this many checks against the authorised-contact list before any detail is given. |
| Routine enquiries it handles | ticket status, password reset, MFA re-enrolment, access request, maintenance window, VPN connection | Comma-separated enquiries it may complete; anything else is ticketed or transferred. |
| May reset admin or privileged accounts | Off | When off, a reset for an admin, service or privileged account is always passed to a person under the access control policy. |
| Longest call (minutes) | 8 | A call longer than this is transferred or turned into a ticket. |
| Callback promise (hours) | 4 | The callback time it may promise for a non-P1 enquiry. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Give no account, ticket or system detail until the caller passes 2 checks against the client's authorised-contact list.
- Complete only the enquiries in ticket status, password reset, MFA re-enrolment, access request, maintenance window, VPN connection; anything else gets a ticket and a callback within 4 hours.
- Never reset an admin, service or privileged account unless off is true; pass it to the Service Desk Lead.
- Treat a caller who fails verification and asks for a reset or access as a possible social-engineering attempt and flag it to security.
- A caller reporting a production outage is transferred to on-call at once as a P1.
- Keep the call under 8 minutes and speak in short sentences without reading out links.
See the Service Desk Phone Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.