> ## 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.

# Customer surveys

> Collect a simple keypad response during a voice call.

## Before you begin

Define one question and clear response choices. Use a small static audience for the first test.

**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 Voice flow that says the question, collects keypad input, and branches on the supported responses. Add a path for missing or unexpected input and save responses with supported contact updates or tags.

**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 runs and contact fields to confirm that each tested response took the intended branch.

## 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.