How workers report by text message
Field workers do not open dashboards. They have a phone, often a basic one, and a day that ends around three. So the operating loop for them runs over text messages: today's tasks in the morning, a reply with the figures, a check in the afternoon, and a reconcile that turns the day into work orders a manager approves or sends back.
A look under the hood: the day clock, what a worker's channel can and cannot see, how a text becomes an approved record, and why the phrasing is built to work for people who never asked for an AI.
The short version
Each verified worker with a phone has their own isolated channel that sees only their own orders. At 06:30 they receive today's tasks by name. They reply in plain words; each operation type expects two figures, and where and when are required on anything a manager creates. At 14:30 a check asks about what is still open. After the shift a reconcile matches the day's receipts against the orders. The production lead then gets a digest of every worker and an approve-or-return loop; management gets its own evening summary. An order nobody disputes is auto-approved after three days, under a rule management approved beforehand, so the board never fills with the forgotten.
The work orders live in one place, the company HQ, which is the single authority for them. Text messages, a chat app and the HQ itself are three ways to reach the same record.
One working day over text messages. The reconcile (green) is where a set of replies becomes a set of records; the manager's digest closes the loop with approve or send back.
A channel per worker, and it sees only theirs
Every worker's channel is isolated: its agent can read and report that worker's orders and nothing else, and the prompts it runs on are name-free. The worker is not a user in a shared chat; they are one person with one scope, exactly like a manager in the HQ. Delivery is by default for verified workers with a phone, and each send carries a delivery proof, so a message that did not arrive is a known state, not a silence.
The messages travel through a small on-site SMS gateway the company owns, not a cloud messaging vendor, which is what makes a plain phone enough. Where a worker prefers a chat app, the same channel rules apply there.
How a text becomes a record
A reply is not a record until it is reconciled. The agent reads the reply, matches it to the open order, checks the two figures and the where and when, and writes a receipt. The afternoon reconcile compares receipts against orders and surfaces the gaps: an order with no reply, a reply with no order, a figure that does not fit. The manager's digest lists every worker and lets the lead approve or return each one in the same conversation.
Every action a worker or manager takes through a message is an HQ operation by that person, signed with who they are and where the message came from. There is no bot account writing on everyone's behalf. Read the audit and you see people.
Built for people who never asked for this
The workers did not request an AI and the managers did not request a new system, so the rollout is worker by worker, in batches, with the board cleaned first. Before the daily texts start for a group, every inherited order that is overdue or has no location is closed truthfully or re-created properly; a worker's first morning text must be a clean list, not a backlog. The phrasing is the company's own, and the word for the system never appears in a worker's messages.
The same principle governs the managers. The production lead is walked through the backlog one worker at a time in their own chat, and the note that ends it says, in plain language, this is how we work from now on. Adoption comes from the loop being fair and predictable, not from a launch.
A worker has a phone and a day that ends at three. The system meets them there, and everything they say becomes a record only after it is checked.