From Meta lead to a
prepared sales appointment.

“we don't want people showing up blind.”John · Oct 1, 33:34 · meeting reference

Trigger

A prospective investor arrives from an approved Meta campaign, direct link or returning visit. Existing investors receive a clear path to the Avestor portal.

Owner

John approves offer facts/assets; CJ owns campaign context; AI Acrobatics designs/builds the website; the sales team owns human consultations and downstream investor decisions.

Data

Approved current brand/offer, dated source pack, real authorized assets, Vimeo 1185193132, consultation agenda, agreed fit wording and permitted visitor/lead attribution.

Actions

Present one coherent offer, the 12:08 video, readable fund/operator/retail roles, approved three-stage explanation and dated proof. Provide a working company branding guide using observed source materials and a pizza-derived red/ink/white direction; use Forno Street Pizza Co as the selected review brand and confirm current offer/legal identity before client launch. It is a proposed working guide, not a certified official brand manual. Offer question-first or consultation-first paths; connect tested GHL capture/booking when separately configured. Preserve Avestor for documents and transactions.

Exceptions & human review

Unapproved/inconsistent numbers, old dates or unsupported location/team claims stay out of prospect-facing copy. Use approved assets or clearly labeled concept illustrations. Concept artwork is not evidence of real locations or operations; Forno brand marks identify the selected company; any location photography still requires source, usage and currentness approval and is not assumed to prove operating status. A booking/provider failure shows a useful human fallback. No website transaction, eligibility decision or investor commitment is automated.

Acceptance evidence

Review the /investor prototype, /investor/brand-guide and connected fictional journey. Confirm source/material provenance and current brand identity in the working guide. Before client launch: approve facts/assets; test responsive/reload/video access, keyboard/readability, question capture, consent, actual GHL booking/readback, attribution and the correct Avestor handoff. Record measured performance rather than claiming a pass from a mockup.

“giving people a chance to call in immediately after opting in is a huge.”CJ · Oct 1, 00:24 · meeting reference

Trigger

A new lead submits the designated Forno Street Pizza Co Meta form. Imports and unrelated contacts do not trigger this flow.

Owner

Native Meta/GHL intake creates the CRM record; the selected native/custom coordinator owns the agreed AI cohort and next-step state.

Data

GHL contact ID, available form/Page/source identifiers, qualification answers, channel consent and assigned owner. Missing ad IDs remain unknown.

Actions

Map the form answers, link the correct GHL contact, evaluate the approved qualification rules, and present the tested phone path or agreed fallback. Start only the authorized follow-up.

Exceptions & human review

Unmatched or duplicate contacts, missing consent and ambiguous qualification route to review. A failed mobile call CTA falls back to the approved phone/link path.

Acceptance evidence

Submit a real test lead from the actual form on mobile; verify the right GHL record, preserved answers/source and one eligible enrollment. Replayed events produce no duplicate outreach.

“That's my biggest worry is that people are getting turned off by it.”CJ · Oct 1, 11:02 · meeting reference

Trigger

A prospect calls the configured, client-approved phone number after opt-in or through an agreed campaign entry.

Owner

The native GHL or custom voice runtime selected by scenario tests runs the approved assistant; John or the designated closer owns human judgment and escalation.

Data

Caller identity matched to GHL where possible, authorized call context, approved offer-pack version, exact questions and stated qualification information. This is not final eligibility or suitability verification.

Actions

Introduce the assistant clearly, answer supported questions, capture interest and open questions, offer booking or human handoff, and write a concise conversation brief back to the linked record.

Exceptions & human review

Unknown callers are verified without speculative matching. Current minimum, eligibility, location/allocation, financial personalization, listing-status and commitment questions go to a human when not supported by the approved pack. Conflicting or stale source claims are blocked; the handoff includes the exact question and source version. Provider failure uses the approved transfer/fallback route.

Acceptance evidence

Complete real phone tests for known/unknown caller, supported/unknown questions, interruption and human handoff. Verify linked GHL history and no unapproved claims; review voice latency and tone with John.

“take the feedback, maybe the questions that they asked”CJ · Oct 1, 10:27 · meeting reference

Trigger

An eligible lead finishes a conversation without booking, or replies with a question during an agreed follow-up window.

Owner

One agreed sender owns each conversation across native GHL workflows, the assistant and manual sales replies.

Data

Linked conversation history, approved channel tone, unresolved questions, next step, consent/DND, timezone and current ownership.

Actions

Draft or send the authorized contextual touch, continue replies from shared memory, add approved supporting content, and record message IDs/status in GHL and the dashboard.

Exceptions & human review

Opt-out, takeover or a changed lead state cancels queued sends. Missing delivery receipts remain unresolved. Questions beyond the approved sales corpus enter the human queue.

Acceptance evidence

Demonstrate a phone-to-text reply that retains context, an email variant in approved tone, opt-out/takeover suppression and retry replay without duplicate messages. Confirm GHL shows the conversation.

“place an appointment on my calendar or my closers calendar and they show up.”John · Oct 1, 21:59 · meeting reference

Trigger

A qualified prospect requests a sales appointment or agrees to an offered next step.

Owner

GHL calendars remain authoritative; the selected native/custom coordinator coordinates booking, while John/the closer owns the sales appointment.

Data

Correct calendar/closer IDs, live free slots, prospect timezone, client-approved intake details, prior questions, approved offer/asset version and optional self-reported preparation state: not started, part watched, finished or questions.

Actions

Offer valid slots, check availability, create one appointment, read it back, coordinate confirmation, offer relevant approved preparation without making viewing a booking condition, capture optional self-reported progress/questions, and prepare a closer brief with exact unresolved questions and source version.

Exceptions & human review

Slot conflict prompts another valid choice. Missing calendar/provider data goes to review. Confirmed playback signals are separate from self-report and only appear if implemented and verified later. Viewing never establishes understanding or qualification. No 75% gate or automatic cancellation for non-viewing is proposed.

Acceptance evidence

Book a real valid slot once on the correct closer calendar; verify timezone, persistence/readback, one confirmation and the brief. Test conflict, reschedule and reload paths.

“lately we're finding it like it's 25%.”John · Oct 1, 31:36 · meeting reference

Trigger

The agreed appointment status/window identifies a no-show after the team has recorded the outcome.

Owner

The sales team owns attendance status; the assistant follows the approved recovery policy and yields when a closer takes over.

Data

Appointment and contact IDs, confirmed attendance status, prior questions, existing outreach, owner and consent.

Actions

Send a brief contextual check-in, offer actual rescheduling availability, maintain the existing conversation and surface persistent issues to the team.

Exceptions & human review

Unknown attendance does not enroll automatically. Existing manual contact, opt-out or negative response stops the sequence. No-show status is not inferred from absent video telemetry.

Acceptance evidence

Test a known no-show, rescheduling, manual takeover and suppression. Confirm one coordinated recovery sequence and accurate original/rebooked appointment history.

“I think having this as a re. Engagement campaign would actually be incredible, honestly.”CJ · Oct 1, 07:58 · meeting reference

Trigger

John/CJ approve a bounded historical contact cohort, its outreach basis and the pilot sequence.

Owner

The client approves eligibility and exclusions; the selected native/custom coordinator executes only the authorized cohort with one message owner.

Data

Contact age/source, consent, DND, existing relationship and ownership, prior context, exclusion reason and campaign membership.

Actions

Validate the cohort, reconcile current status, review example messages, run a limited pilot and report responses, offered/booked slots and opt-outs with defined denominators.

Exceptions & human review

Ambiguous consent, prior opt-outs, active sales ownership or stale offer details exclude the lead. Failures or unfavorable responses pause the cohort for review.

Acceptance evidence

Review sample inclusions/exclusions; prove no outreach to suppressed contacts, no duplicate enrollment and reliable receipt/opt-out handling before any wider activation.

“We have tons of Zoom calls that I've done with clients over the last nine months.”John · Oct 1, 13:21 · meeting reference

Trigger

John supplies authorized recordings, current offer materials, FAQs and approved channel examples for this one offer.

Owner

John or the named content approver owns factual/tone approval; AI Acrobatics compiles, versions and tests the business corpus.

Data

Authorized/redacted recordings, cited current offer facts, approved answers, channel tone samples, source dates and approval/version state. The current page, intended 12:08 presentation, legacy interview and 2026 meeting are separate registry entries, not one blended truth source. Personal context is excluded.

Actions

Extract recurring questions and approved talk tracks, organize source-backed knowledge, review samples with John, and make only the approved offer-pack version available to the assistant. Approve brand, minimum, eligibility, projections, live locations/listing status and asset identity; preserve conflicting/retired entries for provenance rather than answering from them.

Exceptions & human review

Stale, contradictory or unapproved claims are blocked and surfaced to the content owner with the exact question, conflicting source and version. Investment judgment or a question without an approved answer routes to the human team.

Acceptance evidence

Review a versioned FAQ/tone set with John. Test supported, unknown and conflicting questions across voice/text; verify provenance and that unsupported content is not presented as fact.

“prove this out with this one offer that we have with Fast Fired.”John · Oct 1, 30:07 · meeting reference

Trigger

A lead, message, appointment, receipt or exception changes state, or an authorized team member opens a lead to review/take over.

Owner

The client team owns intervention and attendance status; the agreed operator workspace provides synchronized visibility and enforces the agreed conversation ownership.

Data

Linked GHL IDs, approved lead context, readiness/next step, self-reported preparation versus any separately confirmed player signal, approved pack/asset version, message and appointment receipts, handoff status, failure queue and defined funnel event denominators.

Actions

Show lead context and next actions, open the underlying CRM record, expose failures and unresolved questions, allow authorized review/takeover, and measure offered/booked/confirmed/attended events by cohort.

Exceptions & human review

Unknown or unreconciled status stays visibly unresolved. Failed sync enters the queue. Role restrictions protect access; takeover suppresses pending assistant actions rather than relying on a dashboard badge alone.

Acceptance evidence

Verify the linked GHL record, representative failure visibility and role access. Demonstrate takeover suppression and state persistence after refresh, mobile layout and reload. Reconcile dashboard counts to the agreed event definitions.