> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.conversive.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.conversive.ai/_mcp/server.

# Mobile Number Verification

Improve campaign quality by sending messages only to numbers identified as valid mobile destinations.

## **Why it matters**

Campaign lists can contain invalid numbers or fixed-line numbers that cannot receive mobile messages. Mobile Number Verification checks campaign destinations before sending, helping reduce avoidable delivery failures and unnecessary messaging spend.

## **What the feature does**

* Verifies destination numbers used in supported campaigns before they are sent to the messaging provider.
* Allows valid mobile numbers to continue through the normal campaign send process.
* Skips numbers identified as invalid or fixed-line and records an appropriate reason in message history.
* Reuses previously verified results when available, avoiding unnecessary repeat verification lookups.

## **How it works**

**1. Check existing verification data**

The system first checks whether the destination number has already been verified. If a usable result is available, that result is reused.

**2. Verify new numbers**

If there is no existing verification result, the number is checked using an external number-verification service.

**3. Decide whether to send**

Numbers identified as valid mobile destinations continue to the messaging provider. Invalid or fixed-line numbers are skipped.

**4. Reuse the result**

The verification result is stored so future supported campaign sends can reuse it instead of repeating the external lookup.

## **What customers can expect**

| **Area**                         | **Expected behavior**                                                                                                                                                      |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Campaign delivery**            | Only numbers identified as valid mobile destinations are passed for sending.                                                                                               |
| **Invalid / fixed-line numbers** | The message is not sent to the provider, and the message history records the applicable verification outcome.                                                              |
| **Repeat checks**                | Previously verified results are reused where available, reducing duplicate external verification calls.                                                                    |
| **Verification usage**           | Where verification usage is billable, charges apply to new external verification lookups. Reused internal verification results do not create a new external lookup charge. |
| **One-to-one messaging**         | Number verification is not applied to one-to-one messages or replies under the current scope.                                                                              |

## **Supported scope**

| **Experience**           | **Support**          | **Notes**                                                             |
| ------------------------ | -------------------- | --------------------------------------------------------------------- |
| **Salesforce campaigns** | Supported            | Verification is performed before the message is sent to the provider. |
| **Zoho campaigns**       | Supported            | Applies to supported campaign messages.                               |
| **Conversive campaigns** | Supported            | Applies to supported campaign messages.                               |
| **One-to-one / replies** | Not in current scope | Messages continue through the standard one-to-one send flow.          |

## **Key benefits**

* **Reduce avoidable messaging cost: **Prevent campaign sends to destinations already identified as invalid or fixed-line.
* **Improve campaign quality: **Increase the proportion of campaign traffic sent to usable mobile destinations.
* **Avoid repeated verification cost: **Reuse existing verification results where available.
* **Improve data quality: **Maintain verification outcomes that can be reused across future supported campaigns.

## **Important notes**

* Number verification identifies whether a destination is suitable for supported mobile messaging; it does not guarantee message delivery. Delivery can still depend on carrier, provider, consent, content, account configuration, and other messaging conditions.
* Country and number interpretation use the account configuration and available number context.
* Feature availability, pricing, and billing treatment may depend on the customer plan, account configuration, and commercial agreement.
* The feature may need to be enabled for the customer account before it is applied to campaigns.

|             |                                                                                                                                                                                                                          |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Summary** | Mobile Number Verification adds a quality check before supported campaign sends, helping customers avoid sending to known invalid or non-mobile destinations while reusing prior verification results whenever possible. |