HOLD ACTIVE — decisions are logged for review; nothing is sent. A skip or escalate still retires its item (with an audit row); approvals record only.
The console was updated while this tab was open — you are looking at an older version of the page. Click here to reload.
Console
Sign in with your toastweddings.com account.
Toast console users only.
Console
loading…
everything you need to do, one at a time, in order of importance
Learned Rules
Two steps, both yours: APPROVE says a rule is right (it starts shaping sidebar/console drafts immediately) · PROMOTE pushes every approved rule through the contradiction check and merges the passing ones into the agent stack, where it governs ALL drafting — console, pipeline, and Claude Code sessions alike. Hold = parked · Deny = dead.
The stack is the single source of truth. An approved-but-unpromoted rule is an interim state — promote to make it permanent everywhere, or it only shapes sidebar drafts.
Reads the last 7 days of decisions and PROPOSES rules for your review. Promotes nothing.
Contradiction-checks every approved rule, merges the passing ones into toast-ai-context, reports per rule. Takes a few minutes.
Lead Management
loading the full lead universe… (first load takes ~30s; cached 10 min after)
The flow — where every lead stands (click to filter)
Originating lead source (stacks with every filter above)
Created between
andDaily digest
what happened in the last 24 hours
Delivery preview
loading…
Declines — pending confirmation
Leads who declined, asked us to stop contacting them, or unsubscribed from email (by email reply or SMS). Every draft and send to them — email and SMS — is SUPPRESSED until you decide, except when they asked only for texts to stop ("stop texting me"), which holds SMS alone. Mark lost runs the guarded lost path (won deals and live projects are never touched) and they are never contacted again; try again releases them back to normal cadence. We never change their subscription settings for them.
Loading…
Inbound — no auto-draft
They wrote to us and we did NOT write back automatically — a suppressed contact or a lost lead. Nothing is ever blocked from reaching us: these messages are ingested and listed here so a person can answer them by hand.
Loading…
Soft hold — waiting on their timeline
These couples asked for time ("we won't know our venue for a week", "we're deciding in 30 days"), so every proactive touch is suppressed until their date. On that date they re-enter cadence automatically and the first message back references what they asked for. This is the third ending alongside closed won and closed lost: nothing sits untouched, and nobody gets nagged on our schedule instead of theirs.
Loading…
History — everything that happened with a person
What was said, what a rep decided, and how anything left the queue — newest first, last 30 days. Older than that lives in HubSpot. Search by name, address or phone.
Auto-resolved — every draft that left a lane, and why
Every draft that left a lane — removed by a newer inbound, a send guard or the sweeper; redrafted; skipped or escalated by a rep; or resolved because the thread was answered — with who did it and the text it contained. Removals are listed first: those are the ones that could silently cost a reply, so the full message is kept here even after the draft is gone. If a removal was wrong, the text is right here to send by hand.
Loading…
Created
every deal, quote, invoice, task and note the AI actually made — with links straight into HubSpot, so auditing does not mean digging. Nothing here sends or changes anything.
Activity
everything sent — and console decisions awaiting the hold lift. Outcome chains land with the engagement ledger.
Sales Scoreboard
loading…
Pipeline
loading…
Media picks
why each draft's example links were chosen by the weighted ranking · one row per selection · admin only
Health
review-loop measurement (design § 4) — test rows excluded · admin only
Approval-unchanged rate by touch type
Enrichment errors (items withheld from queues)
Recent server errors (last 50 — nothing errors silently)
Talent notifications
What the ops engine would send to talent (shadow) and does send (direct), per project stage. The thing to watch is disagreements with the HubSpot flows. Nothing changes for talent until a stage turns READY and is switched to direct.
loading…
Review requests
What the review-request engine would ask for (shadow) and what it has drafted for release (live), one row per couple. The thing to watch in shadow is the volume and the gate reasons; nothing goes out until the mode is flipped and a person releases each ask.
loading…
j/k move · a approve · e edit · s skip
Loading…