Skip to main content
Ari’s Prompts are standing instructions: persistent rules that shape how he behaves in every conversation. Think of them as onboarding a new teammate. You explain how things work here once, and he remembers. The rule of thumb: if you’ve told Ari the same thing twice, make it an instruction.

​
How it works

Ari echoes back what he understood and confirms it’s saved. From then on it applies automatically. Instructions are team-wide by default (one person’s coaching improves everyone’s results), can be scoped to a channel, stack with each other, and can always be overridden in the moment with a direct request.

​
The starter coaching plan

Each of these takes about a minute to set, and Ari’s output matches your company from the first conversation:
1

Billing defaults

Payment terms, default currency, PO handling. The rules behind every invoice.
2

Collections playbook

Your escalation ladder, and which accounts are hands-off without a human.
3

Company vocabulary

Internal shorthand, so Ari speaks your language.
4

Formatting preferences

How you want reports grouped and sorted, so every answer arrives meeting-ready.

​
Managing your instructions

If Ari does something unexpected, an instruction is often why. Ask @Ari why did you do that? and he’ll explain which prompts he applied.
Review your active instructions quarterly. Processes drift, and a stale rule from last year’s collections policy will quietly steer this year’s emails.

​
Instructions can also raise the guardrails

Standing rules aren’t just preferences; they’re policy. Use them to require extra approval where it matters most: For the full reference, including scoping, stacking, and more example instructions, see the Prompts feature page.