Solr Standard · The proposed 60 day challenge
Contact. Appointments. Revenue.Pat, here’s the bet I want to make: give me 60 days to run an ad lane for Solr. My aim is to beat every other comparable lead lane you have on both conversion and actual return. We agree the scorecard first, then judge the work by the results. That is the performance target I’m proposing, not a guaranteed outcome.
Start the conversation.
Make the appointment.
Carry the next step through.
AI text messaging and email, alongside rep-led WAVV calls remain part of the intended connected journey. That complete journey is still in build. Finishing the existing delivery remains owed independently of the proposed ad test.
The work already owed
You asked for AI to improve contact, turn older leads into appointments, and review and reengage past appointments. Those are the operating outcomes this work must deliver. I’ll bring the actual result and the remaining gaps, without asking you to validate another dashboard.
Contact and qualify
The intended path uses AI text messaging and email to establish the need, qualify the lead, book the right solar or roofing calendar, and save the outcome and next action.
The earlier overnight target remains unverified as a complete operating journey. A controlled example must produce the actual calendar and CRM records; one example alone does not prove every outcome.
Reengage and recover
Older leads and past appointments remain separate recovery work: review the history, make the appropriate contact, and carry a cancellation, missed visit or unsold conversation to a useful next step.
This remains existing delivery scope. Recovery results will be reported separately from newly acquired leads in the ad comparison.
Finish the handoff
Correct lists and calling behavior, the right appointment handoff, and an owner and date for unfinished work. A designated cover must be able to pick up the same work with its context intact.
Populated daily queues, inbound routing and the complete automated journey still need proof. Limited Coach saves do not establish that the whole operation is working.
WrightLabs owns the configuration, verification and clear handoff. We show what actually worked, identify what remains unfinished, and name the next action and owner. Existing commitments remain owed whether or not you choose the ad test. No new completion date is being represented as agreed here.
Agentic call lanes · our approach
We’re building each rep’s ordered calling list directly inside Command Center, with WAVV embedded alongside it. Reps will dial eligible leads from that same workspace, with a clear view of who to call, why that lead is next, and when the call should happen.
01 · Grade in HighLevel
We use custom fields in Solr’s GoHighLevel account to record lead grades and priority scores, the assigned rep, call lane, next action and due time, customer time zone, and the reason for the ranking. Existing suitable fields are reused; missing fields are added as part of the build.
A high score never overrides an opt out, a calling restriction or a customer’s requested callback time.
02 · Build the live worklist
Command Center reads those fields to place eligible leads into the right rep’s lane: fresh leads, due callbacks, older lead recovery or past appointment follow up. Priority combines the grade with the next due action and the agreed calling rules.
Customer local time, day of the week, permitted calling hours and any agreed callback determine when a lead can enter the callable list. Unknown timing or missing permission is held for review.
03 · Call in Command Center
We’re connecting the embedded WAVV dialer to the eligible calling list in Command Center. The rep will start the calling session there, with the lead’s context and next action beside the dialer. There will be no need to rebuild a separate list to do the same work.
One ordered list, the correct rep’s WAVV session, and the contact history together on one screen.
We’re adding an aged-lead upload section inside Command Center for Lizzie. Each month, she will upload the new file; the system will parse and validate its columns, match existing HighLevel contacts, identify duplicates, and flag missing or ambiguous information for review. She will see the import summary before confirming the records to process.
After confirmation, the system will save the approved records into HighLevel, preserve existing contact history, apply the agreed grades and assignment rules, and distribute eligible leads into the correct human reps’ WAVV calling lanes. Priority, rep ownership, customer time zone, callback commitments and contact restrictions will determine the order and timing.
From there, the same operating loop continues: reps make the calls; AI coordinates text and email follow-up, notes, dispositions and routing. Callbacks return when due, appointments enter the sales-rep schedule, and bookings or opt outs stop conflicting outreach. Each new monthly file joins the existing process without resetting prior conversations or next actions. Import progress, held records and failed updates will remain visible for resolution.
As new leads, conversations, appointment changes and saved outcomes arrive, the agentic process updates the relevant HighLevel fields and refreshes the Command Center lanes. Completed work leaves the active queue; a callback returns when due; a rebooking or opt out stops conflicting outreach. Immediately before dialing, the system must recheck that the lead is still eligible.
Lizzie can see the order, the reason and the next due action. Reps stay focused on the next useful conversation. The target is a worklist that changes with the business throughout the day, with its last refresh and any failed update visible.
The workflow connects the full cycle: grade the lead, choose the right lane and time, dial through WAVV, save the outcome, and update the next action in HighLevel and Command Center. Rep calling through WAVV sits alongside the separate AI text messaging and email acquisition journey.
WrightLabs AI · ongoing operations
We’re building an ongoing AI operations layer inside Command Center to handle customer text messaging and email, alongside rep-led calls through WAVV. Agents will initiate eligible outreach, respond to incoming conversations, follow up, coordinate appointments and bring in the right person when needed—all using the same lead history and next-action records.
01 · Read and organize
HighLevel is the source of record. The agent service will process new messages, WAVV call events, available transcripts, rep notes and appointment changes; organize the useful information; and update lead grades, dispositions, notes, routing, priorities and next actions. Event updates and periodic reconciliation will keep Command Center aligned with the underlying records.
02 · Communicate and act
The AI will use the conversation history to choose the next appropriate communication, send contextual texts and emails, organize notes and dispositions, and route the next action to the right person. It will handle replies and follow-up within the agreed outreach rules, coordinate bookings and hand the conversation to a rep when a person is needed. Rep-led WAVV calls and AI communication will share the same lead context to avoid conflicting outreach.
03 · Use tools and measure
We’re connecting defined tools for checking availability, booking appointments, updating HighLevel fields, creating tasks, assigning follow-up and moving leads into the correct calling lane. Command Center will surface activity, contact rates, appointments and outcome-based KPIs with the underlying records, so the team can see what happened and what needs attention.
We’re adapting our existing tracking-tab approach into a sales-rep appointment view in Command Center. The agent will organize each rep’s daily schedule using appointment times, service areas, availability and travel time, then adjust the proposed route as cancellations, reschedules and new appointments arrive.
Reps will see the next stop, appointment context and schedule changes in one place. The agent will flag timing conflicts, propose reassignment when needed, and coordinate text or email updates under the agreed rules. Route changes will preserve confirmed customer appointment times; changes to those commitments will require confirmation before the schedule is finalized.
Command Center will provide controls for agent instructions, business knowledge, text and email channels and permitted tools. Each action will have a visible result or failure, with pause and human takeover controls. Customer preferences, opt outs, contact timing and rep ownership will govern the next action across every channel.
The operating cycle: read the latest activity, understand the context, communicate or use the appropriate tool, verify the result, update HighLevel, and refresh the team’s worklist and reporting.
01 / A better day for every person
The target is fewer routine contacts waiting on a human caller. AI makes contact and moves qualified leads toward an appointment. Staff receive the context they need for the visit, close or exception. Older leads and previous appointments remain part of the recovery work.
The experience below is the delivery destination. Role notes distinguish the limited checks recorded on October 19 from the work still being connected. They do not establish current full queue coverage or a complete operating AI journey.
“I know where we’re winning—and what needs my decision.”
An overview of today, yesterday, and the week. The KPIs are the front door, with money and operating problems in plain view.
02 / The complete revenue loop
Explore the complete lead-to-revenue journey. Each stage has an operating result to demonstrate, from AI contact through the appointment, close and customer handoff.
A named owner gets a recovery task. Approved nurture follows the correct reason and stops when the person rebooks or opts out.
The objection and promised next step travel together. A dated follow-up, a permitted nurture path, or a genuine closed outcome replaces limbo.
Record the attempt accurately. Apply the approved retry cadence or assign a review. Never invent a conversation, customer promise, or appointment.
03 / The front door
One navigation. Readable type. Generous space. Today, yesterday, and the week use consistent definitions. A help button explains each page in plain language.
Appointments created today, even when the visit is on another date.
Appointments whose scheduled start is today, in Solr’s time zone.
Confirmed completed visits. Keep in-progress and missing results separate.
Closed deals and collected revenue are different measures.
Separate outcomes with an owner, reason and recovery status.
Unfinished promises and staff tasks, including missing dispositions.
Calls, human conversations, talk time and conversion by rep.
Actual spend, CPL, show rate and acquisition cost by source.
Review confirmations, timing changes and unresolved visit outcomes.
Resolve overdue actions, failed appointments and missing ownership.
Choose a rep coaching point or vendor decision backed by the data.
Week-to-date totals, daily averages and prior comparable periods stay distinct. Show/no-show/cancel rates use the same scheduled-appointment cohort; pending results remain visible. Each metric shows source coverage and freshness.
The complete operating experience
Routine acquisition moves through AI text messaging and email. The team focuses on real appointments, closing, customer work and the exceptions that need judgment.
Pat sees the business. Lizzie sees the floor. Each rep sees their own work, today’s team comparison and real number readiness. Yesterday’s missing outcomes already have a person and a next step.
Calls and messages improve the context. Coach captures the result. New bookings, replies and completed actions update the next useful work. The rep spends time talking, not reconciling tabs.
Every visit is accounted for. Unsold and failed appointments have a recovery path; sold work has a delivery owner. Managers can see what improved, what remains open and what tomorrow needs.
This is the full delivery destination. The earlier overnight target still needs complete operating proof; the unfinished rollout remains work to deliver.
04 / Make the upside visible
Adjust the assumptions to see how contact, booking, show and close rates combine. This is an illustrative model using synthetic inputs, not Pat’s actual results or a forecast.
Illustrative baseline: 1,000 leads/month → 40% conversation rate → 25% booking rate → 70% show rate → 25% close rate.
17.5 sales
Same as the illustrative baseline.
Rates multiply. A 25% → 30% booking rate is +5 percentage points, or +20% relative. Holding the other assumptions fixed yields 21 expected sales/month—3.5 more, not 21 more. Real results depend on capacity, lead quality and elapsed time.
The bet · proposed for agreement
Give me one ad lane to run. My aim is to beat every other comparable Solr lead lane on both conversion and actual return. We name those lanes before we start, keep the rules consistent, and show the records behind the result. If the data does not support a win, we say so.
60 days
Run the lane. Earn the next decision.
Proposed test duration, beginning on the agreed launch date after the required intake, contact, booking and tracking path is verified. No campaign starts from this proposal alone.
No verified baseline, budget or performance result is being presented here. The start date, fees, spend cap and commercial terms remain to be agreed.
Jamie runs the agreed ad lane within the approved spend cap and owns its intake, contact and booking handoff. Pat and Lizzie confirm the comparator lanes, qualification rules and operating coverage. We agree a reporting owner and a weekly review of actual spend, unique leads, conversations, bookings, held visits, sales and collected jobs.
At day 60, review the acquired cohort and the observed results. If collections need more time, use the same maturity window for every lane and the review date agreed before launch. Open jobs stay open; projected revenue never counts as collected revenue.
A win means beating every agreed comparable lane on both primary measures with adequate data. A split result, missing source records or an immature cohort is not a win. The next spend decision follows the evidence.
This is a proposed performance challenge, not a guarantee. No payout, refund, fee, budget or accepted terms are established by this page. Existing delivery commitments remain owed independently of the ad test.
What completion means
These are the outcomes we will review together. A step is complete when it works for the intended person and its result is visible in the operating records.
Full intended work scope, real names, correct owner, conversation-driven priority and appropriate timing. Fresh paid leads and older recovery stay distinct. The saved GHL list, rep seat and manager view agree.
Required proof: populated ordered membership + recipient access + refresh.AI text messaging and email carry routine acquisition. Human handoffs use the correct GHL/WAVV seat and caller identity; problems have an owner.
Required proof: actual rep session, settings readback and permitted call evidence.The recorded call produces a summary and supported disposition. Unclear, unavailable and unanswered calls stay accurately classified.
Required proof: same call → saved outcome → native CRM → manager view.Every nonterminal outcome has a named owner, specific action and due time—or a visible assigned exception. Customer promises and staff deadlines are distinct.
Required proof: open native task, exact deadline, later completion or escalation.The assigned rep submits the result once. The exact appointment and opportunity update together; repeated delivery creates no duplicate work.
Required proof: normal rep form → exact deal → workflow execution → readback.Cancelled, no-show and unsold outcomes enter the appropriate approved path. Rebooking and opt-outs end conflicting sequences.
Required proof: routing, timed next action, authorized execution and stop behavior.Pat and Lizzie see readable KPI definitions, consistent cohorts, actual costs, vendor comparisons and next-week outlook. Reps see securely embedded booked-created performance, personal/team comparison and sourced phone health.
Required proof: source reconciliation + role walkthrough + visible freshness.The team has clear access, coverage, useful help and actionable exceptions. Pat can judge the result without another readiness walkthrough.
What we review: Lizzie or a cover completes a normal day and a real exception handoff.The full delivery scope
First · connected acquisition
Then · recover and deliver
Across the full system
Held - Sold · Held - Follow-Up Needed · Held - Not Interested · One-Legger · Porched / No-Show · Virtual No-Show · Cancelled Ahead · Rescheduled · Couldn't Reach.
Each outcome must preserve the exact appointment and deal, the correct next event or reason no event exists, and the appropriate recovery or fulfillment path.
Our next working conversation
The decision is concrete: review the work already owed, then decide whether to agree the 60 day ad test, its comparison rules and its operating responsibilities.
Review the challenge ↑The actual results available to inspect, the unfinished delivery items and their next owners, and the proposed scorecard. No completed journey or improved revenue is being claimed without its records.
The existing rep and GHL/WAVV experience, full appointment-result contract, older-lead and past-appointment recovery, management visibility, and the broader solar and roofing operating journey.
Agree the comparable lanes, qualification and attribution rules, both primary measures, sample and maturity windows, spend cap, fees and launch date in writing. Then verify the operating handoff before launch. This page does not authorize spend or establish accepted terms.