Run Atender, end to end
440 articles across 12 categories — written by the team that builds the platform.
Browse by topic
12 categoriesAnalytics
Channels
Conversations
CRM
CSAT
Handbook
Incidents
Knowledge Base
Monitor
New Article Suggestions
Settings
Trials
Latest articles
Updated continuouslyDeactivate a user when they leave the team or shouldn't have temporary access — they can't log in, but their conversation history is preserved. Reactivate later by toggling. Permanent deletion is a separate, irreversible action.
When a user is deactivated, their conversations, drafts, comments, and team memberships are preserved — nothing is auto-reassigned. Plan the handover before deactivating; the system protects history, not workflow continuity.
A built-in collector for bug reports and feature requests from your team — submissions land in a triage queue with status, priority, module context, and comment threads.
Tie a team to a specific opening-hours rule so SLA timers, IVR routing, and chat availability all reflect the team's actual schedule. Most useful for multi-region teams or specialist teams with hours that differ from the workspace default.
Build a new team — pick a name, add initial members, optionally link an opening hours rule. The team becomes available for routing automations and SLA scoping immediately.
Wire a channel — email inbox, voice number, web chat widget, etc. — to a default team so inbound conversations land with the right group. The default-team setting lives on the channel, not on the team.