Skip to content
⌘K
InboxAsk a human

Rules

Updated by Vaishnavi

Rules are saved guidance for Enterpret Agent, such as terminology, formulas, defaults, and formatting preferences. Agent gets the relevant Rules with each request. Check the answer to see how it used them. Rules have two scopes: workspace and personal. Each scope has its own shared character budget.


Workspace and personal rules

Workspace rules provide shared definitions and guidance for users in the workspace. Owners, Admins, and Editors can manage them. Use them to define how your team calculates a metric, uses an internal term, or assigns an issue.

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.

Workspace and personal Rules are supplied together. Use workspace Rules for shared guidance and personal Rules for your own context. Avoid conflicting instructions and check important results; Rules are not enforced query filters or access controls.

Your team might use “missing delivery” for two different problems: the package never arrived, or the package arrived with items missing. Write down how your team distinguishes those cases in a workspace Rule, then check how Agent uses that definition.

You do not need to invoke each saved Rule by name. Applicable Rules are supplied as guidance when the Agent processes a request.


The rules character budget

Rules in the same scope share one character limit.

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 counter in Settings shows the total characters used by all Rules in that 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 a rule can make it easier to edit. The combined text still counts toward the same limit.


Writing effective rules

Give each Rule one instruction. If you use a term that has a specific meaning at your company, define it in the Rule. After you save a rule, run a few queries it should affect and confirm the agent responds the way you expect. As you approach the character limit, shorten existing rules or delete ones you no longer use.

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 ownership

When reporting a login or authentication issue, list Identity as the owning team.

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. Keep instructions for sources, dates, terminology, and output format in separate Rules so you can edit each one on its own. The combined length still counts toward the same scope budget.


Rules vs Skills

A Rule gives the Agent standing instructions, such as "always exclude internal users," "our fiscal year starts in February." You do not need to invoke it by name; check the result for compliance.

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 reusable method; its result depends on the request, data, tools, permissions, and model. Rules provide standing guidance, while a Skill provides a workflow for a particular job. See Skills for how to invoke and create them.


Managing your rules

  1. Open Settings → Rules.

  2. Select the Workspace or Personal tab for the scope you want.

  3. Click Add Rule, enter a descriptive Name (for example, "NPS Calculation Formula"), write the rule Content, and click Save.

The saved Rule is supplied as guidance for subsequent requests in its scope, with no need to invoke it by name. Test it with a relevant request.

Who can edit which scope:

  • Workspace rules can be created and edited by Owners, Admins, and Editors.

  • 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.

Rules and recurring reporting

Use Rules for Enterpret Agent guidance such as report tone, terminology, or preferred structure. Use scheduled Agent automations to configure actual daily reports, weekly digests, schedules, and delivery destinations. Verify the automation's own scope and instructions; a Rule alone does not activate recurring delivery or authorize connectors.