Internal operator console
Qualification, conversion, blockers, and next actions
Lightweight sales handoff, not a CRM
Record the call outcome, open qualified workspaces, and keep customer blockers visible.
Qualification remains inclusive for legitimate businesses while launch readiness stays separate. Hard disqualifiers are policy, authority, access, deceptive claims, and guaranteed-result expectations.
Console state
- Prospects
- 3 fixture rows
- Selected
- qualified_for_dashboard
- Conversion route
- live
Prospects
Review queue
Summit HVAC
Jordan Lee / $3,000-$7,500
Jordan Lee
$3,000-$7,500
call_completed
Free Meta audit
Northline Roofing
Maya Chen / $7,500+
Maya Chen
$7,500+
qualified_for_dashboard
Website plus Meta bundle
ClearFlow Plumbing
Andre Mills / $1,500-$3,000
Andre Mills
$1,500-$3,000
follow_up_needed
Free ad strategy
Lead delivery and quality
Capture path, handoff path, and feedback mode
Keep the lead capture destination separate from the handoff destination. Meta Instant Form is the default first path when it fits, while alternate destinations need readiness evidence before launch.
Delivery summary
Raw lead delivery, quality feedback, and report confidence are tracked separately.
- Lead capture destination
- Meta Instant Form
- meta instant form
- Lead handoff destination
- Shared sales inbox and Jordan as response owner
- pending response time confirmation
- Quality feedback mode
- aggregate feedback
- Report label
- Raw lead count available; quality feedback not complete.
Meta Instant Form
meta instant form
default ready
Default first path for this offer. Questions, privacy path, delivery, and follow-up owner still need launch-gate evidence.
Managed Website Agent form
managed website form
qa required
Use as alternate when the offer needs a page, proof, or higher-intent form before the lead is captured.
Existing website or booking path
existing external path
verify only
Verify live page, mobile fit, lead delivery, response owner, and fallback plan before approval.
Feedback modes
Operator chooses the mode based on where leads are actually handled. Unknown-quality mode is valid, but it lowers report confidence.
Direct per-lead feedback
directLeads enter the product through Meta Instant Form, managed form, or direct integration.
Weekly aggregate feedback
aggregateLeads are handed off to an outside inbox, phone, booking, CRM, or sales workflow.
Unknown-quality mode
unknownRaw lead data exists, but the business has not provided quality feedback yet.
Meta Instant Form
delivered
contactable
raw lead included
customer lead
Managed form QA
delivery test passed
unknown
excluded from performance
test lead
Weekly report
Draft, review, approve, and log delivery
Reports can be generated from stored records, but first-release customer sends require internal approval. Stale, partial, unknown-quality, and reduced-confidence labels stay visible before approval and after delivery.
Current report draft
Reporting period: June 17-23, 2026
- Last data refresh
- June 23, 2026 at 8:10 AM
- partial data
- Quality label
- unknown quality
- reduced confidence
- Delivery status
- not sent
- Reviewer note
- Raw spend and lead counts are present. Lead quality is incomplete, so recommendations should stay conservative.
Work completed
drafted
Lead path confirmed, early pacing reviewed, weak creative angle paused, and QA test leads excluded.
Spend and leads
drafted
$684 spend, 11 raw leads, 3 known good leads, 4 leads still unknown-quality.
Client actions
needs review
Customer should confirm unknown lead quality and response-time ownership.
Recommended changes
reduced confidence
Hold budget steady and improve qualification copy before increasing spend.
stale data
not applied
Data refresh is current enough for this draft.
partial data
applied
Quality feedback is incomplete for the reporting period.
unknown quality
applied
Raw leads exist, but not every lead has quality feedback.
reduced confidence
applied
Recommendation copy must explain the cautious confidence level.
Internal fix tasks
Missing, stale, or partial report data must create operator work before the next report cycle.
Request missing lead quality feedback
openOwner: operator. Unknown-quality label is applied to 4 leads.
Check weekly refresh before approval
queuedOwner: operator. Report should not be approved if data becomes stale before send.
jordan@example.com
not sent
Awaiting approval
First-release report send is blocked until approved_to_send.
First 72-hour monitor
Launch health, support escalation, and manual exceptions
Use this workspace for health, delivery, tracking, lead routing, policy, spend pacing, page/form availability, provider drift, and data freshness. The first 24-72 hours are not optimization conclusions; customer action is limited to funding, access, approvals, business clarification, client-owned lead delivery, or unresolved material disruption.
Active monitor
hour 18 of 72. Last check: June 23, 2026 at 11:10 AM.
- Learning-window rule
- Separate launch health and material blockers from normal 24-72 hour learning-window noise.
- Recommendation confidence
- early directional
- Notification gate
- client action needed only
Delivery state
pass
none
health
Campaign delivering in approved state.
Spend pacing
watch
low
health
Spend is inside cap, but needs next scheduled check.
Policy and ad review
pass
none
material disruption
No policy block visible in latest provider status.
Conversion recording
watch
low
tracking
Lead delivery is visible; event quality still needs later confirmation.
Page and form availability
pass
none
health
Destination and form rendered in the latest check.
Mobile state
watch
medium
health
Mobile destination works, but image weight remains a follow-up.
Lead routing and handoff
needs customer action
medium
client action needed
Response owner confirmation is still open.
Wrong geography or offer signs
pass
critical
material disruption
No spend outside the approved service area or offer was detected.
Provider drift
watch
medium
health
Provider object references still match the approved build sheet.
Data freshness
pass
medium
health
Latest provider sync and internal refresh are current enough.
Early performance noise
do not escalate
none
learning window
Too early for optimization conclusions.
Support ladder
Default every issue to the lowest-client-work path before asking for customer action.
Auto resolved
auto resolvedThe system detected and fixed the issue without human action.
Agent resolved
agent resolvedThe agent diagnosed and executed an approved safe action inside the envelope.
Operator required
operator requiredEvidence, recommendation, and steps are prepared for internal handling.
Client required
client requiredCustomer-owned access, funding, approval, lead delivery, or business clarification is required.
Severity routing
low
operator watchNormal watch item or low-risk health uncertainty.
No customer notification unless action is needed.
medium
support taskCustomer action needed or unresolved health check.
Notify only with a clear client action or material disruption.
high
protective pause reviewPolicy, broken lead routing, wrong geography, broken page, or spend risk.
Escalate to customer when disruption affects launch outcome.
critical
founder operator escalationSpend, compliance, customer complaint, or provider state risk.
Immediate internal escalation and customer-facing next step.
Lead alert response owner
client action needed
high
client required
actionable
Confirm the response owner receives alerts and can handle new leads during business hours.
Mobile destination weight
internal fix in progress
medium
operator required
early directional
Compress assets internally; no customer approval is needed because public copy is unchanged.
Notification gates
Normal learning-window variance stays internal. Client communication is notification-first, not permission-first, unless customer-owned authority is required.
normal learning window noise
suppress customer noticeEarly variance alone is not a client action or material disruption.
client action needed
allow customer noticeThe customer must confirm response owner and lead handling.
unresolved material disruption
allow customer noticeBroken delivery, policy, page, form, tracking, routing, or spend guardrail issue.
Campaign plan and creative
Draft launch artifacts before external action
Use this workspace to prepare the Meta Leads campaign plan, build sheet, claims review, static creative, copy variants, QA, and Instant Form draft. Static image generation is direct in the MVP; Arcads is not required. Launch remains blocked until approvals and readiness gates pass.
Campaign plan draft
Emergency HVAC repair estimate request for Denver metro, excluding lower-priority suburbs.
- Objective
- Meta Leads
- Destination
- Meta Instant Form first, managed landing page fallback
- Budget
- $85/day inside the approved monthly cap
- Default path
- Create a new ad set for this plan; no existing ad set is required.
Campaign
draft
Leads objective, paused-first build, no live spend from draft state.
Ad set
draft
New ad set with approved geography, schedule, placements, and budget.
Ad creative
needs review
Static image asset plus default copy variants after claims review.
Instant Form
draft
Questions, privacy text, and lead handoff need review before approval.
UTMs
draft
Source, campaign, ad set, ad, creative angle, and variant labels drafted.
Licensed local HVAC team
approved claim
State license lookup and customer intake
Confirm source link before customer approval.
Same-day emergency response
needs review
Call notes only
Ask customer for terms and proof before public use.
Guaranteed leads or savings
banned claim
Not supportable
Block from ads, pages, forms, and reports.
Emergency repair static image concept
generated static image
draft
Direct generation path; Arcads is not required.
Technician truck photo
customer asset
needs_permission
Confirm usage rights and avoid implying unavailable staff or locations.
Emergency response
draft
needs review
Need HVAC help today? Tell us what is happening and our team will follow up.
Home comfort
draft
needs review
Get your heating or cooling issue reviewed by a local team serving Denver metro.
Qualification outcome
Record call result
Mark whether the prospect should receive dashboard access, follow-up, or a respectful disqualification. Conversion remains gated until the outcome is `qualified_for_dashboard`.
Blockers
Customer-owned or operator-owned gaps
Blockers should be visible in the customer dashboard when they need customer action and internal-only when they require operator work.
Free review evidence
Review customer-visible audit and launch-plan output
Operators review scan evidence, tracking confidence, unknowns, and action-plan findings before anything is shared. Customers get the plain-language recommendation, not raw technical scan chores.
Primary URL
stored
high
Homepage, title, H1, phone CTA, and privacy link were recorded.
Conversion path
needs follow up
medium
Phone CTA is clear. Form path exists but handoff destination is unknown.
Proof and claims
needs review
medium
Reviews are present. License and emergency-response claims need source confirmation.
Mobile and speed proxy
warning
medium
Mobile view is usable, but slow hero assets may hurt paid traffic.
Meta dataset candidate
found
medium
Dataset-like ID discovered, but recent lead event quality is not confirmed.
GA4 or GTM
unknown
low
No trusted operator confirmation yet.
Duplicate or wrong-action tags
not confirmed
low
Needs scanner and operator review before customer summary.
Confirm lead handoff destination
customer
launch plan confidence
Verify dataset and lead events
operator
tracking confidence
Collect public proof for response-time and license claims
customer
customer-visible audit copy
Confirm starting budget comfort
customer
package recommendation
Offer clarity
usable
medium
Emergency HVAC repair is a clear first offer, but proof for response time should be confirmed.
Lead path
partial gap
medium
Phone calls are easy to find. Form routing and response owner still need confirmation.
Tracking
blocks confidence
low
Do not promise reporting quality until the dataset, event mapping, and lead handoff are verified.
Recommended 14-Day Launch Plan review
Website scan, tracking candidates, free strategy answers, and call notes support a Website plus Meta recommendation.
- Confidence
- medium
- Package recommendation
- website meta bundle
- Unknowns
- Tracking quality, lead response owner, proof claims, and final budget comfort remain open.
- Boundary
- Sales handoff only, not final execution packet
Do not share until tracking uncertainty and proof language are written in plain customer terms.
Meta access readiness
Record provider access and assets
Slice 4 stays dry-run/manual safe. Operators can record the account, Page, tracking, form, funding, and approval state without activating live Meta spend.
Ad account
verified
Selected dry-run account act_demo_4812
operator
Page identity
verified
Summit HVAC Denver Page matched to business
operator
Pixel or dataset
needs review
Dataset found, event health not confirmed
operator
Lead form or Instant Form
dry run ready
Draft form preview created by dry-run provider
operator
Funding and account health
blocked
Funding owner and restriction check still needed
customer
Approval and launch gate
blocked
Launch approval snapshot and gate pass missing
customer
ad account
Summit HVAC ads
act_demo_4812
meta:ad-account:act-demo-4812
selected for dry run
page
Summit HVAC Denver
page_demo_2281
meta:page:page-demo-2281
identity verified
dataset
Website leads dataset
dataset_demo_6409
meta:dataset:dataset-demo-6409
needs tracking review
instant form
Emergency HVAC estimate request
form_demo_1140
meta:instant-form:form-demo-1140
dry run only
Dry-run build state
Review paused provider objects
Dry-run builds store stable references for campaign, ad set, ad, creative, and Instant Form pieces. Partial failures should keep the saved references and retry only the missing or failed piece.
campaign
paused simulated
meta:campaign:dry_run_1001
campaign:dry-run-1001
stored
ad set
paused simulated
meta:adset:dry_run_2001
ad-set:dry-run-2001
stored
ad
paused simulated
meta:ad:dry_run_3001
ad:dry-run-3001
stored
creative
draft simulated
meta:creative:dry_run_4001
creative:dry-run-4001
stored
instant form
retryable failed
meta:form:dry_run_5001
instant-form:dry-run-5001
retry missing fields only
Website Agent setup
Record preview, domain, tracking, form, QA, and publish readiness
This is a managed landing page workflow, not a broad builder. Operators can record the controlled site records needed by the customer-sites preview path. Public publish remains blocked until the exact site version has an approval snapshot and QA evidence.
Preview routing
ready
Draft preview URL points to one site_id
operator
Draft version
ready for review
Version v2 is available for customer review
operator
Published version
not published
Production route has no published version yet
operator
Custom domain
needs dns
Customer-owned domain recorded; DNS and SSL pending
customer
Tracking
needs review
Pixel, GTM, GA4, and event mapping need operator verification
operator
Managed form
draft
Fields and lead handoff are not QA-passed
operator
Publish gate
blocked
Requires approval snapshot and QA evidence
customer
v2
draft
/preview/12121212-1212-4121-8121-121212121212
not requested
v1
superseded draft
internal only
superseded
published
none
blocked
approval required
Approval snapshots
Create and review immutable approvals
Operators create snapshots from reviewed artifacts. A decided approval should never be edited in place; material changes create a new snapshot and supersede the old one.
campaign_plan
v3
requested
pending
qa-meta-leads-2026-06-23
site_version
v2
viewed
pending
site-qa-mobile-form-2026-06-23
Launch gate and waivers
Classify readiness before spend or publish
The gate records hard blockers, waivable warnings, required evidence, waiver authority, and the approval snapshot used for launch activation.
Execution records
Track safe external changes
Every provider, publish, report-send, or manual fallback change needs actor, approval source, status, idempotency key, provider IDs, evidence, failure reason, and next recovery step.
Offboarding
Stop changes, export, revoke, clean up, and archive
Operators need one place to confirm the customer choices, stop unsafe new work, package customer-owned files, remove product access, apply retention rules, and preserve the required audit history.
Offboarding status flow
Current organization status is offboarding. Final churn or archive is blocked until export, revocation, removal, and retention cleanup have evidence.
Request received
complete
customer_success
Cancellation request, reason, requested end date, paid-through date, and affected products are recorded.
Stop new mutations
active
system
New campaign changes, page publishes, report sends, and non-offboarding jobs are blocked.
Export and handoff
in progress
operator
Package customer-owned artifacts, reports, approvals, task history, and handoff notes.
Access and routing removal
queued
operator
Revoke product-controlled access, remove product webhooks, and disconnect product lead routing.
Retention cleanup
queued
system
Delete or de-identify customer-scoped working data after export and retention checks.
Churn/archive
blocked
billing_admin
Final archive waits for export completion, required removals, and retained-record confirmation.
Stop-new-mutations state
Only export, revocation, removal, retention, billing, and customer notification actions can run.
- new campaign or ad changes
- new page publish
- new lead webhook registration
- new scheduled report send
- new non-offboarding provider sync
Export manifest and package
Package status: preparing. Manifest separates customer-owned exports from internal records and secrets.
Managed page package
included
Page copy, approved assets, form structure, QA notes, and publish history.
Campaign and creative records
included
Approved launch plan, ad copy, static creative references, and Instant Form draft summary.
Reports and approvals
included
Sent reports, reviewed draft reports, approval snapshots, and customer decisions.
Excluded internal records
excluded
Internal-only notes, decrypted secrets, access tokens, and unrelated tenant data.
Revocation and removal tasks
Revoke product-controlled Meta access
queued
operator
Remove product lead webhook
scheduled
system
Disconnect managed lead routing
scheduled
operator
Cancel recurring subscription after paid-through date
paid through
billing_admin
Deletion and de-identification tasks
Delete or de-identify lead/contact working data
waiting for exportRetain only required audit/legal/security references.
Remove generated working files after export window
queuedRetain only records tied to billing, legal hold, security, or audit evidence.
Apply deletion tombstone for restored backups
policy requiredRestored environments must re-apply completed deletion decisions.
Final churn and archive action
Mark churned only after paid-through reconciliation, export delivery, product access removal, webhook/subscription cleanup, and retention tasks have recorded evidence. Archive remains an internal state and must not erase required history.
Audit history preservation
Offboarding cleanup removes working access and unnecessary customer-scoped data. It does not purge required audit, legal, accounting, or security records.
- Approval history, launch decisions, and external-change records remain append-only.
- Billing, invoices, payments, refunds, tax, and dispute records are retained as required.
- Credential, admin access, deletion request, and security event history remains preserved.
- Legal hold or incident evidence is retained separately from customer-facing export files.
Endpoint contracts
This console exposes the first internal vertical-slice path from prospect qualification through weekly report draft. Implemented API routes are listed without a pending marker; the remaining pending entries are explicit follow-on helpers: /api/operator/qualification-outcomes, /api/operator/blocker-tasks, /api/operator/workspaces, /api/operator/free-review, /api/approvals, /api/approvals/[approvalId]/decision, /api/waivers, /api/execution-records, /api/launch-gates, /api/launch-gates/[launchGateId]/evaluate, /api/operator/meta/provider-connections, /api/operator/meta/discovered-assets, /api/operator/meta/dry-run-builds, /api/operator/meta/paused-builds, /api/operator/protective-pauses, /api/operator/sites, /api/operator/sites/pages, /api/operator/sites/domains, /api/operator/sites/tracking, /api/operator/sites/forms, /api/operator/sites/qa, /api/operator/sites/publish-readiness, /api/operator/campaign-plans, /api/operator/campaign-plans/review, /api/operator/build-sheets, /api/operator/build-sheets/review, /api/operator/creative/claims, /api/operator/creative/assets, /api/operator/creative/variants, /api/operator/creative/variants/review, /api/operator/creative/qa, /api/operator/instant-forms, /api/operator/instant-forms/review, /api/operator/lead-capture-destinations, /api/operator/lead-capture-destinations/readiness, /api/operator/lead-handoff-records, /api/operator/leads, /api/operator/lead-feedback, /api/operator/lead-feedback/aggregate, /api/operator/lead-quality-mode, /api/operator/reports, /api/operator/reports/review, /api/operator/reports/send, /api/operator/launch-monitor-checks, /api/operator/support-escalations, /api/operator/manual-exceptions, /api/operator/offboarding, /api/operator/offboarding/exports, /api/operator/offboarding/finalize, pending: /api/operator/call-notes, pending: /api/operator/prospects/status, pending: /api/operator/onboarding-prefill, pending: /api/operator/next-actions.