HighLevel Setup

Reviewed October 5, 2026. Status: not verified ready for launch.

This is a read-only review and implementation specification. No live routing, ads, workflows, or customer messages were changed. The screenshot was treated as reference material; the user's request defines the intended behavior.

Corrected operating model

HighLevel owns lead identity, attribution, marketing follow-up, and the lead journey. GoTo Connect handles telephone routing. AccuLynx owns the operational job record after handoff. HighLevel must receive selected job updates to keep its lead journey and follow-up accurate.

Ads / Google Business Profiles
  → HighLevel tracking number → GoTo routing → Team / queue / voicemail
  → HighLevel contact and opportunity

Meta / website forms → HighLevel contact and opportunity
  → Qualification and owner assignment
  → AccuLynx lead / job → Job ID and status updates → HighLevel
  → Nurture when not ready

HighLevel → Reporting by source, location and outcome

The diagram's GoTo-to-CRM and GoTo-to-AccuLynx arrows should not imply that the PBX creates customer/job records. Any such behavior needs a separate, verified integration. The HighLevel tracking bridge itself should feed CRM intake while the call is routed to GoTo.

Verified phone inventory

The five screenshot numbers are in the GoTo inventory. They are routing destinations, not the public-facing HighLevel tracking numbers.

The inspected HighLevel subaccount is Northpoint Roofing, Kennesaw, GA, location ID 8YFK7KVGUCVbmVzuGxCu. It shows three phone numbers. All three show A2P Verified and a 20-second call timeout. A2P verification is not evidence of individual consent or complete call routing.

HighLevel friendly names: Northpoint | Franklin, Northpoint Roofing | Kennesaw | Ads, and Atlanta Northpoint Google Ads Call Asset Number, respectively. Both Kennesaw numbers forward to +1 678-210-8288.

GoTo also has Master Roofers Ads +1 603-518-8172, routed to the same 1012 destination. Resolve which downstream number should be canonical before configuring that bridge; do not replace either based on the screenshot alone.

Maintain a master registry with business, market, HighLevel subaccount, public tracking number, placement/channel, GoTo number, dial plan, business hours, fallback, and last successful test date. Verify actual ad assets and each GBP against that registry.

Confirmed readiness gaps

1. Call intake covers completed calls only. Published Phone Call; Create Opportunity triggers on Incoming + completed, then creates/updates Marketing Pipeline → New Lead. It shows 196 total enrollments. This does not prove capture of busy, no-answer, failed, abandoned, or voicemail calls. A PBX auto-attendant answering is not proof that a person spoke to the caller.
2. Call attribution needs an explicit fallback. The opportunity source uses {{contact.attributionSource.sessionSource}}. A direct call may lack website session attribution. Derive business/location/channel from the dialed tracking number when that is the available evidence. Never label a shared GBP/ads number as definitely paid traffic.
3. AccuLynx outbound handoff is a draft. New Lead (AccuLynx) shows zero enrollments. Its Pipeline Stage Changed trigger has no configured filters and leads directly to Create Lead. First name, last name, phone, email, and opportunity source notes are mapped; street, city, state, ZIP and country are blank. There is no visible guard or returned-ID storage step in this draft's canvas.
4. Return synchronization needs repair. Update Contact (Job ID) is also a draft with zero enrollments. Its canvas is Job Created → Get Contact → Get Phone Number → Update Job ID. The final action displays an alert, has no destination field selected (Select field), and its value is {{get__phone__number.1.data.number}}, a phone output rather than a job ID. Repair the field and value mapping and prove contact matching. This job-created workflow does not establish ongoing job-status or revenue synchronization.
5. Pipeline design mixes lifecycle and disposition. Marketing Pipeline has New Lead, Call Attempt 1–5, Automation Campaign, Appointment Set, Current Customer, Warranty, Lost / Not Interested, Telemarketer, DNC, Miss Dial and Bad Lead. Treat attempts as activity/counts; DNC as a suppression condition; and invalid/spam as dispositions. Plan migration before changing stages used by existing workflows.
6. Ownership must be explicit. The account allows different contact and opportunity owners, with a UI notice that workflows might stop assigning owners to opportunities. Specify assignment of both records and test the result.
7. Other businesses are not yet audited. The current subaccount cannot establish Cardinal, Master Roofers or Trimlight readiness. Their HighLevel numbers, workflows and AccuLynx company destinations remain unverified.

Additional observed signals: GHL Form; Create Opportunity is published with 51 total enrollments; that does not prove Meta native forms are connected. The open Meta view reports Lead (Form), making a separate form intake path necessary. Google Ads Overview displays an unverified conversion-tag notice; the affected conversion and account must be identified before concluding that all reporting works. Neither ad assets nor GBP phone settings were individually verified.

Build specification

Lead identity and data

Use one contact per person and one opportunity per actual inquiry/project. A repeat call updates activity on an existing open inquiry; a separate property/project may need its own opportunity. Do not use phone number alone as an irreversible merge rule for different people sharing a household number.

Contact fields: name, normalized phone, email, contact preferences, consent source/time, and suppression status. Opportunity/project fields: brand, market, service, property address, owner, lead-created time, first meaningful response, qualification result, appointment date, disposition/reason, original lead source, latest source, campaign/ad/form IDs where available, dialed tracking number, source evidence, AccuLynx company and job IDs, handoff state, last sync time, and sync error. Use existing native attribution fields where suitable rather than duplicating all metadata.

Persist original source at intake. Keep latest activity/source separately. Capture unknown attribution honestly. A single public tracking number shared by GBP and ads cannot independently separate those callers. Separate static numbers by placement if that distinction is required. For calls after a website visit, evaluate dynamic number insertion with session tracking.

Workflow modules

Handoff timing is a pending business decision. Proposed default for review: qualification plus a booked inspection. Do not implement or publish that timing until selected. Do not require an email when a phone-only lead is otherwise valid; enforce required fields according to the actual AccuLynx action and operational needs.

Lifecycle and system ownership

Proposed sales lifecycle: New Lead → Contacting → Qualified → Inspection Booked → Inspection Completed → Estimate/Proposal → Won/Lost. Keep Not Ready/Nurture as an explicit branch. After handoff, mirror the agreed AccuLynx status in HighLevel or use a separate job-visibility pipeline, with exactly one canonical sales opportunity for reporting.

HighLevel governs attribution, consent, marketing and pre-handoff sales fields. AccuLynx governs job ID, production status and agreed operational/financial fields. Maintain a written mapping of actual AccuLynx milestones to HighLevel stages; never overwrite original attribution with an operational update. Create failures must enter a visible error queue with retries and an owner, not silently mark the lead sent.

Implementation order

1. Complete the registry and confirm HighLevel account architecture across businesses. Identify the AccuLynx destination for each brand/service, including whether Trimlight uses AccuLynx.
2. Confirm handoff timing, owner assignment, permitted messages and operating hours.
3. Reuse suitable existing fields; build intake and duplicate protection in drafts. Audit existing workflow conflicts before adding another intake workflow.
4. Repair the filtered AccuLynx handoff, address mapping, durable IDs, retries and return-status mapping.
5. Build follow-up and nurture with stop conditions, then validate reporting definitions.
6. Test one business end to end, then repeat the same acceptance tests for each remaining business before enabling live automation.

Launch acceptance tests

Readiness requires recorded passing evidence for all applicable tests. Configuration visibility alone is not a successful call or integration test. No test calls, customer messages, AccuLynx submissions or workflow publication were performed during this review.

Vendor references

• HighLevel inbound routing and call flow: forwarding, timeout and answering-machine considerations.
• HighLevel tracking number pools: website session tracking and number swapping.
• HighLevel attribution sources: source and website attribution setup.
• AccuLynx API getting started: integration access requirements. The installed marketplace app's actual supported actions and return events must still be verified.