AI Employees overview
AI Employees (/ai-employees/*) are configurable agents for chat, tools, knowledge, voice, and phone. Populate Knowledge Hub first so answers stay on-brand.
Video
Who can do this
AI Employees view permission.
Before you begin
- Knowledge Hub articles uploaded
- Integrations for tools agents will call
- Optional phone numbers for voice
What you'll accomplish
- Navigation map of AI Employees surfaces
- Plan to create or clone first agent
Step-by-step procedure
| Area | Path | Purpose |
|---|---|---|
| Dashboard | /ai-employees/list | Agent roster |
| Add New | /ai-employees | Creation wizard |
| Command Centre | /ai-employees/command-center | Ops HUD |
| Agent detail | /ai-employees/:id | Tabs below |
| Phone Numbers | /ai-employees/phone-numbers | Voice lines |
Agent detail tabs: Overview, Activity, Tools, Knowledge, Settings (plus Credentials in edit flows).
Typical rollout
- Draft agent in Add New (Identity → Knowledge → Voice → Tools → Review).
- Attach Knowledge Hub collections.
- Connect tool Credentials (WhatsApp, Retell, email, calendar).
- Test chat from agent record.
- Monitor fleet in Command Centre.
Extended guidance
Separate agents by function—support vs outbound voice—so Knowledge scopes stay tight. Rotate Credentials on the same schedule as human password policies. Catalog templates accelerate rollout but still need Knowledge Hub localization.
Practice scenarios
Create sandbox agent, attach one Knowledge doc, ask three factual questions, verify citations in chat. Open Command Centre afterward and confirm the agent appears in the workforce pipeline.
Sandbox validation
Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.
Team rollout checklist
Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.
Keep learning
Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.
Verify your work
- Dashboard lists agents with status
- Test question returns grounded answer
- Command Centre shows healthy pipeline
Tips
Clone patterns from catalog templates when available—faster than blank agents.
Troubleshooting
| Generic answers | Enrich Knowledge Hub | | Missing Add New | AI create permission | | Voice fails | Retell Credentials not connected |