Authorizations
Body
The name of the campaign. Only used for your own reference.
CREATED
, ACTIVE
, INACTIVE
, PAUSED
, PROCESSED
A list of agent IDs that will be assigned to this campaign, you can query them using GET v1/agents. For inbound and outbound calls and SMS, a random agent will be selected from this list for every conversation. For the chat widget, you can select which Agent will be assigned to conversations.
What medium will be used for the initial contact with a lead.
web_voice
, telephony
, sms
, email
, chatbot
The rules for the campaign.
If true, system will not disposition conversations from this campaign.
Calls made in this campaign will have disposition_level_2 and disposition_level_3 fields as null
.
You can use this to create your own dispositioning system using post call tasks.
A list of categories that LLM can use to categorize the outcome of a call. You can use this to setup Task rules based on the dispositions or track the performance of your agents and campaigns.
Tasks allow you to do some processing before and/or after a call. They can be used to retry a call, send a webhook or send a text message. You can also set conditions to execute the task based on the call count or disposition status.
The minimum amount of time, in seconds, that must elapse before a lead can be recalled in a campaign using Call Now feature.
If provided in the Call Now request, that value takes precedence over the campaign's call_now_threshold_recall_time
.
When provided, Call Now will return a 400 status code if the lead was last called within this time frame.
If omitted, the lead can be recalled immediately.
Allows you to add additional context to the Agent during the ongoing conversation.
You can provide a template string with placeholders for the custom fields.
For example, you can provide template:
User purchased {{product_id}}
Then, during the Conversation you can hit the Call Context API to replace the placeholders with actual values and provide it to the Agent.
"customer has purchased their order."
Advanced setting to override the Eqho default system prompt. In most cases, you should not need to use this.
null
With Answering Machine Detection (AMD), you can determine if a human answering machine or fax machine has picked up an outbound call. If omitted or set to false, AMD will be enabled for this campaign. In that case, when the agent detects the call is answered by a machine, it will hang up. If set to true, your agents will continue the conversation with the answering machine. This is useful for navigating IVR or leaving a voicemail message to the user.
Allows you to add variables to the campaign that can be used by Agents during the conversation.
It is a dictionary where the key is the Mention display_name
and the value is the value you want to use.
You first need to create a Mention with the tag campaign
and the display name you want to use.
{ "postal_code": "1234" }
The mode in which the inbound precall tasks will be executed.
If set to prolonged_ringing
, the precall tasks will be executed while the phone is ringing.
This is ideal for short tasks, as the maximum time to execute the precall tasks is 10 seconds. It's also the default mode.
If set to caller_on_hold
, Eqho will answer the call and play hold music to the caller while the precall tasks are executed.
Once the tasks are executed, the Agent will pick up the call. The maximum time to execute the precall tasks is 5 minutes.
The outbound precall tasks will always be executed before the call is made.
Inbound PreCallTasks can be executed:
- During the ringing phase (prolonged_ringing) - the tasks will be executed while the call is ringing. Agent will pick up the call only after the tasks are completed. Max duration is 10 seconds.
prolonged_ringing
Response
Successful Response
Container for a single campaign record.
CREATED
, ACTIVE
, INACTIVE
, PAUSED
, PROCESSED
Phone numbers used by this campaign. Keyed by phone number. Using dict to ensure uniqueness. Stored also in phone_numbers and inbound_phone_numbers for backwards compatibility.
scheduled for removal
scheduled for removal
Use organization.twilio.a2p_status instead.
rejected
, verified
, pending
, unknown
web_voice
, telephony
, sms
, email
, chatbot
Inbound PreCallTasks can be executed:
- During the ringing phase (prolonged_ringing) - the tasks will be executed while the call is ringing. Agent will pick up the call only after the tasks are completed. Max duration is 10 seconds.
prolonged_ringing
The ID of the lead list associated with this campaign. Used to track and manage inbound leads.
List of LLM Judge configurations