Using the Voice Console

The voice product console (Console) covers the complete workflow of templates, sending, result viewing, and usage statistics — you can place a call without writing any code.

Prerequisites

• The voice product is enabled on your account and you can open the voice product console in Console
• Recommended reading first: Understanding Voice Notifications

Page Overview and Recommended Order

Recommended order: Quick Start (test whitelist + trial call) → Template Management (create and submit templates) → Call Tasks (production sending) → Send Records / Statistics and Pricing (track results and spend).

Quick Start and the Test Whitelist

For first-time onboarding, start with the Quick Start flow:

1. Add a test whitelist: During development and debugging, only numbers on the whitelist can be called (account-level, limit of 20 entries; exceeding it returns 120001)
2. Test send: Select an approved template and place a real call to a whitelisted number — note that test sends are billed the same as production sends; the whitelist is the only number guardrail
3. View the Webhook configuration: The CDR push callback URL is configured centrally on the platform side; the console shows the current configuration

Template Management

Create text (TTS) or audio templates and submit them for review; only approved templates can be used for sending. For programmatic management, see the Template API.

Create a Call Task

The main entry point for production sending, suited to manual operation and large batches of numbers:

• Template: Select an approved template; the call country is determined by the template
• Numbers: Add numbers manually or import in bulk from Excel; a single task supports large batches
• Send mode: Immediate or scheduled (specify a start/end time window, up to 8 days long)
• Playback and redial: Playback count, redial count, and redial interval
• Caller number: Leave unset to use the country default route; accounts with a bound caller number can choose the number to display

Outbound calls start as soon as the task is created; acceptance results and errors such as insufficient balance are reported immediately.

Send Records

View per-call results, with filters for recipient number, call result (success/failure), release code, batch number, country, and time range; the detail view shows call duration and the recording.

Field semantics match the query API; see Viewing Results.

Usage Statistics and Pricing

• Usage statistics: View call volume, successful calls, and amounts by day or month, with filters by country and product line
• Pricing query: Look up the unit price, currency, and billing unit per country; actual billing is subject to your bill

TTS Engines and Audition

A text template can specify a TTS engine (the default engine is used when none is selected); the console supports engine audition — enter text and hear it synthesized on the spot (rate-limited), so you can audition the voice before finalizing the template.

Items That Require Operations

The following items are handled by platform operations; reach out via a support ticket or your sales representative:

• Caller number binding: To display your own number on calls, bind it first
• Country route enablement: Request enablement when you hit 120005「国家无可用路由」(No available route for the country)
• Account and credit: Balance top-up and credit adjustments

FAQ

Why is there no Webhook configuration entry in the console?

The CDR push callback URL is configured centrally on the platform side; the console's Quick Start page shows the current configuration. For the protocol and signature verification, see CDR Status Webhook.

Are test sends billed?

Yes. Test sends go through the real call pipeline and are billed the same as production sends; the whitelist only limits which numbers can be called.

Related Resources

• Placing Calls: Single and Batch
• Viewing Results: Send Records and CDR Push
• FAQ