How do I hire multiple assistants in Unified for different roles (support triage, sales follow-up, ops coordinator)?

Most teams reach a point where one “generalist” AI assistant isn’t enough. Support needs fast triage, sales wants consistent follow-up, and operations needs someone to coordinate tasks and data. Unified makes it possible to “hire” multiple assistants for these different roles and keep them working together inside one workspace.

This guide walks through how to structure, create, and manage multiple role-specific assistants in Unified for support triage, sales follow-up, and operations coordination.

---

Why use multiple assistants in Unified?

Using several role-specific assistants instead of a single general assistant helps you:

• Reduce confusion – Each assistant has a clear purpose and scope.
• Improve accuracy – Assistants are trained and instructed for one domain, not everything.
• Scale workflows – You can add or adjust one assistant without breaking others.
• Mirror your org chart – Support, sales, and ops get their own “AI teammate.”

---

Before you start: access and sign-in

To set up multiple assistants in Unified, you’ll need to be signed in to your Unified account:

1. Go to your Unified sign-in page.
2. Enter your Username (user) or the email associated with your account.
3. Enter your Password.
4. If you can’t remember it, click “Forgot Password?” and follow the reset flow.
5. Click SIGN IN.
6. Don’t have an account yet? Click “Sign up” to create one, then sign in.

Once you’re signed in, you can create, configure, and manage multiple assistants from your workspace.

---

Step 1: Decide which assistants you need

A common setup for growing teams is:

1. Support Triage Assistant

   • Reads incoming tickets or chats.
   • Categorizes and prioritizes.
   • Suggests or drafts responses.
   • Routes issues to the right queue or human.

2. Sales Follow-Up Assistant

   • Summarizes calls/emails.
   • Drafts follow-up emails and proposals.
   • Logs notes into your CRM.
   • Reminds your reps of next steps.

3. Ops Coordinator Assistant

   • Tracks tasks and project status.
   • Standardizes processes and checklists.
   • Generates summaries and handoff notes.
   • Helps coordinate communication across teams.

You can always add more assistants later (e.g., a knowledge base curator or an internal training assistant). Start with the three that align to your highest-impact workflows.

---

Step 2: Create a separate assistant for each role

In Unified, the pattern is:

One role = one assistant with its own instructions, knowledge, and tools.

Follow this pattern for each assistant:

1. Create a new assistant
   • Open your Unified workspace.
   • Go to your assistants or bots area.
   • Click Create new assistant (or similar).
2. Name the assistant by role
   • Use clear, purpose-driven names like:
     • “Support Triage Assistant”
     • “Sales Follow-Up Assistant”
     • “Ops Coordinator Assistant”
3. Write role-specific system instructions
   • Clearly define:
     • What this assistant should do.
     • What it should not do.
     • Who it is serving (support agents, sales reps, ops managers, etc.).
   • Keep instructions focused on the assistant’s primary workflows.

Repeat this process three times: one assistant for support triage, one for sales follow-up, and one for operations coordination.

---

Step 3: Configure your Support Triage assistant

Define the scope

The support triage assistant should:

• Read and understand incoming customer messages.
• Identify:
  • Issue type (billing, bug, feature request, how-to question, urgent outage).
  • Priority (low, medium, high, critical).
  • Customer sentiment (calm, frustrated, escalated).
• Suggest or draft a response using your tone and policies.
• Tag/route the issue to the correct queue or owner.

Add knowledge

Attach or connect:

• Help center articles and FAQs.
• Internal troubleshooting guides.
• SLAs and escalation rules.
• Product documentation relevant to support.

This keeps the triage assistant grounded in your real policies and answers.

Set up instructions

Examples of useful instruction elements:

• “Always start by confirming the customer’s core issue in one sentence.”
• “If the issue is billing-related, tag as ‘Billing’ and suggest routing to the billing queue.”
• “If the message indicates a production outage, mark as Critical and escalate.”
• “If you are not certain, ask a clarifying question instead of guessing.”

Integrate into your support workflow

Depending on your stack, you might:

• Connect Unified to your ticketing system or shared inbox.
• Have the assistant:
  • Suggest triage data for agents to confirm.
  • Auto-apply tags and priorities.
  • Draft replies that a human reviews and sends.

---

Step 4: Configure your Sales Follow-Up assistant

Define the scope

The sales assistant should:

• Summarize calls, demos, and discovery notes.
• Draft follow-up emails based on conversation context.
• Suggest next steps and timelines.
• Help reps personalize outreach at scale.
• Log key moments into your CRM (depending on your integrations).

Add knowledge

Attach or connect:

• Product sheets and feature breakdowns.
• Pricing guidelines and discount rules (be careful with visibility).
• Sales playbooks and email templates.
• ICP (Ideal Customer Profile) descriptions.
• Case studies and success stories.

Set up instructions

Useful instructions might include:

• “Always represent our product accurately; never promise unavailable features.”
• “Use a professional, friendly tone that matches our brand.”
• “Summarize every call into 3–5 bullet points and one line of next steps.”
• “Draft follow-up emails that reference the prospect’s goals in their own words.”
• “Never modify or create pricing beyond the documented rules.”

Integrate into your sales workflow

You can use the sales assistant to:

• Generate call summaries after meetings.
• Draft follow-ups that reps quickly edit and send.
• Prepare proposal outlines.
• Help create outreach sequences based on segment, role, or industry.

---

Step 5: Configure your Operations Coordinator assistant

Define the scope

The ops coordinator assistant should:

• Track and summarize project status across teams.
• Turn meeting notes into actionable task lists.
• Standardize templates and checklists (onboarding, implementation, launches).
• Help you enforce process consistency.

Add knowledge

Attach or connect:

• Standard operating procedures (SOPs).
• Project templates and checklists.
• Internal policies (security, approvals, procurement).
• Definitions of key business metrics and reporting formats.

Set up instructions

Some example instructions:

• “Whenever you summarize a meeting, list tasks with owners and due dates.”
• “If an SOP exists for a process, reference it instead of inventing new steps.”
• “Flag any missing owner or deadline as a risk that needs attention.”
• “Use concise bullet-point summaries for status updates.”

Integrate into your ops workflow

Use the ops assistant to:

• Turn ad-hoc conversations into structured tasks.
• Maintain standardized formats across teams.
• Prepare weekly status updates from raw notes.
• Support handoffs between departments (e.g., sales → implementation → support).

---

Step 6: Keep assistants separated but coordinated

To make multiple assistants work together without stepping on each other’s toes:

1. Limit each assistant’s responsibilities

• The support triage assistant should not draft sales proposals.
• The sales assistant should not make decisions about incident severity.
• The ops assistant should not reply directly to customers.

Clear boundaries produce better, more reliable behavior.

2. Route conversations to the right assistant

You can design your workflow so:

• Customer-facing systems feed into the Support Triage Assistant.
• CRM and call/email systems feed into the Sales Follow-Up Assistant.
• Internal tools and documentation feed into the Ops Coordinator Assistant.

In some setups, a “front door” assistant can detect intent and route content to the right specialist assistant behind the scenes.

3. Share only the right knowledge

• Support assistant: deep access to troubleshooting content.
• Sales assistant: controlled access to product and pricing info.
• Ops assistant: broad but internal-only process and policy documents.

Avoid giving every assistant access to every dataset if it doesn’t need it.

---

Step 7: Test and refine each assistant

Start with pilot users

Pick a small group of:

• Support agents to test the triage assistant.
• Sales reps to test the follow-up assistant.
• Ops/project managers to test the coordinator assistant.

Ask them to use the assistant in their real workflows and collect feedback.

Track what matters

For support:

• Time to triage.
• Tagging accuracy.
• Reduction in manual sorting work.

For sales:

• Time saved on follow-ups.
• Meeting-to-follow-up speed.
• Email personalization quality.

For ops:

• Fewer missed tasks or handoffs.
• Consistency of status updates.
• Adoption of standardized checklists.

Improve instructions and knowledge

Adjust:

• System prompts (instructions) when the assistant misunderstands its role.
• Knowledge sources when it gives outdated or incomplete answers.
• Access controls when it sees things it shouldn’t.

Iterate regularly; small prompt and knowledge tweaks can drastically improve performance.

---

Step 8: Governance, permissions, and security

When you “hire” multiple assistants for different roles, treat them like real team members:

• Permissions – Limit each assistant’s access to only what it needs.
• Auditability – Keep a record of how assistants are used and what they generate.
• Approval workflows – For critical actions (e.g., sending external messages), require human review.
• Version control – Document changes to prompts, knowledge, and integrations over time.

---

Practical examples of daily use

• Support triage

  • An email comes in: “My invoice is double what I expected and my account seems locked.”
  • Triage assistant:
    • Classifies as “Billing + Access issue.”
    • Priority: High (billing + account access + frustration).
    • Drafts a response and suggests escalation if certain conditions are met.

• Sales follow-up

  • After a discovery call, the rep drops the transcript into Unified.
  • Sales assistant:
    • Summarizes the prospect’s pain points and goals.
    • Drafts a tailored follow-up referencing those goals.
    • Suggests a shortlist of relevant case studies.

• Ops coordination

  • After a cross-functional meeting, notes go into Unified.
  • Ops assistant:
    • Extracts tasks, owners, and due dates.
    • Highlights dependencies and risks.
    • Prepares a summary for stakeholders.

---

Ongoing maintenance for multiple assistants

To keep your support triage, sales follow-up, and ops coordinator assistants effective:

• Review role definitions quarterly.
• Update knowledge sources when:
  • You launch new products or features.
  • Policies or SLAs change.
  • You revise internal processes.
• Refresh prompts when:
  • You notice recurring errors.
  • Teams adopt new workflows or tools.

By structuring Unified with several focused assistants—each aligned to a clearly defined role—you turn it into a coordinated, role-aware AI workforce that supports support, sales, and operations simultaneously.