Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Add leads to the AI working pool, mute or unmute a lead, write settings, send an SMS through the AI number, or batch-create plan tasks.
manage_sales_agent({
action: "add_to_pool" | "mute" | "unmute" | "update_settings" | "ai_number_sms"
| "create_plan_tasks",
lead_ids?, lead_id?, settings?, ai_assistant_id?, confirm_token?
})
action | Required | Notes |
|---|---|---|
mute / unmute | lead_id (singular) | — |
add_to_pool | lead_ids (plural) | Backed by a genuine batch endpoint — accepts large arrays, unlike the 10-record cap that applies elsewhere. Confirms past 10 leads — replay with the returned confirm_token. Optional ai_assistant_id targets a specific Sales Agent instead of the hierarchy-resolved one for every added lead — seat and quota bill to its owner. |
create_plan_tasks | lead_ids (plural) | Same batch endpoint and 10-record confirm threshold as add_to_pool. |
update_settings | settings.id (Sales Agent id, greater than 0) | assistantName/virtualNumber/callTransferType/agentExperience/channel toggles/active hours/lead filters are all optional partial updates. |
ai_number_sms | settings.content (the message text) | The recipient is the agent themself — the caller by default, or the teammate named by optional settings.agentId. Not a lead_id. |
unmute (CHIME-70595) reverses a mute — the response’s success field reports whether
follow-up actually resumed. If success is false and shouldBuyAi is greater than 0, the
team has no available AI seat for this lead rather than a generic failure.