> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ledgerup.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Prompts
> Give Ari long-term memory and customize how he behaves with persistent instructions.
export const AriMention = () => @Ari;
export const SlackMessage = ({children, name = "Bailey", initials = "B", color = "#611f69", avatar = "/images/bailey-avatar.png", app = false, time = "2:47 PM"}) =>
{avatar ? : initials}
{name}
{app ? APP : null}
{time}
{children}
;
## What are Ari Prompts?
Prompts are persistent instructions that shape how Ari behaves across every conversation. They act as long-term memory, letting you "program" Ari with your company's billing preferences, terminology, processes, and rules so you don't have to repeat yourself.
Think of prompts as onboarding Ari the same way you'd onboard a new teammate. You tell him once how things work, and he remembers.
***
## Why Use Prompts?
Without prompts, you'd need to remind Ari of your preferences every time you start a new conversation. With prompts, Ari already knows:
* Company specific knowledge
* Your default payment terms
* How you want invoices formatted
* Which customers get special treatment
* Your company's collections escalation process
* Internal terminology and naming conventions
***
## Creating a Prompt
You can create prompts by talking to Ari directly in Slack:
remember: \[instruction]
Give Ari a clear instruction about how you want him to behave going forward.
remember: our standard payment terms are net-30. Always use net-30 unless I specify otherwise.
Ari will echo back what he understood and confirm the prompt has been saved. Review it to make sure it captured your intent correctly.
From now on, Ari will follow this instruction in every relevant conversation. You don't need to mention it again.
***
## Example Prompts
Here are some common ways teams use prompts to customize Ari:
Tell Ari the internal acronyms, and specifics that everyone on the team knows.
Set your standard billing preferences so Ari uses them automatically.
remember: our standard payment terms are net-30. For enterprise customers, use net-45. remember: always include the PO number in the invoice memo when the customer has one on file. remember: our default currency is USD. Only use other currencies if I specify.
Define your escalation process so Ari follows your playbook.
remember: for overdue invoices, send a friendly reminder at 7 days, a firmer reminder at 30 days, and escalate to me directly at 60 days. remember: never send collection emails to customers tagged as "strategic" without my approval first.
Teach Ari your internal language so he understands shorthand.
remember: when I say "platform fee", I mean the {"$"}500/month base subscription line item. remember: "MSA customers" are customers on our Master Service Agreement. They always get net-45 terms and a 10% volume discount.
Control how Ari presents information back to you.
remember: when showing revenue breakdowns, always group by product first, then by customer. remember: when listing overdue invoices, sort by amount descending and include the customer contact name.
Set special handling for specific accounts.
remember: Acme Corp invoices should always CC [jane@acmecorp.com](mailto:jane@acmecorp.com) and include their PO number AC-2024-001. remember: Global Systems is on a quarterly billing cycle. Their invoices go out on the 1st of January, April, July, and October.
***
## Managing Prompts
show me all my prompts update the payment terms prompt to use net-15 instead of net-30 forget the rule about Acme Corp PO numbers do I have any prompts about collections?
***
## How Prompts Are Applied
Prompts work at the team level, meaning everyone in your workspace benefits from them. When anyone on your team talks to Ari, he follows all active prompts.
| Scope | What it means |
| -------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Team-wide** | Prompts apply to all conversations across your workspace. If one person sets a billing default, everyone benefits. |
| **Channel Specific** | Prompts are automatically applied across the company, but you can scope them to a specific channel. |
| **Always active** | Prompts are applied automatically in every relevant conversation. You don't need to reference them. |
| **Stackable** | Multiple prompts can apply at once. Ari combines them intelligently based on context. |
| **Overridable** | You can always override a prompt in a specific conversation by giving Ari a direct instruction. Just be explicit. |
If Ari does something unexpected, check your active prompts. A previously set prompt might be influencing his behavior. You can always ask `@Ari why did you do that?` and he'll explain which prompts he applied.
***
## Best Practices
Vague prompts lead to unpredictable behavior. Instead of "be careful with big customers", try "for customers with ARR over \$100K, always ask for my approval before sending collection emails."
Begin with a few key prompts (payment terms, collections process, formatting) and add more as you discover patterns in how you work with Ari.
As your processes change, your prompts should too. Check in on your active prompts quarterly to make sure they still reflect how your team operates.
If you find yourself telling Ari the same thing more than twice, that's a good sign it should be a prompt.
: initials}