Chat vs Intercom
Chat is the zerosoft app that replaces Intercom. By our count it covers 80% of the 79 Intercom capabilities we measure: 57 included, 11 partial and 11 missing. The table comes from the same data as the product page and was last checked against the code on November 18, 2026.
Chat isn't usable yet. The table counts what's already built in the code.
At a glance
- Parity with Intercom
- 80%
- Intercom at list price
- $29 / seat / month
- Chat
- $0 on your server (AGPLv3). On zerosoft Cloud: free plan, then usage. Seats are not billed.
- License of Chat
- AGPLv3, source on GitHub
- Last reviewed
- November 18, 2026
Intercom starts around $29 per seat per month. A team of ten pays $3,480 a year. Chat on your server costs $0.
Capability by capability. Our count, from the code.
parity with Intercom
80%of what Intercom does, by our count
- Included
- 57
- Partial
- 11
- Missing
- 11
We measured 79 Intercom capabilities: each one we have scores 1, a partial one 0.5 and a missing one 0, with double weight for the core ones; this is our own assessment, checked against the code on November 18, 2026. See the changelog
- Inbox and conversations88%
- Collaboration84%
- Automation94%
- Channels, integrations and API50%
- Admin and permissions75%
- Reports100%
- Mobile and offline66%
- AI90%
- Help center66%
- Proactive and outbound58%
- Import and export83%
- Real time and daily use93%
Everything Chat includes69
[x] Included[+] Better[~] Partial
| Capability | Chat | Intercom |
|---|---|---|
| Inbox and conversations | ||
| Embeddable web messenger | IncludedOne script tag with color, position, welcome text, attachments and a Help tab | Intercom: Yes |
| Messenger font and reply time | IncludedSeven fonts built from system font stacks (nothing loaded from outside) and a reply time you choose, shown under the header. The reply time is the text you pick: it is not measured | Intercom: Yes |
| Search inside a messenger conversation | IncludedThe visitor searches the open thread: matches are highlighted and Enter moves between them | Intercom: Yes |
| Control who can upload attachments | PartialPer widget: everyone, only people with a signed identity, or nobody, enforced on the server. Intercom can also decide by custom attributes | Intercom: Yes |
| Shared inbox with open, pending, snoozed and resolved | IncludedFilters for Mine, Unassigned and Anyone | Intercom: Yes |
| Conversation priority | PartialFour levels (low, medium, high, urgent); Intercom has five | Intercom: Yes |
| Conversation tags | IncludedNormalized, with a count per workspace | Intercom: Yes |
| Conversation attributes, required on resolve | IncludedText, number, select and boolean | Intercom: Yes |
| Person and company attributes | IncludedVisitor email, name, notes and page context, free attributes per person and company records with domain, plan and notes. Set from the profile, the conversation panel or your site, with a signed identity, when that person writes | Intercom: Yes |
| Merge duplicate conversations | Included | Intercom: Yes |
| Tickets (customer, back office, tracker) | PartialTrack issues work as tracker tickets: several conversations hang from one issue and each shows its status. There are no ticket types, customer ticket portal or automatic reply to everyone when it closes | Intercom: Yes |
| Visitor sees past conversations | IncludedConversations tab in the messenger with every past thread; with a signed identity it also brings the ones from the same email on other devices | Intercom: Yes |
| Pre-chat form | Included | Intercom: Yes |
| CSAT survey on resolve | Included1 to 5 with a comment, shown in the widget | Intercom: Yes |
| Office hours and away message | Included | Intercom: Yes |
| Identity verification (HMAC) | IncludedSame scheme as the Intercom user_hash | Intercom: Yes |
| File and image attachments both ways | IncludedVisitor and teammate, up to 10 MB per file, with image and audio previews | Intercom: Yes |
| People list with visitor profiles | IncludedEach visitor has a page with notes and their conversations | Intercom: Yes |
| Collaboration | ||
| Assign to a teammate | Included | Intercom: Yes |
| Custom snooze options by team | IncludedAdmins add options with their own name and duration, for everyone or for one team, next to the standard ones in the conversation and in bulk | Intercom: Yes |
| Internal notes with @mentions | IncludedMentions notify; notes can be edited and deleted | Intercom: Yes |
| Edit and delete your own messages | IncludedThe visitor sees an "edited" mark | Intercom: Yes |
| Away status that skips round robin | Included | Intercom: Yes |
| Teams and team inboxes | IncludedTeams with members, a team inbox in the sidebar with its open count, team on each conversation and rules that send work to a team | Intercom: Yes |
| Collision detection (who is viewing or typing) | IncludedShows who else has the conversation open and who is writing a reply, above the composer | Intercom: Yes |
| Follow a conversation without being assigned | IncludedFollow from the header: new visitor messages notify you (in the app and by push) and Following lists them | Intercom: Yes |
| Saved views in the sidebar | IncludedSave the inbox filters (status, assignee, team, priority, channel, tag, search) as a private or shared view under Inbox in the sidebar, with counts; rename, share and delete in Views | Intercom: Yes |
| Automation | ||
| Assignment rules | IncludedBy keyword, by time window, default and round robin, in a set order | Intercom: Yes |
| SLA by priority with breach warnings | IncludedIncluded; in Intercom it needs the Expert plan | Intercom: Yes |
| Saved replies and macros | IncludedA saved reply can change status, assign, snooze and add tags. Opens with / in the composer | Intercom: Yes |
| Saved reply usage | IncludedHow many times each saved reply was used, in its list, and sorting by use to find the ones nobody needs. It counts insertions from the composer | Intercom: Yes |
| Variables in saved replies ({{name}}, {{email}}) | IncludedFilled when a saved reply is inserted: {{name}}, {{first_name}}, {{email}}, {{agent_name}}, {{agent_first_name}}, {{widget}} and conversation attributes by id, with a fallback ({{first_name|there}}). A variable without a value or an unknown one is flagged in the composer before sending | Intercom: Yes |
| Visual workflows | PartialFlow has chat lifecycle triggers. There is no builder inside Chat | Intercom: Yes |
| Skills-based routing | IncludedSkills and a maximum of open conversations per person, counted across all widgets. A rule with a required skill spreads only among available people who have it and are under their maximum; routing by team stays | Intercom: Yes |
| Channels, integrations and API | ||
| Inbound email in the inbox | PartialThrough Resend Inbound: forward your support address to the widget address and answer from the inbox; replies to our emails return to the conversation only when the visitor email is verified. Answers go out within a minute as "<widget> via zerosoft" from the app address, in the same thread (In-Reply-To and References); attachments are saved and the ones that are not get a note. Missing: sending from the customer own domain, and forwarding via received_for was tested with the Resend docs payload, not against live Resend. Needs CHAT_INBOUND_DOMAIN, the MX to Resend and the signed email.received webhook | Intercom: Yes |
| REST API for conversations | IncludedList, get, reply, assign, resolve and reopen | Intercom: Yes |
| Webhooks | IncludedMessage created, conversation created, assigned, tagged, resolved and CSAT received, signed | Intercom: Yes |
| Built-in CRM link | BetterCreates the contact and logs the conversation on its timeline, with no third-party app | Intercom: Yes |
| Actions in Cal, Track and Flow from a conversation | IncludedCreate or link a Track issue from the conversation (it counts as a customer request), CRM natively, and Cal or Flow through Agents and Flow | Intercom: Yes |
| Admin and permissions | ||
| Team workspace | IncludedThe whole team sees every widget | Intercom: Yes |
| Roles and per-inbox permissions | IncludedWorkspace roles plus an Access tab per widget: a restricted inbox is only for admins and the people on its list, in pages, search, reports, notifications, assignment, member API keys and Agents views. Owner and admin keys see the whole workspace. Flow triggers and Flow chat messages do not run for a restricted inbox | Intercom: Yes |
| Multiple brands | PartialSeveral widgets with their own name and color. No help center per brand | Intercom: Yes |
| SSO | PartialComes from the suite login; Chat has no settings of its own | Intercom: Yes |
| Reports | ||
| Volume, first response, resolution and CSAT by agent | IncludedAny date range, with CSV download. First response counts teammates only | Intercom: Yes |
| Bot vs human and bot resolution rate | IncludedConversations answered by the bot, resolved without a teammate, resolution rate and handoffs | Intercom: Yes |
| Reports by tag, widget, peak hours and SLA compliance | IncludedBy tag, widget, team and channel, busiest hours by day in the office hours zone, and SLA compliance for first response and resolution | Intercom: Yes |
| Custom reports | IncludedPick a metric, a grouping (day, week, tag, widget, team, channel, priority, status, assignee, company), a range and a widget; save it with a name and download CSV | Intercom: Yes |
| Mobile and offline | ||
| Inbox on a phone browser | IncludedWorks at 390 px wide, in light and dark mode | Intercom: Yes |
| Push and browser notifications for agents | IncludedWeb Push from the suite PWA (same service worker as Lines): on every new visitor message it notifies the widget owner, the assigned teammate and whoever follows the conversation, on each device where they turned it on. Optional sound in the open inbox. Needs VAPID keys | Intercom: Yes |
| Email notice to visitors who left | IncludedDelay set per widget, in minutes | Intercom: Yes |
| AI | ||
| AI agent that answers with your content | IncludedAI bot over Docs and saved replies, or an Agents agent with tools; hands off to a human | Intercom: Yes |
| Keyword bot that works without AI | BetterWhole-word matching over Docs and saved replies; also the fallback when AI fails | Intercom: No |
| AI for agents: summarize, rephrase, live translation | IncludedIn the composer: draft a reply from published Docs and saved replies, summarize as an internal note, rephrase, friendlier, shorter and translate to the visitor language. Nothing is sent on its own | Intercom: Yes |
| AI insights (topics, CX score) | PartialIn Reports: topics by word frequency and a CX score computed from CSAT, first response and resolution. No AI model behind them yet | Intercom: Yes |
| Help center | ||
| Public help center with search and votes | IncludedPublished from Docs at /h/<handle> | Intercom: Yes |
| Articles inside the widget | IncludedHelp tab in the messenger | Intercom: Yes |
| Proactive and outbound | ||
| Proactive messages by URL, time on page or segment | IncludedOutbound chat messages by URL, seconds on the page and audience (first visit, returning, identified), once per visitor, with views and replies counted | Intercom: Yes |
| Banners, tours, surveys, posts and checklists | IncludedBanners that stay until closed or a date, posts, checklists with saved progress that stay until dismissed, product tours by CSS selector that resume until finished, and 1 to 5 surveys, with page, time and audience targeting. Progress is per browser | Intercom: Yes |
| Email campaigns | PartialPlain text campaigns only to people with explicit consent: an admin marks it on their profile, or your site sends it with a signed identity. Variables, sent and failed counts, retries, one-click unsubscribe, scheduling up to 90 days ahead and 500 recipients a day per workspace (50 in the first 7 days); the rest continue the next day. No consent form in the messenger, opens and clicks or sending from your own domain | Intercom: Yes |
| Import and export | ||
| Conversation transcript export | IncludedText or JSON, with or without notes, or emailed to the visitor | Intercom: Yes |
| Import from Intercom or Crisp | PartialUpload the JSON of the Intercom or Crisp API to a widget: people, messages and status, without duplicates. Tested with the payloads in their docs, not with a real account. No direct connection, attachments or internal notes | Intercom: Yes |
| Bulk export of conversations | IncludedFrom Reports, for workspace admins: CSV with a row per conversation or JSON with messages (internal notes on request), by date range. Every export is logged | Intercom: Yes |
| Real time and daily use | ||
| Real-time message delivery | IncludedInbox, open conversation and messenger listen to a server stream and refetch as soon as something changes, usually within two seconds. Polling stays as a fallback if the stream drops | Intercom: Yes |
| Typing indicator and read receipts | Included | Intercom: Yes |
| Keyboard shortcuts | IncludedC creates, / searches, J and K move, / in the composer opens saved replies, Ctrl or Cmd + Shift + Y resolves and + N switches to a note | Intercom: Yes |
| Cmd+K search | IncludedFinds conversations (by person, subject or text), people, views, teams and widgets | Intercom: Yes |
| Multi-select bulk actions | IncludedAssign, tag, snooze and resolve | Intercom: Yes |
| Visitor context panel | BetterPage, referrer, browser, language, form answers and CRM contact in one panel | Intercom: Yes |
| Messenger in the visitor language | Partial15 languages, picked from the browser or fixed per widget. Intercom covers about 45; no right-to-left yet | Intercom: Yes |
Where we go further
- Built-in CRM linkCreates the contact and logs the conversation on its timeline, with no third-party app
- Keyword bot that works without AIWhole-word matching over Docs and saved replies; also the fallback when AI fails
- Visitor context panelPage, referrer, browser, language, form answers and CRM contact in one panel
Still missing (11)
Intercom has these and we don't yet. If you need one, vote for it on the public board.
- Customer portal for tickets and conversationsVote on the board
- Side conversations with outside peopleVote on the board
- Workforce management: forecasts and schedulesVote on the board
- WhatsApp, Instagram, Messenger and SMSVote on the board
- Phone and voiceVote on the board
- App marketplaceIntercom lists more than 450 appsVote on the board
- Native iOS and Android apps for agentsVote on the board
- Mobile SDK for the messengerVote on the board
- Multilingual, private or custom-domain help centerVote on the board
- Series: multi-step customer journeysVote on the board
- Tooltips on your productVote on the board
Questions.
How do I add the widget to my site?
Create a widget, copy the script tag and paste it before the closing body tag. It works on any site that serves HTML.
Does it handle email or WhatsApp?
Email yes: you forward your support address to the widget's and answer from the inbox. Replies go out from the app address, not from your domain yet, and forwarding was tested with the payload in Resend's docs, not against live Resend. WhatsApp is not in Chat yet; Lines handles it.
How does the bot work?
It answers until someone on your team replies. It uses AI with your canned responses and Docs pages; without AI configured, it matches by keyword. You can turn it off per widget.
Does it connect to the CRM?
Yes. If the visitor leaves an email, Chat creates the contact in the CRM and logs the conversation on its timeline.
What is missing compared to Intercom?
WhatsApp, Instagram, Messenger and SMS in the inbox, phone and voice, an app store, native apps for the team, a mobile SDK for the messenger, and a multilingual or private help center.
Guides and posts
- What to do with a feature request that arrives in chatA four-step method for answering feature requests without overpromising: tag in Chat, link to a Track issue, count distinct customers, and tell them when it ships.
- Migrate from Intercom to Chat: bring your conversationsHow to move from Intercom to Chat: pull the JSON from Intercom's API, what imports (people, messages, status), what doesn't, what to check first.
- Help articles for two readers: your customer and your botHow to write help center articles that answer in the first lines, match the words customers actually type and work for the Chat bot, using the help center built from published Docs pages.
- A help center for your customers, built with DocsHow to set up a public help center with Docs: collections, articles that search can find, the Was this helpful vote, the Help tab in the Chat widget and AI answers. With the limits in plain view.