How do I use Chili Assist to build Rules, Teams, and Distributions?

Chili Assist is an AI assistant embedded in the Chili Piper admin UI. Instead of manually configuring conditions, members, or calibrations, describe what you want in plain language and the assistant builds it for you. You review the change on the page and save it with the standard Publish button.

One assistant, three asset types – all used across every Chili Piper product:

• Rules – routing rules, including ownership rules and cross-object references;
• Teams – groups of users referenced by distributions and ownership rules;
• Distributions – distribution configuration, weights, and Credit/Skip calibration.

Table of Contents

• How Chili Assist works
• Rules
• Teams
• Distributions
• Moving between assets
• Publishing or discarding changes
• Need help?
• Limitations

How Chili Assist Works

The same pattern applies to all three asset types:

1. Open the Rules, Teams, or Distributions page – the Chili Assist icon is available on both the index page (table of all Rules, Teams, and Distributions) and on each individual detail page;
2. Click the Chili Assist icon in the top right of the page to open the panel;
3. Describe what you want in plain language – for example, "Match inbound leads from the US where the company has more than 500 employees" or "Add Alex Kim to this team";
4. Answer any clarifying questions – the assistant asks before acting when a request is ambiguous ("Is this for net-new records coming through forms or chat, or for existing leads in Salesforce?"), and confirms before making a change ("Ready to create this rule?");
5. Publish or discard the change using the controls in the page header (see Publishing or discarding changes below).

The screenshot below shows the icon on a Rule detail page – it sits in the same place on the Rules index, Teams index and detail, and Distributions index and detail.

Rules

Use Chili Assist on the Rule detail page to create, edit, or explain a rule.

Create – describe the routing logic and the assistant generates the conditions:

• "Route leads where the company industry is Healthcare and the number of employees is greater than 500";
• "Match when the lead source is Web";
• "Only assign when the lead owner is on the Enterprise AE team" (ownership rule).

The assistant supports all condition types – field comparisons, object-exists checks, cross-object references (Account, Lead's matched account, Contact's parent account), and ownership conditions.

Edit – open an existing rule and ask for changes: "Add a condition to exclude disqualified leads" or "Change the operator on the industry condition to 'is not'." The assistant modifies the rule in place.

Explain – ask "What does this rule do?" and the assistant breaks the rule down in plain English, including nested OR groups and cross-object paths.

Teams

Use Chili Assist on the Team detail page to create or edit a team. Teams are used by distributions (to pick the next rep via round-robin) and by ownership rules to determine whether a record's owner is a member.

Create – describe the team and the members: "Create an Enterprise AE team with Jen Park, Kevin Lee, and Nicolas Gomez." The assistant matches each name against users in your tenant and adds them.

Edit – "Add Alex Kim and remove Kevin Lee"; "Rename this team to Commercial AE."

Names are matched fuzzily – "Jen" resolves to Jen Park if there is a single best match. If more than one user matches, the assistant asks which one you mean.

Distributions

Use Chili Assist on the Distribution detail page to tune weights and calibrations, or to ask why a distribution is behaving the way it is.

Update weights:

• "Set Jen to 50, Kevin to 100, Nicolas to 100";
• "Give Kevin twice the volume of Nicolas."

Only relative weights matter. Scaling everyone up or down by the same factor does nothing.

Apply Credit/Skip:

• "Credit Alex by 2 meetings" – pulls Alex forward in the order (subtracts from their Current Level);
• "Skip Jen by 1" – pushes Jen back in the order (adds to their Current Level).

Explain assignment order – this is where Chili Assist is at its most useful. The assistant reads live, per-rep state at the moment you ask – Current Level, weight, Credit/Skip, vacation calibration, reassignments in and out, meeting counts. So the answer matches what the distribution will actually do on the next assignment, not a stale picture of the setup. Ask, for example:

• "Why is Jen Park next and not Kevin Lee?"
• "Why is Jen's Current Level higher than Kevin's?"
• "What is driving Alex's position in the queue?"

Moving between assets

Chili Assist is scoped to the asset on the page you have open. If you ask the assistant on a Rule page to modify a Team, or the assistant on a Distribution page to edit a Rule, it can take you to the relevant asset page for you.

Note: Conversations do not carry across assets. When Chili Assist takes you to another asset page – or when you navigate there yourself – the Chili Assist panel on that page starts a fresh conversation. The session you were in ends, and prior context is not transferred.

Publishing or discarding changes

Chili Assist applies proposed changes to the asset on the page as an unpublished draft – the draft is saved, but it is not yet live in your configuration. Nothing affects routing, assignment, or ownership checks until you publish.

You have two options once the assistant has made a change:

• Publish – click the Publish button in the page header to push the draft live;
• Discard – click the ... menu next to Publish and select Clear unpublished changes to roll back every unpublished change on that asset.

Need help?

If a Chili Assist response looks wrong or the assistant is not behaving the way you expect, reach out to your Customer Success Manager or Customer Love (support@chilipiper.com). To help the team investigate, include:

• A copy of the prompt you used;
• A description of what you expected to happen;
• The asset ID from the page URL – the rule, team, or distribution ID (the string at the end of the URL) so the team can look up the same asset you were working on.

Limitations

• Model quality is not 100%. Cross-object references, exact field name matching, and picklist value casing are areas where the assistant can still produce incorrect output. Always review the result on the page before you click Publish;
• Conversation is session-scoped. Each page load starts a fresh conversation. Navigating away or refreshing the browser clears the history;
• No cross-asset memory. The assistant on a Rule page cannot see or modify Teams or Distributions, and vice versa. Open the relevant asset page to work on it;
• No undo after publish. Once a rule, team, or distribution is published, there is no AI-powered rollback. Standard manual editing applies;
• Tenant-specific fields. The assistant reads your tenant's CRM fields, picklist values, and team structure at the moment of each request. Response quality depends on the field list being complete and current.

Related articles

• Creating Rules – manual rule-building reference;
• Managing Teams – manual team configuration;
• Setting up your Distributions – manual distribution configuration.