Sign in to continue
Appointments a homeowner asked to cancel that are still open in Enabled+. Each row opens straight to the lead’s Confirming panel so a person can cancel or reschedule — the tool never cancels on its own. Same list feeds the Enabled+ side-panel and the calendar highlights.
The week at a glance — same appointments, laid out like Enabled+. Anything caught as a cancel that is still open lights up here too. Different view, same list.
People who can use ConfirmLink, what they can do, and which stores they see. Adding, changing a role, or disabling someone writes through the Worker at go-live — here it is a preview on sample users.
| Name | Role | Stores | Status | Added |
|---|
| What they can do | Agent | Admin |
|---|---|---|
| Work the queues (Today, Cancel Watch) | ✓ | ✓ |
| Open leads in Enabled+ | ✓ | ✓ |
| See Results | — | ✓ |
| Change Policy / rules | — | ✓ |
| Manage users & roles | — | ✓ |
profiles table, read and written through /api/admin/users (admin only, verified server-side). Every tab is shown or hidden by your signed-in role.A suggestion, never a switch. The manager or the coach decides — this does the arithmetic first, on the days the appointments actually fall, counting only what a design consultant is there to cover. Runs every morning and goes out with the 9:00 digest, so the rules get looked at daily rather than when someone remembers.
| Market | This week | Next week | Suggests | Running now |
|---|
Where the number comes from. The team’s own live capacity page, not a figure this tool works out for itself — because the output here is a suggestion to a person, and a suggestion that disagrees with the board everyone already looks at is a suggestion nobody takes. The Enabled+ Appointment Calendar stays the fallback, and the cross-check if the two ever drift. This week drives the suggestion; next week is the heads-up, so a market about to tighten can be moved before it does rather than after.
One place where the rules live. Change it here and tonight’s load follows — nobody has to be told, and nobody has to remember which market is running what this week.
Each rule below beats every rule above it. The most specific one wins: a single source beats Traditional / Non-Traditional, which beats a whole market, which beats the company default. Two rules equally specific — the newer one wins.
Every source in the selected market, and which rule decided it.
| Lead source | Message confirm | Decided by | Tonight |
|---|
The window is booking lead time — days between the appointment being set and the appointment date. Inside it, the text is a message confirm. Outside it, we still text, but the text asks them to text C or call in. Which appointments get pulled at all is a separate thing: everything due inside the next 48 hours, whenever it was booked.
Today this is a person remembering to Google the address. It is standard, it is not programmed, and it runs on whoever thought of it. Below is the same investigation as a stack of checks — some everywhere, some only where they apply.
| Check | Where | If it finds something | Last night |
|---|
Cheapest and most authoritative first. Parcel and assessor records answer most of it outright — land use, units, year built, owner of record. A Street View image with vision catches what the data gets wrong, which for manufactured homes is often. The geocoder catches the addresses that don’t exist. Results cache by address, so a revisit or a resale doesn’t pay for the lookup twice. The coordinate comes free with the lookup. The map on the Enabled+ lead is a link out to Bing, not a stored point, so the CRM is no help there — but the parcel record we’re already pulling for land use, units and subdivision returns a latitude and longitude in the same response. One call per address, cached, and the district, borough and San Francisco boundary checks all run off it. The point isn’t better judgement than the team’s — it’s that it runs on all 231 instead of the ones someone remembered.
The board reads every lead before anything goes out. Most of the time it can act. These are the cases where it stops — and what you want it to do instead. Each one becomes a group on Today, cleared in a batch rather than one card at a time.
| What the read found | What the board does | Last night |
|---|
The send runs overnight, with nobody in. The holds wait for a person, so this is the clock they run on.
Two different holds. A no contact hold means the appointment itself is in question — nobody is texted or called until a person looks. A form hold only blocks writing windows, doors, age and HOA into Enabled+; the homeowner still hears from us. Reading every lead only pays off if those stay separate — otherwise every missing note turns into a phone call.
Before you change anything — or when someone asks why a lead got what it got.
So nobody has to ask why today is different from yesterday.
Nobody on the team opens this screen. A change here reaches them one way only: different leads showing up in the queues on Today, already sorted, with the reason written on the card.
Everything else stops and asks you.
Cancels stay with you until the Results screen shows the board is getting them right.
Week of Sept 7–13. Check the board’s work against what the market actually saw.
| Market | Issued | Message | Live | Unconfirmed | Cancelled | Mix | Not home |
|---|