> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/inbox-and-leads/campaigns.md).

# Campaigns

Send messages to many contacts at once.

Open **Campaigns**.

Campaigns send a message to a list of contacts, rather than one conversation at a time.

## Before you start

**Check you are allowed to message these people.** Consent requirements differ by market and are strictly enforced. A purchased list is almost never a lawful basis for messaging.

**Complete carrier registration for US recipients.** Unregistered bulk traffic is blocked. See [US carrier registration (10DLC)](/virtual-numbers/us-carrier-registration.md).

## Building a list

Select contacts by filter — by tag, source, campaign, status or any other field.

Build the list from the filter rather than a static export where you can, so it stays current.

## Writing the message

Three things every bulk message needs:

1. **Who you are.** A message from an unknown number with no sender name reads as a scam and gets reported.
2. **Why they are hearing from you.** Reference the thing that connects you.
3. **How to stop.** Opt-out instructions, always.

Keep it to one segment where possible. Messages are billed per segment, and emoji or other non-GSM characters cut the characters per segment substantially.

## Personalisation

Merge fields let you include the contact's name and other details. Check your data first — a message beginning "Hi ," because the name field is empty is worse than no personalisation.

## Sending

Review before sending. Check the recipient count, send a test to yourself, and read it on an actual phone — line breaks and links look different there.

{% hint style="warning" %}
A campaign cannot be recalled once sending starts. Check the recipient list, not just the message.
{% endhint %}

## Timing

Send during reasonable hours in the recipient's time zone. Many jurisdictions restrict when commercial messages may be sent, and a message at 3am generates complaints regardless of legality.

## Tracking

Each campaign reports what was sent, delivered, failed and replied to.

**Delivered is not the same as sent.** Carriers filter silently; a large gap between the two usually means a registration or content problem rather than bad numbers.

Replies land in your **Inbox** as ordinary conversations, so the team answers them normally — and your AI receptionist can answer them too, if the text channel is on.

## Opt-outs

STOP and similar replies suppress the contact automatically and permanently. Suppressed contacts are excluded from future campaigns without you doing anything.

Do not attempt to work around suppression. Beyond the legal exposure, complaints damage your numbers' reputation and hurt delivery of everything else you send.

## What works

* Small, well-targeted lists beat large, vague ones.
* A message referencing a real prior interaction gets answered; a generic blast does not.
* One clear action per message.
* Be ready to handle the replies — a campaign that generates responses nobody answers is worse than not sending it.


---

# 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://docs.limecall.com/inbox-and-leads/campaigns.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.