Valistry

Twilio completed calls

The account's completed calls inside the window, a page at a time, and six fields on each: its sid, its status, when it started and ended, how long it lasted and which way it went. Never a phone number, never a recording, never a transcript.

Access

Kind
A read-only key you paste
What to give
Standard API key
Why that one
A Twilio API key and its secret, which can list calls. This source writes no spend: it reports what the spend produced.

What it attributes on its own

From the source
calls completed per day, at the moment each ended · its direction and how long it lasted · a reference to the call itself
Needs a rule or a trace
which calls an agent handled — Twilio records no such thing, so cost per completed call is a floor on the cost per agent-handled one · the workflow, which you tell us · whether the caller got what they came for: a completed call is an answered one, not a resolved one · Twilio's own charge for the minutes, which is telephony rather than AI and stays off the ledger

The addresses it calls

  • https://api.twilio.com/2010-04-01/Accounts/

Only these. A call anywhere else is refused before it leaves, and every call is logged.

Connecting it

  1. Create a standard API key. Account → Keys & Credentials → API keys → Create. Choose the Standard type: it can list calls and cannot manage the account. The secret is shown once. Open ↗
  2. Copy the Account SID. On the console home page. It names the account whose calls are listed; the API key authenticates the request. Open ↗
  3. Name the workflow these count for. The voice workflow your agent runs. Its spend divided by these completions is your cost per completed call.
  4. Paste all three and click Test and connect. Valistry reads the last seven days of completed calls, reports how many, then fills thirty.

Twilio does not know which calls an agent handled. Where your agent writes the call sid into a trace, we can join call to spend exactly instead of by workflow, and the cost per call stops being a floor.