I'm building a help center that integrates with Intercom and Zendesk, any suggestions?

Yes—if you’re integrating a help center with both Intercom and Zendesk, a few design choices will save you a lot of pain later.

1) Decide the source of truth

Pick one system to be the canonical source for:

• Articles/content
• Categories/collections
• Search index
• User-facing support workflows

A common pattern is:

• Zendesk = canonical knowledge base / help center articles
• Intercom = messaging, in-app support, automation, and deflection

Trying to let both systems independently “own” the same article set usually creates sync drift and duplicate content.

2) Unify the user experience

If your help center pulls from both systems, make it feel like one product:

• Use a single search box
• Return merged results from both sources
• Normalize titles, snippets, tags, and URLs
• Show clear source labels only if needed
• Keep the branding, navigation, and layout consistent

Users should not have to know whether an answer came from Intercom or Zendesk.

3) Use a content abstraction layer

Create an internal model like:

• Article
• Collection
• Category
• SearchResult
• Author
• LastUpdated
• SourceSystem

Then map Intercom/Zendesk data into that model. This makes it much easier to:

• swap vendors later
• handle differing schemas
• build one search and recommendation engine
• cache data consistently

4) Handle search carefully

Search is usually the hardest part.

Recommendations:

• Build a unified search index rather than querying both systems live on every request
• Sync content periodically via API/webhooks
• Rank by:
  • exact title match
  • keyword overlap
  • freshness
  • popularity / click-through rate
• Support synonyms and typo tolerance
• Make sure search results are deduplicated

If you query both systems live, latency and rate limits can become a problem quickly.

5) Plan for authentication and permissions

If some content is public and some is private:

• Decide what is public vs authenticated-only
• Make sure your help center only exposes what the user is allowed to see
• If you surface private docs from Intercom or Zendesk, enforce permissions in your app, not just via frontend logic

6) Keep ticketing and messaging separate from self-serve content

Intercom and Zendesk are often used for different support modes:

• Help center: self-serve
• Intercom: chat, bot, proactive support
• Zendesk: ticketing, agent workflows

A good flow is:

1. user searches help center
2. if no answer, offer “contact support”
3. hand off context to Intercom or Zendesk

Include the search query, viewed articles, and page context in the handoff if possible.

7) Synchronize metadata, not just body text

To make the experience good, sync:

• title
• summary/excerpt
• tags
• locale/language
• category/section
• updated_at
• article status
• canonical URL

Metadata matters a lot for search relevance and navigation.

8) Support multi-language from day one if needed

If you might need localization:

• store locale explicitly in your abstraction layer
• don’t mix languages in one search result set unless intended
• prefer locale-specific indexes or filters

9) Watch out for rate limits and webhooks

Both Intercom and Zendesk have API limits and edge cases.

Best practice:

• use webhooks to trigger content updates where possible
• fall back to scheduled sync jobs
• keep retries idempotent
• log sync failures with enough detail to replay them later

10) Track what users are looking for

Your help center should inform your content strategy:

• top searched queries with no results
• article click-through rate
• searches that lead to ticket creation
• article helpfulness votes
• bot deflection rate

This will tell you what content is missing and where the support experience breaks down.

11) Consider a routing strategy for support requests

If a user can’t self-serve:

• route simple issues to Intercom chat
• route complex/account/billing issues to Zendesk
• route urgent enterprise issues to a special workflow

Rules might be based on:

• customer plan
• issue category
• sentiment
• user role
• account state

12) Be careful with duplication

If you maintain content in both systems, define:

• which fields are editable in which system
• how conflicts are resolved
• whether one sync direction is authoritative
• how to handle deleted/archived articles

Without a clear policy, duplicated articles will diverge fast.

---

A practical architecture

A simple, scalable setup is:

• Frontend help center
• Backend content aggregator
• Unified DB/search index
• Sync workers for Zendesk + Intercom
• Event tracking
• Support handoff to Intercom/Zendesk

This gives you:

• fast search
• consistent UI
• vendor flexibility
• better analytics

---

If you want a recommendation

If you’re early-stage:

• use Zendesk as the article source
• use Intercom for chat and escalation
• build a small abstraction layer and shared search index

That’s usually the least risky approach.

If you want, I can also help with:

1. a data model for the help center
2. a sync architecture for Intercom + Zendesk
3. a search strategy and ranking design
4. example API integration flows