IntegrationsCallRail
CallRail + Monthwrap

Leads & sales reporting

CallRail reporting for agencies.

Bring CallRail inbound leads into Monthwrap, explain missed calls and connect the conversation to your agency’s work.

AvailableAgency API key
Inside the monthly reportSample data
Northline Heating · fictional example

A month of inbound inquiries

Inbound calls72Recorded in CallRail
Answered63From the sample call records
Missed9For the client to review
A view of the client’s businessSales context
01October 1–715 calls
02October 8–1418 calls
03October 15–2114 calls
04October 22–3125 calls

Call records show demand and handling. They do not establish booked jobs or collected revenue.

Illustrative call activity · October 2026

CallRail, at a glance.

Connect with
Agency API keyChoose the client’s company. Platform API access and usage limits apply.
Updates
Daily sync, with a manual refresh in Sources. Platform reporting delays still apply.
Earlier months
Request an earlier month in Sources. Coverage follows the platform’s available history and your account access.
In your report
Inbound call leads.

Built around your client’s questions

The phone rang. What happened next?

For local growth and paid search agencies whose clients win business over the phone.

A search campaign can generate a strong month of inquiries while the client still feels quiet. An unanswered call, a repeat caller and a booked repair tell different stories. Bring the inbound call records into the same monthly review as the advertising and website work, so the discussion has somewhere concrete to start.

Monthwrap reads the selected CallRail company and carries over the caller details, call time and notes about the outcome where available. Use those records to explain the month, then add confirmed bookings from the client’s CRM or your own reviewed data. Keep a clear distinction between an inquiry and a sale.

Choose the numbers that matter

What CallRail
brings to the report.

Inbound call leads. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.

01

Inbound call leads

Calls arriving at the business become call leads. Outbound calls are excluded, so the reporting view is centered on incoming inquiries rather than the team’s follow-up activity.

02

Answer status

Call notes indicate whether the call was answered or missed. Review the records to find a handling issue before assuming that a disappointing sales month was caused by weak advertising.

03

Call context

Available caller name, phone number, time and duration help the agency understand individual inquiries. The connector brings lead records; it does not import recordings or produce conversation transcripts.

04

Source notes

When CallRail supplies an attribution source, it appears in the lead note. Treat this as CallRail’s recorded source, and keep it separate from an advertising platform’s conversion count.

For your next client report

Explain paid search demand

Place inbound leads beside Google Ads spend and conversions. Explain where the measures differ and what the team reviewed, rather than presenting the two counts as interchangeable.

Arrange the report in your own layout

Read it from the client’s side

See the complete
local growth report.

A full fictional agency report, with the work delivered, the numbers behind it and the plan for next month. Use its structure to plan your own mix of sources and client results.

Open the sample report

Make the connection

From CallRail
to the right client.

Choose the client’s company. Platform API access and usage limits apply.

Connection methodAgency API keyAvailabilityAvailableYour connected account’s API permissions and plan apply.
  1. 01

    Use an authorized API key

    Use the agency’s or client’s CallRail API key with access to the relevant account. Check the platform’s API access and usage terms before scheduling reporting across a large client book.

  2. 02

    Choose the client’s company

    Select the company that holds the tracking numbers for this client. A key can expose more than one company; matching the right company matters more than the account display name.

  3. 03

    Review the first imported calls

    Check a known inbound call, its date and its note against CallRail. Confirm the reporting month, then add call leads and your interpretation to the report.

Know what each
number means.

An inquiry is not a booked job

A phone call may be a repeat inquiry, a supplier or a missed opportunity. Use reviewed lead outcomes or another source for bookings; do not label all inbound calls as new customers.

Platform access still applies

Use a CallRail account with API access. CallRail’s API limits and charges apply to the connected account.

Before you connect

A few useful
answers.

Does this include calls made by the client’s team?

No. This connector reads inbound calls. Outbound follow-up activity can be described separately in the work log when it is relevant to the report.

Can I listen to recordings in this integration?

Use Monthwrap for call leads and available call details. Listen to recordings and review transcripts in CallRail.

Should I add CallRail calls to Google Ads conversions?

Not as one unduplicated lead total. The same call may appear in both systems. Show the source measures clearly and use the reviewed client lead view for the overall story.

Start with your next client report

The data has a source.
The story has your name.

Bring your sources together, choose your layout and add the context your client needs.

Start free trial

14-day free trial. No card needed.

Make yourself comfortableMore about cookies and browser storage