> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-text-agents/campaigns/call-fallback.md).

# Call fallback

Configure an automatic voice follow-up for unanswered WhatsApp outreach and understand manual retry risks.

Call fallback is an optional voice follow-up for a Sequence recipient who has not replied after the WhatsApp template is sent. It is not a retry of the WhatsApp message, and the delay is measured from sending, not a guaranteed delivery/read event.

## Configure it

1. Open the sequence's **Settings** and enable **Call contacts who don't reply**.
2. Choose a wait of **1–24 hours**.
3. Select the **Voice agent** that should call. If the list fails to load and the form offers an ID field, enter the correct agent ID only after verifying it.
4. Optionally map the voice agent's variables to contact columns. Missing values are sent as empty text, so make the voice prompt safe for missing data.
5. Click **Save changes** and verify the saved configuration.

Use a voice agent ready for the intended recipients and a calling workflow your business is authorized to use.

## Automatic call behavior

After the delay, Dapta checks whether the contact has already replied. If so, the fallback is not needed. Automatic calls respect the sequence's allowed time windows and end date; a delay ending outside a window does not authorize an out-of-hours call.

The automatic fallback is a separate attempt from any later operator-triggered retry. Do not interpret “one automatic fallback” as a guarantee that a contact can never receive another call.

## Read the result

Open **Conversations** and inspect the call-fallback column separately from WhatsApp delivery.

| Display        | Interpretation                                                                               |
| -------------- | -------------------------------------------------------------------------------------------- |
| Scheduled      | Waiting for eligibility/time.                                                                |
| Calling…       | Dispatch is in progress.                                                                     |
| Call made      | The call request was accepted; this label alone does not prove a completed or answered call. |
| Answered       | A resolved/answered outcome; not eligible for another fallback retry.                        |
| Not called     | The eligibility checks prevented the call; inspect the reason.                               |
| Could not call | Review the failure before considering a retry.                                               |
| —              | No fallback result for this recipient.                                                       |

## Retry manually only after reviewing the recipient

{% hint style="warning" %}
**Retry can call immediately, outside the sequence's sending window and after its end date.** Manual retry skips the configured delay and schedule/end-date guards. Check local time, consent, and whether another call is appropriate before confirming.
{% endhint %}

1. Review the recipient's reply and call history.
2. Select **Retry** for the fallback and read the confirmation.
3. Confirm only when an immediate call is appropriate. The WhatsApp template is **not resent**.
4. Refresh the result; do not click repeatedly while dispatch is in progress.

The service still checks whether the contact has already replied. It rejects retries when fallback is disabled, already in progress, or successfully resolved; a missing fallback cannot be retried. If the interface reports a conflict, inspect the latest state instead of trying to override it.

*Source review: September 17, 2026.*

{% content-ref url="/pages/JUWraCSo2Y3Ewbn3zsPX" %}
[Message Logic & Limits](/ai-text-agents/campaigns/message-logic-and-limits.md)
{% endcontent-ref %}


---

# 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.dapta.ai/ai-text-agents/campaigns/call-fallback.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.