“Backlog is up 207% while ticket volume is only up 2%, so the queue is not flooded; it is jammed.
Enterprise integration tickets increased 48% after the May 6 API v2/webhook release, take
2.3x longer to resolve than other categories, and now drive 62% of breached SLAs.
The likely action is to prioritize webhook and custom-mapping defects before adding more support staffing.”
Synthesized from the ticket data and conversations, product usage, webhook logs, the release code, engineering Slack, account-team email and account records.
The spike starts at the release
Enterprise integration tickets/day; 7-day average with release markers
The lift begins when v4.2.0 ships API v2 webhooks on May 6 and bends only after the May 28 retry/order hotfix. That makes this release-driven, not seasonal support demand.
The queue is jammed, not flooded
Mean resolution time since May 6, closed tickets
Integration issues take 2.3x longer to resolve because they pend on engineering and partner-API debugging. More agents would treat the symptom, not the bottleneck.
SLA misses are concentrated in integrations
Breached SLAs since May 6, by source
One category is driving 62% of breached SLAs. Fixing the webhook compatibility bug moves the operating metric; staffing the queue mostly hides it.
The same accounts are going quiet
Daily active users, indexed; affected enterprise accounts vs. the rest
The accounts filing integration tickets also show webhook failures and lower usage while other enterprise accounts stayed healthier. The support problem is now a revenue-risk signal.
What the text says
Excerpts the analysis drew on, beyond the counts
Ticket conversationEnterprise · May 9
“Since Tuesday’s update our custom field mappings stopped syncing to our ERP. Nothing errors on our side — the records just never arrive.”
Release codev4.2.0 · webhook payload
- "custom_fields": { "po_number": "4471", ... }
+ "custom_fields": [ { "key": "po_number", "value": "4471" }, ... ]Webhook delivery logsWeek of May 10
5,481 failed deliveries, up from about 1,800 a week. Most return 422 Unprocessable Entity from customer endpoints on payload_version=2.
Engineering Slack#eng-integrations · May 12
“Partner sync errors are the v2 payload shape. Retries are also re-sending out of order. Hotfix for ordering by end of month; the mapping change needs a compatibility path.”
Account-team emailMay 20
“Two of my enterprise accounts have paused their rollout until the sync is fixed. One is asking whether they should stay on the old API.”
The numbers showed where the jam was. The text showed why: a payload change broke custom-field mappings, retries made it worse, and customers have started pausing rollouts. No single dashboard tile carries that.