Spaces

Do and don't guide for your agent at a software or IT firm

This guide gives plain do and don't rules for an AI agent answering clients at a software or IT firm. It covers faults, security, scoping and quotes, and helps owners write clear instructions.

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

Before you start

Clients of a software firm judge an agent quickly. If it stays calm during an outage and asks the right three questions, they relax. If it gives a confident wrong diagnosis or promises a delivery date, they lose trust in you, not just in the agent. Clear do and don't rules protect both sides.

Read each rule and keep the ones that suit your firm. Rewrite any that do not, in your own words, and add an example from a real client chat. Then paste the final list into your agent's instructions, and test it with a few pretend messages.

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

[ ] Do confirm receipt of a fault straight away and say when the client will hear again.
[ ] Do ask for the page, the time and the exact error text on every fault.
[ ] Do treat anything about payments, logins or a whole site as urgent.
[ ] Do say "let me check" when you do not know a release date or status.
[ ] Do ask prospects what the system must do, who will use it and when.
[ ] Don't diagnose the cause of a fault in chat.
[ ] Don't ask for or accept passwords, keys or codes.
[ ] Don't quote a price, a fixed fee or a delivery date.
[ ] Don't change anyone's access or confirm another client's details.
[ ] Don't use technical shorthand with a client who writes in plain words.

Keep the rules short and concrete

An agent follows a short rule with an example better than a long rule with none. Instead of "be careful with security", write "if a client mentions a leak, a strange login or a hacked account, mark it urgent and hand over at once".

Add a real line from a past chat at {business}, with the reply you would have wanted. After a month, look at where the agent still drifts, and sharpen those rules first.

Where owners often go wrong

Be wary of these shortcuts when writing the rules.

  • Copying a generic customer service script with no mention of outages.
  • Leaving severity levels out and hoping the agent will guess.
  • Letting the agent say "we will fix this today" to calm a client.
  • Forgetting to say what the agent does after hours.

FAQ

How many rules should we give the agent?

Ten to fifteen clear rules beat fifty vague ones. Focus on faults, security, quotes and handovers, then add rules only when a real chat shows a gap.

Can the agent explain technical things to clients?

Yes, at the level your documentation supports, in plain words. For judgment calls, such as which approach to choose, it should hand the chat to an engineer.

Should rules be different for prospects and for existing clients?

Often yes. Prospects get questions and a call offer, while existing clients get ticket updates and procedures. Say so clearly, and keep commercial topics with a person for both.

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.