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.

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

When an SMS message is received and the Contact Record is identified:

  • General trigger:
    • Integration: turboDialSMS
    • Call Name: Inbound
  • Inbound Number specific trigger:
    • 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’.
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.

    • 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.

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 1 No