How to Reconcile an Exclusive Organic Lead Invoice

For Trojan memberships, use the 50, 100, 150, 200 and 300 Garrison microsite memberships alongside the agreement for the billing period. Year one includes the build, domains and the first year of hosting and upkeep. Annual renewal includes domain renewals, hosting, upkeep, a fresh batch of local articles, updated pricing guides and FAQs, and the same included qualified lead allowance again. The plan’s included qualified lead allowance applies each 12 month membership year and resets at renewal. Only additional qualified leads above that year’s allowance are invoiced monthly after manual review. At the end of each membership year, record the shortfall renewal credit separately: missing included qualified leads multiplied by the member’s locked additional lead rate, capped at the renewal price. The credit applies to renewal only and has no cash value. Additional qualified leads are billed monthly, in arrears, at your tier rate after review against the agreed qualified lead definition and after the annual included allowance is used. Your additional qualified lead rate is fixed at signup and stays fixed while your membership renews without a gap. Published rates may change for new members.

Record the reporting period, covered sites, recipient business, applicable qualification rule and charge trigger before inspecting individual rows. If terms changed during the period, retain the effective dates rather than applying the newest rule to every historical record.

The membership scope guide explains the decisions to settle before enrollment. Reconciliation is the later operating task of checking whether the records match that arrangement.

In Trojan's qualified lead arrangement, the client's own team answers the calls and follows up on form inquiries. The agreed tracking process flags inquiries for Trojan to review manually against the qualification, source and duplicate rules. An incoming call or form alone does not authorize a charge. Only approved qualified inquiries enter the lead invoice, and unresolved records stay pending. Routing and tracking are set up and tested during onboarding; any separate membership or site fees remain governed by the written scope.

Use an internal inquiry identifier that connects relevant forms, calls and follow up. The same customer may send a form and then call about the same project. Those interactions should be reviewed together using the agreed duplicate rule, rather than automatically counted as separate new opportunities.

A returning customer with a genuinely different project may require a new record linked to the existing customer. The counting rule should be explicit. Avoid relying only on an email address or phone number when one person can represent multiple properties or projects.

An inquiry can be relevant while its discovery source remains unknown. Another can have clear organic source evidence while requesting a service the company does not offer. Keep these dimensions separate so the review does not use one favorable fact to fill a gap in another.

A destination page identifies where a request arrived, not necessarily how the person first discovered the business. Paid traffic, direct visits, referrals and organic visits can reach the same microsite. Customer reported discovery can add context, but it should be labeled as that person's account rather than silently treated as a tracking result.

The branded exclusive delivery standard describes these distinctions. If the agreement charges only for a particular source or lead class, its treatment of uncertain cases needs to be resolved using the actual terms.

Useful review categories include duplicate project, test activity, spam, unsupported service, outside actual coverage, awaiting information, and qualified under the defined rule. A broad label such as bad lead does not explain the decision.

Record the factual basis needed for the review, with appropriate access to customer information. A person who declines a proposal is not automatically an invalid inquiry. A customer the office has not yet reached may remain pending rather than conclusively outside scope.

Google Analytics supports separate qualification and disqualification stages. The reconciliation process should likewise distinguish initial receipt, qualification and later sales outcome. A website event is evidence of an action, not the entire business review.

Imagine a report contains eight form records and four calls. During review, two forms are identified as labeled tests. Two calls concern projects already represented by forms. The remaining records still need review for source, service fit, location and the agreement's treatment of existing customers.

The starting twelve interactions therefore do not establish twelve unique qualified organic opportunities. The purpose of the example is not to prescribe a universal final count. It shows why records must be linked and evaluated under the actual definitions before any charge is assessed.

If one project remains awaiting information, keep it visible with an assigned reviewer and next action. If a later correction changes its treatment, preserve the original status and the reason for the change. That history helps both parties understand the next invoice without rewriting the prior report silently.

Where the agreement provides a review process, identify the inquiry ID, the disputed classification, the relevant term, and the evidence supporting the request. Follow the stated procedure and timing. Avoid sending an unstructured list of customer details to people who do not need access.

A review request could say that two records appear to concern the same project and ask for the duplicate rule to be applied. Another could identify a service outside the agreed scope. The provider may need clarification before deciding how the record should be treated.

The lead terms review article covers the questions to ask before signing. This reconciliation workflow does not imply that every disputed record results in a refund or that a missed sale creates an adjustment entitlement.

The operational system may need contact details to respond to a customer. A shared finance summary often needs only an internal identifier, date, classification and commercial treatment. Use the minimum detail appropriate to the task, with access for the people responsible.

Google Analytics prohibits sending certain personal information. Do not place customer names, email addresses or phone numbers into public page URLs or general analytics labels to make invoice tracing easier. Link records through appropriate internal systems instead.

Keep the evidence needed to understand changes according to the business's actual retention process. A corrected classification should not erase the operational history that explains why the adjustment happened.

If the same service mismatch recurs, revise the offer and intake questions. If source is repeatedly missing, inspect the measurement path. If duplicates are frequent, improve how interactions are linked. If the office cannot resolve pending requests, assign a practical follow up process.

The owned lead measurement playbook connects this record keeping with broader acquisition reporting. Request a lead measurement discussion to identify the definitions and handoffs a reliable review requires.

Does every inquiry in an invoice need to become a sale?

That depends on the agreed charge trigger, but an inquiry and a sale are different stages. Do not assume a lost proposal creates a credit entitlement.

How should a duplicate be handled?

Link the interactions and apply the documented duplicate rule. The same project contacted twice and a returning customer with a new project may need different treatment.

What if the source cannot be confirmed?

Keep the uncertainty visible and apply the actual agreement’s treatment of unknown sources. Do not relabel the record as organic simply because it came through a microsite.

What evidence should accompany a review request?

Use the inquiry identifier, the classification in question, the relevant term and the necessary supporting facts. Follow the actual review process and avoid exposing unnecessary customer details.