# SMS Feature

Useful for low internet access users to receive notifications by SMS

* [Why](#id-1.14.x-smsbundle-businessrules-why)
* [Which context](#id-1.14.x-smsbundle-businessrules-whichcontext)
* [Interfaces](#id-1.14.x-smsbundle-businessrules-interfaces)
* [Configurations](#id-1.14.x-smsbundle-businessrules-configurations)
* [Workflows](#id-1.14.x-smsbundle-businessrules-workflows)
* [Special rules](#id-1.14.x-smsbundle-businessrules-specialrules)
  * [Text messages sent](#id-1.14.x-smsbundle-businessrules-textmessagessent)
  * [Text message answer option](#id-1.14.x-smsbundle-businessrules-textmessageansweroption)

## Why <a href="#id-1.14.x-smsbundle-businessrules-why" id="id-1.14.x-smsbundle-businessrules-why"></a>

The implementation of SMS within Second was done to cater to users with little to no internet connection available on their mobile devices and still requiring immediate response times.

SMS is provided through the OHV SMS technology.

Check if OHV supports your country and operators with its SMS technology through the OVH documentation: (<https://www.ovhtelecom.fr/sms/tarifs/> ).

## Which context <a href="#id-1.14.x-smsbundle-businessrules-whichcontext" id="id-1.14.x-smsbundle-businessrules-whichcontext"></a>

Low connection or internet usage users.

## Interfaces <a href="#id-1.14.x-smsbundle-businessrules-interfaces" id="id-1.14.x-smsbundle-businessrules-interfaces"></a>

There is no interface for the SMS bundle, but SMS texts can be changed through the SBO.

{% hint style="info" %} <mark style="color:blue;">Path: SBO> Content > Messages to users</mark>
{% endhint %}

Find more information on how to manage SMS texts in the following documentation: [Messages to users](/v2.0/superadmin/contents/messages-to-users-notifications.md)

## Configurations <a href="#id-1.14.x-smsbundle-businessrules-configurations" id="id-1.14.x-smsbundle-businessrules-configurations"></a>

SBO > Other > Feature > SMS > SMS

## Workflows <a href="#id-1.14.x-smsbundle-businessrules-workflows" id="id-1.14.x-smsbundle-businessrules-workflows"></a>

There are no special workflows for the SMS feature

## Special rules <a href="#id-1.14.x-smsbundle-businessrules-specialrules" id="id-1.14.x-smsbundle-businessrules-specialrules"></a>

### Text messages sent <a href="#id-1.14.x-smsbundle-businessrules-textmessagessent" id="id-1.14.x-smsbundle-businessrules-textmessagessent"></a>

Users have entered their phone numbers receive text messages at the following steps:

* To the asker:
  * Booking request accepted
  * Booking starting soon
  * Booking requested expired
  * Booking requested refused
* To the offeror:
  * New booking request
  * Booking request expiring soon
  * Booking starting soon
  * Booking cancelled by the asker
  * Booking request expired

Each text message is shortened (these are editable in the SuperBackOffice) to limit the character count, as 1 text message is billed every 140 characters. Hence, a 180 character text message is billed 2 text messages, and a 430 character text message is billed 4 text messages.

Every 10 text messages sent is billed 0.70€ (taxes excluded).

Text message prices may vary depending on the destination country.

This feature is valid for, at most, 2 languages in Latin characters.

### Text message answer option <a href="#id-1.14.x-smsbundle-businessrules-textmessageansweroption" id="id-1.14.x-smsbundle-businessrules-textmessageansweroption"></a>

This option allows offerors to accept or refuse a booking request by text message.

When a booking request is issued, offerors receive the user’s back office, a user can verify his phone number with the following process:

1. The user enters his phone number in the dedicated field.
2. The user receives a text message.
3. User replies to the text message with “Yes”.
4. The phone number is flagged as “Verified”.

The user can perform the following actions from his back office:

* Delete his phone number
* Add a new phone number, along with a text message verifying this number

Only one text message is sent per verification. If sending or receiving the message fails, the user will have to delete his phone number and enter it again.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://features.scnd.com/v2.0/core-concepts/sms-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.