Skip to main content

Manage an AI Employee record

Open any agent at /ai-employees/:id to tune behavior after launch. Tabs mirror how operators maintain human reps—activity history, enabled tools, knowledge scope, and voice/chat settings.

Video

Video coming soon for this topic

Who can do this​

AI edit permission; credential changes may require Admin.

Before you begin​

  • Agent already created via Add New
  • Knowledge Hub updates staged
  • List of tools needing credential rotation

What you'll accomplish​

  • Tools and knowledge aligned with current offers
  • Credentials tested after rotation
  • Activity reviewed for anomalies

Step-by-step procedure​

Overview​

Snapshot of agent status, channels, and quick actions.

Activity​

Recent runs, errors, and usage—use when users report stale answers.

Tools​

  1. Enable/disable integrations (CRM actions, messaging, webhooks).
  2. Each tool shows connected vs not connected.
  3. Open Credentials (edit wizard or credentials section) to Save Credentials / Test.

Knowledge​

  1. Link Hub collections scoped to this agent.
  2. Remove retired docs to prevent hallucinated promos.

Settings​

Adjust instructions, voice (Call Behavior), security (Audit Logging), performance caps.

Conversations monitoring​

Review conversation panels when enabled—escalate sensitive threads to human Inbox.

Extended guidance​

After pricing changes, update Knowledge and re-test three canonical questions before announcing. Tool toggles without credential tests cause silent failures—always click Test post-save. Keep a change log when multiple Admins edit Settings tabs.

Practice scenarios​

Disable one tool, confirm agent refuses related action gracefully, re-enable after credential test passes. Update Knowledge tab and confirm new doc surfaced in a follow-up chat question.

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​

  • Tool test returns success
  • Chat reflects new Knowledge doc within minutes
  • Activity log shows latest deployment

Tips​

important

Credential Management entries are encrypted—never paste secrets into chat tickets.

Troubleshooting​

| Tool shows not connected | Open Credentials → Save Credentials | | WhatsApp limit hit | Check subscription limits message | | Voice Not Connected | Configure Retell in Credentials |

See also​