Category: GoHighLevel

  • GoHighLevel Offline Conversions Not Showing – Trace One Event

    GoHighLevel Offline Conversions Not Showing – Trace One Event

    The Google Ads conversion action appears in HighLevel. It has a name, a source and a counting rule. The same action appears in Google Ads, too. But the campaign still shows zero offline conversions, even though the business has booked appointments or closed jobs.

    When GoHighLevel offline conversions are not showing, those two facts can exist together. HighLevel can create the action that tells Google what to measure without sending a single qualifying event. And even after an event leaves a workflow, Google still has to match, process and report it.

    The useful investigation follows one business outcome from the Google ad click to the Google Ads report. It needs more than another screenshot of the conversion-action setup.

    The conversion action is there. Has an event actually been sent?

    HighLevel’s Ad Manager can create an offline conversion action in a connected Google Ads account. The action defines a category such as a qualified lead or purchase, along with choices about counting and value. It does not tell Google that a particular contact has already qualified or bought anything. HighLevel makes that distinction explicit in its October 2026 offline conversion documentation.

    Think about a home-service operator who wants to count qualified inspection bookings. Creating an action called “Qualified Inspection” establishes the measurement target. Somebody must still send an event when a real qualifying booking occurs. In the documented HighLevel workflow route, that means an appropriate trigger followed by the Add to Google Ads action. Another supported import method may handle the event instead, but the administrator needs to know which route the account actually uses.

    For GoHighLevel offline conversions across client accounts, start with the Google Ads customer account and the exact conversion action. In a multi-client agency, the connected Google account, selected Ads customer and HighLevel subaccount are easy to confuse. An action visible in the wrong account is not a substitute for the one used by the campaign that generated the click.

    Take one booking or won job and identify its route

    Pick an actual outcome that should qualify under the business’s definition. A booked consultation is different from a completed appointment. A closed-won opportunity is different from a job that the field-service system has finished. Before searching for a missing Google event, agree on which event the action is meant to count.

    For that one record, note the source ad account and campaign, the HighLevel location, the relevant contact or opportunity reference, the event timestamp with timezone, and the exact conversion-action name. Record how the outcome reached HighLevel. If a dispatch platform holds the final job status, a won-job conversion cannot depend on a change that never comes back to the CRM.

    BrandLyft’s home-service lead-to-job tracking article deals with that earlier job-result handoff. This investigation starts once the required business outcome should be available for the Google Ads conversion path.

    Then follow the record through the workflow that should send the event. Do not assume the workflow exists because the conversion action appears in Ad Manager.

    Failure path one: Google has an action, but nothing tried to send it

    Consider an illustrative agency account. The operator creates an offline conversion action for qualified bookings and sees it in Google Ads. Appointments continue arriving, but the team never added Add to Google Ads to the workflow that handles qualified bookings.

    If this workflow is the intended import route, no conversion event will reach Google through it until the workflow sends one. The first place to look is not the Google reporting date range. It is the actual HighLevel workflow: its published status, trigger, filters, contact path and downstream action. Does it fire when a booking qualifies, or only when the form first submits? Does the contact reach the Google Ads action, or leave through another branch?

    HighLevel’s Add to Google Ads workflow guide explains the conversion selection and Execution Logs. Check whether the selected action matches the intended conversion name, including capitalization and spacing, and whether a workflow execution actually reaches it. The absence of an event attempt is a different finding from a logged attempt that Google later rejects.

    This example does not claim an observed client failure. It identifies the first causal break to test. Creating a second conversion action would not repair a workflow that never sends the first one.

    Failure path two: the workflow reaches the action, but the click cannot be matched

    Another account has the correct conversion action and a published workflow. A qualified booking reaches the Add to Google Ads step. That is progress, but it does not establish valid Google Ads attribution.

    For HighLevel’s documented click-based workflow route, the contact needs the supported advertising click identifier from the earlier ad interaction. HighLevel lists GCLID, GBRAID and WBRAID, with rules that depend on the conversion and identifier type. A UTM campaign label may be helpful for internal source reporting, but it does not replace the required matching data for this route.

    Imagine a contact whose source says “Google Ads” because somebody selected that value manually. The record may be commercially useful, yet it has no verified Google click identifier. The workflow could reach its Google action and still fail the attribution requirement. HighLevel documents a Skipped result for problems such as a missing identifier or mismatched conversion name. A different log result may indicate the action attempted a send; that still does not prove Google counted it.

    Wholesale flower worker inspecting an untagged bundle of white lisianthus beside other flower shipments with identification bands.
    A real shipment can arrive without enough information to identify its source. Similarly, a valid CRM outcome may lack the click evidence required for Google Ads offline conversion attribution.

    Check the identifier’s presence through the account’s authorized, privacy-safe diagnostic view. Also check where the click entered: an ad to a tracked website form may preserve evidence that a manually entered lead or an unrelated phone call cannot provide. Avoid adding a made-up GCLID or recycling somebody else’s identifier to make the test appear successful.

    Read the HighLevel execution result, then check Google’s side

    The workflow log and the Google Ads report answer different questions. In HighLevel, first establish whether the expected trigger ran, whether the contact reached Add to Google Ads, and whether the action was executed or skipped. Save the exact log time and error text where the system exposes them.

    Next move into the same Google Ads account. Google’s offline data diagnostics can show upload history, data quality and alerts for imported events. Its “No recent data” status means the action has not received recent events in the diagnostic window; it does not identify which earlier step failed. Look for an attempted import, an error, or a processing outcome that corresponds to your event and time.

    A HighLevel step marked Executed is evidence about that workflow action. It is not proof that Google attributed the conversion to the campaign. Google distinguishes upload errors from discrepancies after a successful upload, including wrong account ownership, invalid conversion time, an old identifier, duplicate or one-per-click counting, and processing delays. Follow the evidence to the side that can answer the next question.

    Zero in the campaign column may be a reporting question

    Suppose Google has processed an event, but the marketer is looking at the main Conversions column for one campaign. That column does not always contain every conversion action. Google distinguishes primary actions used for bidding from secondary actions tracked for observation. The All conversions column can include secondary actions that the main column does not show. Check the action and campaign goal settings before concluding that nothing arrived.

    Dates can cause another misleading comparison. Google generally attributes a conversion to the time of the related ad interaction in standard reporting, not to the day staff marked a job won or the day an event was uploaded. The by conversion time columns answer a different date question. An Ads report filtered only to today’s clicks may miss a conversion from an earlier click, even when the CRM outcome happened today.

    Google also documents processing delays. Many imported events appear sooner, but some GBRAID or WBRAID-keyed conversions can take up to 72 hours to reach reports. That is a documented possible delay, not permission to assume every zero will fix itself after three days. Check diagnostics and the correct date range first.

    Keep these stages separate in the action-to-event trace

    A small evidence sheet is more useful than several unrelated green checkmarks. One row should correspond to one eligible business outcome, using internal references instead of exposing personal details in a shared troubleshooting document.

    HandoffEvidence to recordHOLD condition
    Google Ads setupCustomer account, conversion name, source and counting ruleWrong account or action
    Click evidenceEligible ad path, permitted identifier type and availabilityNo valid matching evidence for chosen route
    Business outcomeBooking or job reference, qualifying status and event timeEvent definition or timestamp is uncertain
    HighLevel workflowActual trigger, selected action, execution or skip resultNo run or action skipped
    Google processingImport diagnostics, errors or accepted event evidenceNo received event or unresolved error
    Reporting decisionCorrect campaign, columns, click-date range and named ownerResult still cannot be reconciled

    Use PASS only for the specific handoff that the evidence confirms. A workflow execution can pass while Google processing remains on HOLD. Likewise, a processed event may pass the upload check while its campaign reporting still needs investigation.

    The import method itself needs a current check

    There is an October 2026 detail that older setup tutorials may miss. Google has updated its offline conversion import requirements and is transitioning upload routes toward the Data Manager API. Its 2026 enhanced-conversions changes describe restrictions on legacy Google Ads API uploads. That does not establish that every current HighLevel workflow is incompatible.

    It means the person responsible for the connection should verify which supported route actually sent the event and whether Google accepted it. An action that still appears in the conversion list tells you nothing about the current event transport. If provider logs or diagnostics point to a blocked or outdated import method, confirm the supported replacement with the integration owner before rebuilding workflows or changing conversion goals.

    For a wider problem involving expected events disappearing between systems, BrandLyft’s GoHighLevel integration monitoring guide explains how to match source events with what the receiving system recorded. The Google Ads case needs that same discipline, with Google’s own conversion processing added to the comparison.

    Run a controlled test without manufacturing a conversion

    Choose one authorized test journey that genuinely uses the supported ad-click and import route. Agree on the conversion action and outcome before the test. Keep the test contact or opportunity distinct from production records, and avoid sending private identifiers in screenshots or public tickets. A dummy contact with no eligible ad interaction can help test workflow routing, but it cannot prove Google Ads click attribution.

    Verify the workflow and Google Ads results separately

    At the agreed outcome, confirm that the right workflow fired and reached the selected Google Ads action. Save the execution result and its time. Then inspect the corresponding import diagnostics and, after the applicable processing window, the appropriate Google Ads conversion column and date range. If no eligible test click is available, mark the Ads attribution test NOT TESTED rather than calling it successful.

    Use real event timestamps and any required value only when the business has a defensible definition for them. A completed job’s invoice amount should not become a guessed conversion value just to populate a field. Before retrying a failed upload, check the original event and Google’s duplicate rules so one outcome does not create conflicting records.

    The troubleshooting record should let another administrator point to the first missing proof: no qualifying outcome, no workflow attempt, a skipped action, a Google import problem, or a reporting view that omitted the result. Each leads to a different correction.

    For teams connecting paid leads to booked and won work

    Review the campaign and CRM reporting path together

    BrandLyft’s Paid Ads Management service covers Google campaigns, lead follow-up and reporting beyond form submissions. See the service scope if your team needs paid traffic and downstream outcomes measured as one operating process.

    Explore Paid Ads Management

    When Google Ads shows zero for GoHighLevel offline conversions, find the last stage with evidence before changing anything. A saved conversion action is the starting point. The event attempt, Google’s processing result and the report each need their own answer.

  • GoHighLevel Appointment Wrong Time: Check the Saved Booking First

    GoHighLevel Appointment Wrong Time: Check the Saved Booking First

    A three-hour difference in a GoHighLevel calendar is not enough reason to move an appointment. A manager in California might see noon while a New York branch sees 3:00 PM, and both could be looking at the same booking. The real problem starts when the customer expects 3:00 PM in New York but the appointment itself was created for 6:00 PM there.

    If you are investigating a GoHighLevel appointment wrong time complaint, work from the saved appointment outward. Find out whether someone is viewing the correct moment in another timezone, whether the booking action interpreted the customer’s choice incorrectly, or whether a confirmation or reminder says something that does not match the appointment. Those cases can look identical in screenshots. They need different corrections.

    Start with the one appointment people disagree about

    Before changing a calendar preference, identify the disputed appointment. Record the HighLevel subaccount, calendar, appointment record or ID where available, scheduled date, intended branch-local clock time, and how the customer booked. Was it the public booking page, a staff member booking manually, or a workflow’s Book Appointment action? That last detail matters because each path can interpret a time differently.

    Ask the branch for the appointment time it actually promised. If a consultation must take place at 3:00 PM New York time, record that with the full date and timezone. A screenshot showing only “3:00 PM” does not establish what moment the customer and staff agreed on. The same is true of an old text message that says “tomorrow at three.”

    Keep the received confirmation or reminder alongside the appointment record. When several employees are comparing screens, capture which location and timezone each person was viewing. Do not change the customer’s appointment just to make two screens show the same number.

    A different calendar display can still describe the right appointment

    HighLevel has a user-specific setting called View Appointments In under Calendar Settings > Preferences. It controls how the logged-in person sees appointments in supported calendar views, appointment lists, contact appointment sections, and conversations. Each user can select a preferred timezone. Changing this preference does not change availability, booking links, the scheduled appointment, or confirmation and reminder logic. HighLevel documents that separation in its appointment viewing timezone guide.

    Take Thursday, October 22, 2026. An illustrative New York branch has a consultation at 3:00 PM Eastern Daylight Time. A California regional manager with the calendar displayed in Pacific Daylight Time sees 12:00 PM. That is a three-hour difference, but it is the same moment. If the customer has a New York confirmation for 3:00 PM and the saved appointment agrees, there is no booking to repair.

    Check the timezone label in the Calendar View or Appointment List, then open the viewer’s preference. The regional manager may prefer to view every booking in the branch timezone, or keep their own local timezone for the day’s work. Either choice affects their display, not the customer’s reservation. If the manager uses the HighLevel mobile app, check that app’s appointment timezone preference too; it is a viewing control, not an alternate booking system.

    There is a temptation to change the subaccount’s business timezone at this point. Resist it. A business timezone is a different control, and changing it can affect how other parts of the account interpret time. First establish that the supposed mismatch is not simply two people reading the same appointment in their chosen zones.

    A wrong booking can start when a workflow reads the clock time

    Now consider the other version of the complaint. The New York team intends a consultation for 3:00 PM local time, but a workflow passes the value “3:00 PM” to Book Appointment and interprets that value in a California account timezone. On October 22, a booking for 3:00 PM Pacific would be 6:00 PM in New York. The staff calendar and the customer’s message might faithfully show the later appointment, even though nobody intended to book that time.

    Adult music student holding a guitar case while looking toward an empty teaching station inside a professional lesson studio.
    When an appointment is booked for a different time than the branch intended, the customer and service team may be out of sync. The saved booking and its timezone must be checked before making a correction.

    This is an illustrative wrong-booking case, not a BrandLyft customer incident. HighLevel’s Book Appointment timezone update specifically describes how the workflow action reads its Start Date & Time using the selected timezone. The action supports a fixed timezone or a contact-based choice such as Contact Timezone. If the action has no timezone selection, it uses the account timezone by default. The setting applies to that action; it does not redefine every calendar or workflow timezone in HighLevel.

    For an account that books appointments through automation, read the actual workflow action before correcting anything. Where did the start-time value come from? What timezone does the action use to interpret it? Did the contact have the expected timezone when that action ran? Is the correct branch calendar selected? If someone enabled Override Availability, the action can book without the normal availability check. That is another reason a seemingly valid booking deserves an action-level review.

    A manually created appointment calls for a different inspection. HighLevel’s manual booking guide describes appointment-entry views that show or allow time selection in context. Compare the timezone in the actual booking form and the intended local time. Do not diagnose a manual booking from workflow settings that never created it.

    What did the customer see on the booking page?

    The person making the booking may be in a different timezone from the branch they plan to visit. HighLevel supports a contact timezone selector on eligible booking widgets; a business can also disable that choice so the page uses the subaccount timezone. The relevant controls appear in Settings > Business Profile, as described in HighLevel’s contact timezone booking guide.

    Imagine a California customer booking an in-person consultation at a New York location. A customer-facing slot shown as noon Pacific may correspond to 3:00 PM at the branch. That can be perfectly correct. But a customer who assumes the displayed noon is New York time may arrive with the wrong expectation. The problem is no longer just what HighLevel saved; it is whether the booking screen and confirmation made the appointment’s timezone clear.

    Some calendar types have additional booking-page timezone controls, including a lock for service booking pages. Check the actual calendar type and public booking link rather than assuming all widgets offer the same options. Keep this separate from the staff member’s View Appointments In preference, which cannot correct a customer’s booking-page choice.

    The appointment can be right while the reminder is wrong

    A confirmation or reminder creates another place for the clocks to disagree. The saved appointment may be correct and both staff views may convert it correctly, yet the outbound message might use a hard-coded time, the wrong appointment context, or a workflow that runs at an unexpected hour.

    HighLevel supports appointment merge fields including {{appointment.start_time}} and {{appointment.timezone}}. Those fields can help a message show appointment information rather than manually typed clock times. But a merge field still needs the right appointment context. HighLevel’s merge-field reference identifies the available values; it does not prove that every existing email or SMS in a franchise account uses them correctly.

    Compare the delivered reminder with the saved time

    Trace the particular message that reached the customer. Was it a native calendar notification, an appointment-triggered workflow, or another campaign? Look at the rendered message, not only the template editor. Compare the written appointment time and timezone with the saved record. Then check the time the message went out. A reminder that says “3:00 PM” but arrives at an odd hour presents two possible issues: the content may be wrong, or the sending schedule may be wrong. Sometimes both deserve a check.

    For workflow communications, HighLevel’s Workflow Settings guide distinguishes Account Timezone and Contact Timezone for time-dependent steps such as Wait actions and Time Windows. If the contact lacks a timezone, those workflow settings fall back to the account timezone. That rule affects communication timing; it should not be confused with the separate timezone input in the Book Appointment action.

    Ask which event the workflow uses when it schedules a reminder. A fixed delay from workflow entry is not the same as a Wait step tied to the appointment time. A message generated without a matching appointment context can also render differently from one triggered by the actual booking. Find the sending rule before moving a live appointment or editing a customer’s timezone field.

    Two three-hour cases, two different decisions

    The date and region matter. On October 22, 2026, New York and Los Angeles are three hours apart. Case A shows two people viewing one correctly saved appointment. Case B shows a workflow creating an incorrect appointment by reading a New York clock time as Pacific time.

    EvidenceCase A: Display differenceCase B: Booking interpreted in wrong timezone
    Intended New York appointment3:00 PM EDT3:00 PM EDT
    Actual appointment3:00 PM EDT6:00 PM EDT
    California staff view12:00 PM PDT3:00 PM PDT
    Likely source to inspectUser display timezoneBook Appointment timezone and start-time input
    DecisionPASS if customer confirmation matches the intended appointmentHOLD until staff verify the intended time and fix the booking source

    Changing the California viewer’s preference in Case B just to make the screen say noon would hide the discrepancy. The saved appointment would still be three hours later than the New York branch promised.

    Use one appointment as the evidence record

    The most useful record is not a screenshot of every timezone setting. It is a small comparison tied to the same appointment and the exact event that created it. Keep the real customer’s details out of general troubleshooting notes, and record only what the authorized team needs.

    For each disputed booking, capture the branch and calendar, intended date/time with timezone, source of booking, saved appointment time, each viewer’s selected timezone, customer-facing booking-page timezone, rendered confirmation/reminder time, workflow action or sending rule, and final PASS or HOLD decision. Add a named fix owner only when something genuinely needs changing.

    One more complication deserves attention: daylight saving time. A three-hour offset observed in October is not a universal setting. For example, New York is three hours ahead of Phoenix on October 22, 2026, but two hours ahead on January 20, 2027. Phoenix does not change clocks for daylight saving time. Test the actual appointment date and the relevant timezone names rather than subtracting a remembered number of hours.

    Test the fix without editing a customer’s appointment

    If the appointment appears wrong, make a copy of the relevant configuration details before any edit. A test should use an authorized synthetic contact or a clearly controlled test booking, not a live customer’s appointment. Use the same calendar type and booking path, and select a date where the expected offset can be calculated independently. Where the workflow books the appointment, test that workflow action under the intended timezone. Where the complaint concerns reminders, test the actual delivery method and inspect the received message.

    The test needs one agreed expected instant, with an explicit timezone, before anyone clicks Book. Check the booking record after creation, then view it from the two staff timezones and read the delivered test confirmation. If the team expects 3:00 PM New York, that is the reference. Another employee seeing noon California should not fail the test by itself.

    Rescheduling a real appointment can fire notifications or appointment-based workflows. HighLevel also allows appointment triggers to re-enter workflows under conditions described in its workflow documentation. Before a correction, identify who is allowed to contact the customer, which reminders are pending, and which system owns the change. That avoids turning one timezone disagreement into two competing appointment notices.

    For calendar changes during an account move, BrandLyft’s GoHighLevel calendar migration guide addresses preserving future bookings and notification ownership. A wrong-time investigation should remain focused on one booking unless it uncovers a migration or replacement-calendar problem.

    When the time still looks wrong across locations

    A regional admin may have access to several subaccounts, each with its own business timezone and calendar configuration. Start with the actual branch, not the admin’s home timezone. BrandLyft’s multi-location setup checklist covers the broader location-level configuration decisions; this diagnosis concerns one saved appointment and the path that produced its time.

    Do not change every subaccount timezone because one manager’s screen appears different. Reconcile the original booking, the selected viewer timezone, and the message that the customer received. If one of them still disagrees, the evidence will show which setting, template, or action deserves an authorized correction.

    For franchise teams with recurring booking discrepancies

    Compare the actual location setup before rebuilding calendars

    BrandLyft’s GoHighLevel for Franchises service covers calendar configuration, local workflows, permissions, and the way each branch uses the CRM. Review the service scope if wrong-time appointments keep appearing across locations.

    See franchise GHL services

    The appointment record tells you when HighLevel currently expects the meeting to happen. The customer’s confirmation tells you what the customer was told. Keep both in front of the person making the correction. A different staff display may be fine; a saved appointment that misses the promised time needs a real fix.

  • GoHighLevel Review Link Opens the Wrong Franchise Location? Trace the URL

    GoHighLevel Review Link Opens the Wrong Franchise Location? Trace the URL

    A customer can receive a review request from the right franchise branch and still open the wrong Google Business Profile. The message mentions the local team. The sender looks familiar. Then the customer taps the link and sees another branch’s name.

    When someone reports a wrong review link in GoHighLevel, the first useful question is not who connected Google. It is which URL reached the customer, and where that URL actually opened. Changing a setting before saving the original message can erase the clue you needed.

    This is a troubleshooting process for an existing multi-location account. It deals with the destination of a review request, not with generating more reviews or transferring one that somebody has already posted.

    First, work out what went to the wrong place

    There are two different complaints that sound similar. In one, a customer clicks a text or email and arrives at the wrong branch’s Google listing. In the other, somebody has already published a review on the wrong listing. The first calls for tracing a request link. The second concerns a review already on Google, and changing HighLevel’s link will not move it.

    For the first problem, ask the recipient to identify the business name and city they saw, ideally with a screenshot that excludes personal account details. Keep the original received request. Do not replace it with a newly generated link from the HighLevel settings screen. You need evidence of the message that raised the complaint.

    Also pause that branch’s next batch of review requests until you know where they will open. A one-off incorrect destination is annoying. Sending the same link to the next group of customers makes it harder to separate the original issue from later messages.

    Follow three versions of the URL

    A location’s Review Link setting, the link inside the message, and the final Google page are related, but they are not always the same thing. Some email links pass through a tracking or redirect address before opening their destination. Comparing only the text of the URLs can make a normal redirect look suspicious, or make a wrong destination look correct.

    Under Reputation > Settings > Review Link, the administrator sees the configured link. The received link is the actual clickable URL in the customer’s SMS or email, including any short-link or redirect address. After opening it, check the final destination: the public business profile that appears in the browser.

    Open the received link in a browser outside the HighLevel editor. Read the business name and locality on the destination page, not just the Google logo or the appearance of the review form. A working Google review page can still belong to the wrong branch.

    Google lets a Business Profile owner copy a location’s own review-request URL from Read reviews and Get more reviews. That provides an independent reference for the intended destination. Use Google’s instructions for getting a review link rather than copying an old link out of a different branch’s campaign.

    What the Review Link setting actually controls

    HighLevel offers a review destination through Reputation > Settings > Review Link. Its Custom Link option points requests toward a specified URL. Review Balancing is different: it distributes review traffic among configured platforms. They are separate choices, so check which mode the affected location uses before making changes. HighLevel explains both in its review-request messaging guide.

    The Google connection deserves its own check. HighLevel’s Review Link setup update says the system may select the first connected Google Business Profile page by default when an account has multiple pages. That default is a starting selection, not proof that it matches the franchise location currently sending the request.

    A location can also have a Custom Link without a connected Google Business Profile. Do not treat the presence of a Google-shaped URL as evidence that HighLevel has connected the correct listing. Compare the selected mode, the saved URL, the connected profiles if any, and the intended branch name.

    After you identify a possible correction, run an authorized test before declaring the issue resolved. A better-looking setting is not an acceptance result.

    The email button may deserve more attention than the SMS text

    HighLevel’s SMS review templates can use {{reputation.review_link}} to insert the Review Link for that location. That gives the administrator a clear place to compare the token with the account setting. A copied template containing an older hard-coded address is a different case.

    Email needs a closer look because the visible button may have its own destination. HighLevel’s email builder supports a Review Link element, and its multiple review links feature allows the template editor to select specific connected profiles. An attractive button that says “Leave a review” tells you nothing about which listing it opens until you check the link behind it.

    Review the actual Live email template and any retry template the account uses for that sending path. A screenshot of the email design is useful, but the button’s target matters more than its label. If the template uses a redirect or another configured link, save that detail before editing it.

    This is also where copied franchise assets can cause confusion. Teams may reuse one approved corporate design across branches, but each branch still needs the correct review destination. Reusing the design is reasonable. Sending every branch’s customers to one Google listing is not.

    Find the method that sent this particular request

    Do not assume every request came from the same Reputation screen. HighLevel documents three sending paths: a manual Quick Action, a manual request from the Reputation area, and the Send Review Request workflow action. The official sending guide describes those paths.

    Start with the affected message. Did someone send it manually after a completed job? Did staff use the contact record? Or did a workflow send it when a job, appointment, or opportunity changed status? Find the actual sending location and the asset responsible. A workflow in one branch may use a different request template from a staff member’s manual send in another.

    HighLevel also provides a review-link override option in the request interface. Its availability and choices can depend on the links that the account offers. Check the actual request screen rather than guessing whether someone chose an override. If the default link looks right but the delivered email opens somewhere else, inspect the template or request-specific selection before anybody reconnects Google.

    For broader franchise configuration decisions, BrandLyft’s GoHighLevel multi-location setup checklist covers the surrounding account structure. This review-link problem is narrower: identify the precise outbound path and where it sends the customer.

    A simple branch example shows why the order matters

    Consider an illustrative two-branch franchise with a Northside location and a Lakeside location. Northside sends a review email to a customer who used Northside. The email arrives with Northside’s name, but its button opens Lakeside’s Google listing.

    That observation does not tell the administrator whether Northside’s saved Review Link is wrong, the email template contains a Lakeside-specific URL, or an intermediate redirect points to Lakeside. Each possibility needs a different fix. Reconnecting both Google accounts before comparing the URLs could change several things at once and leave the original cause unknown.

    Check Northside’s saved destination first. If it already points to Lakeside, correct that location-level selection and retest. A correct Northside destination with an email button that still opens Lakeside points the investigation toward the Live template or a request override. When the received URL also looks right but opens Lakeside, follow the redirect chain and check the external destination.

    The example is not a claim that HighLevel caused a real franchise mix-up. It shows how to narrow the cause without guessing.

    Use a review destination acceptance sheet before resending

    A franchise needs one record for each location and sending method that its team checks. Testing the manual request does not automatically clear a separate workflow email. A successful preview inside the builder does not prove the delivered link is correct either.

    Acceptance-sheet fieldWhat the operator recordsWhen to hold the send
    Sending locationHighLevel location name and IDStaff cannot identify which branch sent it
    Intended Google listingPublic business name, city, owner-confirmed review URLNobody has confirmed the expected listing
    Sending methodManual Reputation request, Quick Action, or named workflow; channel and templateThe actual path is unknown
    Configured destinationReview Link mode, selected GBP or saved Custom Link, any overrideThe setting conflicts with the intended listing
    Delivered destinationActual received clickable link and final public Google listingThe final business name or location is wrong
    DecisionTest time, tester, PASS or HOLD, fix owner, retest resultA safe, authorized delivered-link test has not passed

    A PASS means that one specific method, template, and branch opened the correct public listing in an authorized test. It does not mean every future workflow or branch will work. When the destination is still uncertain, record HOLD and leave customer sends paused for that path.

    Make the smallest correction, then verify the delivered result

    Save the original Review Link value, template version, and relevant workflow configuration before editing. Correct a bad location-level destination in that one setting. For a wrong email-button link, update the template instead. Where a request-specific override caused the mix-up, correct that selection if the interface permits it. Avoid changing all three just because the screen is open.

    Run an authorized dummy request through the same sending path that produced the complaint, to a controlled inbox or device. Compare the received link and the final Google listing against the acceptance record. When a franchise uses both SMS and email, test both rather than treating a successful SMS as proof that the email button is correct.

    Ceramics studio craftsperson comparing a newly fired glaze test tile with an approved reference sample under natural window light.
    Correcting a setting is only the first step. Franchise review requests need a delivered-link test that confirms the customer reaches the intended Google Business Profile.

    Also check queued requests, delays, and retries before restarting the campaign. HighLevel supports delayed first sends and retry templates. Correcting a link does not prove the system has cleared or updated requests it already queued. Check what remains scheduled and handle those requests using the account’s actual controls.

    If the destination stays wrong after you correct the relevant setting, keep the original message, its clickable URL, the expected GBP URL, the redirect result, the sending method, and timestamps together. That is a more useful support record than a screenshot of the Review Link setting alone.

    What if the review is already on the wrong Google listing?

    Once somebody posts a review on Google, this becomes a separate issue. Changing a HighLevel Custom Link will affect future routing, not relocate that published review. Google’s review controls and policies govern what people can edit, remove, or report. A business should not assume it can transfer the review between profiles just by reconnecting an integration.

    For future requests, obtain each branch’s link from its own Google Business Profile and confirm it against the name and city on the public page. Google also requires reviews to reflect genuine experiences; a routing test never requires someone to publish a test review.

    If the investigation turns into a wider account-standardization question, BrandLyft’s franchise lead-routing guide deals with the separate issue of getting incoming leads to the right team. Review requests are outbound. Keep the two jobs distinct.

    When the link is only one part of the problem

    Review requests need to reach the right branch every time

    BrandLyft’s Reputation Engine covers review-request timing, follow-up, and the path customers take to leave feedback. If your franchise needs that process reviewed as part of its wider reputation setup, the service page explains the scope.

    Explore the Reputation Engine

    Working across several branches? See BrandLyft’s franchise GHL services.

    Before the next review campaign goes out, somebody should be able to show the original message, the link the customer clicked, and the exact business profile that appeared. If those three records disagree, fix the confirmed difference and test that sending method again. The next customer should not have to discover the mistake.

  • Moving a Franchise Phone Number in GoHighLevel: What Stays Behind

    Moving a Franchise Phone Number in GoHighLevel: What Stays Behind

    A franchise branch is closing. The phone number printed on its vans, business cards, and customer invoices is staying with the business. The plan sounds simple: move that familiar number into another GoHighLevel location and let the receiving team answer it.

    There is a catch: HighLevel can move an eligible number between subaccounts in one agency, but the prior contacts and conversations stay in the source account. Messaging registration and call settings need their own checks. The new branch might have the right number in its phone list and still be unready for the next caller.

    If you need to move a GoHighLevel phone number between subaccounts, the useful decision happens before anyone clicks Move Numbers. What must the destination be able to do on the first call, and what information will remain behind?

    First, identify which kind of number move you’re making

    This article covers one specific case: reassignment of an eligible number between two existing subaccounts under the same HighLevel agency. It does not cover transferring an entire subaccount to another agency or porting a number from an outside carrier.

    According to HighLevel’s September 4, 2026 Move Numbers guidance, the agency-level tool supports LC Phone to LC Phone moves. It also supports Twilio to Twilio moves when both subaccounts share the same Master Twilio account. The in-app route currently supports US and Canadian numbers, with up to ten eligible numbers in one move.

    Those conditions matter when a franchise restructures. Two branches can share a brand and still sit under different agencies or phone providers. A Twilio number under another Master Twilio account is not eligible for the same in-app transfer. A provider change between LC Phone and Twilio belongs to a different process.

    HighLevel’s phone-number migration and porting guide explains the other paths. Use that guide when the agency relationship, provider, or country does not match the same-agency tool. BrandLyft’s multi-location setup checklist covers the wider branch rollout. This move assumes the receiving branch already has its own subaccount.

    The number moves. Five kinds of history and setup do not simply follow it

    Imagine an established branch transferring its main line to a nearby office after the original location closes. The new office knows the telephone number, but a returning customer expects somebody to recognize an unfinished estimate from last month.

    Moving the number alone will not put that estimate conversation in the destination inbox. HighLevel separates the phone number’s assignment from other records stored against a subaccount. That is the central boundary to plan around.

    ItemWhat the move establishesWhat to do separately
    Phone numberEligible number is reassigned to the destination subaccountConfirm the exact number appears in the intended location
    Contacts and conversationsCustomer records and prior threads are not copied with itDecide how authorized staff will find needed history
    AnalyticsPast account reporting does not move with the numberPreserve source-period references before access changes
    Recordings and voicemailsHistorical assets do not automatically transferRetain permitted assets while the source is accessible
    Messaging registrationThe destination’s A2P registration is not carried overConfirm the receiving location and number are ready for messaging
    Call settings and workflowsDo not assume every number setting, assignment, or automation works afterwardReconfigure where needed and run live-path tests

    A familiar number can make a customer assume the person answering has the former location’s account notes, even though those records are still elsewhere. When that assumption is wrong, the receiving team needs a legitimate way to retrieve context. The move did not bring those records over.

    Decide what the receiving team can see before cutting off source access

    Find the relationships that remain active: appointments, open estimates, service issues, unpaid invoices, and promised callbacks. Then establish where those records currently live and which employee can answer questions about them after the transition.

    Commuter bicycle secured in a repair stand with its front wheel removed and tire-service materials on a nearby workbench.
    A familiar number may reach a new branch while unfinished customer work and its history remain associated with the original location. The receiving team needs an approved way to retrieve that context.

    A franchise may keep approved access to the old location for a period. It may retain permitted exports or move selected customer information through a separate process. Each option is a separate data and permission decision. Move Numbers does none of that. Nor does moving the number give staff permission to copy conversations or ignore communication preferences.

    Keep source references with enough detail to explain what happened. If a customer says, “I left a voicemail yesterday,” staff need somewhere to look. Who can access the older voicemail, and when does that access end? An internal owner and an accessible record are better than a promise that someone will somehow find the old thread.

    BrandLyft’s CRM data migration article addresses broader record-selection decisions. For this cutover, ask what history a caller will reasonably expect the next branch to have.

    Check destination messaging registration before relying on texts

    For eligible US local numbers, A2P 10DLC status belongs to the subaccount and its registration. It does not follow the digits alone. After the move, check the destination’s approved brand and campaign, then link the number where required by the messaging setup. A number appearing in the destination’s Phone Numbers screen does not prove it can send compliant business SMS.

    HighLevel’s September 8 A2P number-linking instructions describe the number-level check. In the destination, review the approved campaign and link the number when needed. Then check for the expected A2P Verified indicator. An approved campaign and a linked number are two different conditions.

    Toll-free messaging takes another path. Do not assume a toll-free verification automatically accompanies a transferred number; confirm its status in the receiving account. International and other messaging configurations have their own requirements. Avoid testing outbound SMS through an account that has not met the applicable registration and permission rules.

    Moving a phone number does not create fresh permission for new automated texts, even if the receiving branch serves the same customers. The destination’s consent, opt-out, and communication-preference handling needs review apart from number ownership. A missed-call text-back workflow is particularly easy to overlook because it may send without an employee touching the conversation.

    Write down the call path customers already use

    A franchise number may ring several places depending on the hour: the front desk during business hours, an answering service after closing, or a backup employee when the desk is busy. When nobody answers, callers hear a voicemail greeting, and a separate workflow may offer a callback by text. The same number could also appear as outbound caller ID for staff.

    Inventory the working behavior before moving it. Record forwarding, ring behavior, assigned users, voicemail, recording, whisper messages, business hours, and missed-call handling. Add the workflows that select or reference that number. Then name the intended destination behavior for each one.

    The new branch might need a different greeting and routing rule, which is reasonable if the team planned it. Trouble starts when staff assume the old setup follows the phone number unchanged.

    Check what external systems still publish or reference the number, too. A website, Google Business Profile, directory, ad, or old invoice may still send people to it. Keeping the digits can preserve that entry point, but it does not make the destination’s answering workflow correct.

    The wider question of which branch should own each new lead belongs to BrandLyft’s GoHighLevel lead-routing guide for franchises. This move is smaller: prove that calls to one number reach the intended team.

    Choose the cutover window based on call coverage, not convenience

    An admin may have time to make the change on Friday afternoon. The business might not have anyone available afterward to test every route and fix a failed callback. A less busy window is useful only if someone can stay accountable through the checks.

    Assign the HighLevel admin, test-call recipient, SMS registration owner, and final approver before the move. Someone else should own provider escalation if the setup fails. If a route fails, staff need a supported fallback for customer contact.

    Do not build the plan around a guaranteed zero-interruption cutover. HighLevel does not promise that a moved number arrives with its old routing, messaging approval, and history already usable. Nor does a phone-number move provide a one-click restoration of customer context.

    Set a short validation period after the transfer and tell the receiving team what will be checked. Someone should record the first failed test without marking the transition complete merely because the number shows up on screen.

    Use the in-app move only after the preflight is signed off

    For an eligible same-agency move, go to Agency Settings and open Phone Integration. Under Sub Account Settings, choose Move Numbers. Choose the source and destination subaccounts, select the eligible number or numbers, review the destination, and complete the move. The current interface permits up to ten numbers in one operation.

    Pause before the final action. The source and destination Location IDs should already be in the change record. Confirm the exact number, country, phone provider, and receiving branch against that record. Similar location names are a poor substitute for IDs when the franchise operates several offices in one region.

    Once the number appears in the destination, the transfer itself may be complete. The customer-facing cutover is not. That second decision belongs to the acceptance tests below.

    Phone Number Move Acceptance Sheet

    Use one sheet per moved number, even when several numbers are transferred together. The purpose is to prevent a successful tool action from becoming an unverified declaration that the branch is ready.

    Record the number in international format, both Location IDs, agency, provider, country, planned window, and actual move time. Add test owners and the release approver. Keep any registration evidence and historical-data access decision attached to the same record.

    Acceptance checkEvidence to recordRelease condition
    Identity and eligibilityNumber, provider, source/destination Location IDs, countryCorrect pair and supported move confirmed
    Historical contextOld contact/thread access owner and permitted retained assetsActive customer history has an agreed access path
    Destination numberPost-move number-list verification and timeCorrect number appears in correct location
    Inbound and outbound voiceTest caller, time, answered by, displayed outbound caller IDBoth directions reach intended people
    Unanswered and after-hoursVoicemail, forwarding, fallback and callback resultsCoverage matches the branch’s operating rule
    Messaging registration and consentA2P/campaign or toll-free status; permitted test recipientApplicable approval and number linking verified
    Inbound and outbound SMSTest time, sending number, receiving account and delivery resultBoth directions work where SMS is enabled
    Release or holdExceptions, owner, next check time, approving operatorBlocking failures resolved or covered by an approved fallback

    The sheet should allow three outcomes for every test: Pass, Blocked, or Not applicable with a reason. A blank SMS result is not a pass. A branch that does not use SMS should say so rather than inventing a successful messaging test. Review the final release decision once every required row has an owner and result.

    Run the tests from outside the destination, not just inside the settings screen

    Start with an inbound call from an external test handset. Check whether the right location receives it and whether the intended staff member answers. Then make an outbound call and confirm which caller ID the recipient actually sees. Outbound-number preferences can differ from what the team expects, especially when users have access to more than one number.

    Next, test an unanswered call. Listen to the voicemail or forwarding behavior rather than reading the configuration and assuming it is correct. For an after-hours path, use an approved test window or a safe configuration review. Do not interfere with real callers. Any missed-call text-back path should be included when messaging is allowed.

    For SMS, use an authorized test contact after checking the destination’s registration and consent requirements, then send an inbound message and verify the receiving account. Then send an outbound reply through the intended workflow or operator and verify the recipient sees the right sender. Record failures and their error details, not just a checkbox.

    Finally, inspect a test conversation and associated task or alert. Does the destination team see the message, know who owns the reply, and receive the expected notification? The tests should reflect real branch behavior. One call from the admin who moved the number is not enough.

    A failed test changes the release decision

    Voice may work while SMS fails because the number still lacks the appropriate campaign link in the destination. That is an incomplete handoff. Keep that messaging path on hold while the registration issue is resolved. Do not send unregistered automated texts simply because calls are now reaching the correct office.

    If calls reach the wrong employee, check forwarding, assignments, and the number’s configuration first. If customers cannot reach the destination, use the planned escalation path and an accurate temporary contact method. Moving the number back is not a guaranteed rollback. It could require another eligible move, setup work, and the same tests.

    If an eligible LC Phone move fails, HighLevel asks for both Location IDs and the affected numbers when contacting Support. Keep the failed action, error, time, and support reference in the change record. When the provider is unsupported, use the applicable migration process instead of repeating the failed attempt.

    Do not declare the cutover complete while the receiving branch is unready

    The destination must own the number, the intended team must answer its calls, and any active messaging path must have its required registration. Older customer context needs an agreed access route, too. An authorized operator should sign off on any remaining exceptions.

    That is how a familiar franchise phone number can keep doing its job after the office behind it changes. The number itself is only one part of the handoff.

    The cutover decision

    The number moved. Is the branch ready to answer it?

    If the move affects calls, missed-call texts, or active conversations, a discovery call can help identify the relevant review scope.

    Before release: Voice tested  •  Messaging verified  •  History access assigned

    Discuss your number cutover

    Exploring the broader franchise setup? See BrandLyft’s GoHighLevel for Franchises service.

  • Are Angi Leads Worth the Cost? Track What Won Jobs Actually Earned

    Are Angi Leads Worth the Cost? Track What Won Jobs Actually Earned

    The estimator got the job. In GoHighLevel, the opportunity is marked Won, with a $4,800 value beside it. That looks like a good outcome for a lead the company paid to receive. But the work may still be on the schedule, the final invoice may be different, and nobody has checked what it cost to complete.

    This is where Angi lead ROI for contractors becomes a different question from lead response or estimate booking. A won estimate can be good news. It cannot tell you whether the Angi lead was profitable. To answer that, the original charge needs to meet the completed-job record and the actual financial result.

    BrandLyft’s Angi and HomeAdvisor lead follow-up guide covers what happens from a paid inquiry through the estimate process. Here, the estimate decision is already recorded. We need to find out what the business earned, what it spent, and which numbers are still unconfirmed.

    Go straight to the paid-lead profitability worksheet if your Angi charges and job records are ready.

    A Won opportunity is not the same as a completed, paid job

    HighLevel’s Lead Source Report, updated October 6, 2026, groups opportunities by their recorded source, status, and value. It lets a user open the underlying opportunity records and see missing sources. That is useful when a contractor wants to know what happened to the inquiries coming from Angi.

    But the report counts opportunities, not unique purchased lead charges. One customer with three opportunities can appear three times. And an opportunity value might have come from the initial estimate, a salesperson’s update, or an automation. HighLevel’s own reporting FAQ says that its dashboard revenue based on Won opportunities is the sum of their monetary values, not the payments actually received.

    A contractor needs three different confirmations after marking a deal Won. Did the customer accept the scope and price? Was the job completed and its final revenue recorded? How much was collected, and what did the work actually cost?

    Those facts may live in field-service software, invoicing tools, payroll records, or the accounting system. A CRM report can point you toward the jobs. It does not automatically settle the accounts.

    Start with charged Angi leads, not every marketplace record

    Before calculating cost per won job, count what the contractor actually paid for. In Angi’s current terminology, an Opportunity is a homeowner project the pro can review. A lead is a connection that supplies contact details and may trigger a fee. The billing arrangement depends on how the business receives leads and on its account terms. A GoHighLevel opportunity is a separate CRM sales record.

    Those distinctions were important to intake in the earlier article. Here they matter for a narrower reason: the denominator for paid-lead economics must reflect charges, not the number of GHL opportunities, contact profiles, or marketplace projects someone opened.

    Angi’s billing guidance says lead pricing varies by task, location, and demand. Subscription and pay-per-lead arrangements also have different billing patterns. Pull the actual statement for the period. Do not multiply lead count by a supposed average Angi price from another contractor’s article.

    A delivery can also reach your CRM more than once without creating another charge. Angi’s partner API reference describes a unique lead ID, leadOid, a service request ID, srOid, and a fee field. It also documents delivery retries when an endpoint fails. The available integration data may differ by connection, so check your receiving records rather than assuming those fields were preserved.

    Keep the billed lead and its source identifier once. A second webhook delivery should not create a second purchase in the profitability worksheet. If Angi actually billed the same lead twice, preserve both billing lines and investigate the credit separately; hiding the second charge as a technical duplicate would understate spend.

    If the source IDs never reach your CRM, BrandLyft’s earlier Angi integration guide explains the receiving connection. The financial check here needs those purchases and their charges to remain traceable after the first handoff.

    Match one lead to its jobs without multiplying the customers

    A person may call about gutter work in March and buy a roof repair in July. That’s one contact with different service requests. Another homeowner may accept an estimate that turns into two separately billed jobs. The financial record has to handle both situations without inventing more leads or more customers.

    The matching rule should start with the paid lead identifier, the original service request, and the GHL opportunity ID. When the estimator records acceptance, add the actual job ID from the system that controls scheduling and billing. Save that relationship even if the office later renames the opportunity or the customer returns for different work.

    Where one paid inquiry leads to several genuine jobs, link each job to the original lead, while keeping the lead fee only once. If two different paid inquiries may have influenced the same job, mark the attribution as disputed. Pick a documented primary attribution rule or a clearly identified allocation method before assigning revenue. Counting the full job under both leads would make the channel look twice as productive.

    There will be imperfect matches. Some job systems have no Angi lead ID, and a technician may open a fresh customer profile. Use the address, job reference, contact history, and acceptance paperwork to investigate. Mark the link Verified, Probable, or Unknown. That last category is a reporting gap, not a zero-dollar job.

    Subtract only credits you can actually support

    A paid lead that does not turn into work is not automatically eligible for a credit. Angi’s lead-credit guidance describes possible reviews for problems such as invalid contact details, service mismatches, wrong locations, or duplicate charges. It also excludes ordinary outcomes such as a homeowner choosing another contractor. Eligibility and deadlines depend on the current account rules.

    Separate the stages in your cost record. A requested credit is not an approved credit. An approved credit is not necessarily cash refunded. Angi says issued credits are applied toward future lead charges, with expiration conditions. Subscription accounts have different treatment.

    For financial reporting, record the original fee, credit status, credited amount, and when that value was actually applied. Attribute it to the original charged lead only once, while retaining the later statement where the credit appeared. Otherwise you might subtract the same adjustment from the old lead cohort and again from next month’s purchase total.

    Include any fixed Angi account expense or other directly attributable acquisition charges under a documented allocation rule. A contractor with a subscription should not treat a nominal per-lead field as the whole channel cost if other required fees were paid.

    What the job record must prove after the estimate is accepted

    Once a job is sold, the opportunity value becomes a reference point. It is not the final number to place in a profit calculation.

    Take a quoted roof repair worth $4,800. The scope changes after work begins, and the final customer invoice is $5,150. The crew uses $2,100 in materials, $1,350 in direct labor, and $300 in subcontractor costs. Before other direct job expenses, that leaves $1,400 of job gross profit based on the final revenue figure, assuming the revenue is properly recognized.

    That example still says nothing about whether the customer paid the invoice. Nor does it include the cost of obtaining the lead. If the finance team cannot establish the job’s actual direct costs, the gross-profit field should remain unverified instead of quietly treating missing costs as zero.

    For each matched job, record its accepted date, completion date, final invoice, recognized job revenue, cash collected, and direct job costs. Direct costs normally include job labor, materials, subcontractors, and other costs directly attributable to doing that job under the business’s accounting method. Keep lead purchases and related acquisition costs separate. Those are subtracted after job gross profit to show what remains from the lead cohort before other overhead and taxes.

    This is also why a payment is not interchangeable with revenue. A deposit may arrive before completion. An invoice may remain unpaid after a completed job. Track both, and have whoever owns the books confirm which amounts count as recognized revenue.

    A worked example: 20 charged leads, five finished jobs

    The figures below are hypothetical. They are not BrandLyft client results or Angi pricing benchmarks. In this example, each paid lead has a final estimate disposition, and every won job is completed. One invoice is not yet fully collected.

    Cohort measureHypothetical result
    Charged Angi leads20
    Original lead fees (20 x $75)$1,500
    Two confirmed, applied $75 credits-$150
    Net lead spend$1,350
    Qualified estimates completed8
    Won jobs, all subsequently completed5
    Recognized revenue from completed jobs$14,500
    Cash collected so far$13,000
    Verified direct job costs$9,300
    Job gross profit$5,200
    After net lead spend, before other overhead and taxes$3,850

    Cost per qualified estimate is $1,350 divided by eight, or $168.75. Cost per won job is $1,350 divided by five, or $270. Those denominators include the cost of unsuccessful purchased leads. Using only the five leads that won jobs would make acquisition appear much cheaper than it was.

    The $5,200 job gross profit comes from $14,500 in recognized revenue minus $9,300 of direct job costs. Subtracting the $1,350 in net acquisition spend leaves $3,850 before other operating costs and taxes. That is an acquisition-adjusted contribution, not the company’s final net profit.

    There is still $1,500 in revenue not collected in this example. The recognized-revenue calculation and the cash position therefore tell different stories. Before spending more on Angi, review that unpaid balance. The projected financial result is not cash already available.

    Don’t compare fresh leads with jobs that have had time to finish

    Roofing jobs bought through October leads may not finish until November. Remodeling estimates can also take weeks to turn into firm decisions. If you divide October charges by only October’s completed work, the source may look poor simply because the jobs have not had time to close.

    Group purchases by the date the charged lead arrived. Then follow each cohort through estimate, acceptance, completion, and collection. Show the reporting as-of date, the number of still-open jobs, and the number of completed jobs with missing cost or payment evidence.

    Partially installed kitchen cabinets with unfinished toe-kick trim and installation materials in a residential remodeling project.
    A purchased lead can turn into real work before the job is finished. Profitability comparisons need to account for jobs that have not yet reached a verified financial outcome.

    Compare cohorts at equivalent maturity, such as the same number of days after lead delivery, or wait until each cohort is sufficiently resolved. The appropriate window depends on the trade and its real job cycle; no universal 30-, 60-, or 90-day cutoff can make slow projects instantly comparable.

    Also compare like with like. A set of emergency pest-control jobs and a set of full roof replacements may carry very different margins and delays. Service type, territory, and billing arrangement can explain differences that a single Angi-wide total conceals.

    Contractor Paid Lead Profitability Worksheet

    Start with one line per billed lead and a separate line for each real job. Keeping those ledgers apart prevents the same lead fee from being repeated every time one customer buys another service.

    Paid-lead ledgerCompleted-job ledger
    Lead ID, service-request ID, arrival date and tradeJob ID and linked source lead ID
    Actual billed fee and account-cost allocationEstimate acceptance and completion dates
    Credit status, credited amount and application dateFinal invoice and recognized job revenue
    Qualified estimate result and GHL opportunity IDCash collected and any amount still due
    Original source, match confidence and exceptionsDirect job costs, gross profit, source confidence and lead-to-job lag

    A completed row should let someone open the original Angi charge, the corresponding estimate, the job record, and the payment evidence. Use the same lead ID on the job ledger only when the link is supportable. Leave uncertain matches flagged for investigation.

    From the completed records, calculate net acquisition spend, cost per qualified estimate, cost per won job, verified completed-job gross profit, and the amount remaining after acquisition expense. Publish those numbers with the cohort window and exclusions. This worksheet is an operating method, not a claim that HighLevel natively reconciles all those systems.

    What to do when a source looks expensive

    A poor result does not always mean every Angi lead should be stopped. The place where the numbers go wrong matters.

    If valid paid inquiries rarely receive a completed estimate, check contact attempts and estimator coverage before making a profitability judgment. Those leads may be losing their chance long before pricing becomes relevant. If estimates are completed but rarely accepted, review trade fit, quoting, and sales follow-through.

    Another possibility is that jobs sell but leave little gross profit. That calls for looking at job scope, quoted prices, direct costs, and the types of projects being purchased. More aggressive follow-up will not repair a consistently underpriced job.

    When certain trades or ZIP codes repeatedly show weak financial results, restrict the lead types or areas you buy and measure the next completed cohort. If the data is incomplete, repair the source-to-job link before treating an absence of recorded profit as proof of a loss. And if the channel still fails an appropriate margin test after the reporting and sales issues are understood, stopping or reducing spend is a reasonable business decision.

    Follow the fee past the Won column

    At the estimate stage, the question is whether the business can turn a purchased inquiry into a real opportunity. After the job closes, it changes. Which Angi charges produced work, which jobs were completed, what did those jobs earn, and how much of that money was actually collected?

    GoHighLevel can help identify the original opportunity and the recorded source. A completed-job and finance record must supply the rest. Once those records meet, the contractor can decide whether to keep buying the same lead types, change the follow-through, or put the money somewhere else.

    Before the next Angi purchase

    You have the Won count. Can you prove the profit?

    An Angi charge, a finished job, and the payment record should point to the same work. When that trail stops at a CRM opportunity, it may be time to review how your systems exchange the result.

    PAID LEAD JOB RECORD PAYMENT + COSTS

    Discuss lead-to-job tracking

    Want to see the implementation approach first? Explore Revenue System Build.

  • When a Franchise Changes a KPI Definition – How to Keep GoHighLevel Reports Comparable

    When a Franchise Changes a KPI Definition – How to Keep GoHighLevel Reports Comparable

    A franchise reports 100 booked appointments for September and 95 for October. The dashboard shows a decline. But September counted bookings that were later cancelled, while October excludes them. Leadership is comparing two different measurements under the same label.

    Franchise KPI definition changes can make a location appear to improve or fall behind without a matching change in its actual work. This is particularly easy to miss when several GoHighLevel locations feed a corporate report. Someone updates a filter or a workflow rule, and the chart keeps looking familiar.

    The question is not which KPIs a franchise ought to track. BrandLyft’s multi-location reporting guide covers that decision. The problem here starts after leadership has chosen a metric and somebody wants to change what qualifies for it. Before the next report goes out, the team needs to decide what happens to the old numbers.

    One changed booking rule can reverse the trend

    Consider a fictional two-month example. In September, the franchise created 100 appointments. Twenty had been cancelled by the reporting cutoff. October produced 110 bookings, with 15 cancelled by the same cutoff. There is no claim here about BrandLyft client results; these figures simply show what a definition change does to a comparison.

    Under the original rule, all appointments booked during the month count, including those later cancelled. The comparable totals are September 100 and October 110, a 10% increase.

    Under the revised rule, appointments cancelled by the month-end cutoff are excluded. September becomes 80 and October becomes 95, an 18.75% increase on that basis.

    Now suppose the franchise leaves September at 100 but publishes October at 95. The displayed result is a 5% decline. Nothing in that comparison tells leadership whether booking activity weakened. It mainly reveals that the definition changed between the two months.

    Even the cancellation cutoff needs attention. Does the metric describe the appointment’s status at the end of its booking month, or whatever status appears when somebody opens the dashboard later? Those are not interchangeable rules.

    Write down the old rule before anyone edits a report

    The existing formula is often described casually: “We count appointments booked.” That is too loose for a change request. The record needs to say what one booking represents, which calendars qualify, and the date used to place it in a reporting month.

    For the example above, the old rule is specific: count each distinct appointment first created during the reporting month, including appointments cancelled by that month’s reporting cutoff. The new rule keeps the same booking date and population but excludes cancellations recorded by that cutoff.

    That also means settling the treatment of reschedules, no-shows, appointments created by staff, and repeat bookings for the same person. A rescheduled appointment might generate another event in a connected tool. It should not automatically become a second booking if the metric is meant to count unique booking decisions.

    A qualified-lead definition needs the same care. Changing from “contactable inquiry” to “inquiry inside the service area with a confirmed job type” changes who qualifies. Record the inclusion and exclusion rules, not just a revised pipeline stage name.

    Where reporting uses a ratio, capture both its numerator and denominator. A better-looking booking rate means very little if the counted bookings changed but the lead population did not, or the other way around.

    Find everywhere the definition is already being used

    The change request may begin with one corporate dashboard, but the number may also appear in regional reports, emailed summaries, location scorecards, incentive calculations, and management presentations. Some teams may use it to decide which branch receives more ad budget.

    GoHighLevel can hold appointments in several calendars and opportunities in separate pipelines. A franchise may also receive a booking event from another scheduling or operating system. Make an affected-location list and name the source used by each one. Do this before changing shared filters.

    The location review needs to identify the reporting assets, not just their names. Which calendar groups supply the booking count? Are opportunity stages being treated as appointments? Does one location record cancellations in GHL while another updates them only in external software? Could a workflow change alter the status used by the report?

    Where available in the account, HighLevel supports custom metrics with formulas, filters and date properties. That gives operators ways to calculate business-specific measures, but the same metric can become unreliable when its underlying fields differ by location. HighLevel also notes that formulas moved with Snapshots depend on the destination account having the required data sources and fields.

    Where another platform owns the booking or job event, document that boundary rather than treating an incomplete GHL record as proof nothing happened. BrandLyft’s franchise integrations guide deals with those wider system boundaries. This change request only needs the sources that affect the KPI being revised.

    Choose an effective date or recalculate history

    There are two legitimate ways to release a changed definition. Neither should be selected just because the dashboard builder makes it easy.

    Prospective change: the new rule takes effect on an approved date. Earlier periods retain their original basis. Leadership sees a visible break in the series, and comparisons across it carry a note. This is often the safer treatment when old cancellation events or booking timestamps cannot be reconstructed.

    Historical restatement: the team recalculates selected earlier periods using the new rule. That requires trustworthy source records, the same time basis, the same inclusion rules, and documented checks for every affected location. Keep the originally published numbers and label the restated series. A restatement should not quietly overwrite the only copy of the earlier report.

    A third option can help during a transition: publish old-rule and new-rule totals beside each other for a limited overlap period. That reveals the effect of the definition itself before the new version replaces the old one in routine reporting.

    For whichever route is approved, specify the effective date and time zone. A midnight change in one region can land on a different calendar date elsewhere. Also agree on the reporting cutoff. A “September booking” measured as of September 30 is different from that same booking judged by its current status in November.

    Check the records that actually survive in HighLevel

    Being able to export today’s opportunity list does not mean every earlier stage or appointment status can be rebuilt. HighLevel documents CSV exports from Opportunity Smart Lists, but a current-record export is not automatically a time-stamped history of each change.

    There is another reporting trap. HighLevel’s Opportunities Widgets documentation warns that a latest status-change date can reset when a record is reopened. A report using that property may show a different historical result later. Created dates, outcome dates and status-change dates answer different questions.

    HighLevel also provides audit-log CSV exports for authorized users where the feature is available. Its current guidance says in-app audit records are retained for 60 days and completed export files for 30 days. That makes a timely export useful, but it is not a promise of complete appointment-event history or perpetual access.

    Review the actual fields available in each location and any connected booking system. When cancellations were overwritten, records were deleted, or historical status timestamps never existed, mark the period as not safely reconstructable. Changing the formula cannot restore an event that nobody recorded.

    Survey technician brushing dirt from a brass benchmark embedded in older sidewalk concrete beside a recently resurfaced section.
    A preserved survey benchmark remains a reliable reference after its surroundings change. Historical KPI comparisons likewise depend on records that still exist and can be verified.

    Prove the new result with records from both sides of the date

    A test should use recognizable source records, not only a dashboard total. Pull a small set of appointment IDs from the old period and the proposed new period. For each one, record what the old rule counts, what the new rule counts, and why.

    • Cancelled before cutoff: it counts under the example’s old rule but not its new rule.
    • Cancelled after cutoff: check that a frozen month-end number does not change merely because the current status later changed.
    • Rescheduled booking: confirm the defined unit is counted once, even if a connected calendar produces another event.
    • Location with different calendar mapping: verify the same eligibility rule reaches the correct source fields.
    • Unmapped location: record that its result is unavailable for comparison rather than displaying a misleading zero.

    Test both the location-level detail and corporate total. A correct total for one branch cannot establish that every branch uses the revised rule. If a location fails, keep it out of the comparable roll-up until its exception is understood and approved. Show the excluded location and the reason, so leadership can see the limits of the report.

    One more detail can affect the date test. HighLevel’s custom reporting guide describes timezone differences between the browser-based builder and scheduled email previews. Check the actual generated report at the agreed reporting cutoff, not only the screen in the editor.

    Keep a one-page KPI Definition Change Record

    The approval record does not need to be long. It does need to exist outside the changing dashboard settings. Use the following field list as a one-page record for each metric revision. A named owner should complete the entries and attach the evidence before the change goes live.

    Record fieldRequired entry
    Metric and versionExact displayed KPI name, unique change ID, previous version and proposed version
    Previous ruleCounted unit, filters, inclusions, exclusions, date property, reporting cutoff and calculation
    Revised ruleEvery changed condition stated explicitly, including cancellation or qualification treatment
    Effective dateApproved start date, time, reporting time zone and first affected report
    Affected scopeLocation IDs, pipelines, calendar groups, external sources and downstream reports
    History decisionProspective break, historical restatement or dual reporting; periods covered and evidence supporting the choice
    Source gapsMissing fields, unreconstructable periods, unmapped locations and exclusions from the corporate total
    TestsSample record IDs, expected and actual results, pass/fail status and reviewer
    Release and rollbackDashboard/report changes, published comparison note, saved previous configuration and rollback trigger
    Named approvalFranchise operations owner, reporting owner, implementation owner, approval date and communicated locations

    The record belongs with the reporting change ticket or other corporate documentation, where both the old definition and the approval can be found later. It is not a claim that GoHighLevel natively versions KPI definitions or maintains this approval form.

    Make the break visible before reporting growth or decline

    A changed number may feed a corporate slide, a regional ranking, or a decision about coaching and budget. Publish the revised definition and its treatment of history wherever those comparisons are used. If old months remain on the previous basis, label them as such.

    For the fictional booking example, the executive note can be plain: “From October, booked appointments exclude cancellations known by month-end. Earlier months use the previous inclusive definition and are not directly comparable.” If history was recalculated instead, say which months were restated and retain the originally published values.

    Locations that have not mapped the revised rule need an explicit exception or a separate reporting group. Their missing results are not zeros. Likewise, a blank calendar field does not prove the branch booked nothing if its appointments live in another system.

    Check what else uses the metric before releasing it. Reporting emails, scorecards, incentive thresholds, team training, and any dashboard button or next-step instruction tied to the number may require updated wording. Change communications should name the owner of those follow-up edits.

    Rollback is a reporting decision, not a quiet overwrite

    Set rollback conditions before publication. Examples include an unmapped location entering the corporate total, a formula counting the same booking twice, missing cancellation status, or a scheduled report disagreeing with the signed-off samples.

    Keep the prior report configuration and the old published figures. If the new rule fails testing, restore the previously approved reporting view while the team investigates. Avoid bulk-editing underlying bookings simply to make a chart resemble the old result.

    When the corrected definition is ready, repeat the sampled-record checks and secure the same named approval. That may feel slower than changing a dashboard widget. It is quicker than asking every regional manager to explain why last month’s performance suddenly changed.

    Keep the meaning stable when the rule has to change

    Franchise reporting will change as services, calendars and sales processes change. That is reasonable. The problem begins when a new meaning arrives under an old KPI name and leadership reads the difference as business performance.

    Before release, the franchise needs a precise former rule, a precise revised one, a treatment for history, evidence from real records and visible exceptions. Then corporate can compare like with like, or admit that the comparison is not available.

    If your locations already use GHL and reporting definitions need to change across the network, BrandLyft’s GoHighLevel for Franchises service is the relevant implementation path. Book a discovery call to review the affected locations, data sources and reporting decisions before the next corporate report goes out.

  • GoHighLevel for Medical Weight Loss Clinics: From Inquiry to Clinic Handoff

    GoHighLevel for Medical Weight Loss Clinics: From Inquiry to Clinic Handoff

    GoHighLevel for medical weight loss clinics is most useful when its job is clear. A marketing inquiry comes in, the clinic knows where it came from, somebody owns the next step, the person can book or be helped into a consultation, and the follow-up changes as soon as the situation changes.

    The trouble starts when the CRM is expected to become everything else too.

    A medical weight loss clinic may already have a practice-management platform, EHR, billing tools, telehealth software, lab systems, or other clinical technology. GoHighLevel does not need to replace those systems to be useful. It can sit in front of them and handle the marketing-to-consultation path, then hand the conversation to the right employee or system when the work becomes clinical.

    The first decision is where GoHighLevel stops

    Before building forms, workflows, or calendars, decide what belongs in the marketing system and what does not.

    For this kind of clinic, the cleanest boundary is usually the point between a marketing inquiry and the clinic’s legitimate clinical process. GoHighLevel can capture an inquiry, record the source, create or update the contact, assign an owner, offer a consultation time, send approved reminders, and show whether the opportunity moved.

    It should not be treated as the place where an automated workflow decides medical eligibility, recommends treatment, discusses dosing, chooses medication, or replaces the clinic’s medical record.

    That boundary also matters for privacy and compliance. HighLevel’s own documentation says its HIPAA package is an optional account-wide add-on and that HighLevel accounts are not HIPAA compliant by default. Turning on a platform feature is not the same thing as proving a clinic’s whole process is compliant. The clinic still has to decide what information belongs in each system, who can access it, what can be sent through SMS or email, and what its own legal or compliance requirements allow.

    That is a better starting point than building a large workflow first and trying to decide what it was allowed to do afterward.

    Treat the first contact as a marketing inquiry

    A prospect may arrive from a paid ad, a landing page, the main website, a chat widget, a phone call, a referral campaign, or a form tied to a specific location. Those entry points should not become separate little systems that staff have to reconcile later.

    At the marketing stage, the clinic needs enough information to answer a practical question: Who is this person, what did they ask for, where did the inquiry come from, and what should happen next?

    That does not require turning a lead form into a medical questionnaire. In most cases, the marketing form should stay focused on the information needed to respond and route the request. Anything that belongs to clinical intake can stay in the system the clinic already uses for that job.

    Source tracking matters here because a contact without a useful source is harder to evaluate later. HighLevel can record attribution for supported events such as forms, calendar bookings, chat interactions after contact information is submitted, and tracked external forms. That gives the clinic a better chance of separating an inquiry from Google Ads, Meta, organic search, a campaign landing page, or another source instead of relying on a vague “website lead” label.

    The setup still needs testing. If an outside form or integration creates the contact but drops the campaign data, the dashboard can look complete while the source story is wrong.

    A new inquiry needs a real owner

    Fast acknowledgement is useful. Ownership matters more.

    A simple first response can confirm that the clinic received the inquiry and tell the person what happens next. After that, somebody on the clinic side should be responsible for the next legitimate business step.

    For one location, that may be a front-desk employee or consultation coordinator. For a larger group, assignment may depend on location, service area, calendar, business hours, campaign, or staff capacity. HighLevel’s workflow tools can assign contacts to individual users or distribute them across users, including round-robin or weighted splits.

    The rule itself should come from the clinic, not from the software. If nobody can explain who owns an inquiry from a certain location or channel, automation will only make that uncertainty happen faster.

    Clinical questions are another ownership rule. A workflow or AI assistant can handle approved business information such as office hours, location, consultation availability, or how to book. Questions about symptoms, side effects, medication, eligibility, treatment, or patient-specific care need a human handoff defined by the clinic.

    Booking should match the clinic’s actual consultation process

    Some medical weight loss clinics want qualified marketing inquiries to book a consultation directly. Others want staff to speak with the person first. A multi-location group may need the booking path to change by location or consultation type.

    The calendar should reflect that real process rather than forcing every lead through the same link.

    Once a consultation is booked, the marketing system can handle the business-side events around it: confirmation, approved reminders, rescheduling information, and internal notifications. HighLevel supports appointment notifications for booked, confirmed, canceled, rescheduled, reminder, and follow-up events.

    This is where the build starts becoming more than a form connected to a calendar. The pipeline stage, assigned owner, conversation status, calendar, and follow-up workflow all need to agree about what happened.

    BrandLyft’s Revenue System Build is built around that kind of operating path: capture the lead, route it, assign responsibility, follow up, and make the result visible instead of leaving each feature to run by itself.

    Follow-up has to change when the person changes direction

    One generic nurture sequence is rarely enough.

    An inquiry that replies should not keep receiving messages written for somebody who has gone silent. A person who books should move out of “still trying to book” follow-up. Somebody who asks to stop should stop. A lead who needs a staff answer should not be pushed through another automated sales message while the real question sits unanswered.

    The practical workflow is closer to a set of stop conditions than a long sequence.

    An immediate acknowledgement can buy the clinic a little time. If there is no response, a short follow-up path can continue. A missed call may trigger a simple text-back so the person knows the clinic saw the call. Once the person replies, books, opts out, or reaches a staff member, the next action should change.

    This is also where clinics should be careful with automation volume. A medical weight loss inquiry is not improved by ten messages that all ask the same person to book. The system should keep the opportunity from disappearing, not make the contact regret raising a hand.

    No-show recovery is still a business workflow

    A consultation no-show does not need a medical decision from the CRM.

    It needs a clear business response.

    HighLevel can use appointment status changes such as confirmed, showed, canceled, or no-show as workflow triggers. A no-show path might send an approved rescheduling message, create a task for the assigned employee, and move the opportunity into a stage that tells the team what happened.

    A no-show should not quietly become a dead lead just because the original appointment time passed.

    Empty consultation chair in a medical weight loss clinic after a missed appointment, with an analog wall clock visible nearby.
    A missed consultation still needs a defined next action instead of quietly disappearing from the clinic’s follow-up process.

    An inquiry that never books needs a defined path too. The clinic should know how long marketing follow-up continues, when a human task is created, when the lead is considered inactive, and what stops the sequence.

    Those are operating rules. Once they are written down, GoHighLevel can make them repeatable.

    What GoHighLevel for medical weight loss clinics should report

    A useful dashboard does not need to pretend the CRM knows the entire patient journey.

    For the marketing-to-consultation path, the clinic may want to see inquiries by source, consultations booked, consultation show rate, no-shows, pipeline movement, location, assigned owner, and the number of opportunities sitting without a next action. Response-time reporting can also matter when the underlying timestamps and routing are reliable.

    Those measures tell the clinic whether marketing is producing inquiries and whether the business is actually moving those inquiries toward a consultation.

    They do not automatically tell the clinic whether somebody was medically eligible, what treatment was recommended, what medication was prescribed, or what happened clinically after the consultation. If the clinic needs later-stage business reporting, it should decide which limited status or event can safely return from the downstream system rather than pulling the whole clinical record into the marketing CRM.

    That distinction keeps reporting useful without making the dashboard pretend to know more than it does.

    Pass the event between systems, not the whole chart

    Medical weight loss clinics often need GoHighLevel to coexist with other software. The integration question is not “How do we make GHL become the EHR?” It is “What event does the next system need to know about, and what should come back?”

    HighLevel supports APIs and outbound webhooks that can send contact or event data to other applications. That makes it possible to build a handoff without asking staff to copy the same information between tabs all day.

    The useful integration map is specific. For example, a booked consultation may need to create or update something downstream. A downstream system may later return a limited business status that tells the marketing team to stop a reminder or close an opportunity. The exact fields, direction, access, ownership, error handling, and retry behavior should be decided before the connection goes live.

    BrandLyft’s CRM & App Development work covers API, webhook, and custom integration problems when the clinic’s existing systems cannot be connected cleanly with a basic setup.

    More data is not automatically better. The cleanest integration often moves only what the receiving system needs to complete the next approved step.

    Test the handoff before more leads hit it

    A workflow diagram can look perfect and still fail on the first real inquiry.

    Before sending more traffic through the setup, test the path from each important entry point. Use test contacts, real calendar conditions, actual ownership rules, and the same integration route the clinic plans to use after launch.

    • Confirm that each major lead source creates or updates the correct contact and preserves useful attribution.
    • Check that the right employee or location owns the inquiry.
    • Book a consultation and confirm the correct calendar, owner, stage, and notifications.
    • Reply to the follow-up and verify that irrelevant automation stops.
    • Mark a test appointment as a no-show and confirm the reschedule and staff follow-up path.
    • Send a question that requires clinic judgment and confirm that it reaches a real employee instead of receiving an invented clinical answer.
    • Test any external handoff with only the fields and events the integration is supposed to move.

    If one of those tests fails, the clinic has found the problem before a live prospect does.

    The useful stopping point is the clinic handoff

    For a medical weight loss clinic, GoHighLevel does not have to own the entire customer or patient lifecycle to do important work.

    The useful job is narrower: carry the inquiry from source to owner to consultation path, keep a stalled opportunity visible, and show the team what still needs a next action. That is where GoHighLevel for medical weight loss clinics can earn its place without swallowing work that belongs somewhere else.

    That is also a sensible place for the CRM to stop.

    Once the next step requires clinical judgment, medical records, treatment decisions, prescribing, or another regulated process, the clinic’s people and clinical systems should take over according to the rules the clinic has set.

    Build the marketing-to-consultation path around the way your clinic actually works.

    BrandLyft can map the lead sources, ownership, calendars, follow-up, reporting, and system handoffs around your current operation instead of forcing the clinic into a generic GoHighLevel template.

    See the Revenue System Build

    Already know the account needs work? Book a discovery call with BrandLyft.

  • A GoHighLevel Funnel Domain Move Is More Than a DNS Change

    A GoHighLevel Funnel Domain Move Is More Than a DNS Change

    A GoHighLevel funnel domain can resolve correctly and still send visitors through a broken journey.

    The new domain opens. SSL appears. A landing page loads. That only proves the browser can reach something.

    The real cutover starts after that. Forms still need to submit to the right place. Buttons and booking links need to land where the business expects. Tracking has to survive the URL change. Old campaign links need somewhere useful to go. Public pages that already rank or receive traffic need a clean relationship with their new URLs.

    A GoHighLevel funnel domain migration is therefore a visitor-path migration as much as a DNS change. The new domain is ready when a customer can enter through the same real-world paths, complete the same actions, and reach the same next step without falling back into the old setup.

    Map every public path that depends on the old domain

    Start with the old root domain or subdomain, then work outward.

    List the funnels, websites, landing pages, confirmation pages, forms, booking pages, resource pages, and other public assets using that domain. Record the important paths, not only the home page. A funnel may have several live step URLs, and outside campaigns may point directly to a middle step rather than the first page.

    Then search outside HighLevel. Email templates, SMS messages, ads, QR codes, social profiles, PDFs, saved replies, browser bookmarks, partner pages, and printed materials may still contain the old URL.

    The point is to build a cutover map before changing DNS. A domain migration becomes harder when the team discovers old public links only after customers start clicking them.

    BrandLyft’s GoHighLevel buildout timeline already owns broad pre-launch page, form, and funnel QA. This article starts with an existing public path that already works and now has to move.

    Connect the destination domain before treating DNS as finished

    HighLevel currently connects funnel and website domains through its Domains & URL Redirects setup. Depending on the registrar and setup, the account may use Domain Connect or add the required DNS records manually.

    For a root domain or subdomain, the useful cutover question is not whether somebody changed an A or CNAME record. HighLevel needs to recognize the destination domain and attach the intended funnel or website to it. Where a default page matters, confirm that too.

    HighLevel also provisions SSL after the domain is linked. Give that process time to finish before deciding the cutover failed. If Cloudflare manages the DNS, follow HighLevel’s current proxy guidance rather than assuming a proxied record will behave like a normal funnel or website connection.

    Do not remove the old domain from the working setup before the new one has reached a stable connected state. DNS propagation, record conflicts, SSL issuance, and domain-assignment mistakes are easier to recover from while the source path still exists.

    Page assignments and URL paths need their own migration map

    A domain change can leave the pages intact while the public URLs change underneath them.

    Record the old URL and intended new URL for every important page. Keep the path structure where it still makes sense. When paths change, decide whether the old URL should redirect to a new page, another funnel step, or an external destination.

    HighLevel distinguishes a funnel’s domain-level URL from the individual step paths inside that funnel. Changing the domain does not remove the need to check each important step. Thank-you pages, application steps, confirmation pages, and hidden campaign pages can be missed if the team tests only the first URL.

    Open every priority URL directly after the new domain is connected. Check the page itself, then follow its buttons and next-step actions. A page loading at the right hostname does not prove the rest of the funnel stayed on the same path.

    Forms need a real submission from the new public URL

    A form can render normally and still fail the business test.

    Submit it from the new domain with a controlled test contact. Confirm the contact lands in the intended sub-account and the expected fields populate. Then check attribution and the follow-up workflow or notification.

    If the form redirects after submission, inspect that destination too. Confirmation URLs are easy places for an old domain to survive. The form may work while the customer gets sent back to the previous page afterward.

    Repeat the test on mobile. Embedded forms, pop-ups, and multi-step experiences can behave differently once the page is published on the final domain, especially when outside scripts, custom CSS, or third-party embeds are involved.

    Do not sign off from the form builder. Sign off from the public page.

    Booking paths and embedded tools can survive the page move but keep an old destination

    A landing page may move cleanly while the appointment button still opens an old calendar URL.

    Check buttons, embedded calendars, pop-ups, forms that route into booking, and confirmation pages that send visitors to the next appointment step. The same applies to chat widgets, surveys, payment steps, or other embedded tools that the page uses to continue the journey.

    There is another HighLevel domain layer worth separating here. A funnel or website domain hosts public pages. A branded API domain can affect system-generated links such as forms, surveys, calendar links, trigger links, payment links, and review links. Changing the funnel domain does not automatically prove those generated links now use the same hostname.

    That is not a reason to turn this article into an API-domain setup guide. It is a reason to inventory the links a visitor actually sees and confirm which domain controls each one.

    Tracking has to be tested after the URL changes

    A page view is not the same thing as a tracked visit.

    HighLevel has built-in funnel and site analytics. Many businesses also use Google Analytics, Meta Pixel, Google Ads tags, call-tracking scripts, or other outside measurement tools. A domain cutover can alter the URL, page path, referral context, or final destination those systems expect.

    Open the new public page in an incognito window and trigger the events the business actually cares about. That may include a page view, form submission, button click, booking, or purchase. Confirm the expected event appears in the relevant platform rather than assuming an existing tracking snippet kept working because the page copied correctly.

    If campaign attribution depends on query parameters or UTMs, test a real tagged link. Preserve the parameters through the visitor path where the campaign needs them, and verify that redirects are not dropping information the reporting process uses.

    HighLevel’s current funnel analytics can show page views and opt-ins for funnel assets, but outside advertising and analytics platforms still need their own validation after a public URL changes.

    Email and SMS links need a separate old-domain search

    The web cutover can be correct while yesterday’s automation keeps sending tomorrow’s visitors to the old URL.

    Search workflow emails, campaign emails, SMS templates, saved snippets, appointment messages, nurture sequences, and one-off templates for the old hostname. Include button URLs and linked text, not only visible copy.

    Custom Values can help when the account already uses one reusable URL in several assets, but hard-coded links still need to be found individually. The practical question is simpler: does a live customer message still point at the domain being retired?

    Trigger a few important messages after the change and click the links from a real inbox or phone. That catches redirects, tracking parameters, and mobile behavior that are easy to miss inside the editor.

    Ads, QR codes, and outside references can keep the old domain alive

    Some of the most expensive old links sit outside HighLevel completely.

    Paid-search and social campaigns may use the old domain as a final URL. QR codes can be printed on signs, mailers, event materials, packaging, or business cards. Partner sites, directories, Google Business Profile links, social bios, PDFs, and sales documents may send traffic directly to a specific funnel step.

    Customer scanning a QR code at a transit shelter, showing how outside links can keep an old GoHighLevel funnel domain in circulation.
    Links outside HighLevel can keep the old domain alive after the cutover.

    Do not assume a redirect makes every outside reference permanent forever. A redirect is a safety net, not a substitute for updating destinations the business controls.

    Ads deserve extra care because final-URL mismatches and unexpected redirect behavior can affect review or delivery. Test the final landing URL from the advertising platform after the new domain is live, and update the destination deliberately rather than relying on an old chain.

    Use 301 redirects when the old public URL is permanently moving

    HighLevel currently supports 301 redirects for an entire connected domain or for specific URL paths. The destination can be a custom URL, a funnel step, or a website page.

    That gives the migration a clean way to preserve old links when a public URL has permanently changed. Build the redirect map from the inventory rather than creating one broad redirect and hoping every old path lands somewhere sensible.

    A former lead-magnet URL should reach the corresponding new resource. Campaign pages should reach their replacements. Retired pages may need a deliberate alternative rather than the home page.

    Watch for redirect loops and unnecessary chains. The old URL should normally move directly to the final destination instead of bouncing through several intermediate addresses.

    HighLevel’s current 301 redirect guide distinguishes full-domain redirects from path-specific redirects and recommends keeping the old path useful when URLs change.

    Indexed pages need an SEO decision, not just a redirect decision

    Not every funnel page matters to search engines. Some do.

    If the old domain or path has been indexed, linked to externally, or already receives organic traffic, map the move like a normal URL migration. Preserve the intended destination, use permanent redirects where the old URL is going away, and review the new page’s indexability and metadata.

    Canonical tags solve a different problem. HighLevel’s current funnel-indexing guidance says a canonical can identify the preferred URL when multiple versions remain accessible. It does not redirect the visitor. If the old URL is being retired, a 301 is usually the more direct migration tool.

    After launch, check the URLs in the search tools the business already uses. Look for unexpected indexed variants, old pages that remain accessible, or new pages that point their canonical back to the retired hostname.

    Do not turn a campaign-only funnel into an SEO project merely because the domain changed. Apply the indexing work to pages that actually have search visibility or are meant to earn it.

    Test the new visitor path on more than one browser state

    Cached DNS, cookies, saved sessions, and browser history can hide migration problems.

    Test the priority pages on desktop and mobile, then repeat the important path in an incognito or private window. Use a device or connection that did not participate in the build when practical.

    Start from several real entry points. Type the new URL directly, click an email or SMS link, follow an ad test link, scan a QR code, and use one redirected old URL. Submit the form, follow the thank-you step, and complete any booking or conversion action that belongs to that journey.

    If different subdomains serve different parts of the experience, watch the address bar as the customer moves. Unexpected jumps back to the old domain are evidence that a link, embed, redirect, or generated URL still needs work.

    Keep the old domain available until rollback stops being useful

    Old-domain retirement should be the last step, not the first proof of confidence.

    Keep the source configuration long enough to verify DNS, SSL, page assignments, forms, redirects, analytics, customer links, and real traffic. If the cutover fails, the rollback plan should say which DNS record or domain assignment needs to be restored and who has the registrar access to do it.

    A practical rollback threshold can include the new site failing to load consistently or forms not creating the intended records. Paid traffic reaching the wrong page, SSL errors, broken redirects, or lost conversion tracking can justify the same response.

    Do not promise instant DNS rollback. Caches and propagation can delay what different visitors see. The useful plan is knowing which known-good state the team can restore and which traffic sources can be paused while the domain settles. During a GoHighLevel funnel domain migration, that recovery path matters more than pretending DNS can be reversed instantly.

    A GoHighLevel funnel domain migration is finished when the visitor path is predictable again

    Domain resolution is the beginning of the test, not the end.

    Pages need to load on the intended URLs. Forms need to submit. Booking and embedded tools need to continue the journey. Tracking needs to record the events the business uses. Old links need redirects or replacements. Indexed pages need the right permanent signals. Outside campaigns need to stop sending traffic into retired paths.

    Once those pieces behave consistently from real entry points, the old domain can move from production dependency to redirect and historical infrastructure.

    If this domain move sits inside a larger lead-to-revenue rebuild, BrandLyft’s Revenue System Build is the broader implementation path. If the work is mainly inside an existing HighLevel setup, the GoHighLevel Partner service is the closer fit. When the move also requires deeper website or custom web work, BrandLyft’s Web Design service covers that layer.

    Move the domain without losing the path that turns a visit into a lead

    BrandLyft can trace domains, page paths, forms, booking links, redirects, tracking, and live visitor journeys before the new GoHighLevel domain takes over.

    Review Revenue System Build

    Already know the cutover needs hands-on help? Book a discovery call.

  • Will Your GoHighLevel Webhook Still Work After the Endpoint Changes?

    Will Your GoHighLevel Webhook Still Work After the Endpoint Changes?

    A webhook can keep returning 200 while the business result is already wrong.

    The endpoint changed. The workflow still fires. A test record reaches the new service. Then production starts. The new receiver creates a second contact, drops the opportunity ID, rejects one field type, or loses the source value reporting depended on.

    A GoHighLevel webhook migration is not finished when the URL is replaced. The cutover has to prove that the same event still carries the right data and authenticates correctly. It also has to find or create the intended record, expose failure, and give somebody a workable recovery path.

    The safest starting point is the existing contract. Document what the live webhook does before changing the system that receives or sends it.

    Map the live handoff before you touch the endpoint

    Write down the current sender, receiver, trigger, endpoint, authentication method, payload, and business purpose. Add what record is supposed to change and what the team expects to happen after a successful request.

    That sounds basic until an old integration turns out to contain three jobs at once. A form submission may send contact data to middleware, the middleware may enrich it, and a second request may update an opportunity. Another webhook may look similar but exist only to send an internal event into a reporting database.

    Do not describe both as “the GHL webhook.” Name the actual handoff.

    BrandLyft’s GoHighLevel Custom Build article already covers the architecture question. It deals with what should send, what payload is expected, what record should change, how duplicates are handled, and who owns failure. This article starts later. That contract already exists, and now production has to move without silently changing it.

    Know which kind of GoHighLevel webhook is actually moving

    HighLevel has more than one webhook path, and their behavior is not interchangeable.

    An outbound Workflow Webhook sends data from a HighLevel workflow to another service. A Custom Webhook action gives the workflow more control over the HTTP method, authorization, headers, query parameters, content type, and request body. An Inbound Webhook works in the opposite direction: an outside system sends JSON into a HighLevel workflow trigger.

    Marketplace app webhooks are another case. They use the developer platform rather than the normal workflow action and have their own signing, delivery, logging, and retry behavior.

    Identify the type before planning the migration. Moving a simple outbound workflow action to a new catch URL is one job. Replacing an OAuth-protected Custom Webhook or changing a Marketplace app endpoint is another.

    HighLevel’s current Custom Webhook documentation and Inbound Webhook documentation show those differences directly. Each path exposes different controls and constraints.

    Change the endpoint and the authentication as separate cutover items

    A new URL can accept the request and still reject the credentials that made the old path work.

    For Custom Webhooks, HighLevel currently supports authentication patterns including Bearer tokens, API keys, Basic Auth, OAuth2, and custom headers. The platform also stores supported secret keys in masked credential controls at the location level. If the integration is moving into another sub-account, confirm that the destination has the credential it needs. Do the same when the credential owner changes.

    Keep secrets out of screenshots, migration spreadsheets, chat threads, and query strings unless the receiving API explicitly requires the query-string pattern. Rotate credentials when the migration itself changes who or what should have access.

    If the receiver validates a webhook signature, include that verification in the cutover test. For Marketplace apps, HighLevel’s current SDK supports signature verification for webhook delivery. An endpoint can be reachable and still fail because the new service does not preserve or validate the request the same way.

    Preserve the data contract during a GoHighLevel webhook migration

    Capture a known-good example from the old path before editing the new one.

    Compare field names, nesting, data types, required fields, null behavior, identifiers, timestamps, and static values. If middleware transforms the request, document both sides: what HighLevel sends and what the final receiver gets.

    The ordinary outbound Webhook action can include default contact and location data plus additional data tied to the workflow trigger. HighLevel’s current documentation notes that object-specific data depends on the trigger context. Appointment details, for example, do not simply appear because the contact has an appointment somewhere in the CRM.

    Custom Webhook actions can build a more deliberate JSON or form-style payload. That flexibility makes field-by-field comparison easier. The team does not have to trust that two requests merely “look about right.”

    Do not change field names, casing, nesting, or types casually during the endpoint migration. If the receiver also needs a contract change, treat that as a separate decision.

    Inbound webhook schema changes can break the workflow after the request is accepted

    An inbound request reaching HighLevel does not prove the rest of the workflow understands it.

    HighLevel’s current Inbound Webhook trigger accepts JSON through supported HTTP methods and uses received sample data as a mapping reference for later workflow steps. Its documentation says to reselect the mapping reference when the incoming data structure changes. Downstream actions then have a current reference for those fields.

    The trigger also requires an email or phone number when it needs to find or create the contact. That makes identity part of the contract, not an optional cleanup detail.

    The new sender may rename phone, nest it under another object, or stop sending email. The request can still arrive while later workflow steps lose the information they depended on.

    Retest the whole workflow with the new payload. Do not stop at “HighLevel caught the webhook.”

    Record identity rules before testing duplicates

    The migration needs one written answer for what makes two events belong to the same business record.

    For an inbound HighLevel workflow, email or phone may be used to find or create the contact. Other integrations may rely on a HighLevel contact ID, opportunity ID, external customer ID, order ID, or another durable key. The receiver may use an upsert rule instead of a create-only rule.

    That distinction becomes dangerous during side-by-side testing. Sending one sample event to both production paths can create duplicates. That may mean two contacts, two opportunities, two jobs, or two downstream notifications.

    Use controlled test records and a clear duplicate rule. Where the receiver supports idempotency or a stable event ID, test it. Where it does not, keep the side-by-side validation read-only or isolated from production writes.

    The migration is not proving that two endpoints can both receive data. It is proving that the new path produces one intended business result.

    Protect source and attribution fields during the field-map review

    A webhook can create the right contact and still damage reporting.

    Source, campaign, location, service, owner, pipeline, and external-system identifiers often look less important than name, email, and phone during a migration. They become important later. Reporting may need to explain the lead source, owning branch, offer, or why two systems disagree.

    Compare the field map against the reporting and routing logic that uses those values. The old middleware may normalize source names or translate an external status before sending it into HighLevel. The new path has to reproduce that behavior or deliberately replace it.

    A technically successful request that turns every source into “Webhook” can still be a failed migration.

    Build test payloads around real variations, not one perfect sample

    Start with a clean happy-path record, but do not end there.

    Use a small test set that reflects the data the integration actually sees. Include one record with the normal required fields and one with optional fields missing. Add a pre-existing contact and a case that exercises opportunity or appointment data when the webhook depends on that object.

    If the integration handles multiple locations, services, products, or source types, include the variations that change mapping or routing. If one field can arrive as blank, zero, false, or an empty list, test the representation the receiver actually needs to handle.

    HighLevel’s standard outbound webhook documentation recommends testing the workflow with a sample contact and reviewing Execution Logs. For exact request inspection, HighLevel points to the receiving application or a webhook-testing endpoint. The standard workflow log does not expose the full outbound payload.

    Success and failure responses need an agreed meaning

    The receiver should return a response that tells the sender what happened, and the team should know where to see it.

    For a Custom Webhook, HighLevel’s current guidance uses familiar HTTP outcomes during troubleshooting. Examples include 400 or 422 for invalid data, 401 or 403 for authentication problems, 404 for a wrong path, 409 for a conflict, 429 for rate limiting, and 5xx for server failure.

    Do not treat every non-200 response as the same incident. Authentication failures, schema failures, duplicate protection, rate limits, and an unavailable server need different fixes.

    What the test provesWhat to inspect
    The request reached the intended receiverEndpoint, method, timestamp, request log
    Authentication still worksToken or key, scopes, headers, signature validation
    The payload still matches the contractRequired fields, names, types, nesting, mapping
    The correct record changed onceContact or opportunity identity, duplicate rule, resulting record
    Failures are visibleWorkflow log, middleware log, receiver log, response code
    Recovery is understoodRetry, replay, manual repair, rollback owner

    Do not assume every HighLevel webhook has the same retry behavior

    Retry logic is one of the easiest places to borrow the wrong rule from the wrong webhook product.

    HighLevel publishes automated retry behavior for Marketplace app webhooks, including delivery identifiers that receivers can use when guarding against duplicate processing. The same documentation explicitly scopes that feature to Marketplace webhooks rather than Workflow Inbound Webhook triggers.

    That means a workflow webhook migration should not be designed around a retry promise taken from Marketplace developer documentation. Check the actual sender, middleware, queue, and receiving service involved in this connection.

    Define what happens when the receiver times out, returns a rate-limit response, or accepts the request but fails during downstream processing. Decide who can replay an event and how they know it was not already processed. Use a stable identifier when the receiver supports one.

    Idempotency is useful even when the platform retries are limited because people replay events too.

    Side-by-side validation should not double-write production

    Running old and new paths together can be useful when the validation method is controlled.

    A safer pattern is to let the new endpoint observe or log representative payloads without performing the final production write. Another option is to replay captured test payloads into a staging receiver and compare the transformed result with the current production path.

    If both production endpoints must stay active briefly, define which one is authoritative. Make the secondary path harmless. Do not let both paths write the same production result. That includes contacts, opportunities, charges, bookings, and customer messages.

    Parallel validation is useful only when it reduces uncertainty. Two systems changing the same record at once creates more of it.

    Failure visibility needs an owner before the cutover

    The new endpoint should have somewhere obvious to tell the team it is unhealthy.

    For workflow webhooks, review HighLevel Execution Logs alongside the logs from the middleware or receiving service. The standard outbound Webhook documentation says Execution Logs can confirm that the action ran. Exact payload inspection may still require the receiver or a webhook-testing endpoint.

    Marketplace app webhooks have a separate developer-side logging surface. HighLevel’s current Webhook Logs Dashboard documentation describes payload, response, attempt, and delivery history for those app webhooks. Do not assume that dashboard represents normal workflow webhook actions.

    Decide who watches failures after cutover, what counts as an alert, and how long the team will monitor more closely. “The developer will notice” is not an ownership plan.

    Set rollback criteria before the new endpoint receives production traffic

    Rollback should be based on observable failure, not on how nervous the cutover feels.

    Rollback signals can include unresolved authentication failures, missing required fields, duplicate records, or material attribution changes. Repeated receiver errors or a missing downstream action can qualify too.

    Keep the old endpoint, credentials, mapping notes, and relevant middleware configuration available until the new path has passed the agreed tests. If the migration changes secrets, keep the old credential only as long as the fallback path requires it. A security policy that requires immediate revocation takes priority.

    For inbound HighLevel webhooks, remember that replacing the trigger can generate a new webhook URL. HighLevel says deleting and recreating an Inbound Webhook trigger changes the URL. Requests to the old URL then stop entering that workflow. Coordinate the external sender before using that as the cutover step.

    Retire the old endpoint after the business result is stable

    A GoHighLevel webhook migration is ready to finish after the new path handles representative events and preserves the required field map. It should also produce the right records once, keep needed attribution, and expose failures somewhere the team can act on them.

    Then watch the production path long enough to catch events that did not appear in the controlled samples. Rare cases can still expose a contract assumption later. That may be a weekend source, an unusual opportunity status, or one location with a different mapping.

    The old endpoint can be retired when the new one is not merely reachable but trusted.

    If the webhook sits inside a broader custom integration, BrandLyft’s CRM & App Development service is the strongest fit. It covers API calls, webhooks, middleware, and data movement between systems. If the work is mainly inside an existing HighLevel account, the GoHighLevel Partner path is the closer fit.

    Change the endpoint without changing what the integration means

    BrandLyft can review the endpoint, authentication, payload, field map, record behavior, middleware, and failure path before a live GoHighLevel integration moves.

    Review CRM & App Development

    Already know the integration needs hands-on review? Book a discovery call.

  • Keep Existing Bookings Intact During a GoHighLevel Calendar Migration

    Keep Existing Bookings Intact During a GoHighLevel Calendar Migration

    A GoHighLevel calendar migration can look finished the moment a new booking link opens. That is usually too early to trust it.

    A live calendar already has commitments behind it. Future appointments are attached to people, users, meeting locations, linked calendars, reminders, cancellation rules, and sometimes rooms or other bookable resources. Moving the visible calendar without moving those dependencies can leave customers booking into one setup while staff are watching another.

    The cutover is complete when the new booking path works and the appointments already on the books still make sense. That means proving the old and new sides agree before the business retires anything customers or staff still depend on.

    First, identify what kind of calendar move this actually is

    A full sub-account transfer is different from rebuilding a calendar inside another sub-account.

    HighLevel’s current sub-account transfer guidance says supported account history stays with the sub-account when the whole account moves between agencies. A snapshot works differently. Snapshots can carry calendar configuration but exclude appointments from snapshot contents.

    That distinction changes the cutover plan. If the business is transferring the same live sub-account, the job is mostly about verifying that the scheduling system still behaves correctly after the account move. If the destination is a rebuilt or newly created sub-account, future appointments need their own migration decision because copying the calendar asset does not bring the bookings with it.

    BrandLyft’s CRM migration article owns the broader question of what data deserves to move. This page starts after that decision. The calendar is staying, and now the booking system has to survive the handoff.

    Inventory the live booking system, not only the calendar names

    Start with every calendar customers or staff still use.

    Record the appointment type, assigned users or teams, meeting location, duration, availability source, and booking URL. Add the linked external calendar, conflict calendars, reminder path, and any room or resource the booking consumes. For round-robin calendars, record the users in the distribution and the rule the team expects the calendar to follow.

    Service businesses may also have rooms, chairs, bays, equipment, or other limited resources tied to appointment capacity. HighLevel supports rooms and resources inside service scheduling. A calendar can show staff availability and still be wrong if the physical resource behind the booking was never recreated.

    This inventory should also separate active calendars from old ones that still happen to exist. The goal is not to reproduce every scheduling object in the account. It is to identify the live paths a customer can still reach and the internal calendars staff still rely on.

    Existing future appointments need their own cutover plan

    This is the part a copied calendar cannot solve.

    HighLevel’s snapshot documentation says appointments are not included, even though calendar assets can be copied. If the destination is a new sub-account, a calendar that looks identical can still be empty while the old account holds next week’s consultations, estimates, demos, or service visits.

    Use Appointment List View or another reliable appointment view to identify future bookings by date range, calendar, owner, and status. HighLevel’s current Appointment List View supports filtering across those fields and lets users edit appointment details, including the assigned calendar, inside the same account.

    For a same-account calendar change, that may give the team a controlled way to move a future booking to the intended calendar. For a rebuild in a different sub-account, do not assume an in-account edit becomes a cross-account migration tool. Decide how those future appointments will be recreated or preserved, then verify each one against the old record.

    At minimum, retain the customer, appointment date and time, assigned person, meeting location or link, and appointment type. Keep any notes that matter and the communication path that follows the booking.

    Rebuild ownership before you open the new booking path

    A calendar can be present while the people behind it are wrong.

    Round-robin calendars distribute appointments across assigned team members, and service calendars can depend on staff availability as well as rooms or resources. A user may have been recreated under a different profile, left the company, changed roles, or missed the correct calendar access. In any of those cases, the destination may expose time that nobody can actually cover.

    Check the users attached to each live calendar. Then compare the destination against the real operating team instead of copying old assignments automatically.

    Rooms and resources deserve the same treatment. A consultation room may host only one appointment at a time. A service may depend on a particular station or piece of equipment. That capacity belongs in the migration review too. Staff availability alone does not protect the business from resource conflicts.

    Linked and conflict calendars have to be reconnected by the right users

    External calendar sync is one of the easiest dependencies to overlook because it often lives at the user level.

    HighLevel’s current Google Calendar documentation says the connection is tied to each individual user profile, not to one global company setting. Linked calendars can receive or sync booking activity, while conflict calendars are used to block availability when outside events already occupy the user’s time. HighLevel supports similar connected-calendar behavior for Outlook.

    That means one admin connecting their own Google account does not prove the sales team, estimator, clinician, or consultant has the right conflict calendars in place.

    Reconnect the external calendar under the user who owns it. Confirm the intended linked calendar, the calendars that should block availability, and the permissions granted to HighLevel. Then create a real outside event on the external calendar and verify that the expected HighLevel slot becomes unavailable.

    HighLevel’s linked and conflict calendar guide is the right reference for that distinction.

    Availability rules need more than copied business hours

    Two calendars can both say Monday through Friday and still offer very different booking windows.

    Review weekly availability, date-specific overrides, time zones, meeting duration, slot interval, minimum scheduling notice, booking range, daily limits, and pre- or post-appointment buffers where the business uses them. HighLevel’s current buffer guidance also notes that, on Round Robin calendars, buffer settings from a user’s other calendars can affect availability.

    Time zone deserves a separate check because HighLevel now separates appointment display preferences from the scheduling logic itself. A user can view appointments in a preferred time zone without changing the calendar’s availability or what a customer sees on the booking page.

    Do not use the staff calendar view as the only test. Open the public booking link in a separate browser and compare the slots against what the business actually intends to offer.

    Old booking links do not quietly become new booking links

    This is where an otherwise clean calendar migration can stay split for weeks.

    HighLevel’s calendar duplication guidance says a duplicate calendar gets its own booking link. The old link remains tied to the original calendar rather than redirecting to the new one.

    Search every place the business can still send customers to book. That may include forms, funnel buttons, website pages, confirmation screens, email templates, SMS messages, and workflow actions. Check QR codes, staff signatures, saved replies, ads, and external profiles too.

    Old booking-link decal being peeled from a service business glass entrance.
    A calendar cutover is not finished while customers can still reach an old booking path.

    During a GoHighLevel calendar migration, replacing the old public link is part of the cutover, not a cosmetic cleanup. Do not stop after the most obvious website button. An old nurture email or saved text message can still carry the previous calendar link. Customers may reach it long after the team thinks the cutover is done.

    BrandLyft’s GoHighLevel buildout timeline already owns broad pre-launch calendar setup and QA. The migration problem is narrower: find every live booking path that still points to the old scheduling object.

    Reminder and confirmation automation can overlap during the cutover

    Existing bookings create a second risk: both setups may think they are responsible for the same appointment.

    HighLevel can send calendar notifications and can also trigger workflows from appointment events and status changes. The old account may still hold a future booking while the new account contains a recreated version. Now two reminder systems may be watching what the team considers one appointment.

    Map the customer communication before recreating or moving bookings. Identify native calendar notifications, appointment-triggered workflows, internal alerts, and any follow-up that starts after a confirmed, cancelled, rescheduled, or no-show status.

    Rescheduling deserves special attention. HighLevel’s current Appointment Status workflow documentation says a reschedule can re-enter the contact into an appointment workflow. That depends on the trigger and re-entry settings. That can be useful in normal operation and confusing during migration if the old and new sides are both active.

    Use test contacts while the cutover is being validated. The business should know exactly which setup is allowed to send the next reminder before real appointments are duplicated or moved.

    Test cancellation and rescheduling from the customer’s side

    A booking path is not proven because the original appointment can be created.

    HighLevel can add cancellation and reschedule links to calendar invites, and appointment-specific merge values can also be used inside appointment-triggered workflows. Those controls depend on appointment context, so the migration test needs to use the same path customers will use after launch.

    Book a test appointment from the public link. Open the confirmation. Reschedule it. Check the new time in HighLevel and in the linked external calendar. Then cancel it and confirm the status, customer message, internal alert, and any workflow behavior that should follow.

    Do not use a booking created manually by an admin as the only proof when most customers schedule through a public link. Test the public journey the business actually sells or services through.

    A short booking freeze can be useful when the two systems would otherwise overlap

    Not every migration needs a freeze window. Some do.

    If customers can keep booking the old calendar, new work can keep arriving on the source side. That becomes a problem when the team is rebuilding the destination and recreating future appointments at the same time. That creates a moving target.

    For a busy calendar, choose a controlled cutover period when somebody can monitor both systems. Depending on the business, that may mean temporarily removing the old public link or pausing a booking campaign. Another option is setting a clear time after which new bookings must use the destination.

    Keep the window as short as the migration allows. The point is not to make customers wait unnecessarily. It is to stop the source calendar from changing underneath the team while the final appointment and link checks are being completed.

    Run one booking all the way through before opening the new calendar

    The final test should behave like a customer, not like an administrator reviewing settings.

    Use an outside browser and a real test contact. Open the destination booking link. Check the available times. Make the booking. Confirm the correct user or team receives it. Verify the external calendar sync and conflict behavior. Read the customer confirmation. Check the internal notification.

    Then reschedule the appointment and cancel it. Watch the workflow history and the customer messages. If the business uses a room, resource, payment, meeting link, or other calendar dependency, include that in the same test.

    Afterward, book a second appointment or create an external conflict to make sure the first test did not leave availability in an impossible state.

    One successful booking is not proof of every edge case. It is the minimum evidence that the new path can survive the same basic lifecycle as a real appointment.

    Shut down the old calendar only after the new path stops producing surprises

    The old calendar is safe to retire when the business no longer needs it to catch missed dependencies.

    Cutover questionWhat should be true before shutdown
    Are future appointments accounted for?Every needed booking is preserved, recreated, or deliberately left on the source until completion.
    Can the right people be booked?Assigned users, round-robin members, rooms, and resources match the live operating team.
    Does availability reflect real capacity?Hours, overrides, time zones, buffers, booking limits, and conflict calendars have been tested.
    Do customers reach the destination?Live forms, pages, email, SMS, and other booking links no longer send people to the old calendar.
    Do reminders come from one intended path?The team has ruled out duplicate confirmation, reminder, reschedule, and cancellation messages.
    Can the team recover if something breaks?The old setup remains available long enough to verify records and restore a working booking route if needed.

    Do not delete the old calendar simply because the new one accepts a booking. Keep enough access to compare future appointments, verify old links, and understand any reminder or sync behavior that surfaces after cutover.

    A rollback plan does not need to pretend the migration can be reversed with one click. It needs to say what the business will do if the destination stops accepting bookings, external sync fails, or a future appointment cannot be found.

    Keep existing bookings intact during a GoHighLevel calendar migration

    A GoHighLevel calendar migration is not a calendar-copying task. It is a live scheduling handoff.

    The destination has to know who can be booked and when they are available. It also needs the right conflict calendars, future appointments, customer links, and messages after a booking changes.

    Once those pieces agree, the old calendar can stop carrying real work.

    If the calendar move is one part of a larger rebuild, BrandLyft’s Revenue System Build is the broader implementation path. If the account already exists and the booking system needs to be traced, moved, or tested inside GoHighLevel, the GoHighLevel Partner service is the more direct fit.

    Move the booking system without losing the commitments already on it

    BrandLyft can trace live calendars, future appointments, staff ownership, external sync, reminders, and booking links before the destination setup takes over.

    Review GoHighLevel Partner Help

    Need help with the wider account rebuild? Book a discovery call.