Reply "fix #2" and it happens.
The business digest is a short recurring brief in three parts — what needs you, what happened, and where an opportunity is — assembled from your conversations, campaigns and workflows. It is a normal email, so replying to it with an instruction is how you act on it.
The digest draws on your plan’s included credits and is assembled from work you already have. No separate reporting add-on.
Needs you
- 1Northvale has asked about the March statement three times and nobody has replied.
- 2The Saturday-hours question came up 9 times. Nothing in the knowledge base covers it.
- 3Your reminder campaign has 31 no-answers waiting on a retry decision.
What happened
184 conversations, 147 handled without you. Six calls after hours, all logged with transcripts. Two new contacts from the website widget.
Opportunity
22 people who booked in March have not been back. That is the largest group you have not contacted this quarter.
Or just ask for it
The digest is the interface.
Three parts, and replying to it is how you act on it.
InboxMonday brief: 3 need you
Needs you: 1. Kepler refund decision · 2. bookings@ authorisation expiring · 3. a caller asked for you by name. Happened: 214 conversations, 3 campaigns, 1 workflow failure. Opportunity: nine people asked about Saturdays.
Fix #2. Give Kepler the refund. And put Saturday hours in the greeting.
@Octo post the brief in here as well as emailing it
On it 🔧(runningget_analytics…)
It’ll land here at 7am with the same three parts. Acting on it works the same — just reply. (edited)
🎉 32 replies · last reply 5m ago
and alert us if spend passes 80%
Email octo@agent.omniocto.com · WhatsApp 1-MAN-ASK-OCTO · Slack #omniocto
Three sections
Not a dashboard. A brief.
Reports get skimmed and closed. This is written to be read on a phone in two minutes and acted on in the same gesture.
Needs you
The things that will not resolve themselves — a customer waiting, an automation that stopped, a decision only you can make.
What happened
The week in a paragraph. How many conversations, what they were about, what got handled without you.
Opportunity
The pattern worth acting on — a question five customers asked, a group worth following up, a thing you keep answering by hand.
It is an ordinary email, which is the whole design. Replying to it is how you act on it.
How it works in practice
It arrives, you reply, it adapts.
It arrives
On a cadence that matches your week.
A brief in three parts, at a time you are awake, without you setting up a report.
Reply to it
"Fix #2" is a complete instruction.
Answer the email the way you would answer a colleague. The item becomes a task Octo carries out, and anything that spends money stops for a confirmation code first.
It adjusts
Quiet weeks get shorter mail.
The cadence follows what is actually happening, so it does not become the daily email you filter away unread.
What is actually happening
Why this one does not get filtered away.
Replying is the interface
The digest is a real email on a real thread, so an instruction in a reply is acted on. There is no separate app to open, which is the reason most internal reports go unread.
reply-to-act · confirmations still applyThe facts are queried, not summarised
The gathering step reads your data directly rather than reading transcripts, and a test fails the build if that changes. What you get is a brief built on counts and states, with one pass to write it up — not a summary of summaries drifting away from the truth.
direct data gather · enforced by testThe cadence adapts
It follows how much is actually happening rather than sending an identical brief every morning regardless. The failure mode being avoided is the report everyone auto-archives.
adaptive cadenceQuiet hours are respected
The digest and the alerts arrive when you are awake. Being notified at 3am is something you choose rather than something that happens because a threshold was crossed.
quiet hours · your timezoneUrgent things do not wait for it
Breakage and budget alerts fire when they happen, at 50%, 80% and 100% of budget. The digest is the summary; the alerts are the interruption.
breakage alerts · 50/80/100% budget alertsQuestions
The things people actually ask.
- What is actually in it?
- Three sections. What needs you — the things that will not resolve themselves. What happened — the week in a paragraph rather than a chart. And an opportunity, where the pattern in your conversations suggests something worth doing.
- What does "reply fix #2" mean?
- The digest is a real email, so replying is how you act on it. Reply with an instruction referring to an item and it becomes a task Octo carries out — no dashboard, no ticket. Anything that spends money still stops and asks for confirmation first.
- Is it reading all my customer transcripts?
- No. The facts are gathered by querying the data directly, and there is a test that fails the build if the gathering step starts reading transcripts. It is deliberately not a summary-of-summaries.
- Weekly or daily?
- The cadence adapts to how much is actually happening rather than sending you an identical near-empty brief every morning. A quiet week does not generate the same volume of mail as a busy one.
- Will it land at 3am?
- No. Quiet hours are respected, so the digest and the alerts arrive when you are awake.
- What if something breaks before the next one?
- That is what alerts are for, separately: breakage and budget alerts fire at the time, at 50%, 80% and 100% of budget, rather than waiting for the next digest.
Keep reading
Related jobs you can hand over.
The digest draws on your plan’s included credits and is assembled from work you already have. No separate reporting add-on.