Set up SMS provider

To send a verification or authentication SMS to your users, you must have an SMS provider solution. ReachFive provides Twilio as the default solution. However, you can use any SMS provider solution that you wish.

SMS Prerequisites

  • You must have access to the ReachFive Console.

  • You must have the SMS feature enabled.

  • You must have an SMS provider account.

    Please contact support if you do not see SMS enabled.

Set up Twilio

  1. Log in to your Twilio account.

  2. From your Twilio console dashboard, copy your Account SID, Auth Token, and My Twilio phone number.

    This is typically found on your Project’s home page, under Account Info.

    Expand to see visual.

    account info
ReachFive Console
  1. Go to Settings  SMS  Providers and choose Twilio from the Client type dropdown.

  2. Enter your Twilio Account SID.

  3. Enter your Twilio Auth Token.

  4. Enter the phone number from your Twilio Account that you configured to be your sender.

    By default, Twilio assigns you a number. However, you can configure your own number to be used if so desired.
  5. Type something and click the Send Test SMS button.

    You might have a local test server to see these messages.
  6. Don’t forget to Save your input.

    Expand to see visual.

    console twilio

Set up Custom SMS provider

  1. Go to to Settings  SMS  Providers and choose Custom SMS Provider from from the Client type dropdown.

  2. Enter the endpoint for your custom provider’s SMS API.

    When sent, the REQUEST and payload are set and not customisable.
  3. Enter the HTTP Authorization value (if applicable).

    If the API uses a non-standard authorization header, ensure you tick the Use non-standard name for the Authorization header box and enter the header name.
  4. Select the Send Test SMS button.

  5. Don’t forget to Save your input.

Select the endpoint where you would like ReachFive to send requests

An example request and payload are as follows:


  "phone_number": "+33688888884",
  "template_id": "password_reset", (1)
  "personalizations": {
     "id": "id",
     "external_id": "externalId",
     "given_name": "Max",
     "last_name": "Robertson",
     "gender": "M",
     "sms_code": "smsCode",
     "lang": "fr",
     "has_password": "boolean", (2)
1 The template_id is the sms template. This is the ID for the template found at Settings  SMS  Templates or alternatively for MFA at Settings  MFA  sms templates.
2 The has_password boolean is only included in the payload for the password_reset template.

The has_password boolean gives custom providers the option to let users create a password.

  • true: The user already has a password; the user should be asked to reset the existing password.

  • false: The user does not have a password associated with their account; the user should be asked to create a password.

Custom personalization fields

The following are all of the possible personalizations you can use as part of the payload sent for custom providers.

  • id

  • external_id

  • given_name

  • last_name

  • gender

  • sms_code

  • lang

  • has_password

  • link