AI Voice Outbound

Use this skill when the user asks to create, configure, test, or manage AI voice outbound calling workflows.

Trigger examples include:

• AI voice outbound calling
• voice bot
• outbound task
• call campaign
• dialogue flow agent
• agentic prompt agent
• TTS
• ASR
• upload call list
• Excel contact list
• callback URL
• call transcript callback
• Chinese-language requests about outbound call tasks, voice bots, dialogue agents, call-list uploads, or call-result callbacks.

Core Rules

• Never invent account credentials, tenant IDs, tokens, callback URLs, agent IDs, TTS IDs, ASR IDs, task IDs, line group IDs, or contact list IDs.
• Never start a live outbound task unless the user explicitly confirms the final task summary.
• Treat real phone calls, production task starts, bulk contact uploads, and callback endpoint changes as high-impact actions.
• Use a sandbox, staging, or test environment when the user is exploring or validating setup.
• Validate Excel contact lists before upload.
• If an API call fails, report the user-facing cause and the technical error code if available.
• If API details are missing, continue with the workflow design and ask only for the missing API-specific fields needed for execution.

Capability Map

The skill supports five product capabilities:

1. Account login and authentication.
2. Voice agent creation, using either dialogue flow configuration or agentic prompt configuration.
3. Outbound task creation, associating TTS, ASR, and voice agent IDs.
4. Excel contact list validation and upload, including phone numbers and script variables.
5. Callback configuration for outbound call results, including timing, duration, transcript, and structured call data.

End-To-End Workflow

When the user asks to create a complete outbound campaign:

1. Authenticate or verify the active account.
2. Collect missing business inputs from the user in plain language.
3. Create or select a voice agent/process.
4. Create an outbound task and associate the selected process and outbound line.
5. Validate the Excel contact list.
6. Upload the contact list.
7. Configure the callback URL and callback fields.
8. Summarize the final task configuration.
9. Ask for explicit confirmation before starting live calls.

Natural Language Field Collection

Users usually describe the business goal instead of API fields. Do not ask them to provide raw field names unless they are technical users or the field has no business-friendly name.

When required values are missing, ask concise follow-up questions in business language.

For outbound task creation, collect:

• Task name: ask "What should this outbound task be called?"
• Dialogue process: ask the user to choose from available process names, then map to processCode.
• Outbound line: ask the user to choose from available line names, then map to outboundNumber and outboundNumberId.
• Task type: ask whether calls should be manual or scheduled, then map to taskType.
• Start time: ask only when the task is scheduled/automatic.
• Concurrency: ask "How many calls can run at the same time?", then map to lineAmount.
• Duplicate-phone rule: ask whether duplicate phone numbers are allowed, then map to permitRepeatNum.

If a required value can be discovered from an API, fetch candidates and present the names instead of asking the user for IDs or codes.

Before calling a creation API, summarize the mapped fields and proceed only if the missing required inputs have been resolved.

1. Authentication

Before using protected APIs, authenticate or verify the active session.

Required inputs:

• Environment: production, staging, sandbox, or private deployment.
• Account, tenant, or workspace identifier.
• Login method.
• Credential source or existing access token.

Return:

• Authenticated account identity.
• Tenant or workspace ID.
• Token/session status.
• Expiration time, if available.

Read references/auth.md when implementing or using API-specific authentication.

2. Voice Agent Creation

Support two creation modes:

• flow: create or update a structured dialogue flow.
• agentic_prompt: create or update a prompt-driven voice agent.

Required inputs:

• Agent name.
• Scenario and business goal.
• Creation mode.
• Opening message.
• Required variables to collect.
• Fallback behavior.
• Transfer, retry, or hangup rules.

Return:

• agent_id.
• Agent name.
• Creation mode.
• Status.

Read references/agent.md when mapping user requirements to agent configuration.

3. Outbound Task Creation

Create an outbound task after the agent, TTS, and ASR resources are known.

Required inputs:

• Task name.
• agent_id.
• TTS voice or resource ID.
• ASR model or resource ID.
• Call time window.
• Concurrency or rate limit.
• Retry policy.
• Caller number, line group, or routing resource.

Return:

• task_id.
• Task status.
• Associated resource IDs.

Read references/outbound-task.md for the task schema and lifecycle.

4. Excel Contact List Upload

Validate the contact list before upload.

Required column:

• phone_number

Common optional columns:

• customer_name
• city
• product_name
• due_date
• Custom variables used by the voice agent.

Validation checklist:

• Required columns exist.
• Phone numbers are valid for the expected region.
• Empty rows are ignored or flagged.
• Duplicate numbers are reported.
• Variable column names match the agent's expected variables.
• Row count and upload limits are respected.

Read references/contact-upload.md before validating or uploading contact files.

5. Callback Configuration

Ask the customer for a callback URL before enabling result push.

Recommended callback fields:

• task_id
• call_id
• phone_number
• start_time
• end_time
• duration_seconds
• call_status
• hangup_reason
• transcript
• extracted_variables
• recording_url

Read references/callback.md when configuring or testing callbacks.

Missing API Details

The API contract is intentionally kept in reference files. If the implementation details are not available yet, produce a configuration plan and clearly mark unresolved fields as TBD.

Do not block the entire workflow only because API endpoint paths or request schemas are missing.

API References

For the full SaaS API map, read references/saas-api-overview.md.

For raw extracted text from the source Word document, read references/saas-api-extracted.txt only when the overview and focused reference files do not contain enough detail.