Monitor call answer rates, SIP outcomes, and voice spend.

Track how inbound and outbound calls perform across your phone numbers, SIP trunks, and destination countries without stitching together carrier logs and PBX traces. Spot answer-rate drops, ring delays, and short calls in the Bird dashboard, diagnose whether a failed attempt was refused by an account check or a remote carrier, and audit billable talk time and per-leg costs.

Get StartedContact Sales

Answer rates and call quality

Separate network connection rates from completed customer tasks.

Track answer-seizure ratio (ASR), average call duration, median and 95th-percentile ring delay, and audio quality scores across your workspace. Because a connected phone line or voicemail pickup is different from a finished customer task, you can pair network metrics with call sequence exit outcomes and application events to see whether callers actually booked an appointment or reached your team.

Break down traffic by direction, trunk, and country

Blended totals can hide a drop on a single phone line or carrier route. Filter metrics by inbound or outbound direction, Bird phone number, SIP trunk, and destination country to spot whether an answer-rate dip comes from a specific region or a change in traffic mix.

Compare ringing time, billable talk time, and short calls

Bird tracks total leg duration from setup to hangup separately from billable answered time. Monitor the share of answered legs ending under 30 seconds alongside audio quality scores and ring delay to catch routes that connect without carrying clear two-way audio.

Per-leg call diagnostics

Diagnose why a call failed at the carrier, PBX, or account check.

Drill straight from a spike in failed or rejected calls to the affected leg records. Each record captures start, answer, and end timestamps, the inbound route or SIP trunk, the final SIP response code, and the specific platform rejection reason so you know immediately whether a call hit a busy line, an unallocated number, an unverified caller ID, or a daily spend cap.

  1. 01

    Inspect correlated call legs, timelines, and recordings

    When an incoming call is forwarded or bridged to another number, Bird links the arriving leg and the outbound leg under a shared call ID. Inspect each leg’s outcome, ringing time, and attached audio recordings or transcripts to confirm whether the final destination actually picked up.

  2. 02

    Stream real-time webhooks and query stats from the CLI

    Subscribe to signed webhook events as calls start, answer, and end so your application can update ticket or dialer state without polling. Query aggregate breakdowns by country, trunk, number, or SIP response code from the Bird CLI and MCP server, or fetch and export leg records over the API and CSV.

Voice spend and cost attribution

Audit per-country calling spend and cost per completed outcome.

See the rated cost on each completed call leg in your wallet currency alongside billable talk duration and destination country rates. When a workflow spans multiple legs, such as an inbound call forwarded to an external support line, you can review both legs together and export filtered records to CSV for finance reconciliation.

Tie call and session IDs to bookings and resolved tickets

Store the Bird call or session ID alongside the booking, support ticket, or callback record in your own database. Joining rated call legs to confirmed application outcomes lets you measure voice spend per resolved issue or confirmed appointment across countries and campaigns.

Distinguish unrated active calls from zero-cost attempts

Unanswered and refused attempts carry zero billable talk time, while an active or newly ended leg displays an empty cost until post-call rating finishes. Keeping pending rating states distinct from zero-cost calls prevents undercounted spend in your automated reporting.

Questions about voice analytics

Does answered mean a successful customer outcome?
No. It means the call connected. Join a confirmed business event, such as a booking or resolved case, to evaluate task success.
Why is cost empty on an active call?
An active call has not completed rating. Read the final record after the call and rating lifecycle finish; a missing value is not a zero price.
How should I handle duplicate webhook delivery?
Verify the signature, deduplicate using the webhook identity and tolerate out-of-order arrival. Reconcile the final result against the call record.
Can I compare incoming and outgoing calls?
Review direction and the report’s filters explicitly. The mix of traffic and the applicable rated components may differ.
How do I measure cost per completed task?
Join rated calls and their sessions to confirmed outcomes in your application. Include every relevant call leg and use a consistent period and definition of completion.

Connect the rest of your voice stack

Call log and diagnostics guide Filter leg records, inspect SIP response codes and rejection reasons, and export call history to CSV.

Recordings and transcripts Capture per-leg call audio and speaker transcripts around specific steps with 30-day storage retention.

Inbound routing Route each Bird phone number to a SIP trunk, an IVR call sequence, or a verified forwarding number.

Voice pricing Check published per-minute rates, billing increments, and plan limits by destination country and call direction.

Scale without
losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

WorkspacesTeam rolesAPI authentication
Explore Enterprise

Start with Voice.
Build across channels with Bird.

Get StartedContact Sales

Start building with Bird in minutes.

Get StartedContact Sales