Channels

The Amazon channel is an early-access integration for Amazon sellers. Connect your Seller Central account, and buyer-message emails from Amazon arrive in Atender as conversations linked to the relevant order.

The full list of webhook event types your subscriptions can listen to, grouped by what they're useful for.

Create a webhook subscription with POST /v1/webhooks. You pick the events you want, give Atender a URL, and your server starts receiving signed event payloads.

Create a conversation programmatically with POST /v1/conversations/outbound. Pass an externalReference for idempotent retries, a contact, a subject, and optionally the channel, tags, and custom fields.

Use a built-in channel (Email, Web Chat, Voice, SMS, WhatsApp, Messenger, Amazon) whenever one fits. Use the API only when you have a touchpoint outside Atender's supported channels.

Atender's v1 REST API lets you create conversations programmatically and subscribe to webhook events for outbound notifications. Authenticated with tenant API keys — no separate channel UI to configure.

Set an email channel's Route To to AI Agents so the orchestrator answers inbound mail. Covers the two reply-delay floors and the guard that stops the AI from replying to autoresponders, OOO messages, bounces, and spam.

An email domain needs MX, CNAME, and TXT records to verify in Atender. This page explains what each record does and why all three are required.

Every domain in Settings → Email carries a status: Pending, Active, Failed, or Disabled. Each one means something specific about what Atender will and won't do with that domain.

Add the MX, CNAME, and TXT records Atender generated at your DNS provider, then wait for the status to flip from Pending to Active. Verification can take minutes to a few hours depending on DNS propagation.

Set the From name and From email customers see when they receive replies. These are per-domain settings on the domain row in Settings → Email.

Connect a sending and receiving domain to Atender. You pick a region (US or EU), enter the domain, and Atender generates the DNS records you'll add at your provider.

If customer emails don't appear in the inbox, the cause is almost always one of: the domain isn't Active, mail is being delivered to a different mailbox, or the sender is being filtered as spam.

Verification fails when Mailgun can't confirm one or more of the required DNS records. Almost always a typo, a truncated TXT record, or partial setup.

Atender's Email channel runs on your own domain, with Mailgun handling delivery. You can configure multiple domains per tenant, each pinned to a US or EU data-residency region.

Create a Meta channel in Atender, log in through Facebook OAuth, pick the Page you want to connect, configure routing, and save. Messages to the Page now arrive as conversations in Atender.

The Messenger channel connects your Facebook Pages to Atender. Customer messages from each connected Page flow into the same inbox as Email, Web Chat, and every other channel.

When agents send a proactive SMS without specifying a sender, the default outbound number is used. Pick one from your assigned numbers in Settings → SMS.

Route incoming SMS to a team, an AI agent, or the general inbox. Each assigned number gets its own routing, configured from Settings → SMS.

SMS is Atender's text-message channel, powered by Vonage. Numbers are provisioned by your account team and assigned to your tenant; you configure routing and the default outbound number from Settings → SMS.

The IVR builder ships 17 node types organized into Actions, Routing, and Terminals. Each node represents a real step in a call — speak a message, gather digits, branch on a condition, send to a queue, hang up.

Route calls to your support queue during business hours; outside business hours, play an after-hours message and send the caller to voicemail. A common starter pattern.

Create a queue in Settings → Voice → Queues, pick the team that serves it, set the reservation timeout and wrapup, and then reference the queue from your IVR's Send to Queue node.

Recording is configured at the tenant level as a default, with per-IVR-node overrides for paths that should always or never record. Atender plays a consent message before recording starts and lets callers opt out.

Pick the voice that speaks your IVR's Say Message and Customer-First greeting text. Voices are configured per language — Atender's catalog includes Twilio-renderable Amazon Polly voices plus Google Chirp3-HD voices where Twilio supports them.

What callers hear while they wait — silence, music, or a ring tone, plus an optional customer-first greeting when the agent connects — is configured on each queue.

Callback lets a caller hang up without losing their place in line — the system calls them back when an agent is free. Configure it on the Callback tab of your phone number, then send the call to a Callback Queue node in your IVR.

Open the IVR builder, drag nodes from the palette, connect them with edges, and configure each node from the side panel. Save when validation passes.

Each phone number routes through exactly one IVR flow. Assign the flow from the number's Flows tab — pick from existing flows, or create a new one from the same screen.

Provision a phone number for a country you serve. You pick the country, submit any compliance details the country requires, and Atender requests the number through Twilio. Numbers don't appear instantly — most go through a regulatory review.

If callers reach a generic message instead of your IVR flow, the cause is almost always one of: no flow is assigned to the number, the flow failed validation, or the number is still Pending.

The Voice channel is Atender's cloud call center, powered by Twilio. Tenants provision phone numbers, design IVR flows, configure queues and callbacks, and route to human teams or AI voice agents — all from a single interface.

Turn on the 'Share page location with Agent Stacks' toggle in Web Chat widget settings so the AI can see which page a visitor is chatting from and skip asking which product or module they're in.

Hand Web Chat conversations to an Agent Stack to handle autonomously, with human escalation when needed. Configured in the widget's Routing tab.

Copy the embed snippet from the Installation tab and paste it into your site's HTML — typically just before the closing </body> tag. The widget renders automatically on every page where the script loads.

Match the widget to your brand — primary color, dark-mode palette, bubble colors, launcher icon (or team-photo launcher), background and input-box colors. All in the Appearance tab.

Create a new widget in Settings → Web Chat, name it, pick a primary language, set the welcome message and primary destination. Everything else can be configured tab by tab afterwards.

When a visitor's connection drops, Atender can switch the conversation to email, SMS, or WhatsApp automatically so they don't lose the thread. Configured per widget with a custom message and a minimum 300-second timeout.

Let visitors move a chat to email, SMS, or WhatsApp mid-conversation. Pick which channels are available in the widget's Channel Switching tab.

Set a primary language for the widget and add as many secondary languages as you need. Each language can override the welcome message, input placeholder, and system text.

Collect the visitor's name, email, phone, or any custom field before the conversation starts. The answers are attached to the conversation and the contact, so your agents have context from the first message.

If the launcher doesn't show up, it's almost always one of: the widget is disabled, the script didn't load, the snippet's data-widget-id is wrong, or a content-security policy is blocking the script.

Web Chat is the embeddable chat widget you place on your website. Each widget has its own settings — branding, routing, channel switching, languages — and you can run multiple widgets per tenant.