WEBVTT 00:00:00.000 --> 00:00:02.433 Hi. Welcome to XMPie. 00:00:02.433 --> 00:00:08.633 This video introduces the new SMS or text message feature introduced in Circle version 8 00:00:08.633 --> 00:00:15.233 that provides an easy method of adding mass or bulk SMS messaging to your cross media campaigns. 00:00:15.233 --> 00:00:22.799 XMPie has developed the SMS feature to integrate easily with Vonage (formerly called Nexmo) 00:00:22.800 --> 00:00:26.366 as well as other 3rd party SMS providers. 00:00:26.366 --> 00:00:31.299 XMPie is not reselling the service, you will need to create an account with Vonage. 00:00:31.300 --> 00:00:33.733 You can find their pricing here: 00:00:33.733 --> 00:00:39.366 If you have any problem creating your Vonage account, please contact your XMPie Account Manager 00:00:39.366 --> 00:00:42.999 who can put you in touch with the right person at Vonage. 00:00:43.000 --> 00:00:52.100 If you already have an account with a different SMS provider, that has API access that works by posting JSON to their endpoint URL, 00:00:52.100 --> 00:00:56.066 you should be able to configure Circle to work with them. 00:00:56.066 --> 00:01:04.866 In order to take advantage of the new SMS feature in Circle, you will need to have PersonalEffect version 9.7 or later. 00:01:04.866 --> 00:01:09.499 If you have an earlier version, you will see this warning dialog. 00:01:09.500 --> 00:01:13.200 Let's take a closer look at the SMS feature. 00:01:13.200 --> 00:01:19.000 When you login to Circle, you can configure SMS Providers here under the File menu. 00:01:19.000 --> 00:01:28.033 You can configure multiple SMS providers and define which is the default that will be first selected when you create a new SMS message. 00:01:28.033 --> 00:01:33.799 The setup panel, allows you to enter and test your Vonage API key and password. 00:01:33.800 --> 00:01:38.866 Or, if you are working with a custom SMS provider, you can configure the endpoint URL, 00:01:38.866 --> 00:01:44.432 and the JSON parameters that will be posted to the endpoint when sending the message. 00:01:44.433 --> 00:01:51.166 The format of the JSON can easily be edited to meet the requirements of your custom SMS provider. 00:01:51.166 --> 00:01:54.632 Note that only the Parameters are stored encrypted, 00:01:54.633 --> 00:02:00.766 so any sensitive information like passwords should be in the JSON and not the URL. 00:02:00.766 --> 00:02:05.566 In the Circle Plan tab, you can drag out the new SMS touchpoint. 00:02:05.566 --> 00:02:10.066 Notice that the touchpoint ID now starts with "s". 00:02:10.066 --> 00:02:15.799 In the Build tab, you can use the production icon on the touchpoint to configure the message. 00:02:15.800 --> 00:02:18.466 The sender can be a name or number. 00:02:18.466 --> 00:02:23.699 For example if your SMS provider is using one shared phone number to send from, 00:02:23.700 --> 00:02:32.100 you may want to use a name to identify the sender of the message – perhaps to identify different customers that you run campaigns for. 00:02:32.100 --> 00:02:39.000 Also note that: In this first release, ADORs are not supported in the Sender name or number. 00:02:39.000 --> 00:02:42.566 And, each country has different regulations for the sender. 00:02:42.566 --> 00:02:52.599 For example in USA, you cannot send an SMS from an alphanumeric sender, it has to be a long number, short code or toll-free number. 00:02:52.600 --> 00:02:58.200 The required format for the recipient mobile number is dependent on your SMS provider. 00:02:58.200 --> 00:03:05.966 For Vonage, you should enter the country code and digits only. – No plus, dash or spaces are permitted. 00:03:05.966 --> 00:03:15.499 To help with this, PersonalEffect 9.7 introduced a new function called CleanNumber into uPlan, uCreate Print and uProduce. 00:03:15.500 --> 00:03:21.300 This function is designed to remove any non-digits from your recipient list mobile phone numbers 00:03:21.300 --> 00:03:26.600 and should be used on the mobile phone ADOR object that you use here. 00:03:26.600 --> 00:03:31.400 You can enter the Message text directly here in the production panel. 00:03:31.400 --> 00:03:39.600 The message can include static text and ADOR objects by starting to type the two opening brackets to get the list of ADORs. 00:03:39.600 --> 00:03:50.666 Messages in other languages are supported including European accented characters, Asian CJK characters and right-to-left languages. 00:03:50.666 --> 00:03:58.766 For URLs, it is recommended to use a URL shortening service to reduce the number of characters in your message. 00:03:58.766 --> 00:04:05.599 Notice that the default SMS provider is automatically selected, but you can change it here. 00:04:05.600 --> 00:04:11.700 Mass SMS is the only option. Individual Triggered SMS will come in future. 00:04:11.700 --> 00:04:15.033 Also, Transactional is the only option here. 00:04:15.033 --> 00:04:22.699 A future release will add an option for Promotional SMS that will work in a similar way to the Commercial Email setting. 00:04:22.700 --> 00:04:33.900 The new SMS feature supports sending up to 100,000 messages in one send. Batching and throttling are handled automatically behind the scenes. 00:04:33.900 --> 00:04:41.900 Back in the flow diagram, the SMS touchpoint preview shows the message on a simulated phone handset. 00:04:41.900 --> 00:04:50.466 Right now with the initial feature release, there is no tracking of SMS events, but it will be added in a future release. 00:04:50.466 --> 00:04:57.332 Also in future, the team hopes to add a feature to handle SMS replies and unsubscribes, 00:04:57.333 --> 00:05:01.599 but these features will be further into the future than tracking.