Step 3 – Confirm
Step 3 lets you review the expected cost of sending messages and the number of contacts added; set the ‘send route’ or the phone number that will send the messages; and schedule when the engagement goes live.
Once reviewed and confirmed that everything is set up as you wanted, click Launch. To edit and launch the engagement at a later time, click Save as draft.
This section is where you can set the “send route” or assign the phone number to use for sending messages. There are three routes:
- engageSPARK Network
The default network used for sending outbound messages via high-quality routes. Remember to use a Caller ID or Sender ID when using the engageSPARK network so users will see your phone number or sender name.
- Local Phone Number
The virtual phone number purchased via the platform is used for sending the messages.
- Android Relay
The messages will be sent through the mobile network or telco of the primary SIM card and the Caller ID cannot be changed.
When using a Local Phone Number or Android Relay as the Send Route, note the following:
- The Local Phone Number or Android Relay is used for two-way engagements (e.g. SMS Poll, AutoReply and Webhook). To use your local phone number as the Send route, click Change beside engageSPARK Network. Choose the local phone number or Android relay that will send the messages to your contacts. Then click Save.
- When creating multiple two-way SMS engagements, a Keyword Prefix can be used. This helps engageSPARK differentiate which incoming messages belong to which particular engagement for reporting purposes.
- For Voice engagements, you cannot use the same phone number to receive calls (where the recipient calls and listens directly to the message) and for people to subscribe via a Missed Call. The reason is that our system will not know when someone calls whether to “answer” the call or not.
- Caller ID cannot be changed when using the Android Phone or Local Phone Number.
Caller ID or Sender ID
- The rules vary depending on the country and can also differ per telco, and they often change, so please test for your own engagement.
- In many countries, a Caller ID can be set as follows: alpha characters when sending SMS, numeric characters when sending Voice.
- Only registered Sender IDs of your organization will work with the SMS engagements. Please contact support if you want to register a Sender ID. Learn more »
- By default, engagements start running immediately after you click Launch.
- To schedule the engagement to start at a future time, change to “Schedule for Later” from the dropdown.
- If the triggerer’s personalized data is inserted into the SMS, the Start Time will default to “when triggered by another engagement“, which means the system will only send this SMS message if triggered by a user during an IVR call.
- The engagement will be completed when all messages are sent or when you stop the engagement.
- To set a specific End Time, choose “set a date and time” from the dropdown. The default timezone is based on your location, but you can change it by selecting the country timezone.
- Note: Engagements with Missed Call/SMS Opt-in and SMS trigger messages have a default End Time of “never (only when I stop this engagement)“
Save as draft
Below the launch button, click Save as draft to save the changes made and you’ll be directed to the Engagements dashboard. You can continue working on the draft later on by clicking its corresponding 🖉 Edit button on the Engagements list.
Click Launch when you are ready to set the engagement live. If any issues are detected, you’ll see an error status message and tips on what to do. Once you’re directed to the Engagements dashboard, it means the engagement was successfully launched.
Analyze the results of your engagements on the Reports page. The reports are real-time to quickly get actionable insights. From the Engagements dashboard, find the engagement whose report you want to view from the list. Go to Actions column and click the Reports button.
Have questions or need a little extra help? Get in touch via live chat or drop us a message here: