Call Tracking for Marketing: From First Ring to Booked Work

Call tracking connects a phone enquiry with a marketing source. A dedicated number can identify calls from a postcard. A website number that changes for an eligible visitor can connect a call with available visit information. Staff or a connected business system then establish whether the caller was a suitable prospect and what happened next.

Here is a fictional example. Someone arrives through a paid-search campaign, sees a tracking number on the website and calls. Reception confirms the requested service and location, then books an appointment. The caller phones again to check the time. The phone system has two inbound call events, but marketing has one new enquiry and one booking.

That distinction is the foundation of a useful call report. More calls can mean more demand, repeat questions, spam or difficulty reaching someone. The business outcome makes the count understandable.

See the report you are trying to build

A small report can connect the source, the caller’s experience and the next business step without starting with a long list of technical fields.

These examples come from the call-tracking planning worksheets. The ZIP includes a number/source map, fictional call records and proposed acceptance tests. It is a planning kit, not call-tracking software or evidence of a tested installation.

The examples contain no actual caller information, recordings or client outcomes. Every proposed test in the kit starts as “not run”. You can use the files to plan a setup and explain a report, then record real test results for your own approved configuration.

How tracking numbers work

A tracking number receives a call and forwards it to the business’s chosen destination. The tracking service records information about that event. Depending on the product and configuration, that may include the number called, time, duration, connection status and available marketing information.

The destination can still be your reception desk or existing phone system. A tracking number does not necessarily require staff to answer calls in a new application. What matters is that the entire forwarding route is supported and tested.

The number supplies evidence about how the call entered the system. It does not tell you by itself whether the caller is new, qualified or buying. A supplier can call a campaign number. A customer can save a number and use it again months later. Someone can dial a wrong number that happens to belong to your tracking pool.

Think of the tracking number as the start of the explanation. The call record and the enquiry outcome complete it.

Static tracking: one number for a placement

A static number stays with a particular campaign or placement. Give one postcard edition an exclusive tracking number, forward it to reception and label its incoming calls with that placement.

This is useful when the question is simple: did the postcard produce phone enquiries? There is no need to connect the caller to a website visit to answer that question.

The number must remain exclusive for the comparison to mean what its label says. Printing the same number on the postcard, a van and a directory listing combines those sources. A dashboard label reading “postcard” would then be more specific than the evidence supports.

CallRail’s source-tracking documentation describes assigning a unique number to each marketing source and forwarding it to the business. Its specific features and integrations still need checking against the plan you intend to use.

Dynamic number insertion: change the website number

Dynamic number insertion, or DNI, replaces a displayed website number according to tracking rules. Those rules may identify a broad source or assign a number from a pool to an individual eligible visit.

The distinction matters. One number displayed to every visitor from a particular channel provides source-level evidence. A visitor pool can associate a call with available information about a particular visit under the provider’s assignment rules.

CallRail’s visitor-tracking documentation explains its number-pool approach. Pool capacity, assignment behaviour and the available source information affect the result. The existence of a number swap does not establish perfect attribution or access to every search term.

Choose the simplest approach that fits the question

For a printed placement, start by considering a dedicated static number. It provides a clear relationship between the published number and the placement without the complexity of visitor tracking.

For broad website-channel comparisons, source-level insertion may be enough. If you need available visit-level campaign details, a visitor pool may be appropriate. For Google Ads calls, review the eligible Google measurement routes alongside any third-party option already in use.

The choice also depends on where the call begins. A person tapping a number directly in an ad may never visit your website. A website-only setup cannot be assumed to measure that call. Someone reading a printed brochure creates another path again.

Write down the main calling paths before selecting software: direct from an ad, from a website page, from a directory, from print and from a saved contact. Decide which paths need to be measured separately and what you can reasonably know about each.

A small example for a two-location business

Suppose a service business wants to compare an autumn postcard with paid-search website enquiries, while keeping callers connected to reception.

It could use one static number for the postcard and a visitor pool for eligible website visits. Both forward to central reception. Its established main number remains available as the website fallback when the tracking script does not operate.

A second location has its own routing requirement. A call handled by that branch should retain the original acquisition source when known, alongside the receiving location. The place that answers the phone is not necessarily the source that generated the enquiry.

This is a design example, not a deployed configuration. The actual provider, number availability, consent behaviour and forwarding path need to support it. A clear design makes those checks easier because each number has one intended job.

When a phone-system comparison is the real next step

If the main problem is unreliable routing, poor audio, an unsuitable queue or missing business-hours coverage, the underlying telephone system may need attention first. Marketing attribution will not repair a phone path that customers cannot use.

The separate business phone-system comparison addresses that broader selection task. Here the focus is how numbers and outcomes become useful marketing evidence, regardless of which supported system answers the calls.

Set up the calling path before relying on the report

A practical setup moves from the existing phone route to a limited measurement design, then through a controlled test. The exact settings differ by provider, so use the current product instructions for the service you choose.

1. Identify the number customers already know

List the main business number, branch numbers and numbers published in ads, directories, printed materials and email signatures. Include any numbers managed by a former agency or supplier.

Find out who controls each number and where it forwards. A number is both a measurement asset and a way to reach the business. Losing it when a contract ends can affect callers long after a campaign has stopped.

Keep the existing routing available as a rollback reference before changing anything. If the new route fails, the team should know how customers will still reach the right place. Record that route in an appropriately restricted operational document.

2. Connect the tracking number to a known destination

For each tracking number, specify the receiving number or queue, business-hours behaviour and after-hours behaviour. Include overflow or voicemail where applicable.

Follow the route all the way through. A tracking number might forward to a hosted phone system, which then forwards to a branch queue. Test that complete path rather than assuming the first successful forwarding step proves the call reaches a person.

Watch for accidental loops. If one destination forwards back to an earlier number in the chain, the tracking dashboard can record an event while the caller has a poor or failed experience. Correct routing takes priority over a clean marketing label.

3. Place or insert the number where it belongs

For a static placement, check the published digits against the intended tracking number and ensure the number has not also been used elsewhere. Review artwork before printing, and place a controlled test call before distribution.

For website insertion, use the provider’s supported installation method. Check every relevant phone location: header, footer, contact page, location page, sticky mobile button and any embedded customer journey.

The visible number and the click-to-call link must agree. If the display changes but the underlying dial link does not, a desktop visitor manually dialling and a mobile visitor tapping may travel through different measurement paths.

4. Keep a usable fallback

Test what visitors see when optional tracking is declined or the tracking script is blocked. The website should still provide the approved callable fallback and an honest measurement limitation.

A visitor’s privacy choice is not a defect to circumvent. The business may receive a useful enquiry with less source detail. Keep that uncertainty visible rather than assigning a precise campaign without evidence.

Use the site’s approved consent configuration and your provider’s current guidance. A working test under one browser condition does not establish that every consent state or browsing environment behaves the same way.

Verify the provider’s actual capabilities

A product page can help identify a candidate, but the implementation depends on the exact plan, country, number type and integration. Ask for confirmation against your intended call journey.

Start with number control and continuity. Can the provider supply the required numbers? What are the conditions for moving them in or out? Who controls the account, and what happens to routing if the service is cancelled? Confirm these matters for the specific numbers rather than assuming a general portability claim covers every case.

Then look at the evidence available in the call record. Ask which source fields are observed, how visitor assignments work, what happens when pool capacity is insufficient and how delayed calls are handled. Do not assume a supplier uses a universal session timeout or number-reuse interval.

Check the full cost: numbers, usage, recording, transcription, integrations and any other features required by the proposed design. A low headline subscription price is not a complete cost comparison if the necessary features sit elsewhere in the plan.

For integration, describe the outcome you need. “Create a phone activity on the existing enquiry and return the eventual booking status to reporting” is more specific than “connect to our CRM.” The latter can mean anything from a one-way activity log to a more complete outcome exchange.

Ask to see the behaviour with fictional records. A demonstration should show what appears in the destination system, not only a success notification in the sending application. No provider comparison in this guide should be read as a tested product ranking.

Keep Google forwarding numbers in their supported contexts

Google’s call-reporting documentation describes forwarding numbers for supported call measurement and lists Canada among the available countries. It also states that those numbers can change or be reassigned and must stay within supported call-reporting and website-call-conversion use.

Do not take a Google forwarding number from an ad and print it on permanent business materials. Its appearance in a current ad does not give the business permanent control of that number.

If Google reporting and a third-party provider are both involved, document which system measures each calling path and how conversion actions overlap. More measurement routes do not automatically produce more accurate totals; they can also create duplicate reporting of the same call or outcome.

Decide whether recording is needed before enabling it

You can collect call events and staff-entered outcomes without making audio recordings the foundation of marketing reporting. For many questions, knowing the source, whether a person answered, whether the enquiry qualified and whether work was booked is the useful information.

Recording, voicemail storage, transcription and automated analysis introduce additional purposes and data handling. Review each feature deliberately rather than treating it as an incidental checkbox in a tracking setup.

Google publishes separate recording settings and eligibility guidance, including defaults, exceptions and supported call types. Check the actual account settings and applicable terms. A feature being available or enabled does not establish that its use meets your business’s legal obligations.

For businesses subject to PIPEDA, the Office of the Privacy Commissioner of Canada’s customer-call recording guidance addresses appropriate purposes, notice, meaningful consent, alternatives, access, safeguards and retention. Purposes need to reflect the intended uses. An announcement about quality assurance should not conceal a different marketing or profiling purpose. If recording involves biometric voiceprints or other sensitive personal information, express consent may be required. Review that question before relying on an opening announcement and continued participation.

The applicable law also depends on the activity and circumstances. The OPC’s PIPEDA overview explains the relationship with provincial private-sector laws and cross-border handling. Sector-specific information, including health information, may require further consideration.

Have a qualified privacy or legal adviser review the relevant locations, sector, suppliers and purposes before deployment. Include staff notice, who can access recordings or transcripts, how long they remain available and how requests or deletion are handled. This guide explains measurement choices and is not legal advice.

Tracking metadata can itself relate to an identifiable person. Restrict operational records appropriately even if no audio is kept. Marketing reports generally need less detail than the team handling the customer’s request; avoid exporting sensitive conversational information merely because the system makes it available.

Separate call handling, qualification and sales

A useful call record answers three different questions.

First, what happened on the telephone? A person answered, the caller reached voicemail, no one answered, the caller abandoned the queue or a technical failure occurred.

Second, what kind of enquiry was it? New business, an existing-customer request, a supplier, recruitment, spam, a wrong number or something still unknown.

Third, what happened next? Follow-up is due, an appointment was booked, a quote was sent, work was won or the enquiry was closed for a stated reason.

Keeping those questions separate prevents a vague “good call” field from doing too much. A technically connected call can end in voicemail. A genuine new-business enquiry can remain unqualified because intake is incomplete. A qualified prospect can decide not to book.

Make qualification easy to apply

For a fictional repair company, qualification might mean the requested service is offered, the work is inside the service area and there is enough information to take a legitimate next step. Booking happens after that assessment.

Use criteria that the person answering can understand and establish. Ask staff to classify a few fictional examples and discuss disagreements before using the labels to compare campaigns. The exercise is about a consistent definition, not grading employees by a new score.

An existing customer requesting additional work may belong in an expansion pipeline while remaining outside new-customer acquisition. A person calling on behalf of someone else may belong to that person’s enquiry. Leave uncertain matches for review instead of forcing them into the nearest category.

If the qualification definition changes, identify when it changed. Moving from “service fit” to “appointment booked” changes the denominator. A rise or fall in qualified calls after that change cannot automatically be described as a marketing effect.

Duration is a clue, not the outcome

A long call can be a supplier conversation, time on hold or an unsuitable request. A short call can confirm an appointment for an existing enquiry. Duration may help prioritize review, but it cannot establish lead quality alone.

Check what the duration field covers. Ringing, automated menus, connected time and human talk time are different measures. A rule based on “two-minute calls” is hard to interpret if the report does not say which two minutes it counts.

Where a provider supplies an automated qualification label, retain its method separately from a staff-confirmed business outcome. Review whether the label is based on audio, duration or another signal and what it is intended to mean. Avoid presenting every automated conversion as an independently verified qualified prospect.

Give missed calls a next step

A missed call describes the connection, not the caller’s suitability. Until the business establishes the request, qualification may remain pending.

In the fictional Q002 example, the inbound call goes to voicemail. Staff later call back, confirm service and area fit, and send a quote. The original inbound event remains missed, while the enquiry becomes qualified and recovered through follow-up.

That history answers two useful questions: the caller was initially unable to reach a person, and the business later recovered the opportunity. Changing the original event to “answered” would hide the service problem; treating the callback as a second new lead would inflate acquisition.

The Q005 directory enquiry is different. Its voicemail indicates new-business intent, but qualification remains incomplete at the reporting cut-off. It should stay visible as pending, with someone responsible for the next action.

For each unresolved enquiry, the team needs an owner and an appropriate response expectation. An urgent repair line and a scheduled consultation desk should not make the same promise by default. Use the actual staffed hours and backup arrangements, including the relevant location’s time zone.

A callback must follow the business’s approved contact process. Automatic texts or promotional follow-ups introduce separate messaging and permission questions; they should not be added simply because call tracking can trigger an automation.

If the core problem is response coverage, the separate speed-to-lead guide addresses that operating decision. The call report should show where the gap occurs and which enquiries remain unresolved.

Connect repeated calls to one enquiry

The phone system and the customer system serve different jobs. The phone system records interactions. The CRM or equivalent enquiry record follows the business request over time.

Use a stable event identifier for each call and an enquiry identifier for related activity. A repeat call, a transfer and a callback can then retain their individual histories while belonging to one enquiry.

The acquisition source should stay on the enquiry separately from the source of later interactions. A callback from the main business number should not overwrite the paid-search source recorded on the original incoming enquiry.

Do not assume a phone number always identifies one person. Households, assistants, business switchboards and withheld numbers can make matching ambiguous. Use the available context and send uncertain matches to review instead of automatically creating or merging customer records.

Confirm what the integration actually created

During a controlled test, inspect the destination record. Did the call appear on the correct enquiry? Did the expected owner receive it? Did the original source remain intact? Did a booking or quote status return to the report as intended?

A repeated delivery should not create another identical activity. Technical teams can test the provider’s event identifiers, retry handling and transfer relationships using the approved integration method. The business-level requirement is straightforward: repeated messages about one event should not become repeated leads.

When records fail to match or update, keep them visible for review. An integration can appear healthy overall while a subset of enquiries has no owner or no final outcome. Comparing only successful records would make the report look more complete than it is.

The CRM implementation guide covers the broader field and stage design. For call tracking, specify the particular activity, enquiry relationship and outcome that must travel between systems.

Sending outcomes to an advertising platform is a separate step

A usable internal call report does not automatically satisfy an advertising platform’s import requirements. Google’s phone-call conversion import documentation describes eligibility and matching requirements for that route, including relevant call details and the later conversion.

Verify the applicable route, permitted data and duplicate-conversion treatment before implementing it. The CSV planning kit provided here is not a Google Ads upload template. Its fictional IDs and aliases cannot be submitted as evidence of real calls.

Read source information with its limits attached

A caller’s route into the phone system is one piece of their buying journey. Someone might see a sign, search the business name, visit the website and call later from a saved number. The most recent identifiable source does not necessarily describe everything that influenced them.

Keep the evidence method visible when it matters: a dedicated placement number, a visitor assignment, a platform-reported attribution or the caller’s own description. An unknown source should remain unknown unless additional evidence resolves it.

If staff ask how the person heard about the business, store that answer separately from technical tracking. “A friend recommended you” and “paid-search website visit” can both be true. Replacing one with the other loses useful context.

Visitor tracking also has practical boundaries. A delayed call, a shared number, a changed device or unavailable source data can weaken the connection between a visit and the person calling. Ask the provider how those situations are represented and test the supported scenarios.

CallRail’s visitor-tracking troubleshooting guidance explains why hardcoding a pool number disrupts the intended assignment and why calling an unassigned pool number can contaminate a test. Follow the documented test method rather than copying a number from the pool and assuming the resulting source proves the website journey worked.

The report should distinguish observed attribution from a claim that a campaign caused the enquiry. Tracking connects records under defined rules. Demonstrating how many enquiries would disappear without the campaign requires a different evaluation, usually with a defensible comparison or experiment.

Turn the event log into a readable marketing report

The supplied fictional file contains 12 events: one marked test, one outbound callback and 10 non-test inbound calls. Seven inbound events concern six distinct new-business enquiries because Q001 called twice. The remaining inbound events are spam, an existing-customer request and a wrong number.

At the sample cut-off, four of the six new-business enquiries are qualified, one is not qualified and one is pending. The report therefore has more calls than new enquiries and more new enquiries than confirmed qualified enquiries. That is a normal consequence of the definitions, not a discrepancy that must be hidden.

The sample cut-off is 6 October 2026 at 16:00, UTC−04:00, for a fictional Toronto operation. A multi-location report needs the relevant time-zone treatment; that offset is not a Canada-wide setting.

Start with a small group of columns: source, distinct new enquiries, confirmed qualified enquiries, pending enquiries and the relevant booking or sales outcomes. Include calls and missed connections when the operating question needs them, but label them separately.

Keep one outcome from being counted several times

The Q001 booking appears beside both calls in the sample event file because both events concern the same enquiry. It is still one booking. Likewise, revenue attached to an enquiry must not be summed again for each related call.

In the full fictional file, only the won enquiry has a confirmed revenue amount. Empty revenue fields mean “not confirmed here”, not zero customer value. A quoted opportunity may eventually produce revenue, but a quote value should not be mixed with completed sales without a clear label.

Use the latest reviewed enquiry status at or before the report cut-off. If a callback resolves an earlier voicemail, the current enquiry view should reflect that update while preserving the earlier event. To recreate historical reports after later changes, a production system needs timestamped assessment history; the flat sample file does not provide a full audit-history database.

Include unresolved work before comparing sources

A source with more pending enquiries may appear to have a lower qualified share simply because its outcomes are less complete. Show pending counts alongside qualified and not-qualified counts.

Similarly, calls arriving after staffed hours can be more likely to remain unresolved. Compare the handling pattern before concluding that the marketing source attracts poorer prospects. The report may be exposing a coverage problem rather than a demand-quality problem.

Recent bookings or quotations can still be open at the reporting date. Give the enquiry group appropriate time to develop and retain the date of each view. A later increase in sales may reflect the same enquiries progressing, rather than a new improvement in advertising.

Match call outcomes with the right cost

For a narrow fictional cost example, suppose the paid-search source spends CAD 600 during the sample period and produces Q001 and Q002. Both qualify after review. Media cost per qualified phone enquiry is $600 divided by two, or $300.

The repeat inbound call and outbound callback do not increase that denominator. Counting them as additional leads would make acquisition appear cheaper without creating additional prospects.

The figure is media-only and phone-only. If the campaign also produces forms, do not compare the phone-only result with an all-lead report as though they cover the same outcomes. Include tracking fees, campaign services and other acquisition costs separately when the decision needs a fuller cost measure.

This tiny dataset is an arithmetic illustration, not a benchmark or evidence for a budget change. Use the cost-per-qualified-lead guide for the fuller connection between acquisition costs, customer contribution and an affordable price.

Test a complete journey before calling the setup ready

A successful number swap is only one checkpoint. A controlled test should reach the intended destination, create the expected call record, connect to the right enquiry and appear correctly in the report.

Use authorized test callers and fictional enquiry details. Mark the records as tests and exclude them from business totals. Record what was expected and what actually happened, including failures or blocked steps.

Begin with one ordinary journey: an eligible website visit, the displayed number, the call, reception, qualification and a fictional booking. Check the mobile dial link as well as the visible digits. Then test a static placement number separately.

Next, test a missed call and callback. Confirm that the event remains missed, the follow-up is assigned and the original source stays with the enquiry after the callback. Include after-hours routing and any branch transfer involved in the planned service.

Check approved consent and blocked-script states to confirm a usable fallback. Ask the provider to demonstrate assignment limits and delayed-call behaviour using a supported method. Avoid generating uncontrolled traffic or calls simply to exhaust a number pool.

Finally compare the call log, CRM record and report by their identifiers and timestamps. A success message at one stage does not establish that all later stages worked. Resolve missing owners, duplicate activities or inconsistent outcomes before relying on the report.

The downloadable test matrix provides these scenarios as proposed checks. It does not claim they have passed in your system, and no production call or integration was tested for this article.

If a test fails, follow the last confirmed step

A failed test becomes easier to diagnose when you know where the expected journey stopped. Start with the caller’s experience, then follow the record into the report.

If the page displays a tracking number but tapping the phone button dials the main number, inspect the button’s destination. The display and dial target may be managed by different page elements. Correct the affected control and repeat that same journey before treating other page tests as relevant.

If the tracking system records an incoming call but the intended team never receives it, inspect forwarding and routing. The destination may be wrong, a queue may be unavailable or an after-hours rule may send the call elsewhere. An attributed event is not a successful customer connection.

If staff receive the test call but no expected event appears, confirm which number was actually dialled and which account or location owns it. A browser’s saved contact, an unswapped link or a different published number may have created another path. Establish the path before concluding that the tracking provider lost the event.

If the call record exists but the CRM activity does not, check the integration’s delivery result and the destination record. It may have rejected a required field, created an activity elsewhere or matched an existing enquiry unexpectedly. Keep the original event identifier available so the technical reviewer can trace one case rather than compare aggregate totals.

If the CRM activity is correct but the report omits it, check the reporting period, time zone, test exclusion and outcome definition. A test intentionally marked as excluded should not be expected in live lead totals. Check its presence in the test view instead.

The purpose of these checks is to narrow the failure. Avoid changing number assignments, website scripts and CRM rules together unless the diagnosis requires it. A single controlled change followed by the same test gives a clearer explanation of what resolved the issue.

Keep failure records out of the success story

A blocked or failed test should remain visible until the affected requirement is resolved or explicitly removed from scope. Do not mark it passed because another route worked.

For example, a successful manual dial on desktop does not clear a failed mobile button. A successful daytime call does not clear an untested after-hours route. If one path remains unverified, describe that specific limitation to the person deciding whether to launch. That makes the decision about the customer experience concrete and keeps the report from implying broader coverage than was demonstrated.

Keep the numbers useful when campaigns change

A printed tracking number can continue receiving calls after the campaign ends. Someone may keep the postcard or save the contact. Reassigning the number immediately to an unrelated campaign can make old demand look like new campaign activity.

Record the placement’s last use and agree on a retirement approach that reflects its likely useful life. Confirm the number still reaches an appropriate destination while it remains in circulation. Removing it from a dashboard does not remove it from customers’ phones or printed materials.

Review the setup after changes to the website theme, consent manager, phone routing, tracking provider or CRM. Each can affect a different part of the journey. Recheck the affected path rather than assuming last month’s successful test covers the new configuration.

The useful end result is a report someone can explain: where the call entered, whether the caller reached the right place, which distinct enquiry it belonged to and what happened next. Start with one important calling path and verify that whole journey. Expand only when the added detail will support a real business decision.

Frequently asked questions

What does call tracking mean in marketing?

Call tracking links a phone enquiry with the marketing source that produced it. A dedicated number can identify calls from one postcard, and a website number that changes for an eligible visitor can tie a call to available visit information. Staff or a connected business system then record whether the caller was a suitable prospect and what happened next.

How should a business track calls that come from its marketing?

List the main calling paths first: from an ad, a website page, a directory, print and a saved contact. Use a static number for a printed placement and number insertion on the website only where you need visit-level detail. Then record each enquiry's outcome, such as qualified, booked or still pending, because a count of rings alone mixes new demand with repeat calls, spam and missed connections.

How do I choose call tracking software for marketing?

Choose the simplest setup that answers your question, then check the plan's actual capabilities instead of the feature list. Confirm number availability, how a visitor pool assigns numbers, what source information is passed on, how it behaves when a visitor declines tracking and what any integration really creates in your CRM. Make sure it can forward to your existing reception line or phone system.

What is CallRail used for in marketing call tracking?

CallRail is one call tracking provider, and its documentation describes giving each marketing source a unique number that forwards to the business. It also offers a visitor pool that assigns numbers to individual website visits. Pool capacity, assignment rules and the source details available all affect the results, so check the specific plan you intend to use.

What is dynamic call tracking on a website?

Dynamic number insertion swaps the phone number shown on your website according to tracking rules. One number per channel gives source-level evidence, while a pool of numbers can tie a call to a particular eligible visit. The visible digits and the tap-to-call link must change together, and visitors who decline tracking should still see a working fallback number.

How does a call tracking number reach my existing phone line?

A call tracking number receives the call and forwards it to the destination you choose, such as reception, a hosted phone system or a branch queue. The service records details like the number dialled, time, duration and connection status. Test the full path through to a person, and watch for loops where a destination forwards back to an earlier number.

Which call tracking metrics matter most for a business?

The useful measures are new enquiries, qualified enquiries, bookings and the follow-up still owed, connected to the source of each. Call duration is a clue, not an outcome, since a long call can be a complaint and a short one can book work. Link repeat calls to one enquiry, so a caller who phones back to check a time is not counted as fresh demand.

How can I check that call tracking is working correctly?

Place controlled test calls through each published number and each website phone location, including the sticky mobile button. Confirm the call reaches a person, the record shows the expected source and the outcome appears where the team works. If a test fails, follow the route back to the last step that was confirmed, and keep failed tests out of the marketing report.