TL;DR: Intercom throttles update calls: up to 10 unthrottled calls per page refresh, then a maximum of one call every 30 minutes. A full page reload resets the counter. In an SPA with frequent route changes you will burn through 10 calls fast, so do not blindly call update on every navigation.

## Fix
1. Intercom throttles update calls: up to 10 unthrottled calls per page refresh, then a maximum of one call every 30 minutes.
   Expected: this specific failure stops.
2. In an SPA with frequent route changes you will burn through 10 calls fast, so do not blindly call update on every navigation.
   Expected: this specific failure stops.
3. Debounce it, only call update when something actually changed (user data, company), and rely on the page-view ping sparingly.
   Expected: this specific failure stops.
4. If the messenger stops reacting to route changes, throttling is the first thing to check, not your integration code.
   Expected: this specific failure stops.
5. Context: Stack Overflow #40223246 (accepted answer, 3 votes): AngularJS SPA calls Intercom('update') after login and again on every $stateChangeSuccess route change, following the single-page-app integration docs.
   Expected: this specific failure stops.

## Details
A full page reload resets the counter. Network tab shows the ping stops working after the first 10 route changes.

## When to use
You hit exactly this: Intercom update goes quiet after 10 calls per page load, throttle rules explained in Intercom.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Intercom.