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

# Give Ari Instructions

> Coach Ari once on how your company works, and he applies it in every conversation, for everyone on the team.

export const AriMention = () => <span className="slack-mention">@Ari</span>;

export const SlackMessage = ({children, name = "Bailey", initials = "B", color = "#611f69", avatar = "/images/bailey-avatar.png", app = false, time = "2:47 PM"}) => <div className="slack-msg not-prose">
    <div className="slack-avatar" style={{
  backgroundColor: avatar ? "transparent" : color
}}>
      {avatar ? <img src={avatar} alt={name} /> : initials}
    </div>
    <div className="slack-msg-body">
      <span className="slack-name">{name}</span>
      {app ? <span className="slack-app-badge">APP</span> : null}
      <span className="slack-time">{time}</span>
      <div className="slack-text">{children}</div>
    </div>
    <div className="slack-actions">
      <button type="button" className="slack-action-btn" aria-label="Copy message" title="Copy message" onClick={e => {
  const msg = e.currentTarget.closest(".slack-msg");
  const el = msg && msg.querySelector(".slack-text");
  if (el && navigator.clipboard) {
    navigator.clipboard.writeText(el.innerText);
    const btn = e.currentTarget;
    const prev = btn.innerHTML;
    btn.innerHTML = '<svg viewBox="0 0 24 24" fill="none" stroke="#2AD48A" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"><polyline points="20 6 9 17 4 12"/></svg>';
    setTimeout(() => {
      btn.innerHTML = prev;
    }, 1200);
  }
}}>
        <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round">
          <rect x="9" y="9" width="13" height="13" rx="2" ry="2" />
          <path d="M5 15H4a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2h9a2 2 0 0 1 2 2v1" />
        </svg>
      </button>
    </div>
  </div>;

Ari's [Prompts](/ari/features/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

<SlackMessage><AriMention /> remember: \[instruction]</SlackMessage>

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:

<Steps>
  <Step title="Billing defaults">
    Payment terms, default currency, PO handling. The rules behind every invoice.

    <SlackMessage><AriMention /> remember: our standard payment terms are net-30. For enterprise customers, use net-45.</SlackMessage>
  </Step>

  <Step title="Collections playbook">
    Your escalation ladder, and which accounts are hands-off without a human.

    <SlackMessage><AriMention /> 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.</SlackMessage>

    <SlackMessage><AriMention /> remember: never send collection emails to customers tagged as "strategic" without my approval first.</SlackMessage>
  </Step>

  <Step title="Company vocabulary">
    Internal shorthand, so Ari speaks your language.

    <SlackMessage><AriMention /> remember: "MSA customers" are customers on our Master Service Agreement. They always get net-45 terms and a 10% volume discount.</SlackMessage>
  </Step>

  <Step title="Formatting preferences">
    How you want reports grouped and sorted, so every answer arrives meeting-ready.

    <SlackMessage><AriMention /> remember: when listing overdue invoices, sort by amount descending and include the customer contact name.</SlackMessage>
  </Step>
</Steps>

## Managing your instructions

<SlackMessage><AriMention /> show me all my prompts</SlackMessage>

<SlackMessage><AriMention /> update the payment terms prompt to use net-15 instead of net-30</SlackMessage>

<SlackMessage><AriMention /> forget the rule about Acme Corp PO numbers</SlackMessage>

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.

<Tip>
  Review your active instructions quarterly. Processes drift, and a stale rule from last
  year's collections policy will quietly steer this year's emails.
</Tip>

## 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:

<SlackMessage><AriMention /> remember: for customers with ARR over {"$"}100K, always ask for my approval before sending collection emails.</SlackMessage>

For the full reference, including scoping, stacking, and more example instructions, see
the [Prompts](/ari/features/prompts) feature page.