Spaces

When your AI agent must hand a user's message to a person at a software company

This checklist names the situations where an AI agent at a software company must stop and pass the chat to a person: money, security, legal requests, outages and angry users. Use it to write your own hand-over rules.

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

Before you start

An agent that knows your product can answer most how-to questions well. The trouble starts when a message looks like a question but is really a decision: a refund, a deletion request, a claim that someone else got into an account. Those need a person who can say yes or no and stand behind it.

Read each rule and decide whether it applies to your company. Add any you need, such as rules for enterprise customers. Then copy the final list into your agent's instructions and tell your team who receives each type of hand-over, so no chat waits in a pile.

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

[ ] Refund and credit requests of any size go to a person.
[ ] Reports that someone else accessed an account go to a person at once.
[ ] Requests to delete or export personal data go to a person.
[ ] Anything mentioning a lawyer, a regulator or a contract dispute goes to a person.
[ ] Users saying the product is down or data is missing go to the on-call person.
[ ] Cancellation requests from paying customers go to a person.
[ ] Questions about custom pricing, discounts or enterprise terms go to sales.
[ ] Messages from press, investors or partners go to the founder.
[ ] Users who are clearly upset or who write again after a reply go to a person.
[ ] Requests for a feature, a bug fix or a date go to product, with a note.

Make hand-overs painless

A rule is only useful if someone picks the chat up. Name an owner for each line, even if the same person owns three of them. Tell the user plainly what happens: 'I am passing this to Priya on our team, and she will reply today.'

Review the hand-over list every few months. As your team grows, some rules can loosen, such as letting the agent explain how a standard refund policy works, while the decision still goes to a person.

  • Write the owner and the expected reply time next to each rule.
  • Have the agent leave a short note with the user's plan and the problem.
  • Never let the agent tell a user a bug will be fixed by a date.

FAQ

Can the agent answer refund questions at all?

It can explain your refund policy in plain words and tell the user what happens next. The decision to refund, and the amount, should always come from a person on your team.

What should the agent say when it hands over?

It should say that a named person on your team will take over, what they will look at, and roughly when the user will hear back. It should not pretend to still be handling it.

Do we need hand-over rules if we are a tiny team?

Yes, and a tiny team needs them most. With a few people, one wrong promise from an agent can cost real money, so write the short list down and keep it handy.

More free tools for software companies

Read the guide: Answer your users' messages with an AI agent.