To know how the week went in a multi-store chain you have to open the dashboard, yet most regional managers spend Monday morning on store visits, not in front of a screen. BranchVoice's weekly digest email closes that gap: it drops a seven-day scorecard and the changes that need attention into the inbox as a short e-mail. This post covers what the digest contains, how its highlights are selected and how it differs from scheduled reports.
What the weekly digest email is
The weekly digest is an automatic e-mail sent every Monday at nine in the morning, Turkish time, to the active users of the account. There is nothing to configure; it starts arriving as soon as review data is being collected. Its scope is always the whole brand and its period is always the same: last week, compared with the week before.
The goal is not to deliver a report but to start the week with the right question. The only button in the e-mail is "Open dashboard"; the detail waits there.
The scorecard: four numbers, four comparisons
The top of the e-mail is the week's scorecard. Each figure sits next to the previous week's value:
- Reviews: the number of reviews collected from all platforms during the week.
- Experience score: a 0 to 100 satisfaction score computed from the content of reviews the AI analysed; 50 is the neutral point.
- Negative reviews: the number of reviews whose content was classified as negative.
- Urgent + critical: unanswered reviews that need same-day attention plus reviews carrying a safety, legal or reputational risk.
These four numbers use exactly the same definitions as the dashboard scorecard. What the digest calls negative is what the dashboard and the reports call negative, so nobody argues over definitions. The full set is explained in the dashboard metrics guide.
How highlights are chosen
Below the scorecard sits the "Highlights" section. These items are not written by a text model; each one is produced from the data by a rule, and only items that clear the rule's threshold make the list. In a quiet week the section stays empty and the e-mail says there were no notable changes. The item types that can appear are:
| Highlight | When it appears |
|---|---|
| Rising topic | A topic's share of reviews grew noticeably versus the previous week |
| Falling complaint | A complaint topic's share dropped noticeably |
| Store needing attention | The store with the lowest experience score and a high negative rate |
| Best store | The store with the highest experience score |
| Awaiting reply | Count of unanswered negative reviews and how many days the oldest has waited |
| Critical risk | Number of reviews carrying a safety, legal or reputational risk |
| Churn signal | Number and share of customers saying they will not come back |
| Most discussed topic | Number of reviews gathered under the same tag or thread |
| Rating contradicts content | Reviews with high stars that describe a negative experience |
| Suspicious reviews | Reviews that look templated or part of an organised campaign |
| Strength | A topic with a high positive rate |
Every item comes with context next to the number, along the lines of "Returns and exchanges share rose: fourteen reviews, seventy-nine percent negative". A regional manager knows which store and which topic to look at before finishing the e-mail.
Data health and the quota line
A digest is only as reliable as the data behind it. If a source received no data that week, for example because a store's Google listing failed to sync, a data warning appears at the end of the e-mail stating how many sources are affected, which ones they are, and that the figures may be incomplete. You know whether the data is complete before celebrating a drop in negative reviews.
The same section shows the AI analysis quota used so far this month. If the allowance is close to running out you see it in the digest and can act before the next sync leaves reviews unanalysed.
How it differs from scheduled reports
The weekly digest and scheduled reports are easy to confuse, but they do different jobs. The digest has one shape: brand-wide, last seven days, short text in the e-mail body, no attachments, sent to every active user. Scheduled reports are flexible: you pick a store, region or brand scope, choose sections and send PDF and Excel attachments to the recipients you name; the details are in automated PDF and Excel reports.
In practice the two work together. The digest arrives Monday morning and tells the team where to look; the same morning the regional report lands in regional managers' inboxes with an Excel attachment for the detailed review. Events you need to hear about within minutes wait for neither; those are delivered instantly by critical review alerts.
How a regional manager uses it
Before leaving for store visits they open the digest on their phone. If negative reviews are up on last week, they scroll to the highlights. The store under "Store needing attention" moves to the top of the day's visit list; the "Rising topic" item sets the question to ask when they get there. "Awaiting reply" is the reason to remind store managers about unanswered reviews. At the meeting, the manager of the "Best store" is asked what they did differently so the others can copy it.
The value of this routine is that the team talks about the same numbers without opening the dashboard. Because everyone read the same e-mail, the regional meeting is spent discussing actions rather than verifying data.
Next steps
The weekly digest email is the first piece of review data that becomes part of a team routine; it needs no setup and starts the first full week after data collection begins. Connect your store list and the first digest arrives the following Monday. To see your own chain's scorecard, request a demo.