Settingsbeginner

What is Sidekick?

Sidekick is the conversation-intelligence layer that runs over every conversation. For agents, it's a slide-out panel that opens with a brief and a proposed next step, and answers follow-up questions with cited sources. For the system, it runs background workers that auto-tag conversations and extract structured data into custom fields.

5 min read

What is Sidekick?

Sidekick is the conversation-intelligence layer that runs over every conversation in Atender. It reads what’s being said in real time, understands it, and routes that understanding to whoever — or whatever — is on the other end. For human agents, Sidekick shows up as a slide-out panel that opens with a brief of the conversation and a proposed next step, and lets the agent ask follow-up questions. For the system, it works in the background — tagging conversations, detecting structured data, populating custom fields.

Sidekick assists. Agent Stacks act on their own. Agent Stacks handle conversations autonomously; Sidekick understands every conversation and surfaces that understanding wherever it’s useful — to the agent in the panel, to the system in the background, and increasingly to Agent Stacks themselves. Sidekick can run an action only after the agent’s Yes, do it, and it runs the action as that agent, then leaves an internal note on the conversation.

Three kinds of understanding

Sidekick reads the conversation and extracts three kinds of understanding. Only entity detection runs as a background worker; the topic summary and the pattern matching are computed when an agent opens the conversation, then cached — the summary for up to five minutes or until the next customer message arrives, whichever comes first.

  • Topic — What the customer is asking about, what’s already been tried — The Ask Sidekick brief in the panel; the Conversation summary module when Ask Sidekick is off
  • Entities — Structured data inside messages — IBANs, phone numbers, domains, and anything a custom regex rule matches — Detected Insights module + written to the rule’s mapped custom field
  • Patterns — Cross-conversation relationships — incident matches, multiple open conversations from the same contact — Incident hint card above the modules in the panel; a chip in the conversation header for the duplicate-conversation case

That understanding is the same regardless of who’s handling the conversation. What changes is how it’s used.

For agents — the panel

When an agent opens a conversation, Sidekick appears as a slide-out panel with a brief of the conversation and a proposed next step. The brief starts by itself on open conversations handled by a person. On Agent Stack conversations and on Done or archived ones, the agent clicks Suggest the next step instead. The proposal takes one of these forms:

  • An action — the agent approves it with Yes, do it or declines it with No. Sidekick runs the action only after Yes, do it.
  • A reply draft — with Insert into reply, Rewrite, and Copy buttons.
  • Next-step buttons — shortcuts for the most likely things to do next.

Agents can also ask Sidekick follow-up questions about the conversation. Answers stream in as they are generated and cite the sources they draw on. Agents can give a response a thumbs up or a thumbs down; a thumbs down asks what was wrong.

Above the brief, the panel shows any detected insights and a folded Related articles row with the matching Knowledge Base articles, internal Handbook procedures and other related sources. Open the row to see them. A separate folded Similar conversations row lists up to 3 closed conversations of other customers with the same request and the same customer language, with conversations Trends described in the same words first, then the same team’s. Each one shows its subject, a one-line “what to do” written from how the team solved it, and the date it was closed, and opens in a new tab. Similar conversations appear when Ask Sidekick is available (the Ask Sidekick module is not hidden in Panel layout), and not in the first minutes of a new conversation.

Modules are configurable per tenant — enable, disable, reorder via drag-and-drop in Settings → Sidekick → Panel layout. See the panel modules reference for what each module does.

When Ask Sidekick is off (the Ask Sidekick module is hidden in Panel layout), the panel shows its stack of modules instead: a quick summary, matching articles and procedures, relevant links and the other visible modules. There is no proposed next step and no follow-up questions.

For agents — the hint card

One contextual card can pop above the modules when something material is happening:

  • Possible Incident Match — when a customer describes a problem matching an active incident, Sidekick offers to link the conversation and subscribe the customer to updates. Linking and subscribing from the hint card requires the Conversations reply permission; users who cannot reply will not see the Link & subscribe button. See Link a conversation to an incident from the panel.

When the same contact has other open conversations, that is flagged outside Sidekick: a chip in the conversation header reads “N other active conversations” and opens the Other Conversations panel when clicked.

For the system — background workers

Most of what Sidekick does is invisible. Two background workers run on every conversation regardless of whether a human is reading the panel:

  1. Detection rules — pattern-matching that extracts structured data (IBANs, phone numbers, domains, or anything a custom regex you write matches) from customer messages and writes it to the rule’s mapped custom field. Per rule, you can also enable scanning of internal notes and the conversation subject. See Detection rule types and Create a detection rule for scan toggles and the subject ride-along limitation.
  2. Auto-tagging — shortlists tags by semantic similarity to their descriptions, then has an LLM pick which of those actually apply. Recorded and transcribed phone calls can also be auto-tagged after transcription completes. Off by default — opt tags in via Tag Management and enable the global toggle in Settings → Sidekick.

Incident discovery is not a background worker: the match runs on demand when an agent opens the conversation, against the latest customer message. It is toggleable in settings.

What you tune

Sidekick’s behaviour is controlled from Settings → Sidekick, organized into four tabs:

  • General — incident discovery toggle, inline-highlight toggle, auto-save toggle, confidence threshold, and a usage card showing Sidekick usage over the last 30 days.
  • Panel layout — module ordering and visibility.
  • Detection rules — create, edit, reorder, test rules. Map to custom fields.
  • Auto-tagging — enable the worker, set the max-candidates cap, and control whether newly transcribed phone calls are tagged with the Tag phone calls toggle under the AI auto-tagging card. The phone-call toggle defaults on and only affects calls transcribed after it is enabled, not historical transcripts.

The master switch (Enable Sidekick) is not on a tab — it sits in the header card above the tab strip, so it is visible from all four tabs. Turning it off greys out and locks every other setting.

Where to start

Tags

Ai FeaturesGetting StartedConcept