Track Calls and Form Leads From Websites You Own

We start with an inventory: the main website, campaign pages, service area sites, forms, phone routing, analytics properties and the system that holds your inquiries. Record the account owner, the operating contact, and the access needed to maintain each item. Keep credentials in the appropriate secure system rather than in a shared reporting spreadsheet.

Review what the agreement says about domains, site content, exports, number portability where applicable, ongoing hosting, renewal responsibilities, and the end of service. These are operational questions that affect continuity. A dashboard can look complete while the business lacks the access needed to preserve its records or keep an asset functioning.

An owned network on Garrison, the microsite software from Trojan Digital Marketing, sits on domains registered to your business. Your team answers the calls and reads each form directly. Our published Garrison inquiry counts leave missed calls out. When you review any network, ours included, check those promises against the actual scope and agreement. Domain ownership, ongoing operation and search visibility are separate questions.

Choose the unit that reflects the business process. An inquiry might be a distinct request for an offered service. A form submission, follow up call, and reply about the same project can belong to that inquiry. A later request for a different project may create a new opportunity linked to the same customer.

We write the rules for duplicates, spam, tests, existing-customer support and out-of-area requests before the first count. We won’t change them later to make a channel look better. Consistent definitions allow an owner to compare sources and periods without wondering whether the counting changed.

Give unresolved requests a pending status. The team may need more information before determining fit. A pending inquiry is useful operational information and should not automatically be labeled a qualified lead or a failed campaign.

Use fields the team can maintain reliably. If a detail is not needed to respond or evaluate the process, reconsider collecting it. Keep personal contact information in the business system intended for that purpose, and use internal identifiers in broader reporting where practical.

A request that comes in through a service area page tells you where the visitor landed. It does not necessarily establish that the customer’s project is located in that area. Ask for the information needed to confirm service fit and keep it separate from the page label.

For a hypothetical contractor with several local sites, a visitor might reach a suburban page while seeking work at a property elsewhere. The source record can preserve the page and the inquiry can preserve the actual project location. Combining them too early can produce a misleading market report.

The same rule applies to our own district strategy pages. We work from Indianapolis, with no public street address, and serve businesses in other markets remotely. An area page describes a market; it doesn’t mean we have an office or a client in that district.

Test the important contact paths with clearly labeled test records. Confirm that a completed request reaches the intended system, that the customer receives an accurate confirmation, and that someone is responsible for responding. A visible form alone does not prove the handoff works.

Document what each measured website event represents. Google Analytics describes key events as important actions. The implementation should correspond to the business action being reported, such as a completed request, rather than an incidental click that can occur without submission.

Keep test and internal activity distinguishable from customer inquiries. Recheck the handoff after a form replacement, routing change, or website migration. A reliable completion check can prevent a reporting problem from becoming a customer service problem.

Define the information that makes an inquiry suitable for the next step. A commercial roofing company may need an offered roof service, a property in a served area, and enough context to arrange an assessment. It may also need to distinguish a facilities request from a residential inquiry.

Use reason codes that help the business learn. “Outside service area,” “service not offered,” “duplicate project,” and “awaiting information” are more useful than a single rejected category. Keep the list concise enough that the person reviewing inquiries can use it consistently.

We don’t qualify a request just because it came through a favorite channel. Source performance should emerge from the same rules applied across the process. Review a small sample together when several team members handle inquiries so the definitions remain aligned.

Record when a request was received, assigned, and first meaningfully handled. Those times show which requests nobody picked up and which handoffs keep getting stuck. A business can lose useful opportunities after the website has done its job.

Choose a response expectation the team can actually support. The website should describe the real process, and the internal review should identify exceptions. Avoid an automatic promise of immediate service when availability depends on staffing, scope, or location.

The service inquiry design playbook helps align the form, confirmation, and follow up. Improving that sequence can be a higher priority than expanding the number of pages sending requests into it.

Show received inquiries, unique inquiries after the agreed duplicate rules, qualified opportunities, proposals, and completed outcomes separately. Include pending stages. Explain whether the report follows requests received during the period or outcomes completed during the period.

Group by service and actual project area when those fields are reliable. Keep the destination or campaign view available as a separate analysis. This allows an owner to see whether a source generates relevant requests without assuming that a page name proves customer geography.

Do not add overlapping source rows into a unique total. One inquiry may have several recorded interactions. The article on content assisted inquiry measurement explains how to preserve that contribution without multiplying the opportunity.

Search impressions, AI citations, and website visits provide context for acquisition. They do not replace the operational inquiry count. Use the AI visibility baseline to separate reported exposure, saved responses, referrals, and business outcomes.

If a source is unavailable, label the gap. A direct inquiry can still be handled and qualified even when its full discovery history is unknown. Avoid assigning unknown activity to a microsite, an assistant, or a campaign merely because the business invested in it recently.

The workflow for connecting AI referrals to inquiries provides a focused method for preserving available source evidence. The search to sales attribution playbook develops the broader contribution analysis.

Imagine a service business receives twelve form records and six calls during a review period. The team identifies two test forms, three calls related to existing form inquiries, and one repeat form about the same project. Those records represent interactions that need review; they should not all become separate new opportunities.

The team applies its documented rules, creates the unique inquiry set, and records which requests are suitable, pending, or outside scope. It then compares that operational count with the website’s measured events. A difference prompts investigation into duplicates, missed events, or the event definition rather than an immediate assumption that either system is complete.

This example illustrates a method, not a Trojan performance result. The useful outcome is a reconciled record with explainable differences and assigned follow up, even when the full customer journey remains partly unknown.

Keep an asset inventory and a tested export process. Confirm which business account retains the domain, content, and inquiry records, and who maintains renewals and hosting. An exit or change of provider should not be the first time the team asks whether it can access its own operational history.

For a roofing specific network, review the Garrison service in the context of the written market boundaries and active agreement. Service exclusivity describes the provider relationship under those terms. It does not prevent a homeowner or property manager from comparing several contractors independently.

Keep the customer’s preferences and the business’s communication process respected during any transition. Transfer only the records and access appropriate to the agreed scope, and verify the new routing before retiring the old workflow.

Use the inquiry record to check whether the team can support the work being requested. If suitable inquiries repeatedly wait for assignment, identify the operational bottleneck before adding more destinations. If requests consistently fall outside the offered service, clarify the page and qualification language before assuming the source itself is unsuitable.

Bring the person who handles inquiries into the review. They can explain recurring misunderstandings, incomplete requests, and the details that make a first response useful. Compare that practical knowledge with the recorded reason codes and update the process when the evidence supports a change.

Keep the definition changes dated. A revised service area or a new division can make previously unsuitable requests appropriate. The next report should reflect the business’s current capacity while preserving the rules used in earlier periods, so a change in operations is not mistaken for a change in marketing quality.

Does owning a domain guarantee future leads?

No. Domain control, ongoing operation, useful content, visibility, and customer demand are separate matters. Measurement should show what the asset actually produces and what it costs to maintain.

Can we call an inquiry exclusive?

Describe the routing and agreement precisely. A request routed only to the business through its own form can still come from a customer who independently contacts other providers.

What if the analytics and inquiry totals disagree?

Check definitions, duplicate rules, test activity, routing, and measurement gaps. Preserve both source records while investigating. A discrepancy is a reason to reconcile, not to choose whichever total looks more favorable.

What should a first review deliver?

A clear asset inventory, a reliable inquiry definition, a tested contact path, assigned follow up, and a short report with explainable totals. Those foundations make later channel comparisons more useful.

Request an owned lead measurement review with your website destinations, routing process, and current inquiry stages. Trojan Digital Marketing can help connect the assets and records into a practical system your team can use.