Overview
Your agent’s identity includes the basic information that helps you and your team identify, organize, and manage agents in your dashboard. Some details like name and avatar are also visible in demo links.

Agent Name
The agent name helps you identify this agent in your dashboard, campaigns, and reports.Best Practices
For customer-facing agents (visible in demos):- “Acme Support”
- “Alex from Acme Sales”
- “Booking Assistant”
- “Customer Support - Product Questions”
- “Outbound Sales - Lead Qualification”
- “Appointment Booking - Dental Clinic”
- “Agent 1”
- “Test”
- “New Agent”
[Function] - [Specialty][Department] - [Agent Type][Use Case] - [Language]
Examples by Use Case
Support Agents
- “Technical Support Agent”
- “Billing Support - English”
- “Order Status Helpline”
Sales Agents
- “Inbound Sales - Enterprise”
- “Lead Qualification Bot”
- “Demo Scheduler”
Operations
- “Appointment Booking - Main”
- “Payment Reminder Calls”
- “Feedback Survey Agent”
Multi-Language
- “Support Agent - Spanish”
- “Sales Agent - German”
- “Booking Agent - French”
Avatar
Upload an avatar image to visually identify your agent in the dashboard and in demo links you share with others.

The avatar is visible when you share demo links, so choose an image that represents your brand professionally.
Avatar Guidelines
Image Specifications- Format: PNG, JPG, or SVG
- Size: Recommended 200x200px minimum
- Aspect Ratio: Square (1:1)
- File Size: Under 2MB
Example Avatar Ideas
Support Agents
Headset icon, support badge, helping hand
Sales Agents
Briefcase, handshake, growth chart
Booking Agents
Calendar, clock, appointment book
Tags
Tags help organize and filter agents in your dashboard, especially useful when managing many agents.

Tagging Strategies
By FunctionUsing Tags Effectively
Internal Notes
Use the notes section to document configuration details, version history, and team information about this agent.Useful Note Types
Configuration HistoryOrganization Best Practices
For Small Teams (1-5 agents)
- Use simple, descriptive names
- Minimal tagging needed
- Basic notes for important changes
For Medium Teams (5-20 agents)
- Develop naming conventions
- Use tags for function and status
- Maintain regular notes on changes
For Large Teams (20+ agents)
- Strict naming conventions mandatory
- Multi-level tagging (function, region, language, status)
- Detailed change logs in notes
- Consider creating agent documentation outside the platform
Quick Reference
| Field | Purpose | Visible To |
|---|---|---|
| Name | Identify agent in dashboard | Internal + Demo links |
| Avatar | Visual identification | Internal + Demo links |
| Tags | Organization & filtering | Internal only |
| Notes | Detailed documentation | Internal only |