Independent user logins for employees
Replace the single shared-password gate with per-user accounts so the Hub knows who is logged in. Unlocks personalization, audit trails, and is the keystone for nearly every other backlog item.
Staff Access Only
Sign in with your DNA+ Microsoft account to continue.
DNA+ · Authorized personnel only
Today's call schedule from GHL follow-up tasks. Claim a call to take it, open the contact in GHL, then mark it handled.
Claim a task when call volume is low, then mark it handled when complete.
Existing-patient working queues — package targets and lapsed-patient reactivation.
Shifts synced from QuickBooks Time. Assign each rep to a pod — changes save instantly and appear on the home pod cards.
| Contact | Location | Channel | Waiting | Status | Actions | |
|---|---|---|---|---|---|---|
|
Loading queue…
Fetching inbound messages across all locations.
| ||||||
Blended efficiency + effort across all working queues. Updates every 30 seconds — click a name for the full breakdown.
Ranked by blended Score. Raw counts shown per pod — click a name for the full breakdown.
| # | Rep | Intake | Convert | Outbound | Task Radar | Answer | Touches | Score |
|---|
No queue activity yet
As reps handle leads in Intake, Engage, Convert, Task Radar, and Reconnect, they'll rank here.
First human touch, measured on our clock — not raw wall time.
Track conversions and identify where leads convert best.
Generate PCI-compliant payment links for patients across all locations.
Generate a secure, PCI-compliant payment link for any patient. The link routes them through a branded 4Ever Young page that displays your cancellation policy before sending them to Zenoti's secure card entry.
Opens as a popup window. Password required on first launch.
— Quick Steps —
Per-location hours, scheduling rules, and service pricing for all 20 4Ever Young clinics. Pull up any clinic mid-call.
The assistant now lives on every Hub page — click the Ask DNA+ button at the bottom-right to ask about any clinic's hours, pricing, providers, or scheduling rules. Answers come straight from this Client Reference — no separate ChatGPT login.
Today's prioritized leads across all locations. Refreshes automatically every 2 hours.
Loading inbox hygiene…
Loading pipeline proposals…
Loading Reconnect…
A look ahead at what's to come for the Connect platform.
Replace the single shared-password gate with per-user accounts so the Hub knows who is logged in. Unlocks personalization, audit trails, and is the keystone for nearly every other backlog item.
Adds a second factor on top of B1. Mostly a config flip if B1 uses a managed auth provider; meaningful work if rolled in-house. Closes the security gap before B3 and B8 widen the writeable surface.
Surface brand-new leads inside the Hub within 60 seconds of GHL receiving them. Replaces Module 5.5's 2-hour cron pattern with a push-based webhook listener. Highest immediate revenue impact on the list.
Edits made in the Hub push back to GHL via API — stage changes, notes, follow-up dates. Lets reps live in the Hub for the day instead of tab-flipping. Reuses the same webhook architecture from B2.
Clock-in widget in the Hub so reps don't have to open QBT separately at the start of the day. Builds the QBT API client that B5 reuses.
Show each user their day's shift, who else is on, who's the Spanish handler today. Mostly UI work once B4's API plumbing exists. Could feed back into Module 8 assignments.
Replaces the custom GPT entirely. Real internal KB with embedded chat — reps ask "What's Apex's price for B12?" and get sourced answers from our own data. Multi-phase: ingest pipeline, retrieval, chat UI, admin tools.
Each clinic logs in directly to update hours, providers, services, promos, and flash sales — all flowing into the same KB that B7 serves to reps. Removes the manual sync where ops re-keys every change. Largest single item; build last.
B1 is the keystone — it blocks B6 outright and meaningfully improves every other item. B2 and B3 share the same GHL webhook infrastructure, so they're built back-to-back. B4 and B5 are essentially one project split across two deliverables. B7 and B8 are tightly coupled because the data clinics edit in B8 is the data B7's KB serves to reps — building two separate knowledge stores would be a mistake. B8 sits last because it depends on the most things and is the largest scope.