By KYN AI Advisory Team — AI implementation specialists, Singapore
A daily operations brief is one short message, sent before the team starts, that lists what needs a person today. It is built from three sources: unanswered email, the day's calendar and open CRM records. A scheduled job reads each source with a read-only account, ranks the items by rules you write, and sends the result to WhatsApp or email. It does not act on anything. It tells a named person what to look at first.
This article covers the build for a team with a shared Gmail or Google Workspace inbox, a calendar and a CRM. If your source is an ERP or ledger rather than email, see our note on the daily WhatsApp operations report from an ERP. The pattern is the same. The inputs differ.
What should a daily operations brief contain?
Keep it to what a person can act on in five minutes. Five blocks cover most teams.
- Today's calendar. Meetings, with the one record (deal, client, job) each meeting relates to.
- Email waiting on us. Threads where the last message is from outside and no one has replied. Show age in hours and the owner.
- CRM changes. Deals that moved stage, went quiet, or have a next step dated today or earlier.
- Deadlines. Anything with a due date in the next two working days: quotes, renewals, filings.
- Open flags. Items the system could not classify and needs a person to read.
Each line holds a number, a label, an owner and a link. No commentary. If a block is empty, print the label and "0" so the reader knows the check ran.
What does the build need?
| Part | What it does | Access it needs | |---|---|---| | Mail reader | Lists threads awaiting reply | Read-only, one mailbox or label | | Calendar reader | Lists today's events and attendees | Read-only | | CRM reader | Lists stage changes and overdue next steps | Read-only API key | | Ranking rules | Orders items by age, value and deadline | None | | Sender | Delivers the brief | Send to a fixed list of people | | Log | Records what was read and sent | Write to your own database |
Use the official APIs. Google documents read-only scopes for Gmail and Calendar, and a read-only scope is all this job needs. Do not give the job a scope that can send mail or edit events. If the brief never needs to write, make it unable to write.
How do you decide which email threads count?
This is where most briefs fail. A raw unread count is noise. Use rules a person can read and dispute.
- A thread counts when the last message is from outside your domain and no internal reply follows.
- Ignore threads with a no-reply sender, a newsletter label, or an auto-reply header.
- Group by sender domain, then match the domain to a CRM account. A thread from a customer with an open deal ranks above a thread from an unknown sender.
- Age matters in working hours, not calendar hours. A message that arrived Friday at 17:30 is not 60 hours old on Monday morning.
Write the rules into a file the team can read. When someone says "this should not have been on the list", you change a rule, not a prompt.
A language model helps in one narrow place: reading a thread and labelling it as question, quote request, complaint, or payment. That label is a classification with a fixed set of answers, so you can test it against 100 threads a person has labelled. It does not decide who gets the work.
How do you rank what goes first?
Use a score you can print next to each line. A simple version:
- deadline today: highest;
- open deal value above a threshold you set: next;
- age past your response target: next;
- everything else by age.
Ties break by account value. Show the first ten items and a count of the rest. A brief with 60 lines is a mailbox with extra steps.
How do you schedule and deliver it?
Run the job on a timer in your own cloud account, set to finish before the first person starts. Our own manufacturer system sends a 06:30 report to each department on WhatsApp, and each report costs about S$0.05 to produce. That figure comes from KYN's live system and depends on the model and the length of the text.
Delivery rules:
- send to named people, one brief per role, not one for everyone;
- keep the message short enough to read without scrolling twice;
- link each line to the source record;
- if a source fails, say so at the top ("CRM not read: key expired") and still send the rest.
That last rule matters. A brief that silently drops a block teaches the team to trust a view that is incomplete.
How do you check that the brief is right?
Run it in shadow for two weeks. Send it to one person while the team works as usual.
- Recall. Of the threads and deals the team actually chased that day, how many were on the list? Aim to find the gaps, not a score.
- Precision. Of the lines on the list, how many did a person act on or dismiss as wrong?
- Staleness. Compare CRM "last activity" with the real last email. Gaps point to people working outside the CRM.
- Timing. Did it arrive before the first person logged on, every day?
Fix rules first. Change the model only if labelling accuracy on your 100 sample threads is the problem.
What are the security limits?
The job reads a mailbox, so treat it as an agent with access to private data.
- Give it its own restricted account, not a person's login.
- Log every read with the time and the account used.
- Mail content can contain instructions aimed at the model. Treat email text as data and keep the job unable to send or edit. See prompt injection in business AI agents.
- Keep customer personal data inside your cloud account. Under Singapore's PDPA, personal data you hold stays your responsibility, including when a tool processes it.
Where KYN fits
KYN builds briefs like this as part of the operations system, running in a cloud account in your name. Agents have their own restricted accounts, every action is logged with the actor, and outbound messages wait for a named person. The first 14 days are a review of your stack and interviews with your team. A full build ships in under 90 days. Rights in the custom code and configuration pass to you on full payment. See integrations.
Frequently asked questions
Can the brief be built without changing how the team works?
Yes. It reads the tools the team already uses and changes none of them. The one adjustment is that email and CRM must reflect the same accounts, so domain matching works.
Should the brief reply to emails for us?
No. Drafting a reply is a separate step, and sending waits for a named person. The brief only tells people where to look.
What if we use Outlook instead of Gmail?
The pattern is identical. Microsoft Graph offers read-only mail and calendar permissions in the same way. Only the connector changes.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
