SMS Feature

Useful for low internet access users to receive notifications by SMS

Why

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

Low connection or internet usage users.

Interfaces

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

Path: SBO> Content > Messages to users

Find more information on how to manage SMS texts in the following documentation: Messages to users

Configurations

SBO > Other > Feature > SMS > SMS

Workflows

There are no special workflows for the SMS feature

Special rules

Text messages sent

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

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.

Last updated

Was this helpful?