Valistry

Twilio completed calls

Each completed phone call in the period. Its id, status, start, end, length and direction. Never phone numbers, recordings or transcripts.

Access

Kind
A read-only key you paste
What to give
Restricted API key
Why that one
A Twilio API key and its secret, which can list calls. This adds no cost. It counts what your AI 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 does not record it. The cost per agent-handled call is at least the cost per completed call; 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/

Valistry calls only these addresses. It blocks any other call and logs every call.

Connecting it

  1. Create a restricted API key. Settings → Account settings → API keys & auth tokens → Create API key. Open ↗
  2. Copy the Account SID. On the console home page, under Account Info. Open ↗

Twilio does not know which calls an agent handled. If your agent writes the call sid into a trace, we can match each call to its exact cost instead of by workflow, and the cost per agent-handled call is then exact too.