Create Deployment
Create a new deployment that connects an agent to a phone number for inbound calls.
The deployment is created in active status and immediately begins accepting calls. Optionally configure an inbound_config schedule to restrict calls to specific hours and days.
Overview
A deployment makes your agent reachable on a phone number for inbound calls. When someone dials the number, the system routes the call to the agent version you configured. Think of it as: agent + phone number + schedule = deployment.What happens when a call comes in?
- A user dials the phone number attached to your deployment
- The system checks if the deployment is
activeand within its allowed schedule - If the caller’s phone number matches a user in an uploaded cohort, the agent receives their personalized variables (name, balance, etc.)
- The agent handles the conversation using the version you deployed
paused or outside the allowed schedule, the call is not answered.
Key concepts
Connection config
A connection is your telephony provider setup. You need at least one connection with a phone number to create a deployment.Inbound config (optional schedule)
By default, a deployment accepts calls 24/7. Useinbound_config to restrict it to business hours:
Deployment status
| Status | Meaning |
|---|---|
active | Accepting inbound calls |
paused | Not accepting calls — use this during maintenance or agent updates |
active status. Use the Update Status endpoint to pause or resume.
Typical flow
- Create a deployment — attach your agent to a phone number
- Upload a cohort (optional) — provide user context so the agent can personalize conversations
- Deployment is live — calls are routed to your agent immediately
- Update as needed — change agent version, schedule, or pause/resume
Example request
Key fields
| Field | Notes |
|---|---|
name | Max 50 characters. Alphanumeric, hyphens, underscores, and spaces. |
app_id | The agent to handle inbound calls |
app_version | Which version of the agent to use |
connection_configs | At least one telephony connection with phone numbers |
inbound_config | Optional. If omitted, the deployment accepts calls 24/7. |
End-to-end flow
-
Create the deployment —
POST /deploymentsReturnsdeployment_idwithstatus: active. -
(Optional) Upload a cohort —
POST /deployments/{id}/cohorts/uploadProvides user-specific variables for personalization. - Share the phone number with your users — calls are now routed to the agent.
-
Manage as needed:
- Pause:
PUT /deployments/{id}/statuswith{"action": "pause"} - Update agent version:
PATCH /deployments/{id}with{"app_version": 4} - Delete:
DELETE /deployments/{id}
- Pause:
Next: Upload a Cohort
Authorizations
Body
Request body for creating a new deployment.
Deployment name. Alphanumeric, hyphens, underscores and spaces allowed. Max 50 characters.
50^[\w\- ]{1,50}$"Customer Support Line"
ID of the agent
"my-support-agent"
Version of the agent to deploy
3
Telephony connection configurations with phone numbers
1Optional deployment description. Max 150 characters.
150Optional inbound call schedule configuration
{
"start_time": "09:00",
"end_time": "18:00",
"allowed_days": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"timezone": "Asia/Kolkata"
}Response
Successful Response
Full deployment details including agent configuration, inbound settings, and status.
Unique identifier for the deployment
"dep-a1b2c3d4"
ID of the agent
"my-support-agent"
Version of the agent
3
Telephony connection configurations
Direction of calls (inbound, outbound, or both)
inbound, outbound, inbound_outbound User who created this deployment
"user@company.com"
Timestamp when created (ISO 8601)
"2026-03-01T10:00:00Z"
Timestamp when last updated (ISO 8601)
"2026-03-15T14:30:00Z"
Name of the deployment
Current status of the deployment
active, paused Optional description
Inbound call schedule configuration
{
"start_time": "09:00",
"end_time": "18:00",
"allowed_days": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"timezone": "Asia/Kolkata"
}User who last updated this deployment