A weekly ops review fails on its inputs, not its agenda — and the worst input is a shared dashboard URL, where every viewer opens a different date range, filter set, or default slice. Devotel Orbit ships a scheduled-reports surface under Insights → Scheduled reports that emails the same report snapshot to every recipient on a fixed cadence, so the meeting reads one page. This post covers why that beats link sharing, which insight surfaces you can schedule, a sample weekly cadence for CX leaders, and how scheduled digests differ from the alerts and anomalies surfaces.
Why a scheduled digest beats a shared live URL
A live dashboard link optimizes for exploration; a weekly review needs the opposite — a fixed comparison point. Three properties make a scheduled email digest the better input:
- One snapshot for the whole room. The report renders once per cadence tick, so every recipient reads identical numbers. A shared URL renders per viewer, with per-seat filters and default date ranges doing whatever they default to.
- It arrives before the meeting does. Recipients can include people without a dashboard seat — an exec sponsor, a finance partner, an outsourced QA team — because the digest lands in a normal inbox, not behind a login.
- It builds an archive. Each send is a dated email, so "what did messaging volume look like the week of the incident" is a search over mail, not a re-derivation from the analytics surface.
Live dashboards stay the right tool for drill-down once the meeting finds something worth chasing. The digest's job is to give the meeting its agenda.
What Devotel Orbit ships
The scheduler lives at Insights → Scheduled reports (orbit.devotel.io/en/insights/scheduled-reports). The page lists every report your workspace has configured with its type, cadence, timezone, next send, and last send, and supports the full lifecycle: create, edit, pause, delete, and a send-now action for a one-off dispatch. The same reports are manageable over the public API at /api/v1/analytics/scheduled-reports for teams that script their ops setup.
Which insight surfaces you can schedule
The create form offers a closed set of report kinds; if it isn't on this list, it isn't schedulable today:
- Messaging volume — send and receive totals across your channels.
- Deliverability digest — delivery performance across your messaging traffic.
- Top contacts — the contacts driving the most activity.
- Contact center — queue performance — the contact-center (voice/ACD) queue dataset, for CX and workforce leads.
- Credit spend — where prepaid credit went over the period.
- Custom — a saved query from the report builder. Custom schedules are created through the report builder itself rather than the dropdown, which keeps mis-typed schedules out of the list.
Every report carries three settings:
- Recipients — up to 50 comma-separated email addresses; no dashboard seats required.
- Cadence — daily, weekly, or monthly. Daily fires at 09:00 local, weekly on Monday 09:00, monthly on the first of the month 09:00.
- Timezone — an IANA zone (for example
America/New_York,Europe/Berlin) the cadence anchors to, so "Monday 09:00" means your Monday morning, not UTC.
Editing a report replaces its recipient list and re-anchors its schedule; pausing a report stops sends without losing the configuration.
A sample weekly cadence for CX leaders
A workable Monday review for a contact-center leader combines three inputs:
- Queue performance digest (scheduled, weekly): the contact-center queue dataset emailed to the CX distribution list Monday 09:00 local — the fixed page the meeting reads.
- Containment alert (threshold): an KPI alert on AI containment under Insights → KPI Alerts so a mid-week containment drop notifies in-app with a link straight to the metric rather than waiting for the next digest.
- Sentiment trend (live): the Insights → Sentiment surface opened during the review itself once the digest or a fired alert raises a question.
The pattern is the point: the scheduled digest carries the recurring summary, while anything that can't wait a week gets an alert rule instead of a faster cadence.
Scheduled digests vs alerts and anomalies
Three surfaces cover three different jobs, and the weekly-review workflow usually wants two of them:
- Scheduled reports answer "what happened, on a schedule" — a recurring summary pushed to email. The recipient list is the audience.
- KPI alerts answer "something crossed a line just now" — threshold and anomaly rules on cross-pillar KPIs such as CSAT, NPS, CES, LLM spend, and AI containment, firing an in-app notification with a link to the metric the moment one breaches.
- Anomalies answer "the detectors raised something — show me the raw row" — a real-time ledger over usage and delivery, refreshed roughly every minute, for forensics rather than summaries.
Running a digest where an alert belongs means finding a Tuesday problem on the following Monday; running an alert where a digest belongs means back-to-back notifications no one treats as the agenda. Use each for its own job.
Set your first digest up
Open Insights → Scheduled reports, create a report, and pick one of the kinds above with a weekly cadence and your timezone. If you want to inspect what a report shape returns before committing recipients to it, run it once on-demand under Insights → Reports, then schedule it. The docs guide linked from the surface walks through cadence anchoring, recipient replacement on update, and what send-now actually queues.