> 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-voice-agents/how-to-create-your-first-campaign-in-dapta/create-a-campaign.md). # Create a sequence A four-step wizard builds an outbound calling sequence: name it, pick an agent, set the calling schedule, connect a contact source, and map its columns. {% embed url="" %} Sequences let you launch outbound calls at scale using your voice agents. This guide walks you through every step of the sequence creation wizard. The wizard has **four steps**: 1. **Create a new sequence** — name it and pick the agent(s) that will call. 2. **Configure your sequence** — set the schedule, attempts, and calling windows. 3. **Connect Data Source** — choose how contacts enter the sequence. 4. **Property mapping** — match your data columns to Dapta's CRM fields. *** ## Navigate to Sequences **Step 1:** In the left sidebar, open **Sequences** and click **Voice Sequences** to see the sequences list page. The table displays all your sequences with their **Name**, **Start date**, **End date**, **Agent**, **Active** toggle, and **Status**. Use the search bar to find a specific sequence quickly. **Step 2:** Click the **Create Sequence** button in the top-right corner to launch the creation wizard.
*** ## Step 1 — Create a new sequence Set the basic information for your sequence. 1. **Sequence Name** (required) — A clear name that identifies this sequence in your list. 2. **Sequence objective** (optional) — A short description for your own reference. This field does not affect how the agent behaves during calls. 3. **Agent** (required) — Select the voice agent that will handle the calls. The dropdown shows voice agents only, sorted by last update date. 4. **Add agent (A/B testing)** (optional) — Click this to add a second agent and split the calls between them, so you can compare which agent performs better. Click **Save and continue** to move to the next step.
*** ## Step 2 — Configure your sequence Define the schedule and calling rules for your sequence. 1. **Start date** (required) — The date your sequence begins placing calls. Defaults to today. 2. **End Date** (optional) — The date your sequence stops. Leave blank to run indefinitely. 3. **Max attempts per contact** — The total number of call attempts across all days for each contact. 4. **Attempts per day** — How many times Dapta can call the same contact in a single day. 5. **Define call recurrence** — Choose which days calls are placed (for example, **Weekdays**, every day, or a custom selection). 6. **Time zone** (required) — Select the time zone for your sequence using the searchable dropdown. Defaults to your browser's time zone. 7. **Weekly Schedule** — A day-by-day table where you enable each calling day and set its **Start Time** and **End Time**. Each day can have its own independent windows — click **+ Add Time Slot** to add more. As you fill in the schedule, a **Sequence summary** card restates your configuration in plain language so you can sanity-check it before continuing. Click **Save and continue** to move to the next step.
*** ## Step 3 — Connect Data Source Choose how you want to add the contact list for your sequence. Whatever the source, make sure it includes a column for the **contact name** and one for the **phone number**. You have four options: * **Upload file** — Import a **CSV** or **XLSX** file. This is a one-time import. * **Connect Google Sheet** — Keep contacts in sync in real time from a Google Sheet. * **Connect webhook** — Have your own system send contacts to Dapta in real time. * **Connect HubSpot** — Sync contacts from a HubSpot list.
To import a file, select **Upload file**, then click the upload area to choose a **CSV** or **XLSX** from your computer.
*** ## Step 4 — Property mapping Match each column in your file with the corresponding field in Dapta's CRM. This ensures the data is stored correctly and can be used during the sequence. 1. **Phone Number** and **Contact Name** are mapped automatically when Dapta can detect them. Click **Auto-map** to let Dapta match the rest, and verify each mapping is correct. 2. To add a field that is not listed, click **+ Add Property** and map it to a column in your file. 3. Once everything is mapped, click **Finish**.
### Import errors After you finish, Dapta validates the file. If any rows can't be imported (for example, a phone number with an invalid international format), an **Import Errors** summary lists each failing row and the reason. * **Valid rows** are still added to your sequence and saved to your CRM. * Use **Download Error File** to get the list of failed rows, fix them in your file, and re-import later from the **Contact List** tab. {% hint style="info" %} You do not need to fix every error before launching. You can continue with the successfully imported contacts and add the rest later from the **Contact List** tab. {% endhint %}
*** ## What's next? Once your sequence is created, head to the detail page to manage it, monitor call logs, and track performance. {% content-ref url="/pages/oAicUT9kkH5vABsAXEao" %} [Managing your sequence](/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/managing-your-campaign.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dapta.ai/ai-voice-agents/how-to-create-your-first-campaign-in-dapta/create-a-campaign.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.