Knowledge Base

Run Atender, end to end

440 articles across 12 categories — written by the team that builds the platform.

Latest articles

Updated continuously
beginner3 min readSeptember 4, 2026
Deactivate or reactivate a user

Deactivate 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.

How To
beginner4 min readSeptember 4, 2026
What happens to a user's work when they leave?

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.

Faq
beginner4 min readSeptember 4, 2026
What is User Feedback

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.

Concept
intermediate4 min readSeptember 4, 2026
Link a team to opening hours

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.

How To
beginner3 min readSeptember 4, 2026
Create a team

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.

How ToGetting Started
beginner4 min readSeptember 4, 2026
Assign channels to a team

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.

How To