V3 Cally Square
On this page |
What’s about
Cally Square is a drag-and-drop IVR designer which provides useful tools to create and manage IVR applications for your Asterisk-based telephony system.
It is straightforward to create response applications using the various blocks including the others:
Callback, Dial, Internal Dial
Play audio
Play TTS, Speech Recognition
Get Digit
Options menu
Message Record
SMS/Email Send
DB integration
Concurrent Sessions:
Check your license settings: if you need to increase your maximum number of concurrent IVR sessions, contact us https://xcally.atlassian.net/servicedesk/customer/portal/3
This section covers topics related to:
Managing IVR Projects, where you can create and design an IVR flow on the drag-and-drop HTML5 design area
ODBC, where you can set different Database connections to be used on the IVR structure
Recordings, where you can preview or download audio files recorded in an IVR project
Benefits and use cases
The use of the Cally Square has several benefits:
Intuitive Interface: easily design IVR applications using a user-friendly drag-and-drop web interface;
Versatile Functionality: create Auto-attendants, surveys, callbacks, and more, all within a single platform;
Time-Saving Templates: leverage pre-built examples that can be customized to suit your specific requirements
Enhanced Call Routing: ensure seamless customer experiences by efficiently directing calls to the right queues or agents
Integration with Asterisk System: build IVR solutions optimized for Asterisk-based telephony, ensuring compatibility and performance.
The following are some of the main use cases of designing IVR Scripts:
offer a self-service to allow customers to solve their issues independently without speaking with an agent.
allow you to record customized greetings and messages so that when your customers call your company,
Prioritize calls based on the caller's value. When a customer calls, the caller type can be extracted from a database, and IVR can route VIP customers to the most qualified agent to meet their needs.
connect to a remote DB (ODBC) to extract information
use ASR to gather input and responses through spoken words
perform call recording
In a typical scenario of a company that uses an IVR, the callers are first greeted and asked to choose from a series of prompts (e.g. “Press 1 for Sales”). The callers are routed to the most appropriate queue based on the button they press. If all agents are busy, the caller will wait in a queue or managed differently.
IVR Performance
The purpose of this paragraph is to provide guidance on workload based on different concurrent IVR scenarios on an XCALLY machine.
The tests were performed using 2 IVR campaigns that generate a different number of calls per test, which are managed by a Cally Square project that loops Playback files.
The results may vary depending on the characteristics of the machine on which XCALLY runs.
The below data refers to test done on a machine with 2 vCPUs and 8GB of RAM.
Workload without IVR activities and after machine reboot
CPU: Continuously fluctuating between 15% and 100% (from htop)
RAM: 3.37 GB
Workload with 20 concurrent IVRs
CPU: Continuously fluctuating between 15% and 100% (from htop)
RAM: 4,33 GB
Workload with 50 concurrent IVRs
CPU: Continuously fluctuating between 40% and 100% (from htop)
RAM: 4,4 GB
Workload with 80 concurrent IVRs
CPU: Continuously fluctuating between 42% and 100% (from htop)
RAM: 4,58 GB
Workload with 150 concurrent IVRs
After approximately 100 IVRs, a noticeable slowdown occurs in generating new calls.
CPU: variable between 80% and 100%, with occasional drops to 40-50% (from htop).
RAM: 4,84 GB
Workload with 200 concurrent IVRs
CPU: 100%, with occasional drops to 90% (from htop).
RAM: 4,91 GB
Workload with 250 concurrent IVRs
CPU: 100%, with occasional drops to 90% (from htop)
RAM: 5,13 GB
Workload with 300 concurrent IVRs
CPU: 98-100 % (from htop)
RAM: 5,34 GB