Spaces

Hand-over rules: when a client chat must go to an engineer

This checklist lists the client messages an AI agent should hand to a person at a software or IT firm, such as outages, security worries and contract changes. It helps owners fix the rules before a bad night.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

An AI agent can do a lot of the routine work for a software firm: confirm a ticket, explain your support hours, say whether a release is live. But a handful of messages carry real risk. A wrong answer about a breach or a deleted database can cost a client far more than a slow reply ever would.

Work down the list and mark the rules that apply to you. Then give the final version to whoever sets up your agent, and name the person on call who will receive each type of handover. A rule with no named owner tends to fail at two in the morning.

Tick each one as you go. 0 of 10 done.

[ ] Any report that a live system is down or a payment flow has failed.
[ ] Any suspicion of a breach, leaked data or unusual logins.
[ ] Any request to add, remove or change who has access to a system.
[ ] Anyone offering or asking for passwords, keys or codes in the chat.
[ ] Data loss, failed backups or a request to restore from backup.
[ ] Quotes, fixed prices, discounts and changes to a contract.
[ ] Disputes about scope, hours billed or service credits.
[ ] Requests that need a technical judgment, such as which design to choose.
[ ] Messages from a person who is not a known contact for the client.
[ ] Anyone who is angry, or asks to speak to a person.

Make the handover useful to the engineer

A handover should arrive with the facts already gathered: the client, the system, the time the problem started, any error text and what the agent has already told them. The engineer should never have to open the chat and ask the client to start again.

Tell the client what happens next in one line: I have passed this to our on-call engineer, who will reply here within twenty minutes. Our hand-over notes tool can help you shape the note.

Questions to settle with your team

Before you switch the agent on, agree answers to these.

  • Who is on call tonight, and who is the backup if they do not answer?
  • Which clients have contracts with a fixed response time?
  • Who may confirm a change of access, and how is the client verified?
  • What should the agent say to a client who wants a credit for downtime?

FAQ

Should every fault go to a person?

No. Routine faults can be logged and answered by the agent from your procedures. Only serious ones, such as outages, security worries and anything it cannot judge, need an engineer straight away.

How does the agent know a client is who they say they are?

It only knows what you tell it. For anything touching access or data, set the rule that a person verifies identity first, using a method you already trust with that client.

What if nobody is on call when a handover happens?

The agent should tell the client honestly that an engineer will respond as soon as possible, give your emergency route if you have one, and flag the chat as urgent for the next person in.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.