V3 SMS Channel Setup
- XCALLY Knowledge (Unlicensed)
- Product Knowledge
On this page |
What’s about
The XCALLY MOTION SMS Channel allows you to define the SMS Accounts that the Agents, belonging to specific SMS Queues, will use to send and receive SMS messages from the XCALLY Motion Omni Desktop Interface.
In the SMS Section, you find:
SMS Queues: where you can configure all the queues dedicated to SMS sessions, which the Agents can belong to (routing mechanisms, teams management, and so on)
SMS Accounts: where you must insert all the information needed to configure the capability to send and receive the messages
SMS Realtime: the monitor real-time board for the SMS activities
SMS Triggers: how to configure the SMS application’s automatic operation
SMS Providers Setup: how to set up predefined providers to send and receive SMS
Requirements
The standard channel working mechanism needs a Motion API to notify a new incoming SMS message that must be saved in the provider configuration.
The Motion instance must have a public address accessible via HTTPS. For security reasons we strongly recommend to use a Reverse Proxy → find out more
How it works
The SMS Channel allows you to receive/send SMS from/to predefined providers, whose list is managed by the XCALLY Integration Support Team and is increasing according to market opportunities.
When the XCALLY Motion SMS Channel receives a request from that provider, it manages it providing a standard interface for all types of providers and the Agent will manage the SMS interaction transparently as well as any other request (mail, chat, and so on).
Until the interaction remains open, any SMS coming from the same telephone number will be received and managed as belonging to the same interaction. When the Agent closes it, any other SMS coming from the same number will open a new interaction.
SMS Sections
Debugging/Troubleshooting
All of the log files for SMS channel events are available at:
/var/log/xcally/openchannel-interactions-combined.yyyy-mm-dd.log
/var/log/xcally/telegram-plugin-plugin.pm2.log