Error 11200 loses calls silently
Twilio logs 11200 when your webhook returns an error, times out or cannot be parsed, then carries on. We retry, then tell someone, so a missing call is noticed the same day instead of discovered in the debugger.
Integration · Twilio to Chorus (ZoomInfo)
Twilio and Chorus integration
You built your calling on Twilio, which means no vendor ships a connector for it. We get those calls into Chorus with the participants, the recording and the outcome attached, and we build it so a failed webhook is something you hear about rather than a call that quietly never arrived. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Twilio
Chorus (ZoomInfo)
One call ends in Twilio. In Chorus (ZoomInfo):
- A call completes on TwilioYour own app, your own numbers
- Recording and metadata sentParticipants, direction, outcome
- Chorus runs trackersCoaching and playlists as usual
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
Got it, thank you.
Check your inbox for a confirmation. We will reply within 2 working days with what we would do and what it would cost.
Why bespoke calling never reaches the conversation platform
Chorus earns its place through trackers — themes across every call, objections, pricing, competitors, next steps — and through the playlists managers coach from. All of that assumes the calls arrive. When your team dials through a Twilio app somebody built, nothing arrives by itself: there is no marketplace connector, and the recording sits in your Twilio account with a call SID and nothing a coaching platform can use.
The connection itself is not the hard part. Making it trustworthy is. Twilio creates outbound calls through the API at a default of one per second and queues anything above that, so a burst becomes a delay rather than an error, and a naive integration reports success for calls that have not happened yet. When a webhook does not answer properly, Twilio logs error 11200 and moves on — and a call that never fired its webhook is a call Chorus will never know existed. We build for both of those, so what is in Chorus matches what actually happened on the phone.
- Teams with an in-house dialer on TwilioCalls reach the coaching platform without rebuilding the dialer.
- Product-led teams calling from their own appConversations inside the product are reviewable like any sales call.
- Contact flows with IVR before a repOnly the leg where someone spoke is sent, not the menu.
What we connect between Twilio and Chorus (ZoomInfo)
A typical setup. We adjust each line to how your team uses Twilio and Chorus (ZoomInfo).
When this happensThis is what you get
A completed call with a recordingSent to Chorus with the rep, the other party and the direction
The call outcome from your appAttached, so conversations can be filtered by result
The rep who took the callMatched to their Chorus user, so coaching and usage count the right person
A call with no conversationHeld back, so menus and voicemails do not enter the library
A webhook that failed with 11200Retried, then raised as an alert rather than dropped
A recording that arrives lateMatched to the call it belongs to when it lands
Field mapping, event by event
Each Twilio event and exactly what it writes in Chorus (ZoomInfo). Pick an event to see its fields.
1. Trigger · Twilio
When a call ends
Every call made or received in Twilio
2. Action · Chorus (ZoomInfo)
Log the call record
In Chorus (ZoomInfo), on the contact — Where your team already works
Chorus (ZoomInfo) field
Mapped from
What happens
Activity date
Date created15 Sep, 4:00 pm
Shown in your time zone
Date created15 Sep, 4:00 pm
Shown in your time zone
Call length
Call duration3 min 04 s
Stored the way Chorus (ZoomInfo) expects
Call duration3 min 04 s
Stored the way Chorus (ZoomInfo) expects
Direction
DirectionInbound
Inbound or outbound
DirectionInbound
Inbound or outbound
Recording
Recording urlPlayable audio
Added once the file is ready
Recording urlPlayable audio
Added once the file is ready
Call notes
Transcription textAsked for pricing
Saved as note text
Transcription textAsked for pricing
Saved as note text
Contact
Matched by phone number+1 415 555 0142
A new contact is created only if none match
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Twilio calls
Your team builds and maintains every step
Where it runs
In your own Twilio and Chorus (ZoomInfo) accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Twilio and Chorus (ZoomInfo) setups usually go wrong
One call per second, by default
Outbound calls created through the API run at one per second unless your account limit is raised, and anything above is queued rather than rejected. We reconcile calls attempted against calls Twilio actually completed, so a busy hour does not look like a successful one.
Which leg is the conversation
A Twilio flow can involve an IVR, a queue and a transfer before anyone speaks. We agree which leg is the call worth reviewing, so Chorus gets the conversation and not the hold music.
New trackers are noisy
ZoomInfo’s own guidance is that initial trackers need refining during a pilot. Where it is in scope we check tracker hits against real calls from your Twilio flow, because language from an in-product call rarely matches a tracker written for demos.
How we set it up
- 1
Agree what connects
Which call flows are in scope, which leg counts as the conversation, how reps map to Chorus users, and where failures should be raised. You get a written scope with a fixed one-time price.
- 2
Access for the setup
Twilio credentials or a user you can revoke without touching your main login, and Chorus access covering the work.
- 3
We connect and test
We run calls through your flow, force webhook failures on purpose, and check what reached Chorus, what was held back and what was alerted on.
- 4
Handover
A short document of what is connected, including the failure alerts. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Twilio and Chorus (ZoomInfo), built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Free download
The integration health check
10 checks to make sure your website, CRM and dialer really are passing information between them.
From the blog
Further reading
Integrations
How to log every call from your dialer in your CRM
Every call on the right contact, with the outcome, the rep and the recording, and nobody typing notes afterwards. What to connect, how to match callers, and what to test.
CRM
Why your CRM is full of duplicates, and how to stop new ones
Duplicates come in through forms, imports, integrations and manual entry. Here is how to clean up what is there, and close the doors so they do not come back.
Dialers
Why fewer people answer your calls: spam labels and caller ID
When answer rates drop, the cause is often a warning label on your caller ID. How US carriers check and label calls, and what you can do about it.
Questions about Twilio and Chorus (ZoomInfo)
Can Twilio calls be reviewed in Chorus?
Yes. We send the recording with the participants, direction and outcome attached, so calls from your own Twilio app sit in Chorus like any other conversation and run through your trackers.
What happens when a webhook fails?
Twilio records it as error 11200 and carries on, which is how calls go missing. We retry and then raise an alert, so a gap is noticed rather than found weeks later.
Will a burst of calls break the integration?
No. Twilio queues API calls above your calls-per-second limit rather than rejecting them, and we reconcile attempted against completed calls so the numbers in Chorus match reality.
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your Chorus subscription and Twilio usage are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Twilio and Chorus (ZoomInfo). You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Conversation in ChorusCall reviewed
Call-back taskAssigned to the contact owner