Outbound campaigns

Outbound Campaigns let a Voice Agent call a prepared recipient list. Start with a controlled test recipient, inspect the rendered greeting and prompt, then review the list before launching real calls.

Access and prerequisites

Campaigns is a Private beta feature and must be enabled for your workspace. A Sub-Tenant also needs its parent reseller to be enabled. If the access page is shown, contact the Nuvoca team or your reseller. Feature access and permission to create or start campaigns are separate requirements.

Prepare a configured Voice Agent, an available Caller number (From) and the recipient information required for the call. Use recipients approved for your calling workflow.

1. Set up the campaign

Open Campaigns, create a campaign and complete Setup:

Field	Purpose
Campaign name	Identifies the campaign in your workspace.
Company name	Supplies {my_company} in campaign templates.
Voice Agent	Provides the existing voice, tools and Agent instructions.
Caller number (From)	Number used to originate the calls.
Outbound greeting	First sentence for outbound calls; replaces the Agent's inbound time-based greeting.
Campaign prompt	Adds the campaign mission and recipient context to the Agent's existing system prompt.
Shared values	Values reused for all recipients.
Recipient fields	Declared keys supplied separately for each recipient.

Save Setup before opening Audience, Launch or Run history.

2. Prepare templates

Campaign templates support {agent_name}, {campaign_name}, {my_company} and {recipient_phone_number}, plus your declared shared values and recipient fields. These are campaign variables; do not assume every Agent prompt variable is available here.

For example, declare the recipient field name and use this greeting:

Hello {name}, this is {agent_name}, the digital assistant for {my_company}.
Is this a good time for a short conversation?

Check the preview for each recipient. Undeclared or unresolved variables prevent a valid rendered call. Do not use dummy values to bypass missing information.

3. Build an audience

In Audience, use manual entry, CSV or an API source and save the reviewed audience as a Call List.

• Manual entry: enter E.164 phone numbers and the declared recipient fields.
• CSV: use UTF-8, comma-delimited text, at most 256 KiB, with phone_number and your recipient fields as headers. Header order is flexible.
• API source: configure one GET request, the collection path ($ for a root array), the phone-number path and recipient-field mappings. Optional OAuth, query parameters and sensitive headers are available. Preview fetches the source; it does not place calls.

Review validation errors, duplicates and destination restrictions in the preview. A correctly formatted number is not automatically an allowed destination. Fix rejected rows before launch. A saved list is a snapshot; preview and save fresh source data when recipients change.

4. Review and launch

1. Open the saved Call List and generate its execution preview.
2. Check the recipient count, Agent, caller number, rendered content and displayed price breakdown.
3. Choose Start now or a scheduled date/time with an explicit Schedule timezone.
4. Review the final confirmation and select Start calls now or Schedule calls.

Starting places real calls

Calls run one at a time. Scheduled calls do not start before the selected time. Saving or previewing a campaign does not itself launch a list.

If a start request cannot be confirmed, inspect Launch and the existing Run before starting again. Avoid creating duplicate calls by immediately repeating an uncertain request.

5. Monitor or cancel

Use Launch for current activity and Run history for completed or cancelled Runs and their outcomes. Distinguish completed, no-answer, busy, failed and cancelled recipients.

Cancel Run prevents remaining recipients from being called. A call already starting, ringing or connected may finish normally. Cancellation cannot be resumed; check the results before preparing another Run.

Troubleshooting

Problem	Check
Campaign controls are unavailable	Workspace entitlement and role permissions.
Template preview fails	Declared keys and non-empty recipient values.
Destination rejected	Validation and destination reason shown for that row.
API audience is empty	Collection path, field mappings, authentication and source response.
Preview became stale	Save current changes and generate a new preview.
Scheduled time looks wrong	Selected schedule timezone and displayed date/time.

See Voice configuration, Prompting and Call History for Agent setup and post-call review.