LEADCONDUIT ADD-ON
Twilio | Inbound Calls
Communication APIs for SMS, voice, video and authentication.
SPECIFICATION
Fields & configuration
The exact fields this add-on uses, appends, and the configuration options available in LeadConduit.
Route inbound calls to Twilio numbers through LeadConduit to enhance and deliver lead data to your CRM before your phone rings.
Response Fields
LeadConduit returns the following data to the lead source.
| Response Field | Description |
|---|---|
Id | The lead identifier that the source should reference |
Outcome | The outcome of the transaction (default is success) |
Reason | If the outcome was a failure, this is the reason |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
| Reference | Unique Twilio call identifier |
| Phone 1 | Phone 1 - The phone number or client identifier of the party that initiated the call |
| City | City most closely associated with the caller's phone number |
| State | State most closely associated with the caller's phone number |
| Postal Code | Postal code most closely associated with the caller's phone number |
| Country | Country of origin of the caller's phone number |
| Call Forwarded To Phone | The number to which the Twilio call was forwarded, as specified in the Twilio callback URL |
| Call Forwarded From Phone | This parameter is set only when Twilio receives a forwarded call, but its value depends on the caller's carrier including information when forwarding. Not all carriers support passing this information |
| Call Direction | A string describing the direction of the call. The value is one of inbound, outbound-api, or outbound-dial |
| Call Duration | The duration in seconds of the just-completed call |
| Call Status | A descriptive status for the call: "queued", "ringing", "in-progress", "completed", "busy", "failed" or "no-answer" |
| Call Called Phone | The phone number used for tracking for inbound calls |
| Call Caller Name | The name of the person/entity making the call |
| Call Url | The URL to the call in Twilio |
Redirect an Active Call to a New Number.
Response Fields
LeadConduit returns the following data to the lead source.
| Response Field | Description |
|---|---|
Phone | The phone number to which the call will be transferred after flow execution has completed |
Is Recording | Is the call being recording? - recording audio is available by visiting the Twilio call URL |
Outcome | The outcome of the integration (default is success) |
Reason | If the outcome is error, this is the reason |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
| Call Transfer Phone | The phone number to which the call will be transferred to after flow execution has completed. If the recipient is named as a phone number, this mapping overrides that number. |
| Call Transfer Is Recording | Is the call being recording? (default: true) - recording audio is available by visiting the Twilio call URL |
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
Increase lead conversion by instantly returning a Caller ID Name and Carrier information to provide a caller with a tailored experience, even if it's their first time calling in.
Response Fields
LeadConduit returns the following data to the lead source.
| Response Field | Description |
|---|---|
Caller Name | Caller name |
Caller Type | Denotes whether line is a business or consumer. If not available, value will be null |
Reason | Error reason |
Outcome | Was phone lookup successful? |
Billable | The billable count. 1 if the event resulted in a valid outcome, or 0 if an error occured |
Country Code | Country Code ('US' |
Mobile Country Code | The mobile country code of the carrier (for mobile numbers only). |
Mobile Network Code | The mobile network code of the carrier (for mobile numbers only). |
Carrier Name | The name of the carrier |
Type | The phone number type. Possible values are landline, mobile, or voip. |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
Phone 1 Required fieldTwilio needs this data to function. | Primary phone |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
GETTING STARTED
Add Twilio in three steps
Add the add-on
In your LeadConduit flow, add a new Add-On step and select Twilio.
Provide required data
Map the lead data the service needs. Required fields and configuration options are shown above.
Use the result
Run the flow and use the add-on result for real-time routing, validation, enrichment, or downstream decisions.
KEEP EXPLORING
More add-ons
Catch fraudulent leads before they move downstream
Add trusted services to your LeadConduit flow in minutes, or talk with our team about the right add-on for your workflow.