> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/settings/common-system-settings/sms-settings.md).

# SMS Settings

## Introduction

LUCY supports SMS integration for **smishing campaigns**. SMS messages can be sent using LUCY's default SMS provider or through an account with one of the supported third-party SMS providers.

Before configuring SMS, make sure you have a supported LUCY license, sufficient SMS credits, and an SMS provider selected.

## Requirements

The following prerequisites are required to send SMS messages from LUCY:

* A **Commercial (Pro or Elite)** Lucy license.
* Sufficient balance or credits for SMS delivery.
* An SMS provider configured in Lucy.

## Configure SMS Settings

1. Navigate to **Settings → Common System Settings → SMS Settings**.
2. Select one of the available SMS configuration options.

<figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2FbAAx25klmA19ws3RXFZx%2Fimage.png?alt=media&amp;token=6464c27f-be9a-4e98-8f06-adec2256e265" alt=""><figcaption></figcaption></figure>

#### Default

The **Default** option uses LUCY's integrated third-party SMS provider, **Vonage**.

This option is the simplest way to configure SMS delivery and does not require you to provide your own SMS provider account.

#### Custom

The **Custom** option allows you to connect LUCY to your own account with a supported SMS provider.

The following providers are supported:

* Ducont
* MessageBird
* SMSmode
* Messente
* Vonage

Select the provider you want to use and enter the credentials and configuration details required by that provider.

## Before Running a Smishing Campaign

Smishing campaigns require additional configuration because SMS delivery depends on external providers and mobile carrier networks.

### SMS Provider Whitelisting

Before sending SMS campaign traffic, you must submit the required whitelisting information to your SMS provider.

Whitelisting helps ensure that campaign traffic is permitted by the relevant carrier networks and reduces the risk of delivery issues or restrictions.

Do not schedule a smishing campaign until the required whitelisting process has been completed.

{% hint style="danger" %}
**Allow at least 4 weeks for the whitelisting process.**
{% endhint %}

### Campaign Configuration

Smishing campaigns involve configuration requirements that are specific to SMS delivery and may vary depending on the provider and target environment.

If you are setting up a smishing campaign for the first time, contact your **Solution Engineer** before starting the campaign to confirm that the required configuration is in place.

For instructions on creating a smishing campaign, see [Smishing](/guides/attack-simulations/attack-types/smishing.md).

***

## FAQ

#### How do I check my available balance?

Your available SMS balance depends on the SMS provider and account configuration. Check the configured provider account or the SMS balance displayed in LUCY, if available.

#### What is the cost per SMS?

SMS pricing depends on the configured provider, destination country, carrier, and message type. Contact your SMS provider for current pricing information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.lucysecurity.com/application-reference/settings/common-system-settings/sms-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.