Skip to main content

Contexts: Custom AI Personas for Specialized Tasks

Contexts are reusable instruction sets that transform Revo into specialized experts. Create custom AI personas for different tasks to ensure consistent tone, style, and knowledge without repeating instructions.

Updated over a month ago

Overview

Contexts are customizable AI personas that guide how Revo behaves and communicates during your interactions. Instead of giving the same instructions every time, you create a Context once and switch between specialists instantly in Chat.

Think of Contexts as hiring different experts for different jobs:

  • "Technical Writer" for documentation with precise, formal language

  • "Sales Analyst" for deal strategy with persuasive, business-focused tone

  • "Customer Support" for empathetic, solution-oriented responses

  • "Onboarding Helper" for new team member guidance with step-by-step clarity

Why Contexts matter: Without Contexts, you'd need to re-explain your requirements in every conversation. With Contexts, Revo remembers your preferences and applies them automatically, ensuring consistent, high-quality outputs across your entire team.


How to Create a Custom Context

You can create a Context for any recurring task to save time and standardize quality.

Step-by-Step Setup

  1. Open the Context Menu
    In any Chat, click the Context dropdown on the right side of the interface.

  2. Access Context Library
    Click the "+ More" button to see all available Contexts.

  3. Create New Context
    Click "New Context" at the top-right of the modal.

  4. Name Your Context
    Give it a clear, descriptive title (e.g., "Technical Writer," "CS Strategy Advisor," "SEO Blog Writer").

  5. Add a Description
    Clarify what this Context does so your team knows when to use it (e.g., "Use for drafting customer-facing documentation with a professional, helpful tone").

  6. Define Instructions
    In the instructions field, be specific about:

    • Tone: Formal, casual, empathetic, direct

    • Audience: Engineers, customers, executives, internal team

    • Constraints: Word count, formatting, what to avoid

    • Style preferences: Bullet points vs. paragraphs, emoji usage, technical depth

    Example instruction:
    "You are a technical documentation writer. Use clear, concise language. Avoid jargon unless defining it. Always include code examples when explaining APIs. Keep paragraphs under 3 sentences."

  7. Assign Labels
    Add labels (e.g., "Marketing," "Engineering," "Sales") to help your team filter and find the right Context quickly.

  8. Click Create
    The Context is now available to your entire team in the Chat interface.


How to Use Contexts Effectively

1. Switch Contexts in Real-Time

You can change the active Context mid-conversation without starting a new Chat. Click the Context dropdown and select a different persona to instantly shift Revo's behavior.

Use case:
Start a Chat with "Customer Support" Context to draft a help email. Then switch to "Technical Writer" Context in the same thread to create internal documentation for the same issue.

2. Attach Scoped Documents to Contexts

You can tell a Context to prioritize specific documents over your general knowledge base. This is useful when you want Revo to focus on a particular guide, policy, or dataset.

Example:
Create a "New Hire Onboarding" Context and attach your Employee Handbook. When anyone uses that Context, Revo will prioritize the handbook's information above everything else.

3. Standardize Team Workflows

Create Contexts for recurring tasks to ensure everyone on your team gets consistent outputs.

Examples:

  • "Weekly Sprint Recap" Context with a fixed format for status updates

  • "Customer Objection Handler" Context with pre-approved messaging for sales

  • "Bug Report Analyzer" Context with a standardized template for engineering

Result: No more "everyone does it their own way." One Context = one standard across the team.

4. Brand Voice Consistency

Create a "Company Voice" Context that references your Company DNA module for mission, values, and tone. Use this whenever drafting external communications to ensure perfect brand alignment.


Best Practices

  • Be Specific, Not Broad

    ❌ Bad: One generic "Marketing" Context
    βœ… Good: Separate Contexts for "SEO Blog Writer," "Social Media Copywriter," "Email Campaign Drafter"

    The more targeted your instructions, the better Revo performs.

    Include Examples in Instructions

    If you want a specific output format, show Revo an example in the Context instructions.

    Example:
    "When drafting customer emails, always follow this structure:

    1. Acknowledge the issue

    2. Explain what we're doing about it

    3. Provide a timeline

    4. Offer a follow-up option"

    Iterate Based on Team Feedback

    If Revo is too wordy, update the Context to say "Use concise, punchy bullet points." Because Contexts are shared, one update improves the experience for your entire team instantly.

    Use Human-in-the-Loop for Sensitive Tasks

    Create Contexts with built-in approval steps for high-stakes actions. Add instructions like:


    "Draft the response but explicitly ask for confirmation before creating a Jira ticket or sending an email."

    Leverage Labels for Organization

    As your Context library grows, use labels to keep them organized:

    • Department labels: Marketing, Engineering, Sales, CS

    • Task labels: Drafting, Analysis, Reporting

    • Audience labels: Internal, External, Executive


Can I share my Contexts with the rest of the team?

Yes. By default, Contexts you create are visible and usable by everyone in your workspace. This helps standardize how Revo assists different departments.

Does a Context overwrite my Documents?

No. A Context acts as a "filter" or a "lens." It tells Revo how to process your documents and communications, but it doesn't change the underlying data in your knowledge base.

Can I use multiple Contexts at once?

Currently, you select one active Context per interaction to ensure Revo has a clear, singular persona to follow. However, you can switch Contexts mid-conversation in the same Chat thread as your task evolves.

What is the difference between a Context and a Workflow?

Contexts guide how Revo communicates in Chat (the "how"). Workflows are automated multi-step processes triggered by events (the "do"). Use Contexts for conversational tasks like drafting and analysis. Use Workflows for repetitive automations like weekly reports or ticket creation.

Can I edit a Context after creating it?

Yes. Go to the Context library, select the Context you want to update, and modify the instructions or description. Changes apply immediately for all team members.

How do I know which Context to use?

Use the description and labels to identify the right Context for your task. If you're unsure, start with the default Context and switch if the output doesn't match your needs. Over time, your team will develop a natural workflow for Context usage.

Can I delete a Context if I no longer need it?

Yes. Go to the Context library, select the Context, and click Delete. This will remove it from your team's available options. Be careful, as this action cannot be undone.

Do Contexts work with email drafting?

Currently, Contexts primarily apply to Chat interactions. Email drafting uses your Intelligence Modules and your historical email tone. However, you can use a Context in Chat to draft an email, then copy the result into your inbox for review.

Did this answer your question?