Skip to main content
Custom instructions allow you to customize the base Ari agent, so that it is more contextually aware of how to operate in your Plain workspace, and how to provide support to your customers.

Getting started

  1. Read this documentation about the proper use and limitations of this feature
  2. Go to Ari → Preferences
  3. Write your instructions in the Custom Instructions field, and save
  4. Ari applies the instructions from the next customer message it handles, on both new and existing threads
A good way to build confidence is to write and configure your instructions while Ari is in Shadow Mode. Allowing you to see how they change Ari’s behavior before sending customer replies.

How Ari uses them

Ari applies the instructions are specific steps when it is operating:
  1. Classifying what action to take next on a thread
  2. Searching your knowledge sources
  3. Writing a reply and handoff message
The instructions are one block of text, but Ari applies only the parts relevant to what it is doing at each step. Mixing tone, routing, and terminology guidance in one place is fine. Instructions never override Ari’s built in guardrails. Ari only states product facts your knowledge sources support, so instructions shape how it behaves, not what it knows.

Writing good instructions

  • Phrase preferences, not bans.
    • “Prefer app instructions where the documentation covers them” works well. “Never show API examples” can leave Ari unable to give any documented answer, so it hands off instead.
  • Facts belong in knowledge sources.
    • Ari will not state product claims that only appear in instructions. Use instructions for behavior, knowledge sources for truth.
  • Keep exact wording short.
    • Sign-offs, introductions, and handoff promises are followed most reliably when they are a sentence, not a paragraph.

Examples

Company context

Tell Ari who it works for, so that it is contextually aware of your business, mission, customers, and products.

Custom introduction

Instruct Ari to introduce itself in a specific way when first talking to a customer.

Custom handoff

Instruct Ari to include specific wording when handing off to a user, to ensure expectations are set correctly.

Escalation preferences

Customize which types of threads are routing away from Ari, even if Ari could answer from your knowledge sources.

Clarifying questions

Ari asks for the specifics, waits, and picks the conversation back up when the customer answers. The second sentence matters: it tells Ari the question is the reply, not a reason to stop working.

Terminology mapping

Bridge the words your customers use and the words your documentation uses, so searches land even when they do not match.

Debugging before handoff

Have Ari collect what your team needs inside the handoff message, so the answer is waiting on the thread when they pick it up.

Documentation preferences

Bias which documented approach Ari leads with when your knowledge sources cover several.
Instruct Ari to include a footer when sending a reply.

Tone

Customize the tone and feel of Ari, this can also be done via Tone of Voice preferences.

Deflect actions to MCP

Ari currently is unable to carry out actions, so instead of Ari handing off in a generic manner, you can instruct Ari to push your customers to use your MCP server instead.

Limitations

There are known limitations to how Ari can use custom instructions. Keep these in mind, and contact the Plain team if you need help.
  1. Override Ari’s guardrails
  2. Add links to replies, as Ari can only link to public knowledge sources
  3. Hold a conversation open waiting for information before handing off; Ari asks in the handoff message instead
  4. Guarantee which knowledge sources Ari searches; instructions steer wording, while knowledge source settings control access