Elevate — Operations

Operator access only.

🏠

Elevate Ops

Elevate Ops — jump to

System health

Click "Run health check" — you'll get a plain ✅/⚠️ per connection.

Business KPIs

🚨 Needs attention

Checking…

Clients

ClientVerticalPlanStatus

🧁 Vanilla onboarding

Form submissions land here — one click turns them into a client login.

Loading…

Agent performance

AgentRunsFailuresHealth

Everything, everywhere

ClientItemStatusPlatformScheduledActions

Command the AI

Plain English. e.g. "make this client's next week spicier" · "pause posting" · "redo that caption". Unsafe/unclear commands are parked for review, never guessed.

Command history

Growth Strategist — what to do next

No report yet — generate one.

Company-wide AI spend — last 30 days

Per girl / client

WhoCallsTokensCost (est)Own key?

Every girl brings her OWN Venice key + prepaid credits — "own key ✓" means her AI runs on her money, not Elevate's. Girls watch their own spend in their dashboard (You → Your AI) and their HQ.

Per project / agent

AgentCallsCost (est)

Support tickets — girls log them, you fix them

Each new ticket is also emailed to hello@. The girl never gets your personal contact.

Loading…

🪄 Step 1 — dump everything you already have; AI prefills her profile

Her website link, screenshots of her ads/profiles, any brief she gave you — throw it all in. Girls have DIFFERENT services and rates; nothing is assumed, nothing invented.

screenshots of her profiles (up to 4)

Step 2 — her prefilled draft (edit anything)

📬 Sent forms — answers land here

None yet.

Manual entry (the old way, still here)

Enter her details once. It pre-fills her whole pack from the master template and outputs the variables/codes to feed HER bot — the master prompt is never rewritten, and nothing here touches the live profiles table. Sophie: her phone's already set — this is just "add her number + generate her variables".

Her pack

Fill the form and generate — you'll get her complete variables + the exact onboarding steps.

Version history — what shipped, when

The engine stamps itself automatically on its first run after a deploy. Log Pages deploys here by hand (one line each).

ComponentVersionNotesWhen

🛟 Fix it yourself — search what's happening

💬 Ops chatbot — ask in plain words

Grounded in YOUR map and rules only — exact worker/Pages names, never guesses.

📖 The map — exact names (never guess these)

Engine (API)elevate-dashboard-api → api. · /health · /doctor
Spicy dashboardPages elevate-dashboard-live → spicy.
Vanilla dashboardPages elevate-vanilla-dashboard → vanilla.
The Elevate AppPages elevate-control-panel → app.
This HQPages elevate-admin → admin. (+ /hq.html girls' seat)
Booking sitePages elevate-armarni → book.armarnib.com
The botWorker armarni-bot — NEVER edit; settings via the App
DatabaseSupabase elevate (roiecljeneqwoczbarle)
☠️ Dead — never deployelevate-dashboard · green-cloud-64b8

💰 Elevate's money

Add money in / out

Setup fees, subscriptions collected, hosting costs — anything real.

Plans on the books

ClientPlanStatus

Est. recurring uses the placeholder pricing — flag: real pricing still owed a decision.

HQ links — yours + what each girl sees

Audience "girl" shows in every girl's HQ (hq.html on this same address). "admin" shows only to you here.

LabelAudienceURL

📇 Clients — the vault

Everything we hold on a client to run her setup — payment details for her booking site, her gift/Prezzee details, her URL name, our notes. Stored in the back end, not on a laptop. (Her customers' data is hers alone — that isolation stands.)

💳 Payment details (feed her booking site — exactly like Armarni's flow)

🎁 Gifts

🗒 Our notes on this client

🔑 Support access — logged, 15 minutes, one use

This is a repair tool, not a window into her business. Best path: she taps “Let Elevate in for 15 minutes” in her HQ, then her name shows here with a green ✅ consent window and you open her seat inside it. The emergency path (no consent yet) still works — and every entry, either way, is logged here and shown to her in her own HQ. Nothing from the session is stored.

WhenClientHowWhyEnded