Siptel SMS
Category: Siptel SMS
Description: This module extends system functionalities by enabling the sending of SMS messages to mobile numbers. It can be integrated into attention flows or used as a standalone action in automated responses.
Functionality: Sends SMS messages through Siptel, integrating with attention flows to automate notifications, confirmations, or personalized alerts.
Prerequisites
- Active Siptel account: A valid account with the Siptel provider is required, with permissions enabled for SMS delivery.
- Service access key (API Key): Must be obtained from the Siptel admin portal and loaded into the module to authenticate message delivery.
- Authorized sender number: Must be registered and validated by Siptel. The number should be entered in international format, without the "+" sign (e.g., 569XXXXXXXX).
- Registered campaign (optional): If using messages linked to campaigns, a campaign must be configured in the system with a valid SMS template.
Implementation
Important
To send a single message, define its content in the respective field. If you want to send SMS messages as part of a campaign, use a campaign that contains a valid SMS template.
Service Access Key: A text field used to enter the key associated with the Siptel account. This key allows Lynn to authenticate and use the extension module to send SMS messages.
SMS Sender Number: A string field where you enter the phone number from which the SMS will be sent. This number must be authorized by Siptel and must include the country code without the “+” sign.
The value can be static or dynamic, depending on whether it is sourced from a flow entity.
Message Content: A string field used to define the text of the SMS. It can contain static content or include flow variables using an entity.
It is recommended to validate message length and readability before sending.
Recipient Number: A string field to enter the phone number to which the SMS will be sent. The number must include the country code without the “+” sign.
The value can be static or dynamic, depending on whether it is sourced from a flow entity.
Start Time for SMS Sending: A text field that defines the start time (HH:MM:SS) of the permitted sending window. SMS messages will not be sent before this time.
End Time for SMS Sending: A string field that sets the latest time (HH:MM:SS) allowed for sending SMS messages. Messages sent after this time will be automatically blocked.
Allow sending on Mondays: A radio button field to enable or disable SMS sending on Mondays.
Allow sending on Tuesdays: A radio button field to enable or disable SMS sending on Tuesdays.
Allow sending on Wednesdays: A radio button field to enable or disable SMS sending on Wednesdays.
Allow sending on Thursdays: A radio button field to enable or disable SMS sending on Thursdays.
Allow sending on Fridays: A radio button field to enable or disable SMS sending on Fridays.
Allow sending on Saturdays: A radio button field to enable or disable SMS sending on Saturdays.
Allow sending on Sundays: A radio button field to enable or disable SMS sending on Sundays.
Campaign Name: A string field where the name of the Siptel campaign to be executed should be entered. This field is used when the extension module is configured specifically to send SMS messages as part of a campaign.
RUT for clients WITHOUT designated IPs: A string field used when Lynn’s IP was not previously registered as an authorized application during user account creation. In such cases, the RUT associated with the account must be provided as a valid identifier.
This value can be defined statically or dynamically, and may be obtained from an entity within the attention flow.
If the maximum number of failed attempts is reached, the action flow will be interrupted and the error description will be passed to the selected intent named: SendSMS_SiptelSMS_ErrorError: A string field that allows you to define the name of the intent to be triggered if the maximum number of failed SMS attempts is reached.
If this condition occurs, the flow is interrupted, and the error description is passed to the specified intent.
- Example: SendSMS_SiptelSMS_ErrorError
Note
The defined intent must be previously configured to receive and handle the error context properly.