System health
Click "Run health check" β you'll get a plain β /β οΈ per connection.
Business KPIs
π¨ Needs attention
Checkingβ¦
Clients
| Client | Vertical | Plan | Status |
|---|
π§ Vanilla onboarding
Form submissions land here β one click turns them into a client login.
Agent performance
| Agent | Runs | Failures | Health |
|---|
Everything, everywhere
| Client | Item | Status | Platform | Scheduled | Actions |
|---|
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
| Who | Calls | Tokens | Cost (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
| Agent | Calls | Cost (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.
anything she sent β screenshots, her "about me", a PDF, a Word doc, notes, a spreadsheet. Or click to pick.
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. If her phone is 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.
π Setup Guide β search what you're doing
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).
| Component | Version | Notes | When |
|---|
π 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-api-lab Β· /health Β· /doctor |
| Spicy dashboard | Pages elevate-dashboard-live β spicy. |
| Vanilla dashboard | Pages elevate-vanilla-dashboard β vanilla. |
| The Elevate App | Pages elevate-control-panel β app. |
| This HQ | Pages elevate-admin β admin. (+ /hq.html girls' seat) |
| Booking site | Pages elevate-book-lab β ?client=<slug>, one template for every operator |
| The bot | Worker elevate-bot-lab β NEVER edit; settings via each operator's App |
| Database | Supabase elevate-lab (kmiayheuxqtargklvwgv) |
| β οΈ Dead β never deploy | elevate-dashboard Β· green-cloud-64b8 |
π° Elevate's money
Add money in / out
Setup fees, subscriptions collected, hosting costs β anything real.
Plans on the books
| Client | Plan | Status |
|---|
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.
| Label | Audience | URL |
|---|
π 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 the operator'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.
| When | Client | How | Why | Ended |
|---|