Effectively interact with your customers by integrating voice and SMS capabilities in your business applications

Send or receive SMS messages from your applications, or start SMS conversations with your customers

Let your applications interact with __humans or machines__ through SMS. Send a  simple reminder message, confirmation a delivery, start a business process via SMS, or start a customer __conversation__. 

Notify or interact with your customers or machines via SMS

__Send__ single or multi-part messages __and track__ their status in real-time. Our SMS API also supports the sending of __binary messages__, especially useful for IoT and connected machinery.

Send SMS

__Reserve keywords__ to receive SMS on our shared short number (8937) __or rent your own short number__ to  protect your brand identity and skip using keywords in your messages.

Receive SMS

Because SMS is a truly __universal messaging standard__ (any device, no mobile internet required), it is __perfectly suited for customer conversations__. [Contact us](https://proximusapi.enco.io/contact-us "contact us") for more information on our  __exclusive conversational SMS offering__ for the Belgian market.

Have an SMS conversation

The SMS API allows you to

__Sign up__ on the free plan and __and start sending__ your messages after verification of your identity. Even if you go for the Premium plan, there are __no setup or fixed fees__. We will help you on your way if needed.

Send your API requests from your application and __start sending messages right away__ from our shared shortcode. Configure your callback URL(s) to __track your messages' delivery status__.

__Register your callback URI__ and receive quick replies on outgoing messages, even on our shared short code. In the Premium plan: __reserve your keyword__ via our API, use a __dedicated short code__ or request a __conversational SMS number__ in combination with [#Interact](https://proximusapi.enco.io/asset/interact/overview "#Interact").

How does it work

With [FlexIO](https://proximusapi.enco.io/asset/flexio/overview "FlexIO"), you can __automate incoming phonecalls__, and send any __information/confirmation__ to your callers via SMS. Build your own __vocal FAQ bot__, and __send links__ to detailed articles on your website.

You can also __deflect incoming voicecalls__ to an SMS conversation: easier and less costly to manage.

Send an SMS after an inbound phone call 

With [#Interact](https://proximusapi.enco.io/asset/interact/overview "#Interact"), unlock __conversational messaging for all__ your customer facing employees on any channel.

Configure an SMS and WhatsApp number __for each of your branches__, and improve your __reachability__.

Start SMS conversations with your employees

Launch SMS campaigns or start an SMS conversation from __any other application__ (Genesys, Chatlayer, Naxai, CRM applications, HR applications, ticketing applications).

Automate SMS conversations or campaigns

More information

SMS from and to your applications

<p>Everyday you have interactions with your customers. In these days of social networks, they can voice their satisfaction or frustration in seconds. How can you stay on top and pulse your customer satisfaction by measure your <a href="https://en.wikipedia.org/wiki/Net_Promoter" target="_blank" rel="noreferrer noopener">Net Promoter Score (NPS)</a>, integrating the measurement right into your business flows ? </p>







<h4 class="wp-block-heading">Triggered from your applications</h4>



<p>Integrating systematic customer surveys is an easy job using our APIs: have you just closed a support ticket, hung up the phone or handled that customer complaint file ? As long as your applications or workflows allow to trigger external calls based on such events, you&#8217;re good to go!</p>



<h4 class="wp-block-heading">Unlimited multilingual surveys</h4>



<p>With our new <strong><a href="https://proximusapi.enco.io/asset/customer-survey/overview?utm_source=blog&amp;utm_medium=web&amp;utm_campaign=encoblog" target="_blank" rel="noreferrer noopener">customer Survey API</a><em>,</em></strong> you can create as many surveys as needed to support the various projects or teams that you want to measure. Each survey can be define to support multiple languages.</p>



<h4 class="wp-block-heading">Normalizing the answers</h4>



<p>Using the Customer Survey API, you can make sure to always send the same question for a defined process, interaction or team. Bad responses are automatically eliminated. We also make it possible to add segmentation (like tags) when sending the survey allowing finer grained reporting without revealing personal customer data (we don’t store any personal data).</p>



<h4 class="wp-block-heading">Get your score</h4>



<p>When using the API to retrieve your result reports, you will get a recap of your request, the NPS score and some response statistics. The <strong>NPS score</strong> is a number between -100 and 100. We also provide the number of <strong>promoters </strong>and <strong>detractors </strong>(absolute values) to give a finer view on the response split. Statistics are provided purely on the response so that you can evaluate the response rate and how well your surveys are performing. </p>



<h4 class="wp-block-heading">Get started in minutes</h4>



<p>Do you want to start measuring your NPS score and overall customer satisfaction now ? Developers can get started in minutes by simply signing up to our Customer Survey API <a href="https://proximusapi.enco.io/asset/customer-survey/price?utm_source=blog&amp;utm_medium=web&amp;utm_campaign=encoblog" target="_blank" rel="noreferrer noopener">Free Plan</a>. Once you get your hands on the APIs and tested your integrations, you can scale up to our <a href="https://proximusapi.enco.io/asset/customer-survey/price?utm_source=blog&amp;utm_medium=web&amp;utm_campaign=encoblog" target="_blank" rel="noreferrer noopener">Premium Plan</a>.</p>



<p>Do you have any question ? Feel free to <a href="https://proximusapi.enco.io/contact-us">reach out</a> to us!</p>



<div class="wp-block-image is-style-default"><figure class="aligncenter is-resized"><a href="https://proximusapi.enco.io/asset/customer-survey/overview?utm_source=blog&amp;utm_medium=web&amp;utm_campaign=encoblog" target="_blank" rel="noopener noreferrer"><img loading="lazy" decoding="async" src="https://cobweb.events/wp-content/uploads/2020/07/try-it-now-a.png" alt="Try the Customer Survey API now" width="354" height="126"/></a></figure></div>

Measure your Net Promoter Score with our Customer Satisfaction API

<p>Among all scarce resources on this planet, meeting rooms should definitely be considered one of them. Even if you have a room reservation system, it can be cumbersome to use whatever web site or application to check if a room is available right now, as you need it (open the laptop, wait for it to connect on the network, open Outlook, check the meeting room status, etc). On top of this, a room may be flagged as booked in a reservation system while being actually free, as the people who booked it changed their plans (hello co-working spaces ?).</p>
<p></p>
<p>At Proximus API Solutions, we started to deploy IoT LoRa sensors in our open space as well as meeting rooms. We collect all sensor data on EnCo, decode LoRa payloads using our <a href="https://proximusapi.enco.io/asset/cloe/overview" target="_blank" rel="noopener noreferrer">CloudEngine</a> then redirect reformatted sensor data to the <a href="https://iotfactory.eu/" target="_blank" rel="noopener noreferrer">IoT Factory</a> platform, from where we can consult a nice historical dashboard.</p>
<p><figure id="attachment_3739" aria-describedby="caption-attachment-3739" style="width: 1024px" class="wp-caption aligncenter"><img loading="lazy" decoding="async" class="wp-image-3739 size-large" src="/wp-content/uploads/2018/05/enco-dashboard-1024x392.jpg" alt="EnCo Dashboard on IoT Factory" width="1024" height="392" srcset="/wp-content/uploads/2018/05/enco-dashboard-1024x392.jpg 1024w, /wp-content/uploads/2018/05/enco-dashboard-600x230.jpg 600w, /wp-content/uploads/2018/05/enco-dashboard-300x115.jpg 300w, /wp-content/uploads/2018/05/enco-dashboard.jpg 1819w" sizes="(max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px" /><figcaption id="caption-attachment-3739" class="wp-caption-text">Part of EnCo dashboards on IoT Factory</figcaption></figure></p>
<h3>Need for a simple query interface</h3>
<p>Although presence in the meeting rooms is reported on our dashboard, getting the meeting&#8217;s room availability still requires to consult the dashboard. This is why, using the CloudEngine, we have built a very simple <a href="https://proximusapi.enco.io/asset/sms/overview" target="_blank" rel="noopener noreferrer">SMS</a> &#8220;bot&#8221; which we can query for room availability while leveraging the data stored in the IoT Factory platform and ability to query it using APIs (web services).</p>
<p><figure id="attachment_3746" aria-describedby="caption-attachment-3746" style="width: 250px" class="wp-caption aligncenter"><img loading="lazy" decoding="async" class="wp-image-3746" src="/wp-content/uploads/2018/05/Screenshot_20180528-171714-498x1024.png" alt="SMS bot for meeting rooms" width="250" height="514" srcset="/wp-content/uploads/2018/05/Screenshot_20180528-171714-498x1024.png 498w, /wp-content/uploads/2018/05/Screenshot_20180528-171714-600x1233.png 600w, /wp-content/uploads/2018/05/Screenshot_20180528-171714-146x300.png 146w, /wp-content/uploads/2018/05/Screenshot_20180528-171714.png 1080w" sizes="(max-width: 250px) 85vw, 250px" /><figcaption id="caption-attachment-3746" class="wp-caption-text">SMS bot for meeting rooms</figcaption></figure></p>
<p>The flow to support this solution is pretty simple and straightforward :</p>
<p><figure id="attachment_3741" aria-describedby="caption-attachment-3741" style="width: 1024px" class="wp-caption aligncenter"><img loading="lazy" decoding="async" class="size-large wp-image-3741" src="/wp-content/uploads/2018/05/Image1-1024x481.png" alt="" width="1024" height="481" srcset="/wp-content/uploads/2018/05/Image1-1024x481.png 1024w, /wp-content/uploads/2018/05/Image1-600x282.png 600w, /wp-content/uploads/2018/05/Image1-300x141.png 300w, /wp-content/uploads/2018/05/Image1.png 1323w" sizes="(max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px" /><figcaption id="caption-attachment-3741" class="wp-caption-text">SMS &#8220;bot&#8221; flow</figcaption></figure></p>
<p>Let&#8217;s see step by step how this has been implemented using CloudEngine&#8217;s scripting capabilities.</p>
<h3>1. Sending SMS to EnCo</h3>
<p>We are sending a SMS with a predefined sentence &#8220;enco meet &lt;meeting room name&gt;&#8221; to the shared short number 8397 associated to the <a href="https://proximusapi.enco.io/asset/sms/overview">Proximus SMS API</a>. Our <a href="https://proximusapi.enco.io/asset/cloe/documentation" target="_blank" rel="noopener noreferrer">CloudEngine script</a> has a single inbound SMS endpoint, which triggers on the keyword &#8220;enco&#8221;. Note that this keyword has been reserved and associated to our EnCo account.</p>
<blockquote><p>GOOD TO KNOW : reserved SMS keywords are a billable feature of the Proximus SMS API. When multiple customers are using the same short shared number (such as our default 8937), using a reserved keyword ensures that all incoming messages starting with this specific keyword will be routed to a particular customer. This feature can be very powerful to support marketing campaigns or specific services that need to be activated or initiated from the mobile terminal over SMS. The next level of personalization and control with SMS is to opt for reserved short or long SMS numbers. If you want to know more about these features, please contact enco@proximus.com</p></blockquote>
<p>In the CloudEngine script which you will find at the bottom of this post :</p>
<ul>
<li>we store the received SMS message in a variable</li>
<li>we use the regular expression module (regex) to parse the message and match the string against a defined template</li>
<li>if the regular expression is not matched, we send back an error message over SMS to the sender address</li>
<li>if the regular expression is matched, we&#8217;ll just extract the meeting room number out of the message</li>
</ul>
<h3>2. Querying IoT Factory for sensor data</h3>
<p>Now that we know which is the meeting room the user wants to query for availability, we&nbsp;need to get the latest measured presence metric from the sensor in that room.&nbsp;We are using a new local &#8220;config store&#8221; capability of the cloudengine to keep a simple table matching meeting rooms to devices.It&#8217;s a simple shortcut, we could have used the ability of IoT platforms such as IoT factory to link devices to other assets such as meeting rooms.</p>
<p>We defined a local function called&nbsp;<em>getroomdata</em>&nbsp;which :</p>
<ul>
<li>gets an authorization token from the IoT Factory platform, extracting the right token variable out of the json structure received from a first API call;</li>
<li>uses the authorization token to query the IoT Factory platform for the device&#8217;s latest data;</li>
<li>parses the received data structure until it gets to the &#8220;presence&#8221; data, and extract it together with the timestamp, which is reformated to something more human readable;</li>
<li>constructs the outgoing SMS message</li>
</ul>
<h3>3. Sending back to the originator</h3>
<p>Last step is simple and consists in sending back the message constructed by our <em>getroomdata</em> function to the original SMS sender.</p>
<h3>Conclusion</h3>
<p>As you will see from the script code below, the length of the whole script mostly comes from performing HTTP queries and json structure parsing on received data. The core logic remains however very simple to implement. Without an external platform like IoT Factory to store our sensor data, we could have used &#8220;key values&#8221; &#8211; another feature of the CloudEngine scripting &#8211; to persist the latest presence sensor data in other cloudengine scripts which decodes our sensor payloads and thereby suppress any dependency to external platforms.</p>
<p>This is however a good exemple showing how easy it can be to add that little extra feature over an IoT setup (devices, transport, data storage, dashboard) which will make your users happier, spending less than 2 hours in script development and without the need to spawn any additional application server or software stack.</p>
<h5>Sample script</h5>
<pre># Basic imports
object json = create("Json");
object array = create("Array");
object debug = create("Debug");
object text = create("Text");
object config = create("Config");

# Global vars
object combinedData = [];

# Main function
function run(object data, object tags, string asset) {
 string smsMessage = data["message"];
 object regex = create("Regex", "ENCO\\s(MEET)\\s(\\S+)", text.upperCase(smsMessage));
 object found = regex.find();
 
 if(!found) {
 object dispatchError = create("SMS", data["senderAddress"], "For meeting room enquiries, send : \"ENCO MEET MEETINGROOM_NAME\" to query a specific meeting room");
 dispatchError.send();
 } else {
 string dump = regex.group(1);
 string meetingroom = regex.group(2);
 
 # Get room matching device from our configuration store
 string smsout = getroomdata(config.get(meetingroom).getString());
 
 # Send outgoing SMS to originating mobile
 object dispatchSMS0 = create("SMS", data["senderAddress"], smsout);
 dispatchSMS0.send();
 }
}

# A user defined function to interact with IoT Factory platform
function getroomdata(string devid) {
 # Get authorization token from ioT Factory platform
 object loginhttp = create("HTTP", "https://report.iotfactory.eu/login", "POST");
 loginhttp.setContentType("application/json");
 loginhttp.setData("{\"email\":\"userlogingoeshere\",\"password\":\"passwordgoeshere\"}");
 object logindata = loginhttp.send();
 object loginjsonparsed = json.parse(logindata["BODY"]);
 string iotftoken = loginjsonparsed.get("_id");
 # Fetch latest device data from IoT Factory platform
 string geturl = "http://report.iotfactory.eu/api/measurements/last/"+devid;
 object httpgetdata = create("HTTP", geturl, "GET");httpgetdata.setContentType("application/json");
 httpgetdata.addHeader("Authorization", "Session "+iotftoken);
 object devdata = httpgetdata.send();
 object devdatajson = devdata["BODY"];
 object devdataparsed = json.parse(devdatajson);
 # Search for latest received sensor data until we get to the presence sensor
 int i=0;
 object DevArrayData;
 while (i&lt;5) {
 DevArrayData = devdataparsed.get("parent").expression("/last/"+i);
 if (DevArrayData.get("type")=="presence"){
 break;
 }
 i++;
 } 
 # format timestamp from payload in local time
 object dtModule = create("DateTime", "HH:mm");
 object dtFormatted = dtModule.format(DevArrayData.get("timestamp"),"CET");
 
 if (DevArrayData.get("value")==0) {
 string outmessage = "This room seems free and available, as seen at "+dtFormatted;
 } else {
 string outmessage = "This room seems busy as seen at "+dtFormatted;
 }
 return outmessage; 
}</pre>

A simple SMS bot to check meeting room availability

These cookies are important to the proper functioning of a site. To improve your experience, we use functional and anonymous analytical cookies. Click Agree and Proceed to accept cookies and go directly to the site.

About Cookies On This Site

All rights reserved. © 2020 Proximus | [Cookie policy](https://www.proximus.be/en/id_cr_cookie/personal/products/orphans/cookie-policy.html "Cookie policy")

This site was created and is managed in accordance with Belgian law.

Proximus API Solutions - powered by ClearMedia NV. Merksemsesteenweg 148, B-2100 Deurne.

BE 0831.425.897

A2P SMS