Call tracking report for clients

What a client call report contains

For many businesses a call matters more than a click: the client pays for ads so that the phone rings. Reportkey puts phone enquiries into their own section of a recurring report:

• Total calls compared with the previous period: the size of phone demand.
• Missed calls: enquiries the business lost, and a reason to discuss sales handling.
• Unique calls and new caller share: how many different people called and how many called for the first time.
• Average wait time and talk time: how quickly the team answers and how substantial the conversations are.
• Call channels and top 10 sources: which channels and sources (ad networks, search engines, sites) bring callers.

Blocks come with short AI comments for the client on what grew, what dropped and what deserves attention.

How call tracking data reaches the report through Yandex Metrica

Sixteen of the services listed above send calls to a Yandex Metrica counter. Metrica ties each call to a visit and a traffic source, and Reportkey reads the processed data. So the connection you set up is Yandex Metrica, the counter that carries the calls, not the tracker itself. What gets filled in depends on the service: Roistat calls with talk and wait time populate almost every block, while QUON goals in Metrica mostly provide conversions. Each source page explains the details.

Missed calls and wait time in the report

Missed calls and wait time are the call handling signals clients grasp fastest. They appear when the tracker passes these fields to Metrica, as with Callibri missed calls or UIS calls from Metrica. If a service sends only the fact of a call, the report relies on volume and sources.

Calls next to ads and SEO

The real value is having everything side by side. In the same report the client sees spend and campaigns from ad platforms and rankings and search traffic. That makes it easy to answer how many calls the budget produced, without pulling data from several dashboards.

Metrica’s built-in Calls report suits an analyst, but the client needs a finished document with conclusions, period comparison and a clear structure. Exporting tracker data to a warehouse and BI also works, except that you then build and maintain the dashboard yourself. Reportkey takes over that assembly: calls, ads and search traffic go into one recurring report that reaches the client on a schedule (not on every plan).

Counter setup checklist

1. Turn on call export to Metrica in the call tracker.
2. Make sure the counter has call tracking enabled, or call blocks will not be built.
3. Keep one call tracker per counter, since totals are not split by service.
4. Remember Metrica limits: up to three hours of delay, static numbers are not matched to visits, and the matching window is 21 days.

CoMagic works without a Metrica counter: CoMagic calls, missed calls and waiting time via Data API connect with a key from the CoMagic account, and the same call blocks are built from CoMagic data.

Virtual PBXs also work without a counter: the data comes from the PBX call log itself. Sipuni call log with new clients, Zadarma calls and telephony costs, staff workload in Telphin.Office and Novofon lost calls and campaigns show answered and missed calls, waiting and talk time, and a breakdown by employee and phone number.

Call reports for agencies and in-house teams

Agencies. A PPC specialist sets the report up once, and the client regularly gets calls next to spend. Your first report in 5 minutes. See the PPC agency demo report.

In-house teams. A manager sees how many calls were missed and how long people waited, and can check the sales team without logging into several tools.

Prices and the free trial are on the pricing page; every source is in the integrations catalog.