Call queues

Put contacts on a call queue. If AI calling is active, eligible contacts will receive real outbound calls during the queue's calling hours, using this account's voice and AI credits. Otherwise the team can call them in a dialer. Anyone already on the queue is moved back to pending instead of being added twice.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.add_contacts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_ids": [
      "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
    ]
  }'

Over MCP the same operation is the tool call_queues_add_contacts at https://app.chirply.io/api/mcp, same bearer token, same input.

Take everybody off a call queue, keeping the queue itself. The record of who was on it and what happened on those calls is destroyed and cannot be recovered; the contacts are untouched.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.clear \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_clear at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a call queue — a named list of people for the team to phone through the power dialer. Creating one calls nobody; it only makes the list.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example"
  }'

Over MCP the same operation is the tool call_queues_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete a call queue and everyone's place in it. The contacts and their call history are untouched, but the record of who still needed calling is gone and cannot be recovered.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one call queue by id, with its live counts of who is still to call, who has been called, and who was skipped; its rule for retrying unanswered numbers (`retry`); and how many people are waiting for a retry that isn't due yet (`waiting_for_retry`).

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List every call queue in the account with how many people are still waiting to be called, how many have been called, and how many were skipped, plus each queue's rule for retrying unanswered numbers (`retry`).

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool call_queues_list at https://app.chirply.io/api/mcp, same bearer token, same input.

List the people on a call queue in the order they will be dialled, with each one's outcome and note if they have already been called, and where they stand on retries (`retry`): calls used, retries allowed, the last outcome, and — for someone waiting for their next try — when it comes due.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.list_entries \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_list_entries at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the next people waiting on a call queue, in the order they will be dialled, with their phone numbers. This applies the queue's own power-dialer settings the same way pressing “Start calling” does — outside the queue's calling hours it reports nobody, and people over the attempt limit, on a skipped line type, or without a phone number are left out and counted with the reason. People waiting for a retry that isn't due yet are not listed; `waiting_for_retry` counts them and says when the soonest comes due. So the answer matches who a rep's dialer would actually ring, not just who is on the list (call_queues.list_entries shows the raw list). Reads only — it starts no calls.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.next \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_next at https://app.chirply.io/api/mcp, same bearer token, same input.

Mark someone on a call queue as called (with the outcome that was chosen) or skipped, so they stop coming up as still-to-call. If the queue retries unanswered numbers and the outcome (or the call's own final status) is one it retries, the person instead stays on the queue and comes back at their next try time, until the retry limit. This only writes the queue entry — it sends nothing to anybody and spends no money. KNOWN GAP: unlike the power dialer in the app, this does NOT fire the 'called from a queue' automation trigger and does NOT stamp the queue onto the call log, so an account whose follow-up texts hang off that trigger will not send them for an outcome recorded this way.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.record_outcome \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "entry_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "pending"
  }'

Over MCP the same operation is the tool call_queues_record_outcome at https://app.chirply.io/api/mcp, same bearer token, same input.

Take contacts off a call queue so nobody rings them. Their call history and any outcome already recorded stay on the contact; only their place in this queue is removed.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.remove_contacts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_ids": [
      "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
    ]
  }'

Over MCP the same operation is the tool call_queues_remove_contacts at https://app.chirply.io/api/mcp, same bearer token, same input.

Put people who have already been called or skipped back to still-to-call, so the queue can be worked through again. Their previous outcome and notes are kept on record.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.reset \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_reset at https://app.chirply.io/api/mcp, same bearer token, same input.

Configure an AI agent to automatically call pending people on one call queue during selected local hours. When enabled, real outbound calls use this account's Twilio and AI credits. Voicemail, no-answer, busy and failed calls wait for the chosen retry interval until the per-person attempt limit; live answers complete the queue entry. Disabling stops new calls but lets calls already in progress finish.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.set_ai_caller \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true,
    "agent_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "from_number_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "timezone": "example",
    "days": [
      "Mon"
    ],
    "start": "example",
    "end": "example",
    "retry_minutes": 15,
    "max_attempts": 1,
    "calls_per_minute": 1,
    "record": true
  }'

Over MCP the same operation is the tool call_queues_set_ai_caller at https://app.chirply.io/api/mcp, same bearer token, same input.

Set a call queue's rule for retrying unanswered numbers. When it is on and a call from the queue — from the power dialer or the predictive dialer — ends with one of the chosen outcomes, the person is put back in the queue automatically, becomes callable again the chosen number of hours later (moved to the next opening if that falls outside the queue's calling hours), and is retried up to the chosen number of times; reaching them, recording any other outcome, or removing them from the queue stops it. Every attempt stays on the contact's call history labelled with which retry it was. Saving calls nobody by itself, but with the predictive dialer running it decides that real people's phones ring again, billed to this account's calling. The AI caller keeps its own retry interval (call_queues.set_ai_caller). Turning the rule off leaves people already scheduled waiting until their time; they are then called once more without further retries.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.set_retry_policy \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true
  }'

Over MCP the same operation is the tool call_queues_set_retry_policy at https://app.chirply.io/api/mcp, same bearer token, same input.

Rename a call queue, change its description or colour, attach a call script to it, or take it out of use. Taking a queue out of use removes nobody — it just stops being offered when someone picks a queue.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/call_queues.update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool call_queues_update at https://app.chirply.io/api/mcp, same bearer token, same input.