Knowledge Base

Run Atender, end to end

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

Latest articles

Updated continuously
intermediate6 min readOctober 2, 2026
Recipe: Two-Team Handover Routing by Description

Copy-paste handover setup that routes billing handoffs to one team and technical handoffs to another using the AI picks mode, with prerequisites.

Ai FeaturesRecipe
intermediate4 min readOctober 2, 2026
FAQ — Customer keeps creating new conversations

If a returning customer is starting fresh threads instead of being recognized, walk these five checks. The most common cause is a mismatched identifier.

TroubleshootingFaq
beginner4 min readOctober 2, 2026
Set up auto-archiving

Configure how long a conversation sits in Done before Atender archives it. Timing is measured in business hours per the team's opening hours, not wall-clock.

How To
beginner5 min readOctober 2, 2026
What is the Conversation ID

An optional, configurable customer-facing identifier for conversations — sequential or random, with prefixes, dates, and per-channel or per-team overrides.

Concept
intermediate4 min readOctober 2, 2026
Engagement state — pending vs engaged

Engagement state is the orthogonal axis to lifecycle status. Pending = ball in our court (needs reply). Engaged = ball in customer's court (we replied, waiting). It's deterministic — Atender computes it automatically — and it's what answers 'what should I work on next?'

Concept
beginner2 min readOctober 2, 2026
FAQ — The Customer Says They Replied but I Don't See It

Where a missing customer reply usually landed — an internal note from a sender not on the conversation, the provider's spam filter, or a sibling contact record.

TroubleshootingFaq