Docs / Client Engine

Client Engine: Sequences, Booking & Pipeline

The client engine is the part of AI OS that turns a captured lead into a booked, nurtured, tracked customer. It is five connected features: Google Maps local prospecting that finds businesses worth pitching, a Local SEO / Google Business Profile audit that gives you the pitch itself, email nurture sequences that follow up with every new lead automatically, appointment booking built into your generated sites, and a drag-and-drop pipeline kanban in the CRM. Together they cover the loop from finding a prospect to tracking a customer.

Google Maps local prospecting

Enter a niche and an area — "dentist" in "Austin, TX" — and AI OS pulls real Google Business Profile listings and scores each business 0–100 for website-upgrade fit. The scoring is deliberately biased toward the platform's own managed-website offer: a business with no website at all scores highest, a Facebook page standing in for a website close behind, then sites without HTTPS. Phone numbers, review counts, and ratings add signal (an established, well-reviewed business with no website is the perfect prospect).

API-based, never scraped

Prospecting uses licensed data APIs — DataForSEO's Maps results (the same account that powers the SEO agency) or the Google Places API — never scraping Google Maps itself. Email discovery only ever fetches the business's own public website (homepage and contact page, two pages maximum) looking for a published contact address.

Into the CRM, deliberately

Selected prospects with a public email become CRM contacts (tagged, with the fit score and reasons on their timeline); businesses without one stay in the run list as call-first leads with their phone number. Cold prospects are never auto-enrolled in email sequences and nothing is ever auto-emailed — cold outreach is an operator decision, made per contact.

Local SEO & Google Business Profile audit

Click Audit on any prospect with a website and AI OS runs its full 7-agent SEO audit on their domain — with a 7th dimension added specifically for local businesses: Local SEO / Google Business Profile. It scores GBP completeness (hours, phone, website link, photos, description, category, claim status), review signals, and — the most persuasive number in the whole report — whether the business actually shows up in the Google local pack for its own niche keyword in its own city.

Because the audit was launched from a prospect, AI OS already knows the exact business (name, category, place ID, rating) from the Maps listing rather than guessing from the domain — so the Local SEO score is grounded in the real listing, not a fuzzy name match. A weak score becomes a top-priority "claim and complete your Google Business Profile" quick win, which flows straight into the audit email below. Non-local businesses with no matching Google Business Profile are excluded from this dimension entirely rather than scored as a misleading zero.

Emailing the audit as an outreach opener

A completed audit — any audit, not just prospect-sourced ones — has an Email to Lead button. It sends the headline findings as a clean, personal email: the overall score, the three weakest dimensions, an AI-search-readiness callout when it's weak, and the top three quick wins with time estimates. For a business that came through Local Prospecting, that report usually leads with the Google Business Profile gaps — the single most persuasive thing you can put in front of a local owner.

The email is rendered deterministically from the audit data (no AI call, so every send is free and predictable), and every send is logged — on the audit record and as a CRM contact + timeline note — so the pipeline shows exactly who has been pitched. It uses the same Resend/SMTP sender and unsubscribe compliance as nurture sequences, but is always a single, deliberate, operator-clicked send — audit emails are never auto-sent or added to a sequence.

Email nurture sequences

A sequence is an ordered set of email steps with per-step delays — for example: instantly on signup, again at 24 hours, again at 4 days. New leads enroll automatically the moment they arrive, from whichever capture points you target.

Triggers and targeting

TriggerEnrolls
all-leadsEvery new lead from any capture point
site-leadContact-form submissions on hosted sites (optionally scoped to one site)
free-auditFree SEO/AEO audit requests on the public site
bookingVisitors who book an appointment — ideal for reminder and follow-up sequences

AI-drafted, human-approved

Describe the goal ("convert dental-site leads into consultation bookings") and the marketing agent drafts the whole sequence — step count, delays, subjects, and short plain-spoken bodies with {{first_name}} and {{site}} personalization. The draft lands in the editor for your review; sequences are always created disabled and only send after you deliberately switch them on. A test button sends step one to your own inbox first.

Sending discipline

  • Auto-Mode governed — each send passes the platform's approval gate: automatic in supervised/auto mode, one approval per send in manual mode
  • Compliance by construction — every email carries a one-click unsubscribe link (HMAC-tokened, unforgeable), a List-Unsubscribe header, and your business address; unsubscribing stops everything for that address instantly and permanently
  • Failure-safe — failed sends retry with a hard cap and never skip a step; one active enrollment per contact per sequence; paused sequences hold in place
  • Bring your own sender — a Resend API key (HTTPS, immune to blocked SMTP ports) or any SMTP server, configured in Settings → Email Sending

Appointment booking on generated sites

Appointment-based businesses — clinics, salons, trades, consultants — can include a booking section on any site AI OS builds. It renders a plain HTML form (date picker plus your standard time slots) with no JavaScript dependency, the same philosophy as the lead-capture form.

The platform is the availability source of truth. It knows your business hours, open days, booking horizon, and existing appointments — so a slot that was just taken never produces a dead error; the visitor gets a friendly page re-offering that day's remaining free times. Availability is configured in Settings → Booking (slot length, hours, open days, how far ahead visitors can book).

What a confirmed booking does

  1. Creates the appointment and blocks the slot (double-booking is impossible, and the same visitor can't book the same day twice)
  2. Lands the contact in the CRM with a booking activity on their timeline
  3. Enrolls them in any matching booking-trigger email sequence
  4. Emails the visitor a confirmation with a calendar (.ics) invite attached
  5. Pings you on Telegram/Slack, and lists the appointment in the dashboard's CRM view

Cancelling an appointment from the dashboard automatically emails the visitor — a cancellation is never silent.

CRM pipeline kanban

The CRM view opens with a five-column pipeline board: lead → audited → onboarding → customer, plus churned as a terminal, manual-only column. Drag a contact card to move it; every move is validated server-side against the canonical stage set and logged as a stage-change activity on the contact's timeline — an audit trail, not just a board.

Stages also advance themselves from real platform events: a free audit promotes a contact to audited, a purchase to customer. Automatic advancement only ever moves contacts forward, so a manual placement is never silently undone.

Setup

StepDetail
Prospecting providerSettings → SEO Agency: DataForSEO credentials (shared with the SEO agency) or a Google Places API key — then CRM → Local Prospecting
Local SEO auditUses the same DataForSEO credentials as prospecting/SEO — no separate setup. Click Audit on any prospect with a website
Email senderSettings → Email Sending: a Resend API key or SMTP credentials, plus a From address on your verified domain (verify the domain with your provider for inbox placement)
First sequenceCRM → Email Sequences: describe a goal and click AI Draft, review the steps, Test to your own inbox, then enable
Booking availabilitySettings → Booking: slot length, business hours, open days, booking horizon — then add a booking section to a site and rebuild it
PipelineNothing to configure — the board reads the stages your contacts already have

Frequently asked questions

Does AI OS scrape Google Maps for leads?

No — prospecting uses licensed APIs (DataForSEO or Google Places), never scraping Google itself. Email discovery only reads the business's own public website, and cold prospects are never auto-emailed.

Does the SEO audit check a Google Business Profile?

Yes — Local SEO/GBP is the 7th audit dimension: profile completeness, review signals, and local-pack rank for the business's niche keyword. Non-local sites without a matching profile are excluded rather than scored as a misleading zero.

Does AI OS write the nurture emails itself?

It drafts them; you approve them. Sequences are created disabled, and nothing sends until you review, enable, and (in manual mode) approve each send.

How are unsubscribes handled?

Every email carries a one-click unsubscribe link and List-Unsubscribe header by construction. Unsubscribing stops all sequences for that address instantly and suppresses it permanently.

Does the booking form need JavaScript?

No — it's a plain HTML form, validated server-side at submit. A just-taken slot gets a friendly page re-offering that day's free times.

Which email provider do I need?

A Resend API key (HTTPS — works even where SMTP ports are blocked) or any SMTP server such as Gmail with an App Password.

What stages does the pipeline use?

lead, audited, onboarding, customer, and churned (terminal, manual-only) — enforced server-side, with every change logged on the contact's timeline.