Skip to main content

​
How It Works

  1. You configure an endpoint that Coval can call to trigger outbound calls
  2. Coval starts a simulation and sends a request to your trigger endpoint
  3. Your system receives the request and initiates an outbound call to our simulated customer
  4. The simulation runs with realistic customer responses based on your test scenarios
  5. Coval provides detailed transcripts, recordings, and analysis of the interaction

​
Getting Started

​
Prerequisites

Before setting up outbound voice simulations, ensure you have:
  • An endpoint that can receive HTTP POST requests
  • The ability to initiate outbound calls from your phone system
  • API authentication mechanism (recommended)
  • Phone system capable of dialing phone numbers

​
Quick Setup

  1. Prepare Your Trigger Endpoint
    • Create an endpoint that accepts POST requests
    • Implement authentication (API key, bearer token, etc.)
    • Add logic to extract phone number and initiate calls
  2. Configure in Coval
    • Navigate to your simulation settings
    • Select “Outbound Voice” as the simulation type
    • Enter your trigger endpoint URL
    • Configure headers and payload format
    • Test the configuration
  3. Run Your First Simulation
    • Create a test scenario
    • Start the simulation
    • Monitor the call initiation and interaction

​
Configuration Details

​
Trigger Call Endpoint

Purpose: The URL where Coval will send requests to trigger outbound calls from your system. This is a required field. Requirements:
  • Must be a valid HTTP/HTTPS URL
  • Should be publicly accessible or whitelisted for Coval’s IP ranges
  • Must respond within 30 seconds
  • Should return 2xx status codes for successful requests
Example Configuration: 
https://api.yourcompany.com/triggers/voice-simulation

​
Trigger Call Headers

Configure HTTP headers that Coval will include with every trigger request. This typically includes authentication and content type headers. This is a required field. Format: Valid JSON object 
{
  "Content-Type": "application/json",
  "Authorization": "Bearer your-api-key-here",
  "X-Source": "coval-simulation"
}
Common Headers:
  • Authorization: API keys, bearer tokens, or basic auth
  • Content-Type: Usually application/json
  • X-API-Key: Alternative authentication method
  • Custom headers for routing or identification

​
Trigger Call Payload

The base JSON payload that Coval will send to your endpoint. Coval automatically adds the phone number field to this payload. This is a required field. Format: Valid JSON object 
{
  "campaign_id": "test-campaign-001",
  "priority": "high",
}
Note: The phone_number field will be automatically added by Coval.

​
Phone Number Key

Customize the field name used for the phone number in the payload. This allows integration with systems that expect different field names. Default: phone_number Common Alternatives:
  • phoneNumber
  • phone
  • number
  • phoneNumberToCall
  • destination
Example: If your system expects destination, configure this field as destination, and the payload will include: 
{
  "campaign_id": "test-campaign-001",
  "destination": "+1-555-123-4567"
}

​
Advanced Features

​
Multi-Language Support

Coval supports simulations in multiple languages with native voice models:
  • English (Default): Standard US English voice and responses
  • Spanish: Latin American Spanish with appropriate cultural context
  • French: Standard French with proper pronunciation and idioms
  • German: Standard German with accurate grammar and expressions
Configuration: Language is typically configured at the organization level or specified in simulation parameters.

​
Custom Voice Models

Configure specific voice characteristics for your simulations:
  • Voice Provider: Choose from multiple voice synthesis providers
  • Voice Model: Select specific voice models (multilingual, turbo, etc.)
  • Voice ID: Use specific voice identities for consistent testing

​
Simulation Behavior

Control how the simulated customer behaves during calls:
  • Response Style: Natural, conversational interactions with appropriate emotional responses
  • Conversation Flow: Realistic pauses, interruptions, and speaking patterns
  • Scenario Adherence: Follows predefined customer scenarios and objectives
  • Language Consistency: Maintains language and cultural context throughout the call