# Launch a Batch Call Configure one call strategy and apply it across a large audience with scheduling and safety controls. Read the Batch Call guide in Hello Alex documentation. Canonical HTML: https://docs.helloalex.ai/article/launch-a-batch-call Path: [Documentation](/) / [Batch Call](/batch-call) ## Overview Batch Call is built for scale, but the value comes from consistency: one validated strategy is applied across many contacts with shared controls for pacing, retries, and suppression. Because configuration is centralized before launch, teams can reach larger audiences while keeping quality, compliance, and spend more predictable. ## How it works - The workflow moves from setup to summary in a fixed order so identity, audience, conversation logic, and operational controls are validated before credits are consumed. This sequencing reduces launch errors that usually happen when high-volume sends are configured too quickly. - Global checks like Do Not Call suppression and pacing limits are applied at execution time, which protects compliance and deliverability while the batch is running. That runtime enforcement is why prep quality directly affects launch outcomes. ## Tips - Good to know: running a small pilot audience first gives you real conversion and failure signals, which is safer than discovering issues mid-launch on thousands of contacts. ## Batch Setup Batch Setup establishes traceability first, so each outbound wave has a clear identity and consistent caller presence. Finalize naming and caller ID, then continue to Audience selection. - A descriptive batch name and a fixed outbound number are set before audience loading, which keeps reporting coherent once results populate Call History. Consistent identity makes troubleshooting and campaign analysis faster later. - **Batch Name:** Shown in Call History and launch summaries — use campaign or date context. - **Outbound Number:** Caller ID for every contact in this batch. - Good to know: naming by campaign wave and date makes side-by-side performance comparisons much easier. ## Audience Audience definition determines who is contacted, so input quality here directly drives deliverability and compliance outcomes. Confirm resolved contact count, then configure Call Goal for shared messaging. - You can import CSV, CRM data, or saved audiences, and the preview step confirms effective row counts before launch. Early validation catches formatting and suppression issues before they become failed calls at scale. - **phone_number:** Required column for CSV imports. - **Do Not Call:** Registry numbers are skipped automatically on launch. - Good to know: a 10-20 contact pilot segment is often enough to validate data shape and call behavior before full rollout. ## Call Goal Call Goal standardizes what every contact hears, which is why pathway and voice alignment should be finalized before pacing is tuned. Lock conversation behavior, then decide whether Conversation Memory should be enabled. - A published pathway defines conversation flow for the full batch, while selected voice and opening line control delivery tone. Consistency at this stage ensures outcome differences reflect audience factors instead of script drift. - **Pathway:** Conversation flow for each outbound call. - **Selected Voice:** AI voice used across the batch. - **Opening Line:** First line Alex speaks when the callee answers. - Good to know: previewing voice samples before launch helps avoid tone mismatch that can reduce engagement rates. ## Conversation Memory Conversation Memory is optional context reuse, and it matters when follow-up continuity should influence how Alex speaks to repeat contacts. Choose memory behavior, then apply Call Settings to control execution boundaries. - When enabled, memory reads and writes against the selected store per contact number, allowing return calls to reference prior interactions. When disabled, each call starts fresh, which is better for cold outreach or strict script control. - **Memory store:** Which saved memory bucket to read and write. - **Use memory:** When off, each call starts with no prior context. - Good to know: memory improves recall workflows but can introduce unwanted context in prospecting campaigns, so choose based on outreach intent. ## Call Settings Call Settings defines operational guardrails for every dial, which directly affects cost, compliance posture, and automation reliability. Review guardrails, then move to Launch Controls for schedule and pacing. - Duration, voicemail behavior, and audio preferences are enforced across the whole batch once launch begins. Shared controls reduce variance and keep post-call processing consistent. - **Duration cap:** Maximum minutes per call before auto-end. - **Voicemail:** Whether Alex leaves a message when calls go to voicemail. - Good to know: noise cleanup is especially useful for mobile-heavy audiences where environmental audio can degrade transcript quality. ## Launch Controls Launch Controls manages timing and throughput, because send velocity and retry rules determine both carrier behavior and contact experience. Set schedule and pacing, then confirm everything in Launch Summary. - You choose immediate or scheduled execution, then set pacing and retry policy to shape dispatch behavior. Conservative pacing on new numbers usually improves trust with carriers before volume increases. - **Schedule:** Immediate launch or future date/time. - **Pacing:** Concurrent calls dispatched per minute. - Good to know: gradual pacing ramps make it easier to detect deliverability issues early without risking the entire wave. ## Launch Summary Launch Summary is a final risk check before spend, so the effective configuration is reviewed in one place before dispatch starts. Launch the batch only after summary totals and behavior flags match your intent. - The summary combines setup, audience, and behavior selections, including custom overrides versus defaults. This consolidated view helps catch expensive mismatches before credits are consumed. - **Custom vs Default:** Badges show which values you changed from defaults. - Good to know: matching summary recipient totals against your source audience is a quick way to detect import or filtering drift. ## Next step Assemble a pilot batch, verify outcomes, then increase audience size once results are stable. ## Related documentation - [More Batch Call guides](/batch-call)