Spaces

Hand-over rules: which hosting and data chats must go to a person

This checklist lists the hosting and data processing chats an AI agent must pass to a person, such as outages, suspected breaches and refunds. It helps owners set clear rules before a customer is let down.

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

Before you start

An AI agent is useful for the routine questions: how to point a domain, where backups live, when a batch will be delivered. In your field a wrong answer can also cost a customer their business for a day, or expose their data. Those moments must reach a named person quickly.

Go through the rules and keep the ones that fit your services. Then give the final list to whoever sets up your agent, and make sure a person on every shift knows they may be pulled in. A rule that nobody owns fails at the worst time, usually at night.

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

[ ] Any site, server or job that is down for a paying customer.
[ ] Any hint of a hacked account, leaked password or odd login.
[ ] Lost, deleted or exposed customer data.
[ ] Requests to delete a server, wipe a backup or close an account.
[ ] Refunds, service credits and billing disputes.
[ ] Contract changes, renewals with new terms and cancellations.
[ ] Letters or requests from lawyers, police or regulators.
[ ] Questions about another customer's account or data.
[ ] A customer who is upset, or a fault that keeps coming back.
[ ] Anything the agent does not know or cannot check.

Make the handover smooth

When a chat moves to a technician, the customer should not repeat the story. A good note names the customer, the service, what they asked and what has been said. Our hand-over notes tool helps you write it.

Tell the customer in one line what happens next, for example: I have passed this to our on-call engineer, and they will write here as soon as they have looked.

Questions to settle with your team

Decide these before you switch the agent on.

  • Who is on call at night and at weekends?
  • Who may approve a service credit, and up to what size?
  • Who handles a legal or police request?
  • How does the agent reach that person quickly?

FAQ

Can the agent handle an outage at all?

It can acknowledge the message and collect the domain, the symptoms and the start time. It must then hand over to a technician and must not diagnose or promise a fix time.

Why hand over a billing question if the answer is in the contract?

Many billing questions are simple, but disputes, credits and refunds involve judgment. Let the agent explain published rules and pass anything that needs a decision to a person.

How do I test that the rules work?

Send practice messages that mimic an outage, a suspected breach and a refund request. Check that each one reaches the right person with a clear note before real customers write.

More free tools for hosting and data processing providers

Read the guide: Answer hosting and data processing customers in the chat they already use.