By KYN AI Advisory Team — AI implementation specialists, Singapore
A daily WhatsApp morning report fits on one screen and holds five blocks: yesterday's figures, today's scheduled work, items that are late or blocked, items waiting for a named person, and one link to the detail. Each department gets its own version. The agent builds it from your systems overnight and sends it at a fixed time. It reports and flags. It does not act.
What belongs in the report?
Five blocks, in this order, every day.
- Yesterday. Three to six figures that department owns, each with the change from the day before. Sales: new enquiries, replies waiting, quotes sent. Finance: cash received, bills due, invoices overdue. Operations: orders shipped, stock below minimum, jobs late.
- Today. What is scheduled: deliveries due, calls booked, filings due, payments to approve.
- Late or blocked. Items past their date, each with how many days late and who holds it.
- Waiting for you. Anything that needs a named person's decision, such as a payment to approve or a message to release.
- Link. One link to the full page in the dashboard.
Keep every line to a label, a number and, where relevant, a name. Leave out commentary on why a number moved. The report states facts and the reader decides.
How long should it be?
Short enough to read before the first meeting. Aim for under 15 lines. A message that needs scrolling is a message people stop opening. If a department needs more, put it behind the link.
Test the report with the people who receive it. After two weeks, remove any line nobody acted on. A line earns its place if it changes what someone does that day.
Where does the data come from?
The report reads from the system of record, not from a spreadsheet someone remembers to update. For a manufacturer, that meant the single ledger and stock tables on one AWS account, with a report at 06:30 to each department. For a services firm, it is the CRM, the ledger and the calendar.
The agent runs a scheduled job:
- Query the figures for the previous day.
- Compare with the day before and the same weekday last week.
- Pick the late and blocked items by rule, such as "invoice more than 7 days overdue".
- Check the numbers against totals in the source.
- Build the message from a fixed template.
- Send, and log what was sent and to whom.
The rules in step 3 are written by your team, not chosen by the model. That keeps the output predictable and testable. For a worked example, see daily WhatsApp operations report from ERP.
What are the rules for sending on WhatsApp?
Sending business messages through WhatsApp requires the WhatsApp Business Platform, with an approved sender number and message templates for business-initiated messages. Meta publishes the current requirements and pricing in its developer documentation. Pricing changes, so check the page for the current rates before budgeting. Our notes on this are in WhatsApp Business pricing from 1 October 2026.
Practical rules for internal reports:
- send only to staff who asked for it, from a number they recognise;
- keep a stop command that works;
- keep the template fixed and change only the values;
- never include personal data beyond what the recipient needs for their role;
- log each send with the recipient and the content.
What should the agent never do in the report?
- Invent a number. If a source is down, the line says "source unavailable", not an estimate.
- Send a different figure than the dashboard shows. Both read from the same query.
- Take action. The report can say "3 payments waiting". Releasing them is a person's job.
- Ping people outside the department. Each version goes to its own group.
A failed run should alert a named person, not skip silently. A missing report at 06:30 is information, and someone should see it.
How do you know it is working?
- Delivery rate. Share of reports delivered on time. Aim for every working day.
- Match rate. Spot-check three figures a week against the source.
- Action rate. Late items cleared within a day of appearing.
- Opens. Ask recipients. If a department stopped reading it, change the report or remove it.
What does it cost?
Per report, small. KYN's morning reports cost about S$0.05 each in model and compute, which depends on the model and the amount of data summarised. WhatsApp message fees are separate and set by Meta under the pricing page above. The larger cost is the first build: agreeing which figures matter to which department.
What does a department version look like?
Each department sees only its own lines. The example below is illustrative.
Finance, 06:30
- Cash received yesterday: S$12,400 (up S$3,100)
- Bills due today: 4, total S$8,950
- Invoices overdue: 7, oldest 22 days
- Waiting for you: 2 payments to approve
- Detail: link
Operations, 06:30
- Orders shipped yesterday: 14 (down 2)
- Jobs late: 3, oldest 5 days, owner named
- Stock below minimum: 6 items
- Waiting for you: 1 reorder to approve
- Detail: link
Note that each line is a label and a number. There are no sentences explaining why a figure moved. If the reader wants a cause, the link opens the records.
How do you roll it out to a team?
- Week 1. Interview each department head. Ask which three numbers they check first every morning. Start with those.
- Week 2. Build the data queries and compare each figure with the source by hand for five days.
- Week 3. Send to the department head only, at the planned time.
- Week 4. Add the department's staff, and a way to reply "stop".
- Month 2. Remove lines nobody acted on and add one that was asked for.
Keep the sender number, the time and the layout constant. A report that changes shape each week is read less.
What happens when a source is down?
Decide this before the first send. Three outcomes are acceptable:
- send the report with a line stating which source was unavailable;
- delay the send by a set time and retry;
- skip the report and alert a named person.
Pick one per department. An estimate in place of a missing figure is not an option. The agent should never present a stale number as current, so each figure carries the time of its last update when the source is slow.
How do weekends and holidays work?
Set the calendar once. Skip public holidays in each country where the company operates, and send a reduced version on days when a department works a half day. A team in Indonesia and a team in Singapore have different holidays, so the schedule should be per department, not company-wide.
Where KYN fits
KYN built a 06:30 morning report to each department on WhatsApp for a manufacturer, on top of a consolidation from eleven systems to three on one AWS account. The reporting agent has its own restricted account, reads from the database through row-level security, and logs every send with the actor. Anything that moves money or sends outside the company waits for a named person. The system runs in a cloud account in the client's name.
The first 14 days are a review of your stack and interviews with your team. A full build ships in under 90 days. See operations, finance and security.
Frequently asked questions
What time should the report arrive?
Before the first meeting of the day. Many teams choose early morning, but the right time is the one your staff start work. Set it per department.
Can the report include a chart?
It can include an image, but a table of five or six numbers reads faster on a phone. Put charts behind the link.
What if the data is wrong one morning?
Send a correction as soon as it is found, with the corrected lines. Log the cause. The match-rate spot checks exist to catch this early.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
