Ticket Status Not Updating After Intercom Move

After moving from Intercom, ticket statuses may freeze. This guide covers the most common causes — mapping gaps, webhook failures, permission changes — and shows how to verify and fix each one.

NNeuraDesk TeamNovember 19 20264 min read
On this page

After switching from Intercom to a new help desk, you may notice that ticket statuses no longer change when agents reply, close, or reopen conversations. The symptom usually appears as a static status column, missing timestamps, or automation that never triggers. Below are the most common reasons, ordered by frequency, with steps to confirm each cause and how to fix it.

1. Status field mapping missing or mismatched

How to confirm

  • Open the migration or import settings in your new help desk and locate the status‑field mapping table.
  • Compare each Intercom status value (e.g., "open", "pending", "closed") with the target system’s status list.
  • Look for any status that maps to "—" or to a non‑existent value.

How to fix

  • Add missing status values in the target system or create custom statuses that match Intercom’s terminology.
  • Update the mapping so every source status points to a valid destination status.
  • Re‑run the migration for a small test batch, then verify that the status column updates correctly.

2. Webhook or API integration not configured

How to confirm

  • Check the webhook delivery logs in Intercom (or the new platform) for recent events such as "conversation.updated".
  • Look for failed deliveries, 4xx/5xx responses, or missing signatures.
  • In the new help desk, review the integration settings to see whether the inbound webhook URL is present and enabled.

How to fix

  • Ensure the webhook URL matches the endpoint documented by your new help desk.
  • Verify that the secret or token used for authentication is identical on both sides.
  • Enable the webhook if it was disabled, then trigger a test event (e.g., change a conversation status in Intercom) and confirm the status updates in the new system.

3. Permission or role changes affecting status updates

How to confirm

  • Review the roles assigned to agents who normally change ticket status.
  • Check audit logs for any "permission denied" entries when a status change is attempted.
  • Confirm that the API key or service account used by the integration has the "manage conversations" or equivalent scope.

How to fix

  • Grant the necessary permissions to the relevant roles or service accounts.
  • If you use a shared inbox, ensure the inbox’s default role includes status‑change rights.
  • Test by manually updating a ticket status as an affected agent.

4. Automation rules or workflows not migrated

How to confirm

  • List the automation rules that existed in Intercom (e.g., auto‑close after 48 hours, auto‑assign on reply).
  • In the new help desk, search for equivalent rules; note any that are missing.
  • Observe whether a ticket that should be auto‑closed remains open indefinitely.

How to fix

  • Recreate the missing rules using the new platform’s workflow builder.
  • Map each Intercom condition and action to the closest equivalent.
  • Run a test ticket through the workflow to verify the status transition fires.

5. Caching or indexing delays

How to confirm

  • Open the same ticket in two browser windows; if one shows the new status and the other does not, a cache issue is likely.
  • Check the help desk’s status‑page or admin console for background‑job queues that process status updates.
  • Wait a few minutes and refresh; persistent staleness points to a deeper problem.

How to fix

  • Clear the browser cache or use an incognito window.
  • If the platform offers a manual re‑index button, trigger it for the affected project.
  • Verify that any scheduled sync jobs are running on schedule (check the job history).

6. Data corruption or incomplete migration

How to confirm

  • Spot‑check a random sample of migrated tickets; compare the status field in Intercom’s export with the value in the new system.
  • Run a migration report (if available) and look for rows marked "partial" or "error".
  • Search for tickets that have a status value not present in the new system’s status list.

How to fix

  • Re‑migrate the problematic tickets individually or in a small batch.
  • If the migration tool supports a "delta" run, enable it to capture only changed records.
  • Contact the new help desk’s support team with the migration logs for further assistance.

What to do if nothing worked

If you have verified mapping, webhooks, permissions, automation, caching, and data integrity and the status still refuses to update, gather the following and open a support ticket with your new help desk:

  • Export of the webhook delivery logs (last 24 hours).
  • Screenshots of the status‑field mapping page.
  • List of agents and their roles.
  • Any error messages from the migration report.

A fresh platform that includes ticket status tracking out of the box can eliminate many of these migration headaches. NeuraDesk offers a free plan with shared inbox, AI reply suggestions, automatic email‑to‑ticket conversion, and full status tracking — no credit card required. try NeuraDesk free

For more general migration troubleshooting, see Troubleshooting Missing Ticket Status Updates After Migration. If you also see AI reply problems after the switch, review Troubleshooting AI Reply Errors After Switching Intercom.

Found this useful? Share it with your team.

Join teams already using NeuraDesk

Ready to get started?

Create your workspace and try NeuraDesk for free.

Sign up free