Roofing call tracking: what the record actually shows

Assign tracking numbers to the acquisition assets covered by the program

Every site the network operates gets its own tracking number, or a small pool of numbers if the site covers more than one territory or service line. That number appears on the site instead of a generic line, so any inbound call to it can be matched back to the exact site and page the caller found before dialing.

This matters because a roofing company that rents access to more than one site, or a territory that spans more than one asset, needs to know which property is producing calls. Without a dedicated number per site, you would only know that someone called — not which page, domain, or market generated the lead.

What a number assignment covers

• One tracking number (or small rotating pool) per site, not shared across unrelated markets
• A mapping between the number and the territory it feeds
• Forwarding to the AI receptionist or to a live line, depending on how that site is configured
• A record of the number's install date and the site it has been tied to since

Inventory in the live network is currently concentrated in a small number of markets in Pennsylvania, Texas, and Illinois. Exact site counts and the numbers tied to them vary by market and change as territories are built out or reassigned, so any specific inventory claim needs to be verified at the time you're reviewing a territory, not assumed from this page.

Once a number is assigned, it stays tied to that site's call-tracking history even if the roofing company receiving the leads changes. The network, not the roofer, owns the number and the history attached to it, which is what allows a clean handoff if a territory is reassigned in the future.

Record the call events and source information that are actually available

A call-tracking record is built from the events the phone system can actually observe. That includes the number dialed, the caller's number (when not blocked), the timestamp, the duration, and a connection status such as connected, missed, or voicemail. It also includes which site and, where available, which page on that site the number was displayed on.

It does not include everything a marketer might want. There is no keyword-level attribution — the record can tell you the call came from a specific site or page, but it cannot reliably tell you which search term or ad the caller typed or clicked before they got there. Treat any claim that goes further than source-site and source-page attribution with suspicion, including from us.

Fields typically present on a call record

1. Tracking number dialed and the site/page it was displayed on
2. Caller number, where the caller has not blocked it
3. Timestamp and duration
4. Connection status: connected, missed, voicemail, or busy
5. Territory and assigned roofing company
6. Recording link and transcript, only where recording is enabled and permitted

Missing fields are shown as not available rather than filled in with a guess. If a caller blocks their number, the caller-number field is blank. If a call never connects, there is no duration and no recording, because there was nothing to record.

This distinction is the difference between a usable record and an inflated one. A roofing company reviewing call volume for a territory should ask specifically which of these fields are populated, and treat any blank field as a genuine gap rather than assume the data exists somewhere else.

Use approved recording and transcription settings where supported

Recording is not automatic on every line. It is a setting applied to a number, and it only produces a recording when it's enabled for that number and lawful for the call in question. When a call is answered by the AI receptionist, an AI-generated summary or transcript may also exist for that call; live-answered calls are recorded only where the recording setting is turned on.

Consent rules vary by state

Whether a call can be recorded depends in part on whether the call touches a one-party consent state or a two-party (all-party) consent state. In a one-party state, one participant's consent is generally enough; in a two-party state, all participants generally need to consent. Calls that cross state lines can involve more than one set of rules. This is general background, not legal advice — check the law for the specific states involved, or ask counsel, before relying on a recording for any purpose beyond routine business use.

• Recording is a per-number setting, not a guaranteed feature of every call
• A disclosure or beep may play on recorded lines depending on configuration
• AI-answered calls can produce a summary or transcript in addition to, or instead of, audio
• Consent requirements differ by state and can apply to both ends of the call

Transcripts, where they exist, are generated for AI-answered calls as a byproduct of the AI receptionist's handling of the call. They are not a substitute for a verified legal transcript and should be read as a working summary, not a certified record.

If your team needs recordings for quality review or training, ask during onboarding whether the numbers tied to your territory have recording enabled, and what format the recordings and transcripts arrive in. Settings can differ between sites even within the same network.

Connect call context to territory and CRM delivery

A call by itself is just an event. What makes it useful is the context attached to it: which territory it belongs to, which roofing company is assigned there, and whether the call ultimately becomes a delivered lead record in your CRM. The call-tracking system and the lead-delivery system share the same territory assignment, so a call to a given number is matched to the same company every time, consistently.

What gets attached to a call before delivery

• Territory and assigned roofing company, matched from the number dialed
• Any AI-captured details: name, service requested, address or ZIP, urgency, if the caller provided them
• Call status and duration
• Recording or transcript link, if permitted and available

Delivery into your CRM follows the same queued, sent, delivered, or failed lifecycle used for form leads, with retries and a fallback alert if the push to your CRM fails. See the CRM lead-delivery page for the full mechanics of that handoff; this page covers what happens before delivery, at the point the call itself is captured.

A call that never connects — a missed call, or one abandoned in a queue — can still generate a lead record if enough information exists (for example, caller number and a missed-call text response), but it will carry a status that reflects the actual outcome. It is not relabeled as an answered inquiry.

Texting on network numbers runs under a registered texting campaign, and a missed-call text-back exists as a capability — but it depends on consent rules for the recipient, so it is not sent unconditionally on every missed call.

Your portal shows the call and, where it produced a lead, the linked lead record in one place, so you are not reconciling a call log against a separate lead list by hand.

Review missed calls, caller intent and documented outcomes

Missed calls are not discarded. A missed or unanswered call is still logged with its timestamp, source site, and territory, even though there is no conversation to record. That matters for a roofing company reviewing how many inquiries a territory is actually generating, because a missed-call rate that's invisible is a missed-call rate you can't fix.

Outcome categories your team can use

• Connected and completed — the call went through and ran to a normal end
• Missed — the call rang out or was abandoned before connecting
• Voicemail — the caller left a message where that option exists
• AI-handled — answered by the AI receptionist, which may capture a summary even without a human on the line

Caller intent, where it's known, comes from what the caller said on the call — captured in notes, a transcript, or an AI summary — not from guesswork about why the number was dialed. If a caller mentions a leak, a storm date, or a specific service like a tear-off or flat-roof repair, that detail is recorded as part of the call context when it's available.

Your outcome tracking in the portal (new, contacted, appointment, estimate, won, lost) is a separate layer from call status — a call's connection status tells you what happened on the phone; your outcome tag tells you what happened with the opportunity afterward. Both are useful, and they answer different questions.

Control who can access calls and interpret attribution limits

Access to call records is scoped to the roofing company assigned to that territory. Your team can see the calls, recordings, and transcripts tied to the territories your company is renting — not calls routed to a different company in a different market, even if both are part of the same network.

Who sees what

• Your staff with portal access see calls assigned to your company's territories
• Team access can be granted to additional staff who work leads, under your account
• The network's own staff can see records for support and billing purposes
• No other roofing company in the network can see your calls, and you cannot see theirs

Attribution has real limits, and it's worth repeating them plainly so your team doesn't over-read the data. A call record can tell you which site and which number generated a call. It generally cannot tell you which specific keyword, ad, or search query the caller used beforehand, unless that detail was independently captured as UTM or campaign metadata on the page the caller came from before calling.

Practically, this means your team should use call-tracking data to judge which sites and territories are producing inquiries, and use your own CRM's outcome tracking to judge which of those inquiries turn into jobs. Don't ask the call record to answer a marketing-attribution question it wasn't built to answer.

If you need broader access for a manager who oversees more than one territory, that can be set up through your account's team-access settings rather than by sharing login credentials, which keeps the access boundary intact and auditable.