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

> ## Agent Instructions
> Use Gomobile customer-facing vocabulary.
> Do not infer support for internal, hidden, experimental, or unreleased features.

# Payment reminders

> Send a reminder to a reviewed set of customers.

## Before you begin

Prepare accurate reminder data and an audience reviewed by your team. Include only recipients authorized for the selected channel.

**1. Prepare the audience**

[Create an audience](https://docs.gomobile.ma/quickstarts/create-audience.md) and review its membership and required contact data.

**2. Configure the experience**

Build a Multichannel flow with a short SMS reminder using an available sender ID. Keep sensitive account details out of the message. Use supported conditions and contact updates for the intended path.

**3. Test the workflow**

[Save and test the flow](https://docs.gomobile.ma/getting-started/build-first-flow.md) with contacts and numbers you control. Check each relevant branch and required value.

**4. Review and launch**

Follow [Launch your first campaign](https://docs.gomobile.ma/getting-started/launch-first-campaign.md). Check audience, flow, schedule, calling policy, and channel resources in the summary before launch.

## Expected result and verification

Inspect run activity and contact changes. A sent reminder does not establish that a payment was made.

## Troubleshooting

If work does not begin, check campaign state, schedule, calling hours, audience eligibility, saved flow validity, resources, and credits. For an individual failure, inspect the run path and associated call activity.

See [campaign lifecycle](https://docs.gomobile.ma/product/campaign-lifecycle.md) for enrollment, retries, pause, and stop behavior.


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