Leads
Leads arrive from the client's website forms, your hosted forms and automations, each tagged with the channel, campaign and click that produced it. You and the client work the same pipeline: they mark what happened and record the sale; you see which marketing made money.
Website forms via the tracking script, hosted forms, GoHighLevel forms and automations.
Channel, campaign, keyword, click ID and landing page — first touch and last.
New, Contacted, Qualified, Converted and Lost — the same for you and the client.
Record the job, repeat work and refunds; lifetime value adds up per customer.
Throwaway emails, fake numbers, bots and repeat clickers flagged before anyone calls.
Notes for whoever picks it up next, and the visitor's timeline before the form.
Every website lead carries the visit that produced it: the ad or search, the landing page, the device and location, the pages viewed and how long they spent before the form. Repeat submissions within half an hour merge into one lead, and phone-only leads are fine.
In the portal and the LeadPulse app, clients see their leads as they arrive, change the status, add notes and record the sale when the job closes. That one habit is what turns your reporting from clicks into revenue — and it takes the client seconds.
Better to find this out here than three weeks in.
Start a 14-day trial with 300 credits. Add your first client and send an onboarding link today.
Lead management for agencies starts with a shared definition of the work entering the pipeline. A new sales enquiry, a supplier pitch and a message from an existing customer may all arrive through a website, but they should not all be interpreted as new acquisition opportunities. Review a sample with the client before discussing campaign quality. Decide what information makes an enquiry relevant and what outcome should be recorded when it is unsuitable. This agreement gives the agency a fair basis for evaluating traffic and gives the client's team a practical way to work the list. The software captures the record; the business context determines what that record means.
The shared stages are New, Contacted, Qualified, Converted and Lost. Write a short operating definition for each that everyone using the account can follow. Contacted could mean that the team has made its agreed first attempt, while Qualified should reflect the client's actual suitability criteria. Define the point at which a lead becomes Converted and distinguish that status from recording the value of a sale. A consistent definition is more useful than a perfect label. Without it, one employee may mark a lead converted after a booking while another waits until payment, making the same pipeline report describe two different business processes.
A captured lead still needs someone to act on it. Agree who checks new enquiries during the client's working day and how coverage works during absence or busy periods. The first response should reference what the person asked, confirm whether the business can help and establish the next step. Add a note that another colleague can understand rather than relying on memory. If contact is unsuccessful, record the attempt and the appropriate follow-up plan. This is an operating practice for the client and agency to agree; capturing a form alone does not establish that anyone has spoken to the prospective customer or assessed their needs.
A lead's channel, campaign and landing page provide context for a quality discussion. If a client says the latest enquiries are poor, inspect examples rather than assuming the entire campaign failed. Look for a mismatch between the advertised service and the request, an area the business does not serve, or contact details that need review. Compare those observations with the page and offer that produced the enquiry. A useful agency response identifies the pattern and proposes an adjustment. A source label explains how an enquiry arrived, while the client's notes explain whether the business could turn it into useful work.
A practical lead note records what was learned, what should happen next and who is expecting it. For an illustrative repair business, a note might say that the customer needs an appointment next week, has supplied the model number and is waiting for a quote. That is more useful than a vague label such as good lead. Avoid putting unnecessary sensitive information in a routine sales note. Show the client a few examples during onboarding so the habit feels manageable. The goal is continuity: whoever opens the lead next should be able to continue the conversation without asking the prospective customer to repeat every detail.
Marketing reporting becomes more useful when the client records what happened commercially. Add the job or sale value to the lead when the agreed outcome is known, and keep repeat work and refunds accurate. Explain who is responsible for entering this information and when it should be reviewed. An enquiry marked Converted with no recorded sale cannot provide the same revenue evidence as a complete sales record. Equally, a quoted amount should not be casually described as cash collected. Agree the business meaning of the available sales states and apply it consistently so the agency can discuss revenue with an honest view of the underlying records.
A monthly review should include leads that have not been evaluated, leads with incomplete contact details and outcomes that were never updated. These exceptions can distort the picture even when the campaign data is correct. Ask the client to review a manageable set before the reporting meeting, especially when sales take longer than the reporting period. Explain the difference between a weak conversion result and an incomplete follow-up record. A shared pipeline helps both sides see the same evidence, but it still depends on timely updates. The purpose of the review is to improve decisions rather than assign blame for every enquiry that did not become a sale.
Separate the agency's responsibilities from the client's sales responsibilities, then connect them through the lead record. The agency can investigate targeting, message alignment and form behavior; the client can explain suitability, availability, quotes and closing outcomes. Review a few representative records together and select one specific improvement for each side. For example, an illustrative campaign might need clearer service-area wording while the client needs a more consistent callback routine. Document both decisions and review their effects later. This makes lead management part of the service relationship rather than a list the agency sends once a month and the client has to interpret alone.
Before moving a client into the shared pipeline, identify where new enquiries currently arrive and who acts on them. Test each intended capture source and make sure the client can find and update a representative lead. The published workflow does not offer a bulk spreadsheet lead import, so do not promise a historical migration through that route. Decide how the client will finish older opportunities while new enquiries enter the agreed process. A small, clearly explained transition reduces the chance of missed follow-up or duplicate work. Keep the original source system available as appropriate until the team understands which queue is authoritative for each set of enquiries.
Use criteria the client can actually evaluate, such as the requested service, service area, timing and ability to meet the need. Avoid defining qualified simply as a form with a working phone number. Write down the agreed criteria and use examples so different people apply the same standard when updating the shared pipeline.
Record what happened in the lead note instead of relying on the stage alone. An unanswered callback and a completed needs discussion are different events even if both involve outreach. The next person should know whether they need to try again, prepare an estimate or follow up on an agreed decision.
Start with a smaller habit the client can sustain, such as reviewing new enquiries at a set time and recording sales as they close. Show why the updates change reporting quality. Until the records are complete, describe the missing outcomes clearly instead of assuming that every untouched lead was poor or every conversion was recorded.
The documented pipeline uses fixed stages: New, Contacted, Qualified, Converted and Lost. Map the client's working process to those stages and use notes for the detail needed between them. If a client requires a highly specialized sales process, evaluate that requirement explicitly rather than promising custom stages on this page.
Record the reason it is unsuitable so the agency can investigate whether location targeting, website wording or the customer's understanding contributed. One enquiry does not prove a campaign-wide problem. Repeated examples with clear notes give the team a stronger basis for changing the offer, targeting or explanation of the territory served.
No. It may represent valuable repeat work even though it is not new-customer acquisition. Record the commercial outcome accurately and consider it separately when discussing the campaign's ability to win new customers. Keeping repeat business visible helps explain customer value without overstating how many new relationships the marketing created.
The documented capture workflow merges repeat submissions within half an hour. Review the resulting record before assuming multiple submissions represent separate prospects. When evaluating volume, pay attention to the actual person and request; repeated attempts may reflect a form experience problem, uncertainty about receipt or a genuine follow-up message.
Ask for representative records and the specific reason each was unsuitable. A pattern such as requests for an unoffered service can lead to a concrete change. A general impression without reviewed outcomes is harder to investigate. Use source details and client notes together so the discussion connects marketing context with the actual sales conversation.
The requested service, the reason it was unsuitable, the source or campaign, and a brief account of the contact attempt are usually useful. Keep the note factual. The agency can then compare the enquiry with the landing page and targeting rather than inferring quality from an unanswered phone call or a short message alone.
Treat lead status and sales information as separate parts of a complete record. Update the stage to reflect the agreed outcome and record the sale with its appropriate value and state. Revenue reporting depends on recorded sales, so a converted label alone should not be presented as proof of a specific amount earned.
Review the reasons in context: unsuitable service, unavailable timing, price, lack of contact or a competitor chosen. Some causes suggest marketing changes; others concern sales handling or operational capacity. A respectful discussion uses examples to decide what can improve and recognizes that even relevant enquiries do not all become customers.
The client portal and LeadPulse app support viewing leads, updating status, adding notes and recording sales. Introduce the specific workflow during onboarding and test it with the people who will use it. Mobile access is most useful when the client knows what to update immediately after a real conversation.
Lead count helps describe demand, but it does not establish quality or commercial return. Add the reviewed outcomes, qualified share, recorded sales and source context that are available. Explain incomplete records rather than filling the gaps with assumptions. This gives the client a more useful view of whether marketing is producing work they can serve.
Choose a cadence that matches enquiry volume and the sales cycle. Daily handling can sit alongside a less frequent joint quality review. The important point is to review while the conversations are still understandable and before the reporting meeting depends on stale statuses. Longer sales cycles also need a clear treatment of opportunities still open.
Test the intended capture sources, confirm the client can access the leads, explain the stage definitions and practice recording a note and sale. Review a few real enquiries together after the process begins. Fix gaps in ownership or source capture early, before the team builds its reporting expectations around incomplete or inconsistently maintained records.
