The wrong requester
The forwarder, not the customer, became the user.
BoldBellowsIntercom to Zendesk workflow for teams where the front line chats in Intercom and back-office works in Zendesk
Intercom to Zendesk integration that escalates conversations as complete tickets, keeps both statuses in step and never opens a duplicate
A Zendesk ticket can carry an external ID, and a ticket that is closed can no longer be changed, so any follow-up has to open a new linked ticket. To connect Intercom to Zendesk without a stream of duplicates, BoldBellows reads the payload for its topic, its conversation and the part that triggered it, answers with a 200 at once so Intercom's retries are never needed, then creates one ticket with the requester found by email, the subject, a first comment built from the chat, the group, priority and tags you mapped, and the Intercom conversation ID as the external ID. Later customer replies are added as comments, and a note with the ticket number is left on the conversation. Both teams work in the tool they know.
View Pricing
From $910, billed once.
- Connect Intercom to Zendesk
- Escalations as complete tickets
- Statuses kept in step
Evidence the Zendesk route is dependable
- External ID matchthe conversation ID finds its ticket every time
- Complete ticketsrequester, group, priority and tags are set at creation
- Replies as commentsnew messages add to the ticket, not to a new one
- Closed is finala closed ticket gets a linked follow-up, never an edit
- Scoped accessCredentials are limited to the objects in scope and can be revoked
- Transparent pricingthe entry package is $910; the calculator shows each add-on before you pay
01the double-handling problem
An escalation by forwarded email arrives without the one detail the next team needs
The front line decides a chat needs the back office and forwards it. The ticket arrives with the wrong requester, no priority and a subject line that says Fwd. The customer replies in Intercom while the second team replies in Zendesk, so each side answers half of the conversation. When the ticket closes and the customer writes again, someone tries to reopen a ticket that can no longer be edited.
Two teams answering
Replies split across both tools.
A ticket with no priority
Nothing was set at creation.
The same Intercom escalations, as Zendesk tickets the next team can work
Before: Zendesk trusts every notice
- Every hook delivery becomes a write
- Escalations are forwarded by email
- Both tools hold half of the conversation
After: duplicates cannot form
- Identity is fixed by the Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID and never re-guessed
- Escalations arrive as complete tickets
- Both sides see the same ticket number and status
02how it works
How an escalated chat becomes one complete Zendesk ticket
Every step has a check before it, so a fault stops the run instead of spreading.
- Check it is real and in scope. The Intercom notice is validated, the underlying record is read, and only a qualifying conversation change moves on.
- Verify, match, search. The signature is checked, the requester is found by email and Zendesk is searched for a ticket that already holds this conversation ID.
- Create, comment, note. A complete ticket is created or updated with a new comment, and a note with the ticket number is added to the conversation.
Constraints from Intercom and Zendesk
- Limits apply per app and per workspace. Rate limits are counted per app and per workspace, and a 429 response comes with headers saying when to try again, so a historical read is paced and never hammered.
- Closed tickets are final. Zendesk does not allow a closed ticket to be changed, though it can create a follow-up ticket that points to it, so the build opens a linked follow-up for a customer who writes after closure.
- Lookups before retries. The Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID is the route's way of asking Zendesk whether the work is already done.
03The working parts
The Intercom Zendesk route, one capability at a time
Signal answers whether this should happen. Control answers what exactly gets written. Reconcile answers whether it is still right next month.
SignalControlReconcile
Intake rule reader Signal
Interprets the Intercom payload against the intake rule and stamps the decision on the ledger.
Stable identity ledger Signal
Gives each Intercom record a stable identity inside Zendesk that survives edits and retries.
Map change log Signal
Records every change to the field map, so a later question about a Zendesk value has an answer.
Ticket builder Control
Creates the ticket with requester, subject, first comment, group, priority, tags and the conversation ID as external ID.
External-ID ticket finder Control
Searches Zendesk by external ID before every create, so a repeat escalation updates the ticket that exists.
Group and priority matrix Control
Maps topics, plans and tiers to the Zendesk group, priority, tags and ticket form.
Ticket register Reconcile
Measures how far each ticket has slipped from the Intercom record and reports it.
Field drift monitor Reconcile
Catches a deleted group, a renamed tag or a new required field before creates start to fail.
Failure ledger Reconcile
Records every failed or refused write to Zendesk with its cause and what was done.
Intercom to zendesk integration or intercom to zendesk consultant, plus intercom to zendesk error handling: it is all in scope. Related searches include custom intercom to zendesk automation, intercom to zendesk Zapier alternative, intercom to zendesk duplicate prevention, intercom to zendesk API integration, sync intercom with zendesk, intercom to zendesk historical migration, intercom to zendesk service, connect intercom to zendesk, intercom to zendesk, escalate intercom chat to zendesk ticket, zendesk follow-up ticket from intercom, intercom to zendesk implementation, intercom to zendesk setup service, intercom to zendesk workflow and intercom zendesk external id.
04Who it's for
Where product teams collecting feedback in Intercom need to hand conversations that need a second team to Zendesk as complete tickets, keep both sides in step and avoid duplicate tickets
Intercom is where the customer first described the problem; Zendesk is where the specialist team resolves it.
Front-line agent
"Escalate once and be done."
The ticket is created with everything the next team needs.
Back-office agent
"Stop asking for the customer's details."
The requester, plan and chat summary arrive on the ticket.
Support operations
"One ticket per escalation."
The external ID prevents duplicates.
Zendesk admin
"Keep my forms intact."
Groups, fields and tags are verified before any ticket is created.
Support lead
"Keep customers informed."
The ticket number is noted on the chat for the teammate to share.
Founder
"One story across two desks."
Both teams can find the other side's work from either tool.
05Compare
Where a forwarded email and zaps stop, an external-ID hand-off route begins
Each can hand work over. Only one creates a complete ticket, matches on an external ID and handles a closed ticket correctly.
| How it gets going | a forwarded email | A typical trigger-and-action zap | A BoldBellows Intercom-to-Zendesk route |
|---|---|---|---|
| What starts the work | The next person to look | Each delivery, repeats included | YesRule-approved events, logged with the reason |
| How identity is decided | Guessed from context | A single field treated as the key | YesThe Intercom conversation ID as the Zendesk external ID, plus the ticket ID |
| What reaches Zendesk | A few fields, entered late | A copy without context | YesOne complete ticket per escalation, with comments and a linked follow-up if needed |
| After an uncertain result | Open both apps and compare | Runs again from the start | YesMatches on the Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID, then repairs or holds |
A late arrival
Events that reach the route after a newer one are recognized by timestamp and routed for review instead of applied, for this Intercom to Zendesk route.
A customer writes again after the Zendesk ticket was closed
The closed ticket cannot be edited, so a follow-up ticket is created that points to it, and the number is noted on the conversation. Finding the ticket comes first: the Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID is searched, the hit is compared, and only then is an action chosen. Writing a fresh ticket is the last option, reserved for proven absence.
Nothing is written to Zendesk until the Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID is defined and stored for each ticket.
PricingWhere the money goes: groups, ticket fields and statuses
Set the scope, see the Zendesk price, pick your speed
Begin with Signal at $910 and add only what your rollout needs.
One setup fee · Range shown first · PDF handover included
View Pricing
Pricing
Build your Intercom to Zendesk price
Pick a package, answer three short questions about how Intercom data should reach Zendesk, and your price and turnaround move as you choose.
06The process
Six steps from a forwarded email to a ticket that works
Each of the six steps has an output you can read, not just a status update.
Choose the hand-offs
We list which tags, teams and states turn a chat into a ticket for the second team, and which stay with the front line.
Approve access
We inspect the Intercom objects and the Zendesk target, then fix the identifiers that connect them.
Agree groups and fields
The Zendesk group, priority, tags, ticket form and the external ID rule are written down and signed off.
Stress the edges
Late deliveries, doubled events and partial failures are simulated in a test Zendesk and the results reviewed with you.
Launch with notes
Release is timed to a checkpoint, and the administrator PDF explains what to watch and whom to ask, in the Intercom to Zendesk route.
Post-launch review
We go through the exception list and the checkpoint log with you and agree what, if anything, needs a change.
07Turnaround
Time to launch, by package
Delivery windows start when the connections are in place, for this Intercom to Zendesk route.
Signal
6 to 10 business days
Control
10 to 16 business days
Reconcile
16 to 24 business days
08Before we start
To start the Zendesk build, have these ready
Permission for us to read the relevant Intercom records
A Zendesk Support account where we can create tickets through the API, and Intercom workspace access approved by an admin
Access to the Intercom account that holds the records in scope
Your expected behavior for edits, cancellations and repeats
The hours when changes to Zendesk are safest to release
Records or dates that the route should ignore
09Security and ownership
Narrow permissions, narrow payloads, nothing patched
For Intercom to Zendesk, the connection has a short list of permissions, all written down, all revocable, and none that reach beyond this route.
Untouched core, documented edges
Both Intercom and Zendesk are used as their own documentation describes; no workaround reaches into their internals.
Scoped, revocable access
Access is scoped to what the Intercom field map needs and no further.
Nothing extra travels
The route forwards what was agreed and ignores the rest, so Zendesk never becomes a second copy of everything in Intercom.
Proof before repetition
Nothing is created twice: a missing confirmation triggers a search of Zendesk by the Intercom conversation ID in the Zendesk ticket's external ID, plus the ticket ID before any further write.
Minimal logging
With Intercom to Zendesk in place, what we log is enough to repair a problem and no more.
Full handover
In the Intercom to Zendesk route, the route is yours from day one, and the documentation proves it.
10In their words
What BoldBellows clients say
Verified reviews from operations and finance teams who trust BoldBellows to keep their data moving correctly.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
11FAQ
Intercom, Zendesk and hand-offs: what support operations leads ask
Common questions from teams in your position, answered directly, on the Intercom to Zendesk route.
Does an Intercom to Zendesk Zapier route prevent duplicates?
A zap can provide a ticket for each escalated chat. It is not built to create one complete ticket with the right requester, group and comment, keep the two statuses in step and handle a closed ticket. The work here is the judgment around the connector, not the connector itself.
How do I connect Intercom to Zendesk?
The conversation changes you chose are sent to the route by webhook, and the route creates a ticket with the conversation ID as its external ID. Teams who want to sync Intercom with Zendesk get custom Intercom to Zendesk automation over Zendesk's ticket API, limited to the escalations they choose.
Will replies appear in both tools?
Customer replies are added to the ticket as comments, and the ticket number is noted on the conversation, so each team sees the other's context.
What stops duplicate tickets?
The external ID is searched before every create, so a second escalation updates the ticket that already exists.
What happens if the ticket is closed?
Zendesk will not change a closed ticket, so the route opens a linked follow-up and records the link.
Can statuses sync?
Yes, if you want it. A solved ticket can add an internal note to the chat, while the customer only hears from a person.
Why not use a basic link?
An Intercom to Zendesk Zapier alternative should do more than a basic link: it prevents duplicates, completes the fields, has a path for a closed ticket and recovers when Zendesk is unavailable.
How do you test the mapping?
Mapping is never an extra. The Intercom Zendesk field mapping service is included in the fixed price, and every field is matched to a Zendesk place before anything is written.
How custom can the Intercom to Zendesk route get?
Yes. Branching by region, value or product gives you a custom Intercom workflow for Zendesk, scoped and then built by the same Intercom Zendesk integration consultant. Packages start at $910.
What if Intercom alters a field we depend on?
For Intercom to Zendesk, the notes name every interface and version assumption.
Next stepHand customers to the next team without losing the story
Give your back office escalations that need no follow-up questions
Describe the outcome you want in Zendesk, and we build the pipeline that automates Intercom data to Zendesk so it arrives every time. Entry pricing is $910.
- From $910, paid once
- Complete tickets
- Statuses in step
- No monthly fee from us
On this Intercom to Zendesk route, if your case is bigger than the packages allow, ask for a custom quote.