The evening phone round
"Every night I call four branch managers, write the numbers on paper, and add them up myself." If you run more than one shop, showroom, pharmacy or outlet, this is probably your routine. One branch sends a photo of the khata, another sends a voice message, a third forgets. The figures arrive late and in different formats, and comparing today with last week means digging through old messages.
The fix is a daily summary that builds itself from the entries branches already make, and lands on your phone at a fixed time.
What the daily summary shows
Keep it short enough to read in a minute:
- Total sales today, overall and for each branch
- Split by payment method: cash, bKash, Nagad, card, and credit to regular customers
- Number of bills, and any returns
- A comparison with the same day last week
- Top-selling items, if your entries include items
- Which branches have not submitted yet
An AI can add two or three plain-language lines on what stands out, for example that one branch's card sales were unusually low today. The numbers themselves always come straight from the data, never from the AI.
Setting it up
- One way to enter sales. If branches already use a POS or billing software, the summary can read from it, provided it can export data or offers an API. If they use paper, give each branch a short mobile form with the same fields: branch, date, cash, bKash, Nagad, card, credit, returns, notes.
- A closing deadline. Agree a time by which each branch submits, for example within half an hour of closing.
- Collect in one place. Entries go into one sheet or database, with one row per branch per day.
- Build the summary. At a set time, the system adds up the day, compares it with earlier days and writes the message.
- Deliver it. Send it where you will actually read it: WhatsApp, email, or both. Late branches can get an automatic reminder before the summary goes out.
Things that trip people up
- Different habits per branch. If one manager writes bKash sales in the cash column, the totals are wrong. A fixed form with separate fields solves most of this.
- Power cuts and weak mobile data. Choose a form that can be filled in offline and sent when the connection returns. Make the summary say clearly which branches are missing, rather than showing them as zero.
- Too much detail. A summary nobody reads is useless. Start with totals, and add more only when you notice yourself asking for it.
- Treating it as a cash check. The summary reports what branches enter. Counting physical cash and reconciling it still needs its own routine.
Doing it yourself or getting help
A Google Form and a shared sheet, with a formula-based summary you check each night, is a fair start you can build in-house. What usually needs an expert is connecting to existing POS software, sending the summary to WhatsApp automatically, handling late or corrected entries, and adding the AI notes safely. I set this up as part of AI and workflow automation.
The first useful step
This week, write down the exact five or six numbers you ask each branch manager for every night. That list is your form. Ask every branch to send those numbers in the same order, even by plain text message, for one week. You will quickly see what the automated version needs to do. Get in touch when you want it running on its own.