A Tuesday in the group chat

A delivery arrives in the middle of the lunch rush. The person who signs for it has both hands full, a queue at the counter, and no plan to open a spreadsheet on their phone.

So the delivery gets remembered instead of recorded. Maybe it makes the sheet that evening. Maybe it goes in wrong. This is where most small business data actually goes missing: not in the accounting, but in the ninety seconds nobody has.

Here is what that Tuesday looks like when the system lives in the group chat.

The morning: a photo, then a confirm

Whoever signed photographs the slip and sends it to the group, the same way they would send it to anyone who needed to see it.

That is the whole interaction. No app to open. No form. The person who did the work sent a photo they were going to send anyway.

Notice what comes back. Not “thanks, got it.” Nossy says the image is in Drive, and it asks before a number on the slip becomes a row. If the read is wrong, you catch it in the two seconds you still have, not three weeks later at close.

At Zendai this is not a demo beat. Bookkeeping is 600+ items a month. More than 300 of those are receipt images. Inventory moves in and out every day, in the same group.

We started with plain text in that chat. OCR made the record faster. The image as evidence is what we would not give up. When the Revenue Department asked for documents this year, I exported the summary and sent it. One hour.

Midday: memory, not a report

The middle of the day is when the operational questions show up. These used to route through my phone, because I was the only person who could read the sheet.

Now the floor asks the group. Did we already pay that supplier. How much of this is left. The answer comes from a fresh read of the sheet, with enough context to know how much to trust it. If nothing was logged, the answer is that nothing was logged.

Nossy also acts on time, not only on messages. I set reminders and schedules for myself, the way a secretary keeps a calendar. The same chat reminds staff to do a job. Reminders and scheduled runs are documented capability. Sending proof of work back into the group is how we use it at the cafe.

Evening: the close

At the end of service the day closes the same way it ran. Counts go into the group. Ambiguous messages get a question, not a guess.

An agent that quietly picks the most likely option is an agent whose numbers you eventually stop trusting. One clarifying question, asked while the person still remembers, is cheaper than a wrong row at month end.

The old close was me scrolling a month of LINE into a sheet. One of those months took three to four hours even when I logged only the price. I do not do that scroll anymore.

What is actually happening underneath

None of this is a chatbot with a good memory. Each message lands as a structured row in a real spreadsheet, in the business’s own Google Drive. I can open it any time and read it like a normal sheet.

That is the whole architecture, and it is the point of When the spreadsheet stopped working. A workbook that is both the database and the user interface will fail at one of those jobs. It is always the interface that fails first.

So the two jobs get separated. The sheet stays the database. The chat becomes the interface. Nobody has to learn the sheet. The sheet never has to be friendly.

If Nossy went away tomorrow, the spreadsheet would still be there, still readable, still ours.

What it does not do

Some honest limits, because a demo that only shows the good parts is a sales pitch.

• It does not invent numbers. If nothing was logged, the answer is “nothing was logged,” not an estimate. When it reads a value off an image, it confirms that value before the row is fact.
• It does not replace a POS, an accounting package, or a payroll system. It records what your team tells it and keeps the structure clean.
• It is only as current as what people send it. Messaging is a lower bar than data entry. The bar does not disappear.
• It asks when a message is ambiguous, which means it will sometimes ask about something you thought was obvious.

How you get there

The setup happens once, in the browser, before any of the above.

1. Sign in and create your organization. Standard, takes a minute.
2. Create a project. The agent interviews you about how the business actually runs, and can start from the spreadsheet you already use.
3. Connect your channel. Link the project to the group chat your team already lives in. From that point, the day above is just the day.

The setup conversation stays open afterward. When the business changes, you tell the agent what changed.

See how pricing works if you want the next step, not another article.