Spaces

Do and don't guide for your agent: hosting and data processing

This guide gives plain do and don't rules for an AI agent that answers hosting and data processing customers. It helps owners set the boundaries before the first chat goes live.

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

Before you start

An AI agent follows the rules you give it. For a hosting or data processing company, the rules matter more than usual, because a careless reply can lock a customer out, leak a detail or promise a restore that cannot happen. Clear boundaries make the agent calm, useful and safe.

Read each rule and keep the ones that fit your company. Change the wording to match how you talk to customers, then share the final list with whoever sets up your agent and with your engineers. Review it after your first month of live chats.

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

[ ] Do ask for the domain, the time and the exact error before anything else.
[ ] Do explain routine steps from your own guides in short plain lines.
[ ] Do point to the status page when a wider problem is possible.
[ ] Do say honestly when you do not know and a person will confirm.
[ ] Don't share any account detail until a person has checked identity.
[ ] Don't promise a fix time that your engineers have not given.
[ ] Don't guess at the cause of a breach or lost data.
[ ] Don't quote prices or discounts that are not on your price list.
[ ] Don't ask customers to paste passwords or keys into the chat.
[ ] Do hand over any invoice dispute, cancellation or legal request.

Why plain rules work

A short list of do and don't statements is easier to check than a long policy. When a chat goes wrong, you can look at the list and see which rule would have stopped it, then sharpen that rule.

Keep each rule to one idea. If a rule needs three exceptions, it is probably two rules.

Add rules from real chats

The best extra rules come from your own customers. Look for patterns like these.

  • A question the agent answered correctly but too coldly.
  • A topic that should have gone to a person sooner.
  • A phrase customers misunderstood, such as propagation or failover.

FAQ

How many rules should my agent have?

Ten to fifteen clear rules are plenty to start. Add more only when a real chat shows a gap, and remove any rule that nobody can explain the reason for.

Can the agent break these rules by mistake?

It can, which is why you should read chats in the first weeks and test with tricky questions. When it slips, tighten the wording and check again with the same question.

Who should write the rules for our company?

The owner or support lead, with an engineer to check the technical points. People who answer customers every day know best where a reply goes wrong.

More free tools for web hosting and data processing companies

Read the guide: Answer hosting and data processing questions without a ticket queue.