Spaces

Hand-over rules: software chats that must go to a person

This checklist lists the software chats an AI agent should hand to a person, such as security reports, lost data and billing disputes. It helps publishers set clear rules before a hard case arrives.

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

Before you start

An agent can do a lot for a software company: walk through an install, explain editions, confirm which licence an email holds. But some messages carry real risk. A report of a security hole or a customer who has lost a year of work needs a named person and a written record, not a clever reply.

Go through the rules below and mark the ones that apply to your products. Then give the final list to whoever sets up your agent, and make sure a real person on your team owns each category. A rule with no owner will fail on the day it matters.

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

[ ] Any report of a security flaw or a way to see other people's files.
[ ] Suspected account takeover or someone else using a licence.
[ ] Lost, corrupted or deleted customer data.
[ ] Requests to see, export or delete personal data.
[ ] Refunds, double charges and disputed invoices.
[ ] Company contracts, volume pricing and custom terms.
[ ] Anyone who says a crash caused a wider business loss.
[ ] A customer who has failed two documented fixes.
[ ] Press, researchers or lawyers writing to the company.
[ ] Anything where the customer asks for a human.

What the agent does before it hands over

A good hand-over is not silence. The agent tells the customer it is passing the chat to a named person, says roughly when to expect a reply, and collects the facts: product, version, what happened and when. The staff member then starts with a full picture.

For a security report, the agent should only acknowledge receipt and gather details. It should not discuss whether the flaw is real, how serious it is or when a fix will ship.

Choosing who takes each category

Write a name beside every rule. One person can hold several, but nobody should be left guessing.

  • Security and privacy: a senior engineer or the person who owns compliance questions.
  • Money: whoever manages payments and refunds.
  • Contracts: your sales lead or founder.
  • Everything else: the support engineer on duty.

FAQ

What if the agent is unsure whether a message is a security report?

Tell it to treat any hint of a flaw, leak or unauthorised access as a hand-over. A false alarm costs a minute, while a missed report can cost your customers' trust.

Should the agent tell the customer why it is handing over?

Yes, in plain words. Say a colleague who handles this kind of case will take over, so the customer understands it is care and not a brush-off.

Do small software teams need all these rules?

Yes, though one person may cover everything. The rules matter because they decide what the agent says and does not say, even when the whole team is three people.

More free tools for software publishers and app makers

Read the guide: Answer software customer messages before they become tickets.