Recording, transcription, and attestation
The artifacts a regulator, a carrier, or a carrier auditor asks for, produced by the network itself rather than reconstructed from your application a month later.
Evidence the network produces
Recording, transcription, signing, and call records run in the network, under the call. They do not depend on your application being up at the moment somebody needs them.
- Capture at the media path. Recording at $0.0025 per minute each way, by account or by sub-account, so a single campaign can be recorded without recording everything.
- Text you can search. Transcription at $0.05 per minute, with redaction of personal and payment data included at no additional charge.
- Signed calls. STIR/SHAKEN signing with the attestation level your traffic earns, and visibility into what downstream carriers saw.
- Records you can bill and defend from. Per-leg CDRs carrying the rate that was applied, exported on your schedule.
Recording and transcription rates
Every line below is published pricing, billed by the minute on the same invoice as your voice traffic.
Capture, text, and analysis
| Service | Rate | Notes |
|---|---|---|
| Call recording | $0.0025 / min | Each way, inbound and outbound. Enabled by account or sub-account, with the retention window you set. |
| Transcription | $0.05 / min | Speech to text against the recording, available in the portal and over the API. |
| Call summary | $0.005 / min | Optional post-call summary of what was discussed and agreed. |
| Sentiment | $0.004 / min | Optional sentiment scoring across the transcript. |
| Redaction | No charge | Personal and payment data redacted on transcripts, included at no additional charge. |
| Encryption | No charge | Encryption at rest on stored media and records, on by default. |
| Voicemail transcription | $0.05 / min | Inbound voicemail transcribed and delivered with the message. |
Rates shown are standard published pricing and may vary by destination, DID type, or account configuration. Volume and platform pricing is quoted. See the full rate card.
Attestation, and answering for the traffic
Signing a call is the easy part. The hard part is being able to answer a carrier who asks, six weeks later, who placed it.
- STIR/SHAKEN signing. Calls are signed on the way out with the attestation level we can vouch for about the number and the customer behind it.
- Downstream visibility. See what carriers on the other side saw, so a labeling problem is investigated with evidence instead of with theories.
- Traceback response. Traceback and complaint requests are answered from CDRs and recordings: which account originated the call, which route carried it, how it was signed, how long it ran.
- Identity kept current. CNAM, E911 records, and 10DLC registration live on the identity layer, so the number a carrier inspects matches the customer behind it.
Call records you can bill and defend from
If you resell these minutes, the record has to be good enough to invoice from and good enough to hand to somebody who is unhappy about a call.
| Per-leg detail | Each leg of the call with its direction, route, carrier, and duration, rather than one summarized total. |
|---|---|
| Applied rate | The rate that was actually applied sits on the record, so a line item is never inferred from a monthly total. |
| Attestation | How the call was signed on the way out, kept with the leg it belongs to. |
| Media reference | A pointer to the recording and the transcript, where those were enabled for the account. |
| Sub-account | The tenant the usage belongs to, so a platform can invoice its own customers from our records. |
Delivered where you work
Exports go to S3, GCS, or an endpoint you name, hourly or daily. The same data is available over the API when you would rather pull than receive.
Sub-account rollups
Usage splits by tenant, so a platform reselling these minutes gets one set of records per customer and can bill from them without a reconciliation project.
Retention and the security program
Controls we operate, described plainly, with no certificate claimed that we do not hold.
Retention you set
Retention windows are configured per account, so media and transcripts live exactly as long as the rules you work under require. A platform can run different windows for different sub-accounts on the same invoice.
Encryption included
Encryption at rest on stored media and records is on by default at no additional charge, and it is not a line item you can accidentally leave switched off.
Access control
Least-privilege access to media and records, with sub-account isolation so one tenant on a platform cannot reach another tenant's calls.
What we will not claim
We do not publish a completed SOC 2 or HIPAA audit, an auditor, or a certificate number. We publish the controls above and the evidence the network produces. If your program needs a specific control evidenced, ask and we will tell you what exists today.
Related: voice connectivity, phone numbers, messaging, call routing, and network status.
FAQs
Questions about recording and compliance
What does recording cost, and where does it live?
Recording is $0.0025 per minute each way, so inbound and outbound legs are billed the same. Turn it on for a whole account or for a single sub-account, set the retention window per account, and access the media from the portal, over the API, or through a signed URL handed to your own front end. Encryption at rest is included at no additional charge.
What is included with transcription?
Transcription is $0.05 per minute against the recording. Post-call summary is $0.005 per minute and sentiment scoring is $0.004 per minute, both optional. Redaction of personal and payment data on transcripts is included at no additional charge. Inbound voicemail transcription is $0.05 per minute and is delivered with the message.
What does STIR/SHAKEN attestation actually do for my traffic?
Calls leaving our network are signed, and the attestation level reflects what we can vouch for about the number and the customer placing the call. Higher attestation is what keeps legitimate traffic from being treated as suspect downstream. You also get visibility into what downstream carriers saw, so a labeling problem can be investigated with evidence rather than guesses.
How do you answer a traceback or a complaint?
From the records the network already produced. A traceback request is answered from CDRs and, where recording was enabled, the recording itself: which account originated the call, which route it took, how it was signed, and how long it lasted. Nothing has to be reconstructed from memory or pulled out of an application database after the fact.
How are CDRs exported?
Per leg, with the route, carrier, direction, duration, and the rate that was applied on the record itself. Exports are delivered to S3, GCS, or an endpoint you name, hourly or daily, and can also be pulled over the API. Sub-account rollups split usage by tenant, which is how platforms invoice their own customers from our records.
Are you SOC 2 or HIPAA certified?
We do not claim a completed audit, an auditor, or a certificate, and you should be wary of a carrier that does so casually. What we publish is the control set and the evidence the network produces: encryption at rest included at no charge, retention windows you set per account, least-privilege access to media and records, sub-account isolation, and per-leg records tied to the call they came from. If your own program needs a specific control evidenced, ask us and we will tell you what exists today rather than what is planned.
Something else? Contact us
Bring us the artifact list.
Tell us what your auditor, your carrier, or your own customers ask for, and we will show you which of it the network already produces.