Spaces

Do and don't rules for your software support agent

This guide gives plain do and don't rules for an AI agent answering software customers. It covers troubleshooting, licences, security reports and money, so publishers can brief it quickly.

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

Before you start

Software customers can be impatient, technical or both. They also notice quickly when an answer is vague, wrong or a copy of the help page they already read. A short set of rules sets the tone for how your agent speaks and where it stops.

Read each rule and decide whether it fits your product. Edit the wording to match your voice, then give the final list to whoever sets up your agent. Reread the rules after your first month, when you have seen how real customers write.

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

[ ] Do ask for the version and operating system before suggesting a fix.
[ ] Do give fixes as short numbered steps.
[ ] Do check the known-issue list before anything else.
[ ] Do say plainly when you do not know and a person will check.
[ ] Do hand over after two fixes have failed.
[ ] Don't ask for passwords or full licence keys in the chat.
[ ] Don't discuss whether a reported security flaw is real.
[ ] Don't promise refunds, credits or release dates.
[ ] Don't blame the user or call a problem user error.
[ ] Don't claim a feature exists unless the docs say it does.

Turning rules into instructions

Write each rule as a short sentence the agent can follow, with an example when it helps. For instance: if the customer says the app will not open, ask for the version, the system and any error text before suggesting anything.

Test each rule yourself. Send a message that tempts the agent to break it, such as asking for a refund, and see what it does. Fix the wording until the answer sounds like your best support person.

Adding your own rules

Every product has its own risks, so add rules that fit yours.

  • Games: say how to handle age questions and in-app purchase problems.
  • Business tools: say how to treat questions from a company's admin and from an ordinary user.
  • Creative tools: say how to deal with lost project files.
  • Subscription products: say who handles cancellations.

FAQ

How many rules should I give the agent?

Ten to twenty clear rules are plenty. Too many rules start to conflict, and the agent follows a short, specific list more reliably than a long, vague one.

Can the agent use technical language with customers?

Match the customer. A developer asking about an error code can get a technical reply, while a casual user needs plain steps. Tell the agent to follow the customer's lead.

How do I know the rules are working?

Read a sample of chats each week. If the agent breaks a rule, find the instruction that was unclear, reword it and test again with the same tempting message.

More free tools for software publishers and app makers

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