> 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/dapta-mcp/skills/voice-sequences.md).

# Voice Sequences

Ask Claude to read, build and adjust voice sequences: the outbound calling lists that call contacts on their own retry rules and calling windows.

A voice sequence is an outbound calling list. It calls its contacts on its own retry rules and calling windows. Once Dapta is connected, you can ask Claude to read a sequence, trace what happened to one contact, and make changes with a preview you confirm.

{% hint style="warning" %}
Adding contacts to a sequence, or changing its calling rules, can cause real calls to be placed. Claude flags these actions as reaching outside Dapta and always shows you a preview first.
{% endhint %}

## Read a sequence

Ask Claude what a sequence is doing: its state, its contacts, and the attempts made for each one.

**Try saying:**

* "List my voice sequences."
* "How is the March outbound sequence doing?"
* "What happened to the contact with this phone number in that sequence?"

**You get back:** The sequence's state and rules, its contacts, and for a single contact, every call attempt and its result.

**Writes data?** No, read-only.

**Behind the scenes:** `list_sequences`, `get_sequence`, `list_sequence_contacts`, `get_sequence_contact_attempts`.

***

## Create a sequence and load contacts

Ask Claude to create a new sequence, add contacts to it, or remove contacts that should not be called.

**Try saying:**

* "Create a new sequence for my sales agent."
* "Add these 20 contacts to the follow-up sequence."
* "Remove this contact from the sequence."

**You get back:** A preview of what will be created, added or removed. After you confirm, Claude applies it and reports the result.

**Writes data?** Yes, via preview then confirm.

**Behind the scenes:** `preview_create_sequence` and `commit_create_sequence`, `preview_attach_sequence_contacts` and `commit_attach_sequence_contacts`, `preview_remove_sequence_contacts` and `commit_remove_sequence_contacts`.

***

## Adjust the calling rules

Ask Claude to change how a sequence retries and when it is allowed to call.

**Try saying:**

* "Change the retry rules on this sequence to three attempts."
* "Only call between 9 am and 5 pm on weekdays."

**You get back:** A before and after comparison of the rules. Nothing changes until you confirm.

**Writes data?** Yes, via preview then confirm.

**Behind the scenes:** `preview_update_sequence_rules`, `commit_update_sequence_rules`.

***

## Related

{% content-ref url="/pages/3WR4kvMmgQ3fjfMtwy03" %}
[Voice Agents](/dapta-mcp/skills/voice-agents.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/dapta-mcp/skills/voice-sequences.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.