> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SMS

> A one-time code sent by text to the mobile number in your directory. Settings, phone number format, delivery and troubleshooting.

SMS sends a one-time code by text message to the mobile number on file. It proves the employee has the phone your directory says is theirs. It is familiar and fast, and works best when your directory's phone numbers are accurate.

## Before you start

* A connected directory with mobile numbers in **E.164 format**: a plus sign, the country code and the number, with no spaces or punctuation (`+15551234567`).
* Nothing else. TruU sends texts through its own telephony provider; there's no account or sender number for you to set up.

> [!WARNING]
>
> Check coverage before relying on SMS. In real directories, usable mobile coverage has been as low as 10% while email coverage was above 80%, because numbers were missing or stored as `555-123-4567`, with extensions, or in internal formats. Numbers that aren't E.164 fail at send time. Lead with Email, and keep SMS as a fallback until your directory data is fixed.

## Settings

Open **Factors → SMS**.

![SMS settings panel with Phone attributes listing Mobile Phone, Attempts per run, Code length and Code expiry](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/factor-sms-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=af7c85aabfda13a9f8d52a6581d8771e)

| Setting | What it does | Default |
| - | - | - |
| **Phone attributes** | Directory attributes tried in order; the first with a value for the employee is used. Add a fallback attribute if some employees don't have a mobile number. | `mobilePhone` |
| **Attempts per run** | Wrong codes allowed before the factor fails | 2 tries |
| **Code length** | 4, 6 or 8 digits | 6 digits |
| **Code expiry** | 2, 5 or 10 minutes | 5 minutes |

## What the employee sees

Before any code is sent, the employee confirms the last four digits of the number on file. The full number is never shown in the browser, and the check happens on TruU's servers. Then a code arrives by text and the employee enters it. They can request a new code after a 30-second countdown, up to 3 times.

Before a text is sent, the employee agrees to receive it. See [SMS opt-in](https://docs.truu.ai/idv/resources/sms-opt-in.md) for the consent wording and message details.

## Delivery

* Texts come from TruU-managed senders as plain text.
* When sending a link, help desk agents see the mobile number on file so they can confirm it. The employee-facing verification page never shows the number.
* An agent can send a link to a number the caller gives, but that proves less than the number on file. Fix the directory value instead.
* A text the carrier rejects isn't retried automatically; the employee can request a new code.

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| SMS isn't offered to many employees | Numbers are missing or not in E.164 format | Audit `mobilePhone` for values without a leading `+` and country code |
| The code never arrives | The carrier blocks application texts, or the number is a landline | Use Email or another column for these employees |
| Your organization doesn't allow texts to corporate lines | Internal rules or carrier restrictions | Turn SMS off and use Email as the possession factor |
| The code arrived after the link expired | The link was sent before the employee was ready | Send the link when the employee is at their phone |

## Related

* [Email](https://docs.truu.ai/idv/factors/email.md)
* [SMS opt-in](https://docs.truu.ai/idv/resources/sms-opt-in.md)
* [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.