Skip to main content

​
Overview

Different team members need different things from Annie. An SRE wants terse, action-oriented answers. A CSM needs business-impact summaries. A junior engineer benefits from step-by-step explanations. Annie Personas let you control how Annie communicates by assigning behavioral profiles to team members. Each persona adjusts Annie’s tone, depth, and assumptions without changing what it can do.

​
Built-in Personas

Annie ships with four personas ready to use:
Conversational and direct. Assumes the user is a fellow SRE with deep technical knowledge. Provides brief answers, skips basic definitions, and suggests concrete next actions.Best for: SREs, DevOps engineers, platform engineers
Focused exclusively on finding and presenting evidence. Cites every claim with specific data sources. Uses bullet points and structured data instead of prose. Does not speculate beyond what the evidence shows.Best for: Incident investigations, compliance reviews, audit trails
Patient and thorough. Assumes the user is learning the system. Explains concepts step by step, defines technical terms, and provides context about why things work the way they do.Best for: Junior engineers, new team members, onboarding
Non-technical and business-focused. Translates technical details into business language. Focuses on who is affected, what the customer-facing symptoms are, and what the resolution status is.Best for: Customer Success Managers, account managers, sales engineers

​
Custom Personas

Need something more specific? Create custom personas tailored to your team’s unique roles and workflows. Navigate to Annie → Personas in the sidebar to create custom personas with:
  • Label — A short name (up to 50 characters), e.g. “Lean SRE” or “Sales Engineer”
  • Instruction — Behavioral instructions for Annie (up to 1000 characters) describing the tone, depth, and assumptions to use
Custom personas appear alongside built-in ones in all persona selection dropdowns.

​
Example Custom Personas

Focus on speed and actionability. Skip all context and explanation.
Give me the shortest possible answer: what's broken, what metric
confirms it, and what's the fix. One sentence per point. If you
need to run a tool, just do it — don't ask permission.

Assist with pre-sales technical discussions. Frame infrastructure
capabilities as business outcomes (uptime, cost savings, compliance).
When reviewing incidents, emphasize MTTR and preventive measures.
Keep language accessible to technical buyers — avoid deep CLI
commands or config details unless asked.

​
Assigning Personas

Personas are assigned per project in Settings → Projects & Teams:
  • Default persona — Applied when a team member has no individual assignment, or when the user can’t be identified (e.g., unlinked Slack users). Set this above the team members table.
  • Per-member persona — Override the default for specific team members using the Persona column in the members table.
Members can change their own persona. Admins can change anyone’s persona.

​
Slack Users

Annie identifies Slack users through the Slack user mapping. When a Slack user is linked to their Anyshift account, their assigned persona is applied automatically. Unlinked Slack users receive the project’s default persona.

​
Get Started

Create Account

Sign up for Anyshift

Request Demo

See Annie Personas in action