1. Home
  2. turboDial Triggers to Infusionsoft Campaigns
  3. Automation Triggered when Sending and Receiving SMS text messages

Automation Triggered when Sending and Receiving SMS text messages

When turboDial sends or receives an SMS text message it will trigger corresponding API Goals in your Infusionsoft account if you have created them.

The API Goal requires 2 fields to be configured: Integration and Call Name. This image shows an example:

Bad Number SMS API Goal

The following sections explain the different API Goals you can use to trigger automation when an SMS message is sent or received.

Please Read:   After you add or change an API Goal in your Infusionsoft Campaign Builder you must inform turboDial to look for it by clicking the Reset Disabled Goals button in your turboDial Management Account.

Outbound SMS
  • When an SMS is successfully sent. This goal can be used to register that a phone number is known to be capable of receiving SMS messages
    • Integration: turboDialSMS
    • Call Name: GoodNumber

 

  • When an SMS message fails to send because the phone number is not SMS capable. This goal can be used to register that a phone number is not capable of receiving SMS messages
    • Integration: turboDialSMS
    • Call Name: BadNumber

 

  • When an SMS message fails to send for some other reason.
    • Integration: turboDialSMS
    • Call Name: SendFailed
Inbound SMS

The following API Goals will be triggered when an SMS message is received AND the Contact Record is identified
(will not trigger if no Contact Record exists and is not created):

  • General trigger (will trigger for all inbound SMS messages):
    • Integration: turboDialSMS
    • Call Name: Inbound

 

  • Inbound Number specific trigger (will trigger only for SMS messages to the specified inbound number):
    • Integration: turboDialSMS
    • Call Name: Inboundnnnnnnnnnn
      Where nnnnnnnnnn is the Inbound destination phone number the message was sent to. For example, if the message was sent to +19523142318  then the Call Name will be ‘Inbound19523142318’.
      Note the country code field is included in the number, which in this example is ‘1’.

 

  • Forward-to email address specific trigger:
    • Integration: turboDialSMS
    • Call Name: yyyyyyyyyyyyyyyyy
      Where yyyyyyyyyyyyyyyyy is a modified representation of the email address that turboDial forwarded the inbound message to. For example, if the message was forwarded to a turboDial user with the email address of  MaryAnderson@zmail.com  then the Call Name will be ‘maryandersonzmailcom’.
      Note that the email address is modified to be compliant with the Infusionsoft rules for a Call Name: only letters and digits are allowed. Also, the letters are all converted to lower-case.
      You may want to use this API Goal to trigger a sequence that notifies your user via Campaign SMS that they have received an inbound SMS and should check their email.
Campaign SMS
  • Goals can be separated for SMS messages sent manually or automatically. When an SMS is sent manually:
    • Integration: turboDialSMS
    • Call Name: SendManual

 

  • When an SMS is sent Automatically:
    • Integration: turboDialSMS
    • Call Name: SendAuto
Opt Out and Opt In
  • When an SMS Opt Out is received for identified Contact Records.
    These include “STOP”, “STOPALL”, “UNSUBSCRIBE”, “CANCEL”, “END”, “QUIT”. See this page at Twilio for more information.
    Note the turboDial recognizes that list of opt out words regardless of uppercase or lowercase.
    You should use this API Goal to trigger automation that will change the status of the contact such that your campaigns will no longer send them SMS text messages.

    • Integration: turboDialSMS
    • Call Name: OptOut

 

  • When an SMS Opt Back In is received. These include “UNSTOP”, “START”, “YES”.
    • Integration: turboDialSMS
    • Call Name: OptIn

The OptOut case above is useful for taking action in your Infusionsoft account to prevent further attempts to send SMS messages to the contact.

Also see this Twilio page for important additional information.

Acknowledgement of the Request

There is also an API Goal triggered when your Infusionsoft Campaign sends an HTTP POST to turboDial requesting an SMS be sent (Campaign SMS feature, see below). This functionality can be used to discover cases where your HTTP POST request included bad information – such as a missing phone number, and to verify that Infusionsoft successfully issued the HTTP POST. The API Goal is triggered after the initial checks of your HTTP POST pass validation. To have a goal triggered for the case when a HTTP POST to send an SMS is successfully received from your Infusionsoft campaign you can create an API Goal in a Campaign Builder sequence and set these values in it:

  • Integration: turboDialSMS
  • Call Name: SMSsendRequestReceived
Was this article helpful to you? Yes 2 No