Feature · For developers

Swap one import. Keep every line of code. Cut your bill. The same JavaScript SDK surface, native to SupportWire, AI-native from day one.

See the diff Get started free

TL;DR

The drop-in Intercom Messenger replacement is a JavaScript SDK from SupportWire that exposes the same public API as the Intercom Messenger JS SDK. Same boot, update, show, shutdown and trackEvent signatures. Same app_id and user_id shape. Change one package name, swap your workspace ID, ship in five minutes. Get a native AI agent, flat pricing, and no per-resolution fee.

$ the whole migration

Two lines change. The rest stays.

Same app_id, user_id, email shape. Same boot lifecycle. Same trackEvent contract. The drop-in Intercom Messenger replacement reads like the file you already shipped.

messenger.ts + 3  −  3
- import Intercom from '@intercom/messenger-js-sdk';
+ import Intercom from '@supportwire/messenger-js-sdk';
 
  Intercom({
-   app_id: 'your-intercom-app-id',
+   app_id: 'your-supportwire-widget-slug',
    user_id: currentUser.id,
    email: currentUser.email,
-   user_hash: currentUser.intercomHash,
+   user_hash: currentUser.supportwireHash,
    name: currentUser.name,
  });

Built to swap. Not to wrap.

Not a plugin on top of someone else's SDK. A native replacement, written to read like the file you'd rewrite if you could.

One import swap

Change the package name. That's the migration. No config rewrite, no SDK relearning.

Every method, mapped

boot, show, hide, update, shutdown, trackEvent. Same names. Same arguments. Same lifecycle.

Run both during cutover

Keep Intercom live. Boot SupportWire alongside. Cut over when your team is ready.

Cuts the bill

Same SDK surface. Different invoice. Flat plans starting free, no per-seat tax.

Five minutes. Three steps.

No big-bang switch. No conversation export. No SDK relearning. Migrate from the Intercom Messenger to SupportWire in a single commit.

  1. Install the package

    One package, no dependencies, ESM and CJS bundled. Works with any bundler.

    terminal
    $ bun add @supportwire/messenger-js-sdk

  2. Swap the import

    Change the package name. The shape of the SDK is identical.

    messenger.ts
    - import Intercom from '@intercom/messenger-js-sdk'
+ import Intercom from '@supportwire/messenger-js-sdk'

  3. Swap your app_id

    Drop in your SupportWire workspace ID. Existing user identifiers carry over. Ship.

    messenger.ts
    Intercom({
  app_id: 'your-supportwire-workspace-id',
  user_id: currentUser.id,
  email: currentUser.email,
});

Every Intercom method. Same signature.

The drop-in Intercom Messenger replacement covers the full public surface. Your existing call sites keep working.

boot{ app_id, user_id, ... } ✓ supported
update{ user_id, custom_attrs } ✓ supported
show() ✓ supported
hide() ✓ supported
shutdown() ✓ supported
trackEvent(name, metadata?) ✓ supported
startTour(tourId) ✓ supported
showNewMessage(prefilledText?) ✓ supported

Same code.
New bill.

A messenger that reads the way you wrote it. AI that earns its keep. Pricing that does not punish growth.

Get started free See pricing

Questions about the swap.

Everything teams ask before they switch off Intercom.

What is a drop-in Intercom Messenger replacement?

A drop-in replacement is a library that exposes the same public API as another library, so you can swap one for the other without rewriting your code. SupportWire's messenger SDK matches the Intercom Messenger JS SDK method-for-method: same imports, same boot signature, same trackEvent contract. Change the package name, ship.

How long does the migration take?

Five minutes for a small site. The migration is three steps: install @supportwire/messenger-js-sdk, swap the import line, swap your app_id for your SupportWire workspace ID. No config rewrite, no SDK relearning, no rebuilding flows.

Does SupportWire support every Intercom Messenger SDK method?

The SupportWire messenger SDK covers the full public surface: boot, update, show, hide, shutdown, trackEvent, startTour, and showNewMessage. Method names, arguments, and lifecycle behaviors match the Intercom JS SDK so existing call sites keep working.

Can I run both Intercom and SupportWire side by side during cutover?

Yes. The packages do not collide. You can boot both messengers on the same page while you migrate conversations and user data, then remove Intercom when your team is ready. No big-bang switch required.

Will my Intercom user identifiers still work?

Yes. SupportWire respects the same user_id, email, and custom attribute fields. Existing identifiers carry over, so your analytics, segmentation, and outbound message rules keep firing without remapping.

How much cheaper is SupportWire than Intercom?

SupportWire plans are flat, not per-seat. The Free plan covers small teams. Paid plans start at $29/month and top out at $199/month for unlimited seats. Intercom Advanced starts at $99 per seat per month before Fin AI fees. For most teams the swap cuts the bill by 60-80%.