Elevate Spicy

Elevate — Operations

Operator access only.

Elevate Spicy — home

Elevate Spicy — Ops

Elevate
Elevate Ops — jump to
Elevate
Elevate
MEDIA CONSULTING
THE CONSOLE · the house's own back end
THE HOUSEevery girl ›
🌶Spicy
the girls we run
🤍Vanilla
the everyday side
EVERYTHING
GROUPED SHORTCUTS

System health

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

Business KPIs

🚨 Needs attention

Checking…

🩺 Platform health & support

Every operator's live state · diagnose before support touches anything · life-safety numbers (PIN) · deploys · our AI spend next to theirs.

💡 Operators at a glance
Loading…
🔎 Diagnose one operator
⛑ Safety numbers (PIN-guarded)
Loading…
📦 Deploy store
Loading…
⚡ AI spend — ours vs clients (30d)
Loading…

Clients

ClientVerticalPlanStatus

🌶 Spicy onboarding

Text her a self-onboard link — she fills it on her phone, her answers land back here for your approval (nothing goes live until you apply them).

Sent forms

Loading…

Agent performance

AgentRunsFailuresHealth

Money & infrastructure

🤖SMS Bot HealthVersion + model, live ☁️CloudflareWorkers, Pages, domains, R2 🗄️SupabaseThe database — SQL editor lives here ⚡VeniceAI keys + credits
🚪 The doors — every app & site

Doors into an operator's surface go through 🔑 Support access — pick her, say why, the entry is logged (she sees it), then her seat opens. Elevate-owned/public surfaces open directly.

💌Booking Template?client=<slug> — the public front door (Elevate-owned) 🌐Elevate Landingthe public page

🚨 Safety escalations

Acknowledge every live row the moment you see it. ⓘ

Loading…

Everything, everywhere

ClientItemStatusPlatformScheduledActions

Requests for review

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.

📥 Drop her files here
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. ⓘ

Her pack

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

🔗 A fresh setup link

Her old link stops working the moment you make a new one. ⓘ

🔑 Passwords & getting in

Everything about how you get into this console and into the engine — in one place, not behind a search box.

Your admin password
It is the password on your [email protected] Supabase login. Same one for the console, the doctor and every admin surface — you sign in ONCE and nothing inside ever asks again.
The 🩺 Engine Doctor
It has NO password of its own any more. The Doctor buttons open it signed in with your CURRENT session. If an old /doctor bookmark ever asks for a password, that bookmark is stale — open the Doctor from here instead.
Forgot it entirely?
The reset email lands in your admin inbox, you set a new password, and it works everywhere immediately. No code, no waiting on anyone.

🔒 The second door — your admin PIN

Two doors. Your password gets you in here. A separate admin PIN is what turns a •••• into a value — different secret, different store, so one cracked password is never enough to see anybody's details.

Checking…

Ask for my PIN again after ⓘ

👁 Who looked at what

Every personal field ever opened from this console — the field, the time and the device. Never the value. A log that copies the secret is a second place the secret leaks from.

Loading…

🚨 What would switch security mode on

These run on the server. A browser lock is theatre — whatever a page does or does not do, a blocked address gets nothing and a locked console cannot reveal, export or write, including from a session that was already open.

  • A wrong PIN from an address and a device neither of which has been seen here before
  • Five wrong PINs inside fifteen minutes
  • Twelve personal fields opened inside ten minutes — that is a sweep, not a support call
  • An export from a device that has never been seen
  • The same session used from two countries inside an hour

When it arms: that address is blocked · the console goes read-only · no reveals, no exports · and it tells you in plain words what happened.

🔑 Passwords & getting in — your admin password, the reset, the Doctor and your admin PIN all live on their own screen now.

📖 Setup Guide — search what you're doing

🗝 Keys

Paste a key once — it is encrypted, and reachable from any computer you are logged into. ⓘ

What is on the shelf

NameEnds withLast used by a deploy

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-api-lab · /health · /doctor
Spicy dashboardPages elevate-dashboard-live → spicy.
The Elevate AppPages elevate-control-panel → app.
This admin appPages elevate-admin-lab (one login: home + console + onboarding)
The girls' ONE APPPages elevate-myworld-lab — My World + Bookings/app.html + Money/money.html + Studio/studio.html, one origin, one login
Booking sitePages elevate-book-lab — ?client=<slug>, one template for every operator
The botWorker elevate-bot-lab — NEVER edit; settings via each operator's App
DatabaseSupabase elevate-lab (kmiayheuxqtargklvwgv)
☠️ 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

Set plan pricing to show an estimated recurring total.

HQ links — yours + what each girl sees

Audience "girl" shows on every girl's 💸 Money page (inside HER one app). "admin" shows only to you here.

LabelAudienceURL

📇 Clients — the vault

Everything we hold on a client to run her setup. ⓘ

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

🎁 Gifts

🗒 Our notes on this client

Open a client to see her domains.

Removes everything keyed to her, including her login. Type her name exactly to arm the buttons. ⓘ

Open a client to see her feature map.

🔑 Support access — logged, 15 minutes, one use

A repair tool, not a window into her business. ⓘ

WhenClientHowWhyEnded

📱 Phone setup — her bot phone, step by step

Pick the operator and open her pack: her keys prefilled, the QR, and the exact Tasker profiles for HER phone (outbox polls every 2 minutes — Tasker's minimum). 🔒 Opening a pack fetches her relay keys and is logged — she can see the entry, same as Support access.

No pack open — pick her and press the button. Nothing is fetched (or logged) until you do.

⚙️ How this console looks

The same nine palettes, the same metal, icons, tiles, buttons and marks the girls' app has. Yours, not theirs — nothing here reads or writes a single operator's row.