Solutions / Chat ops

Workflow automation via chat

Your team writes a normal sentence in the chat they already use, and the register, the statuses and the notifications update themselves — no new app, no spreadsheet open on a phone.

Operations Workflow automation E-commerce · Logistics
60–70%
of manual register upkeep removed
0
new tools for the team to learn
1 message
instead of finding the right row
Who it is for

Owners and operations managers at 5–50 person companies whose real system of record is a spreadsheet and whose team already lives in Telegram or WhatsApp.

Short answer

An operator writes one line in Telegram — “order 412 shipped, tracking attached” — and the agent updates the status, writes the row, and tells whoever was waiting. No new app to install, no spreadsheet open on a phone. On this kind of setup 60–70% of manual register upkeep disappears.

The problem

The spreadsheet runs the business, and nobody wants to open it.

01

The register is updated last, if at all

The driver finishes a delivery and messages the manager. The manager types it into the sheet that evening, or tomorrow, or never. Everyone downstream is working from a picture that was true yesterday.

02

The same question, five times a day

“Where is order 412?” goes to the one person who knows how to read the sheet. Answering it is not their job, but it is most of their day.

03

A new system would fix it — and nobody will use it

You have tried a CRM or a task tracker. Adoption lasted three weeks, because the team's actual working surface is a chat window and no rollout changes that.

How it works

From trigger to result, step by step.

01

Sit in the chat they already use

The agent joins your Telegram or WhatsApp group as a normal member. Nobody installs anything and nobody logs in anywhere new.

02

Read plain language

“412 shipped”, “moved to Thursday”, “client refused, wrong size” — the agent maps the sentence to the record and the field it changes, in whatever wording your team actually types.

03

Confirm before it writes

It replies with the change it is about to make in one line. A thumbs-up or a correction settles it. Ambiguous messages are asked about instead of guessed at.

04

Write to the system of record

The Google Sheet, Airtable base or database is updated with the change, who made it and when — so the register carries an edit history it never had before.

05

Answer from the same data

“Where is 412?”, “what is open for Thursday?”, “how many refusals this week?” are answered in the chat, from the register, without anyone opening it.

Before / after

What changes on the ground.

Today, by hand
×Statuses reach the sheet hours or days late
×One person is the interface to the register
×No record of who changed what, or when
×Reports are assembled by hand on Friday
With the automation running
›The register updates within seconds of the message
›Anyone asks the chat and gets the answer
›Every change carries an author and a timestamp
›The weekly digest writes itself
What you get

Delivered, not demoed.

›A chat agent live in your Telegram or WhatsApp group
›A mapping from your team's real phrasing to your fields
›Confirmation and correction flow so nothing is written on a guess
›An edit log and a scheduled digest of what changed
›Documentation and a handover session — the system is yours
Built with

We build in your stack rather than moving you onto ours. The list below is what this solution most often connects to — other systems are a scoping question, not a blocker.

LLM (replaceable) Telegram Bot API WhatsApp Business API Google Sheets API Airtable Postgres n8n Zapier
Time to production3–5 weeks
Build priceFixed quote
First stepFree mini-audit
Honest limits

When this is not the right solution.

·If your process already lives in a CRM that the team genuinely uses, this adds a second surface rather than removing one. Automating inside the CRM is the cheaper project.
·If the register has no owner and no agreed fields, the agent will write faster nonsense. Agreeing what a status means comes first, and that is your call.
·Regulated records that need a signed audit trail belong in a system built for it, not in a spreadsheet with a bot in front of it.

Questions we get about this one

No. That is the point of it. The agent reads ordinary sentences in whatever mix of language, slang and shorthand your team already uses in that group, and asks when it is not sure. We tune it during the pilot on your real chat history, not on invented examples.

Bring us the process that hurts.

The mini-audit is free: we take your version of this process apart and tell you plainly whether automating it pays. If it does, you get a scope and a fixed price.