turboDial can trigger an API Goal in a Keap Campaign when an Inbound call has been completed (inbound calls answered by a person or non-turboDial voicemail).
Please Note these special cases:
- An Inbound Call Complete API Goal is not triggered for calls that are answered by Auto-Attendant, Voicemail, or Inbound Queued.
- If the Inbound Call is handled by Find-Me, and the call is forwarded by Find-Me to a non-turboDial number and answered at that number, then there will be no Inbound Call Complete API Goal triggered.
However, if the call is forwarded by Find-Me to a turboDial number and answered there, then the General API Goal will be triggered when the call is complete. And the Inbound Number specific API Goal will be triggered for the number where the call was forwarded; it will not be triggered for the inbound number that was originally called.
The API Goal setup is as follows:
- General trigger:
- Integration: turboDialCall
- Call Name: InboundComplete
- Inbound Number specific trigger:
- Integration: turboDialCall
- Call Name: InboundCompletennnnnnnnnnn
Where nnnnnnnnnnn is the Inbound destination phone number the call arrived at. For example, if the Inbound call arrives at +19523142318 then the Call Name will be ‘InboundComplete19523142318’.
Note the country code field is included in the number, which in this example is ‘1’.
Please Read: After you add or change an API Goal in your Keap Campaign Builder you must inform turboDial to look for it by clicking the Reset Disabled Goals button in your turboDial Management Account.