Run the ops room from a Telegram group

The problem

Operations already lives in a group chat. Dispatchers, the warehouse, the night shift — the Telegram group is where “truck 14 is stuck” actually gets said first. The systems, meanwhile, live somewhere else: status means opening a laptop, alerts mean an email nobody reads until morning, and the person who can check is asleep.

So the group fills with questions that a database could answer and screenshots of dashboards taken by whoever happens to be at a desk. The information all exists; it just doesn’t attend the conversation.

How your Aivell does it

Telegram is rolling out to early-access customers first — this is the shape of it:

1. The box joins the group. It listens for its name and obeys only the people on its list. A stranger added to the group gets silence, and a log entry.
2. Status becomes a question, not a login. “How are we looking?” returns one composed message from the database — trucks out, orders open, today’s exceptions — instead of four screenshots and a shrug.
3. Alerts arrive translated. Warehouse systems fire webhooks at the box; the Aivell posts them with context — what it means, which order it touches, what the usual fix is — rather than forwarding raw payloads into the chat.
4. Commands run chores, nothing else. “Rerun the morning report”, “chase the carrier on order 3121” — each maps to a chore that already exists and was already approved. Free-form orders have nothing to grab onto.
5. Changes wait for a thumbs-up. Anything that writes to the database pauses for Tommaso’s approval in the thread — the decision happens where the discussion is, with the audit trail written on the box.
6. Nights are quiet by rule. Between 22:00 and 6:00 only genuine urgencies speak; everything else waits for the 7:00 summary.

The group chat your team already trusts becomes the front end. The back end — data, judgment, chores, logs — never leaves your building.