Usecase: After Sales Follow up Call
Back to Articles
API Reference Javascript IVR

Usecase: After Sales Follow up Call

March 21, 2018 2 min
Aivis Olsteins

Aivis Olsteins

This time I want to share with you another application which were we asked to develop as an add-on on our SAARA platform. A company doing online sales wanted to make an automated call after customer made a purchase, play an automated greeting and asked to value the service they provided. Very simple, however, not something which you can find in a regular PBX or IP PBX.

The solution was, of course, to use our script-driven telephony engine. Initially it was designed with an inbound voice call in mind, i. e. it would be waiting for a call to arrive, and then, based on the number dialed, would trigger a script which would execute tasks according to the script. This case called for a slight modification of the process: the script would be triggered not by inbound call, but by request made to RESTful API endpoint. The request which technically looks like this:

{
"number": "12125551212",
"language": "en"
}

It is send by customers e-commerce server, and contains a number to dial, and language in which the messages should be played.

Once the end party picks up the phone, script finds the appropriate media file, and plays it. After message is played, user is asked to value service, either by pressing a numeric key, or speaking a number between 1 to 9 by voice. The script accepts both options.

How the result is processed further, depends on the preference of customer. In the given scenario, the results were stored in the local database of the script engine, and customer downloaded then manually from the web interface when it was necessary. However, there are many other options:

  1. If the sale volume is not high, it is possible to email the results, and attach voice file to the email;
  2. If real-time information is necessary, the script can send the results to the customers servers by API call;
  3. It is also to possible to decode a voice message by speech recognition engine before sending therefore reducing manual work to almost none. (More about speech recognition in later posts).
  4. Additionally, an SMS can be sent to customer in the case the call could not be completed.

Important is to note, that the outbound call is routed via DTL SAARA regular routing engine, therefore correct authentication and billing is always performed. The customer can set up their preferred carriers for specific countries or networks, and also apply black lists to specific destinations, to block potentially fraudulent calls to premium rate service. And since DTL SAARA is a real-time system, customer credit limits are also always enforced.

 

 

 

 

Share this article

Aivis Olsteins

Aivis Olsteins

An experienced telecommunications professional with expertise in network architecture, cloud communications, and emerging technologies. Passionate about helping businesses leverage modern telecom solutions to drive growth and innovation.

Related Articles

Case Study: Global Communications Company

Case Study: Global Communications Company

A leading communications company used our cloud Voice platform to send 30 million OTP calls per month to their customers, resulting in cost reduction and incrased conversion

Read Article
Bridging The Delay Gap in Conversational AI: The Backpressure Analogy

Bridging The Delay Gap in Conversational AI: The Backpressure Analogy

Conversational AI struggles with the time gap between text generation and speech synthesis. A “backpressure” mechanism, akin to network data flow control, could slow text generation to match speech synthesis speed, improving user interaction.

Read Article
How Voice AI Agents Can Automate Outbound Calls and Unlock New Opportunities for Businesses: A Deeper Dive

How Voice AI Agents Can Automate Outbound Calls and Unlock New Opportunities for Businesses: A Deeper Dive

AI voice agents transform healthcare scheduling by reducing costs, administrative tasks, and no-shows. They offer 24/7 service, multilingual support, proactive reminders, and valuable insights, improving efficiency and patient experiences.

Read Article
How to Fix Your Context: Mitigating and Avoiding Context Failures in LLMs

How to Fix Your Context: Mitigating and Avoiding Context Failures in LLMs

Larger context windows in LLMs cause poisoning, distraction, confusion, and clash. Effective context management (RAG, pruning, quarantine, summarization, tool loadouts, offloading) remains essential for high-quality outputs.

Read Article

SUBSCRIBE TO OUR NEWSLETTER

Stay up to date with the latest news and updates from our telecom experts