Rules are standing instructions the Enterpret Agent follows on every turn. Define your company's terminology, formulas, defaults, and formatting preferences once, and the agent applies them automatically across every session, so you stop re-explaining the same context. This article covers the two scopes Rules come in, the shared character budget each scope draws from, how to write rules that work, and how Rules differ from Skills.
Workspace and personal rules
Rules come in two scopes.
Workspace rules are company-wide definitions, managed by admins, that apply to everyone in the workspace. They encode the standards every teammate should inherit: how a metric is calculated, what an internal term means, which team owns which issue category.
Personal rules are yours alone. They apply only to your own sessions and never affect teammates. Use them to add context about how you work that the rest of the company does not need.
The two scopes combine by layering, not overriding. Workspace rules apply first and establish the shared baseline. Your personal rules add context on top of that baseline. You can tune the agent for your role, but you cannot opt out of the workspace rules everyone shares: personal rules extend the company-wide standards, they do not replace them.
Without rules, the same ambiguity surfaces in every query. At one company, "missing deliveries" could mean carrier failures (the box never arrived) or fulfillment issues (items missing from the box). Everyone who asked about "missing deliveries" had to specify which one. An workspace rule encodes that distinction once, and the agent honors it from then on.
Rules are always on. Every turn picks them up automatically. There is nothing to invoke and nothing to remember.
The rules character budget
Each scope has a shared character budget. Every rule in a scope draws from the same pool, so the limit is per scope, not per rule.
Scope | Budget | Who it affects |
Workspace rules | 6,000 characters total across all workspace rules | All users in the workspace |
Personal rules | 3,000 characters total across all personal rules | Only you |
The two budgets are independent. Personal rules never draw from the workspace pool, and workspace rules never draw from your personal pool. Within a scope, the rules share one allowance: if three workspace rules total 4,500 characters, every remaining workspace rule has to fit in the 1,500 characters left.
The character counter in settings reads as the total used for that scope, not as a per-rule count. Adding, editing, or deleting one rule changes the budget remaining for the others in the same scope.
If you reach the limit and cannot save a rule, reduce the total content in that scope: shorten existing rules, delete stale ones, or move a personal preference out of the workspace scope and into your personal rules when it does not need to apply to everyone. Splitting one long rule into several smaller rules makes them easier to maintain, but it does not buy more room. The combined length still counts toward the same shared budget.
Writing effective rules
The agent follows clear, direct instructions better than long explanations. A rule does not need to justify itself. State what should happen, keep each rule to one behavior, and define any term your workspace gives a specific meaning. After you save a rule, run a few queries it should affect and confirm the agent responds the way you expect. As a scope fills up, consolidate: two concise rules usually beat one verbose one, and stale rules still consume the budget.
Example rules
The rules below are examples, not settings the Enterpret Agent ships with. Copy any one, swap in your own terms and sources, and save it under the Workspace or Personal scope.
To standardize… | Example rule you can adapt |
A term | "Churn" means paid subscription cancellations only; "attrition" means free-tier users who stop engaging. Do not conflate them. |
A calculation | When calculating NPS, use (Promoters − Detractors) / Total Responses × 100, and show the formula in the response. |
A default | When no date range is given, analyze the last 30 days, not 90. |
Source mapping | "Support tickets" = the zendesk_main source; "app reviews" = app_store_connect + google_play. |
Team routing | Route login and authentication issues to the Identity team, and name the owning team when reporting an issue. |
An exclusion | Exclude internal users and free-tier accounts unless I explicitly ask for them. |
Output format | Always show the raw feedback count next to any percentage, and state the time period and sources in the first sentence. |
Business context | When ARR or contract value is available on accounts, surface high-value customers first. |
When one rule starts mixing several instructions, split it. A single rule that names primary sources, requires a time period in the first sentence, sets internal product names, and fixes the output format is four rules wearing one coat. Splitting them makes each independently editable. The combined length still counts toward the same scope budget.
Rules vs Skills
A Rule and a Skill both shape how the Enterpret Agent behaves, and the two are easy to confuse.
A Rule is an always-on instruction the agent applies on every turn — "always exclude internal users," "our fiscal year starts in February." You never invoke it; it is simply in effect.
A Skill is a named workflow you invoke for a specific job, such as a voice-of-customer readout or a competitive analysis. A Skill packages a method the agent runs the same way each time you call it. Rules shape behavior everywhere; a Skill runs a named analysis when you ask for it. See Skills for how to invoke and create them.
Managing your rules
Open Settings → Rules.
Select the Workspace or Personal tab for the scope you want.
Click Add Rule, enter a descriptive Name (for example, "NPS Calculation Formula"), write the rule Content, and click Save.
The rule takes effect on every new query, with no need to invoke it.
Who can edit which scope:
Workspace rules can be created and edited only by workspace admins, since they apply to everyone.
Personal rules can be created and edited by every user, for their own sessions only.
Have a question about Rules, or a use case you would like to see covered? Contact support and the team will help.