A contact for every conversation
Every person who reaches out becomes a CRM record automatically. There’s no manual entry, no “should we save this customer” decision — once a conversation starts, the contact exists, and the next time the same person writes in, Atender recognizes them and attaches the new conversation to the existing record.
1Two record types
— individuals and the companies they belong to
●
Individual
A single person — name, multiple emails and phones, profile image, tier, custom fields.
▤
Organization
A company or entity that groups individuals together — often linked automatically by email domain.
Open a contact and you land on a tabbed detail view ↓
2The contact detail view
— everything you know about this customer, in one place
Overview
the summary tab
Identity, tier, custom fields, quick actions
The default tab. Name, contact methods, tier badge, and every custom field you’ve configured — organized into the sections you defined.
Contacts
organizations only
Members of the organization
For organization records, this tab lists every individual linked to the company. Add new members, navigate to their profiles, see who you’ve actually been in touch with.
Conversations
the timeline
Every interaction, in order
A complete chronological list of every conversation this contact has had with your team, across every channel. Click into any past conversation to read the full exchange. Institutional memory.
Notes
freeform
Sticky notes for context that doesn’t fit a field
“Prefers first-name basis.” “Recurring issue with product X.” “Always escalate.” — the unstructured human details that help the next agent on the line.
Attachments
files
Documents tied to the relationship
Contracts, invoices, screenshots, ID documents. Upload, preview, download — anything relevant to the customer relationship lives here, not buried inside one conversation.
Quick actions
act from the contact
Reach out without leaving the CRM
Start a new conversation by email or SMS, make an outbound voice call, or send a one-off message — from any contact card, with one click. No switching modules.
A contact is institutional memory. Even when an agent has never spoken with this customer, the full history is one tab away. The customer doesn’t have to repeat themselves. The team doesn’t have to rebuild context.
Made to fit your business
Atender ships the essentials. From there, you have three knobs to extend the contact record into something that matches your actual operation: custom fields, sections, and customer tiers. Plus a way to keep the ledger clean as it grows: merge.
1Custom field types
— pick the shape that matches the data
Field type sampler
Account ID
ABC-12345
Text
Renewal date
2026-09-12
Date
Industry
Manufacturing
Select
Receives marketing
✓
Checkbox
And more — number, multi-line, multi-select, and others — each with required / optional, default values, and validation. A slice of what’s available.
Group your fields so the form stays scannable as it grows ↓
2Sections, tabs, and pages
— organize fields into as many groups as you need, across as many tabs as you need
Contact view · tabs & sections
Overview
Billing
Compliance
Internal
+ Add tab
Account details
Account ID
ABC-12345
Industry
Manufacturing
Preferences
Language
English
Receives marketing
✓
+ Add section · and the next tab can hold its own. Stack as many sections, tabs, and pages as you need.
Pages and pages of the data you actually care about. Tabs let you split the contact view into as many top-level pages as makes sense — one for every team that touches the customer — and each tab can hold any number of sections, each with any number of fields. There’s no ceiling: shape the contact record the way your team actually thinks about its customers.
3Customer tiers
— the substrate for differentiated service
Define
Each tier has a name, color, and priority order
Call them whatever fits your business — VIP, Gold, Silver, Platinum, Enterprise, Standard. Pick a color so they’re visible at a glance. Drag-and-drop the order so Atender knows which tiers outrank others. A tier can also link to an SLA policy and to auto-applied tags in settings.
Assign
One tier per contact (or none)
Set a contact’s tier manually from the contact view, or set it programmatically — through automations as customers cross thresholds, or through the API as your billing or sales system pushes status changes in.
Recognize
Returning customers carry their tier with them
When a known contact reaches out, Atender matches them by email, phone, or any other address on file. The tier loads alongside the rest of the record — so the agent (human or AI) sees who they’re talking to before the first reply.
Once a tier is on a contact, it changes how the rest of Atender treats them ↓
4What tiers actually do
— the same label, different effects across the app
Voice
phone queue
Higher tiers move up the phone queue
A VIP caller doesn’t wait behind a stack of standard inquiries. The phone queue uses tier as a priority signal, so the right customers are picked up first.
Chat
live channels
Priority routing in chat and live channels
The same idea, in chat: tier raises a customer’s priority in the live queue and can route them to senior agents or dedicated teams.
SLA
tighter targets
Bind a stricter SLA policy to a tier. VIP customers get a 5-minute first-response target while Standard sits at an hour — same conversation engine, different expectations.
Inbox
visibility
Visual badges and inbox surfacing
Tier badges appear on the conversation list, the contact card, and the conversation detail panel. Higher-tier conversations float to the top of the inbox so they don’t get buried.
Tags
automation hook
Auto-applied tags
Each tier can apply specific tags to conversations automatically — the easiest way to feed downstream automations and reports without wiring rules by hand.
Reports
analytics
Slice metrics by tier
Response times, resolution rates, CSAT — broken down by tier so you can prove your best customers are getting your best service.
One contact field, six effects. That’s the point of tiers: define the levels once, in the CRM, and let voice, chat, SLA, the inbox, tags, and analytics each react to them. Tiers earn their place by being the single source of customer-importance across every module.
Even with three knobs and tier effects, ledgers get messy. One more tool keeps it clean ↓
5Merging contacts
— deduplicate without losing history
Multi-select and preview
Pick the records you want to merge. Atender shows you a preview of what the combined contact will look like — with addresses already deduplicated — before you commit.
The survivor inherits everything
Conversations, notes, attachments, custom field values — all carried forward to the merged contact. Merge is one-way; Atender confirms before doing it.
Built around the support relationship
Atender’s CRM is purpose-built for the day-to-day reality of customer support: every channel a customer uses, every conversation they have, every note your team adds, every attachment that matters — all on the right person, available to whoever picks up next. It’s optimized for the support relationship, and connects out cleanly to whatever else lives in your stack.
1Where Atender’s CRM shines
— the support relationship, end to end
Contact ledger
The canonical record of who has contacted you, with every channel, address, and identifier they’ve used.
Conversation history
Every email, chat, call, SMS, WhatsApp, and Messenger thread the customer has ever had with your team — in one timeline.
Custom data your team needs
Any field you wish was on the customer record — account ID, contract type, risk level, language, account manager — modeled in custom fields and sections you control.
Configurable tier system
Customer levels you define, color-coded, prioritized, ready to drive differentiated service across the rest of Atender.
Optimized for support — open to whatever you bring. Atender’s CRM is shaped for the support relationship; that’s where it shines. It isn’t optimized for deal pipelines, forecasting, or quota tracking the way a dedicated sales CRM would be — but you’re welcome to use it however serves your team. Most teams keep both, and let API and MCP keep them in step.
However you split the work, two integration surfaces keep everything in sync ↓
2Two ways to connect
— one for your systems, one for AI
API
for your systems
Example · API
GET /api/contacts/c_2hG9
{ "name": "Jane Smith", "tier": "vip" }
A full API for contacts, organizations, custom fields, and tiers
Push updates from your billing system, pull a current view into your data warehouse, sync customer status from whatever owns it. The whole CRM surface is available through Atender’s API.
MCP
for AI agents
Example · MCP
CALL atender.contacts.update
{ "id": "c_2hG9", "tier": "platinum" }
An MCP server that lets AI read and write your CRM
The Model Context Protocol is the AI-native way to expose tools to language models. Atender ships an MCP server so AI agents can read and write contacts, organizations, and custom fields directly.
Custom fields are your bridge. An “account ID” or “external CRM ID” field lets you map records 1:1 across systems without forking your data model. Sync your other systems into Atender as a tier or a custom field; let your data warehouse pull the support side back out. The integration goes both directions, on both protocols.
