Zadarma call report: extensions, missed calls and costs

Zadarma call report for clients

Teams choose the Zadarma virtual PBX because it is quick to set up: extensions, forwarding, call recording and a callback widget can all be configured in an evening. Reporting on it is harder. Call statistics, billing and the widget live in different parts of the dashboard, so answering “how many calls did we lose and what did we pay for telephony” means opening three pages. Reportkey reads this data through the API and assembles it into one section of a recurring report sent as a link or PDF.

Connecting Zadarma with keys from Settings, API

Access requires a Key and Secret pair generated in the Zadarma dashboard. Every API request is signed with the secret, so the Secret itself is never sent in plain form. In Reportkey the keys are entered once on the integrations page and become a shared connection available in any project; an agency with several Zadarma clients keeps one connection per client. If the keys are revoked, the connection is flagged for re-authorization while project settings stay in place.

Answered and missed cloud PBX calls

PBX statistics return every call with its outcome: answered, busy or no answer. The main block is built from these fields:

• Inbound and outbound calls by day, week or month.
• Answered and missed calls as counts and as the missed share of inbound.
• Talk duration as total minutes and the average answered call length.
• Previous-period comparison for every figure.

A busy signal is a failure from the caller’s point of view too, so the report counts it as missed rather than leaving it between categories.

Calls by extension: who answers and who misses

Each call is tied to an extension, and an extension usually belongs to a specific manager or department. The extension table shows how many calls each one answered, how many were missed and how many minutes were spent talking. Several offices or lines appear in a single table, which replaces the monthly export and spreadsheet sorting.

Telephony costs inside a marketing report

Zadarma billing returns the destination, billed seconds and amount for every paid connection. The report turns that into telephony spend for the period and a split by destination: mobile, landline, long distance. For a company with heavy outbound calling this is a real cost line worth seeing next to the ad budget.

The Zadarma callback widget from show to request

When a callback widget runs on the website, the API returns its statistics: visits to pages with the widget, widget shows, call requests and dismissals. The show-to-request funnel tells an agency whether the widget helps collect inquiries or mostly annoys visitors.

API limits and what statistics leave out

The two Zadarma logs must not be summed, and calls carry no ad source; for channel attribution add Calltouch or UIS. The API returns at most a month per request and only a few requests per minute, so a year of history loads gradually.

The PBX block usually follows Yandex Direct campaigns and website goals in Yandex Metrica. Agencies with clients on other systems can compare it with the Sipuni call log or Novofon calls. See a finished document in the in-house team demo report, all telephony sources on the calls and CRM page, and terms on the pricing page.