What Elira did today, and whether it worked
The three cards at the top of your dashboard: registration results, today’s messages, and the short list of things waiting on a person.
The top of your dashboard answers three questions, in this order.
1. Registrations — did it work
How many of the families you offered a seat have finished registering, as a fraction you can check against your own enrollment system in under a minute, plus how this week compares with last week.
Two things about this number are worth knowing:
- The count comes from your enrollment system, not from us. A family counts as registered when your system says so.
- The weekly comparison needs history. For the first two weeks of an account there is no previous week to compare against, so we show no trend at all rather than an invented one. The card tells you when that's why.
Underneath, a line like *"18 of the 22 registrations we can date had heard from Elira first."* That is a sequence, not a cause — some of those families would have registered anyway, and we won't claim otherwise. Any registration we can't put a date on is counted in the total and left out of the weekly trend, and the card says how many that is.
2. Today — what happened
Texts, emails, calls, how many distinct families were contacted, how many questions Elira handed to your office, and how many your office closed out.
This is a snapshot, not a live feed — the timestamp says *as of*. Elira sends on a schedule and inside family contact hours, so nothing streams in continuously and a ticker would be misleading. Refresh the page for the current picture.
If your account is still in its observation week, everything here is labelled Simulated — Elira prepared the messages, and nothing was sent to a family.
3. Needs you — the short list
Things no automation can finish. Each row names one action, and it should usually be empty. When it is, it says which kind of empty: *"Elira handled everything that came in"* on a day something did come in, and on a quiet day *"Nothing has come in for Elira to handle today either."* An empty list never reads as work that was finished for you when nothing arrived to finish.
What shows up here:
- A family asked something Elira wouldn't answer, and is waiting on your reply.
- Elira stopped on a seat and handed it to you — she will not contact that family again.
- Every call window used with no answer.
- A family accepted a seat but hasn't finished registering, and the last reminder in the sequence has gone.
- Messages held because written consent isn't on file.
- A sequence somebody paused and never resumed.
The list is capped at five so it stays readable. If there are more, it says how many and points you at the roster. One family with three overlapping problems is one row, not three.
Every row's open link goes to the page where that action is actually finished: a family waiting on an answer opens AI Knowledge, which is where you write the answer; the rest open the applicants roster further down this same page.
The full record, and getting it out
At the bottom of the dashboard, Everything Elira has done — every message, call, question and hold, in plain language, grouped by day. Search it, filter by kind, and press Download as CSV for the file to attach to a parent complaint or hand to your authorizer. The download contains exactly the rows on your screen with the same filter applied.
Families are shown by surname — *the Alvarez family* — and student names, phone numbers and email addresses are deliberately never printed on this screen or in the export. Use the applicant row itself when you need the full record.