T
Torres Simmons Land Group
Pilot Command Center
Pilot Preview
Modeled dashboard for a 5,000-lead pilot segment. Your live Salesforce and AI360 data flow here once connected.
Modeled operating view

Make the dashboard read like the GHL working board.

This view is structured around countable states: total records in scope, active records in GHL, reached, contacted, follow-up running, calls handled, booked, and showed. The goal is to mirror what refreshes once workflows and pipeline states are live.

33kTotal in scope30,000 aged records plus 3,000 new inbound leads.
8kActive in GHL5,000 aged pilot segment plus 3,000 new inbound records.
4,120ReachedModeled records that received a text, email, or call touch.
2,264ContactedModeled replies or real conversations started.
1,146BookedConsultations or sales-event registrations created.
929ShowedAttendance after reminders and no-show recovery.
Aged database loaded
30,000
Modeled source volume for reactivation, still worked in batches.
New inbound loaded
3,000
Modeled inbound volume tracked alongside the aged pilot segment.
Modeled cost per showed appt
$41
Illustrative operating metric, not a live spend report.
Modeled total records in scope
33,000
30,000 aged plus 3,000 new inbound
Modeled active in GHL
8,000
Records actively being worked in the pilot motion
Modeled reached
4,120
Text, email, or call touch successfully landed
Modeled follow-up running
1,486
Records still cycling through nurture and reminder steps

Salesforce Coexistence

Salesforce stays the source of truth. AI360 works the engagement layer around it.
SF
System of recordLeads, ownership, history, and reporting remain grounded in Salesforce.
IN
Sync inNew and aged segments can feed AI360 for follow-up and booking.
WB
Write backAppointments, outcomes, transcripts, and dispositions return to Salesforce.
DN
Opt-out both waysSTOP, DNC, and email opt-outs propagate across both systems.

Compliance & Deliverability

The pilot is built for controlled sending, not a blast.
1
Consent auditSegment by source, consent status, and channel permissions before outreach.
2
A2P registered sendingUse verified AI360 sending infrastructure for demo-safe messaging.
3
STOP / DNC handlingEvery opt-out is honored and written back.
4
Drip batchingNo 30,000-lead blast. Work leads in waves the sales team can handle.

Four Stall Points - Fixes

The system maps directly to where land buyers usually go quiet.
F
Follow-upMulti-touch automation keeps new inquiries moving.
R
ReconnectReactivation engine works aged opportunities in waves.
A
AttendanceConfirmations, reminders, and no-show recovery protect booked time.
N
Nurture14-day drip keeps buyers warm after the first response.

Group-Event Readiness

Same intake can route buyers into the right sales motion after the qualification questions.
1:1 ConsultationHigh-intent buyers route to a land specialist for a focused appointment.
Group Sales-Event RegistrationEvent-ready prospects can be registered, reminded, and checked in from the same flow.
HybridBuyers who need scheduling or spouse/partner alignment get nudged to the right next step.

Modeled GHL Refresh Buckets

These are the kinds of count-based buckets this board should refresh from contact status, workflow states, tags, and pipeline stages in Go High Level.
Aged database loaded
30,000
Records available for segmentation and reactivation.
New inbound loaded
3,000
Fresh leads tracked separately from the aged database.
Reached
4,120
A send or call attempt landed successfully.
Contacted / replied
2,264
A person answered, replied, or engaged back.
Follow-up queued
1,486
Still inside nurture, reminder, or no-show recovery steps.
Called / AI handled
938
Voice or AI call touch completed and logged.
Booked
1,146
Consultation or sales-event registration created.
Showed
929
Actually attended after confirmations and reminders.

Refresh Groups from GHL

Operational stage groups for the two main motions: reactivation and new inbound.

Reactivation motionmodeled operational counts

30k
Source
5k
Active
1840
Reached
1118
Contacted
612
Booked
496
Showed

New inbound motionmodeled operational counts

3k
Loaded
2280
Reached
1146
Contacted
534
Booked
433
Showed
526
AI Call
Modeled avg speed-to-lead
38sec
Operational timer for new inbound once the live workflow is connected.
Modeled appointment show rate
81%
Driven by confirmation, reminder, and no-show recovery workflow counts.

Refresh Definitions

These labels are meant to feel factual when someone asks what exactly each number means.
R
ReachedA send or call attempt was successfully delivered or connected.
C
ContactedThe lead replied, answered, or otherwise engaged back.
F
Follow-up runningThe record is still inside a nurture, reminder, or recovery step.
B
BookedAn appointment or group-event registration was created.

Pilot Metrics

The board should answer the operating questions, not just the sales story.
N
New vs aged mixHow much volume is new inbound and how much is database reactivation?
T
Touch completionHow many records were actually touched across text, email, and calls?
A
AttendanceHow many bookings turned into real conversations or event attendance?
$
Cost per showed appointmentWhat did the pilot spend to produce a real attended opportunity?

Sample Activity Feed

Illustrative activity examples only. Live calls, texts, bookings, and transcripts flow here after connection.
AI
Voice AI sample qualified Marcus W. - Waller County, 10-20 acres, owner finance, buying within 30 days. Routed to consultation.
sample item - transcript would save once connected
URGENT
BK
Appointment sample - Delia R. confirmed for Thu 2:00 PM. Confirmation and reminders queued.
sample item
BOOKED
RX
Reactivation sample - Travis B. replied "still looking" from the aged list and moved to booking prompt.
sample item
REVIVED
AI
Voice AI sample reached Yolanda P. - recreation use, 5-10 acres, 3-6 month timeline. 14-day nurture continues.
sample item - transcript would save once connected
WARM
BK
Web form sample - Owen T. submitted a land inquiry and received a speed-to-lead follow-up path.
sample item
BOOKED