Operator Dashboard

Every conversation, every booking, every overdue client. One view.

The dashboard is the operator's command center for the Aria deployment running on your front line. Call activity, booking conversion, lifecycle leakage, revenue capture, and configuration — on a single screen, in the language your front desk already uses.

Not a black box. Not an analytics tab. The same surface where you read the data is the surface where you change the rules.

Talk to engineering

01 — Call activity

What came in.

Every inbound call Aria touched — reconciled against the front desk and the schedule. No counting on memory.

  • Total calls handled Volume across the last 7, 30, and 90 days. Filter by line, by location, by hour of day, by day of week. Compare any period to the same period the prior year.
  • Answered vs. missed Answer rate, side by side with the answer rate before Aria went live. Missed calls are the single number every operator should be watching, and it’s the first number on the screen.
  • Transfers to the front desk When Aria handed the call to a human, and why. Every transfer is tagged with the reason — clinical question, billing dispute, complaint, special request — so you can see the actual texture of what your team still needs to handle.
  • Average call duration Time on line, broken down by call type. New-patient intakes, recall confirmations, insurance questions, billing — each call type has its own baseline so anomalies surface immediately.
  • After-hours and weekend volume The hours your front desk used to lose. Nights, weekends, holidays — every call counted, every booking attributed, every dollar Aria caught that would have gone to voicemail.

02 — Bookings

What converted.

Calls that turned into appointments — broken out by source, slot, and outcome.

  • Appointments booked Total bookings written to your scheduling system, per day, per week, per month. Reconciled against the calendar. If the schedule moved, the dashboard knows.
  • After-hours bookings Evenings, weekends, and holidays — the appointments your old front desk could not have captured. Tracked separately so the impact is visible.
  • Call-to-booking conversion rate Percentage of inbound calls that ended in a written appointment. Drill into the calls that did not convert and see why — insurance not accepted, time not available, caller not ready — with the full transcript one click away.
  • Breakdown by provider, service, and location Which provider Aria booked into. Which appointment type. Which location, if you have more than one. The same cuts your operations partner already runs in a spreadsheet — here, live.
  • No-show and reschedule tracking Every booking carries forward into the outcome view: arrived, no-showed, rescheduled, cancelled. Conversion does not stop at the booking confirmation.

03 — Client lifecycle

What’s leaking.

The customers your front desk lost track of, surfaced as cohorts, with the outreach tool sitting next to the list.

  • Overdue cohorts 60-day, 90-day, six-month, one-year-plus. The customers who haven’t been back. Sorted by lifetime value if you want them sorted by value, by last visit if you want them sorted by recency.
  • One-click cohort pull Names, phone numbers, last appointment, last provider seen, last service performed. Export to CSV, or run the outreach directly from the dashboard.
  • Direct re-engagement Launch an outbound SMS, voice, or email campaign against any cohort without leaving the page. Aria runs the conversations and writes the bookings back into the schedule.
  • Returned vs. didn’t return After every recall campaign, the dashboard tracks who came back and who didn’t. The cohorts that still haven’t responded move to the next outreach window automatically.
  • Lifetime value by cohort Not just count of clients — dollars at stake. The 90-day cohort is worth a number, and the dashboard tells you what that number is.

04 — Revenue capture

What it’s worth.

Calls and bookings translated into dollars — tied back to the front desk in a way that the operator can defend in the next ownership meeting.

  • Revenue tied to bookings Total revenue attributed to appointments Aria wrote, by week and by month. Pre-booking estimates and post-visit actuals, side by side.
  • High-value calls flagged Insurance verifications, treatment plan acceptances, large-ticket service requests, multi-visit packages, retainer agreements. The calls that matter most are pulled to the top and tagged.
  • Revenue per call Average dollars produced per inbound call, by call type, by day part, by lead source. The operator metric that turns voice activity into a P&L line.
  • Recovered revenue from recall Bookings driven by outbound outreach, separated from inbound. The dollars Aria recovered from cohorts the front desk had stopped chasing.
  • Per-provider revenue contribution Which providers and which services Aria is filling the calendar with. The data behind the next hiring decision or schedule rebuild.

05 — Operator controls

The dashboard is also the configuration layer.

The same screen where you read the data is the screen where you change the rules. No engineer call, no support ticket, no waiting room.

  • Adjust hours, providers, services, pricing Edit your operating hours, add or remove providers, add a new service, update pricing — without writing code. Aria picks up the change on the next call.
  • Booking rules Define which appointment types can be booked when, which providers can take which services, which locations require what kind of intake. Set it once, change it whenever the practice changes.
  • Transcripts and recordings Every call is searchable. Read the transcript, listen to the recording, see the booking that came out of it. Every conversation is auditable, by design.
  • SMS, recall, and follow-up flows Configure reminder cadences, recall outreach windows, post-visit follow-up, payment requests. The full lifecycle, configurable per service line.
  • New locations, new providers, new appointment types Roll out a second location, add a hygienist, add a new service line — same dashboard, no engineering call. The configuration scales with the business.

06 — What the dashboard is not

One surface. No second tabs.

The dashboard is not a marketing analytics suite, not a generic BI tool, not a CRM your team has to learn from scratch. It is the operator surface for the Aria deployment we built around your practice — sized for the front desk, sized for the owner, sized for the partner who looks at numbers on the way out the door.

Everything on the screen reflects the configuration we built for you. If your scheduling system changes, the dashboard reflects it. If a provider leaves, the dashboard reflects it. The owned-end-to-end posture means the surface stays in lockstep with the system underneath it.

It is not a reporting bolt-on. It is the operating system for the front line that Aria runs.

Configuration is per-operator. The dashboard your dental practice sees is a different surface from the one your law firm sees — same engine, different shape, because the operator is a different shape.

Contact

See the dashboard against your own front desk.

A discovery conversation is the right place to walk through the dashboard against your actual call volume, your actual provider roster, your actual lifecycle leakage. Bring the problem; we’ll show you the surface that solves it.

Talk to engineering