Use your password, or the six-digit code from your authenticator app.
I can’t get in
If a link did not arrive, ask your manager for a fresh setup link.
People & teams
Who is on the team, what each person can reach, and who is stuck outside.
One-time setup link
Share only with the named person through an approved private method. Sundae will never send it automatically.
People waiting to get in
Sundae cannot email or text a login link, so anyone who is stuck asks here and you hand them the new link yourself.
Nobody is waiting. Requests from the login and setup screens land here.
Who asked
Asked for
When
People
Role and team are how reporting rolls up: person → team → manager → org. Can work leads is who the queue hands leads to. Capacity is tracked here but does not block routing yet. Someone On Leave is still employed; deactivate only when a person actually leaves.
Add a person
Who they are, where they roll up, and whether the queue hands them leads. Their setup link comes right after.
The queue and the desk hand this person leads. View follows it: on means the full app, off means their own appointments only.
Scheduling only: a Closer is placed on the calendar either way. Leads and outbound contact follow Can work leads, nothing else. Nothing is sent to anyone.
Person
Role & team
Timezone & phone
Access
Person
Role & team
Status
Access
Divisions
A division groups teams under a director, so the director sees their whole division without being made an executive. Admin only — a division decides who sees whom.
No divisions yet. Teams work exactly as before without one.
Division
Director
Teams
Status
Teams
A team has one primary manager, who gets escalations and override pay, and any number of co-managers who share its whole downline: appointments, setters, scoreboard. Markets are the exact market names used on booking slots.
Co-managers
No teams yet. Reporting still works per person; teams add the rollup.
Team
Managers
Division
Markets
Members
Status
Appointment owner aliases
An alias is the exact spelling another system uses for a closer. Aliases are case-insensitive, never fuzzy-matched, and do not rewrite imported appointment history.
No aliases recorded.
Source spelling
Resolves to
Calendar subscriptions
A closer adds this URL to the calendar app already on their phone, once. Their appointments show up and stay current with no account and nothing to install. The URL carries customer names, addresses, and phone numbers, so hand it only to the named closer. It exists once, in the box below, and is never shown again.
Closer
Subscription
Calendar URL
Shown once
Busy calendar sync (inbound)
Point Sundae at a closer's own calendar (Google Calendar's "Secret address in iCal format", under Settings → that calendar → Integrate calendar) so a busy block on their phone auto-closes the matching open slot here. Nothing is ever booked or read back from this URL except free/busy timing -- Sundae never sees event titles or guests. The URL itself is write-only: once saved, only the domain and the last four characters of the token are shown again.
Who is in the closer pool, their shift hours per market, and the Google Calendar feed each slot publishes to are set on the Slots & closers board under Appointments. They are linked here, not copied, so one place owns them.
Go-live readiness
Close ingestion
Checking
Checking the canonical Close mirror.
Market unknown remains visible when the source has no mapped value.
Close reconciliation
Checking
Checking the canonical outbox.
Close writeback stays off until every parked outcome is reconciled.
Feature gate status
Read-only. Flags flip only via server environment changes on deploy, never from this page.
Flag
State
Raw value
What it does
Closer nudge dry-run
Checking
Who would get an appointment-outcome email if the closer-loop job ran right now.
Records nothing. Require Blake approval before flipping
KIN_CLOSER_NUDGES_LIVE.
Appointments that have already ended with nothing recorded, oldest first. Copy a row's link and text it to the closer: three buttons, no login, about five seconds.
Every appointment that has run has an outcome. Nothing to chase.
When
Waiting
Customer
Closer
Market
Asked
Redial spacing
The work queue holds a lead back once it has had its attempts for the day, and keeps a gap between dials, so a number never produces the repeat-call pattern carriers score as spam.
Waiting on spacing
Leads that would be in somebody's queue right now if they had not just been dialed. Nothing is lost; each one comes back at the time shown.
Nothing is waiting. Every assigned lead is workable right now.
Lead
Who
Why
Today
Last dial
Comes back
Flagged numbers
When a carrier labels one of our numbers, calls from it stop ringing and every no-answer logged in that window was never really a no-answer.
Sundae does not know which number placed a given call, because setters dial from their own phones. Record the window against the setter who used the number; the number itself is kept as evidence for the carrier dispute.
No flagged windows recorded. Add one when a weekly caller-ID check comes back labelled.