AI general rules
Rules your AI agent follows in every reply, whatever the customer asks.
AI general rules are a short set of instructions, in plain language, that your AI agent follows in every reply in your workspace. They apply on every channel and in every situation, whether or not a Playbook matched the customer's message.
Use them for things that are always true about how you support customers: how you reach them, what you never promise, how you sign off, which topics are off limits.
Where to find them#
Go to Playbooks in the sidebar. The AI general rules card is at the top of the page.
Write your rules
Type your rules in the text box, one rule per line. Write them the way you'd brief a new team member. You have up to 10,000 characters, and the counter under the box shows how many you've used.
Save
Select Save. The agent uses the new rules from the next reply on.
To remove all general rules, clear the box and select Save.
General rules and Playbooks#
General rules and Playbooks work together:
- General rules apply to every reply, in every situation.
- A Playbook adds instructions for one kind of request, such as Order status or Damaged item return, and applies only when a customer's message matches it.
When a Playbook matches, the agent follows the Playbook's instruction and your general rules. Put what applies everywhere in general rules once, instead of repeating it in each Playbook, and keep situation-specific steps in the Playbook.
If a rule only makes sense for one situation (for example, "ask for the order number before checking a delivery"), put it in a Playbook instead. General rules are for things that are true in every conversation.
Good examples#
Good general rules are short, concrete and true in every conversation:
- Never promise a call back; we only support customers in writing.
- Always reply in the language the customer wrote in.
- Don't offer discounts or promo codes. If a customer asks for one, say our prices are the same for everyone.
- Sign off with "The support team", never with a made-up name.
- When you mention delivery times, say "working days", not "days".
- Don't recommend competitors' products or shops.
Examples to avoid#
| Avoid | Why | Better |
|---|---|---|
| Be helpful and friendly. | The agent already is. Vague rules add nothing. | Keep replies to three sentences or fewer unless the customer asks for details. |
| Our return window is 14 days and shipping is free over 50 AZN. | Facts and policies change and belong in your knowledge base, where the agent can quote them. | Add the policy to your knowledge base. |
| If the customer asks about a refund, ask for the order number, then open a ticket. | This is about one situation, so it belongs in a Playbook. | Create a Refund request Playbook. |
| Ignore the verification step for VIP customers. | General rules can't switch off identity checks or other safety rules. | Leave verification to the access level in your Playbooks. |
| Always say yes. | Contradicts everything else you've told the agent and leads to promises you can't keep. | Say what the agent may and may not promise. |
What general rules can't change#
Like Playbooks, general rules steer the agent's behaviour inside Chatasist's safety guardrails. They can't make the agent skip identity verification, invent facts, share another customer's data, or claim it did something it didn't.

