Relay

Caution

Early access. Relay is not open to customers yet, and the launcher shows it as Coming soon. This page documents how it works.

Relay follows a work order — a cut, a batch, a job — through your production, from the moment it arrives to completion. At every hand-over it records who, when, how many, and what they observed.

The point of recording all four is the third one. When the person who hands over counts 197 and the person who receives counts 195, Relay does not stop the line and it does not average them: it records a difference of two against that leg, with both names on it. At the end of the month you have a list of where stock goes missing instead of an argument about whether it did.

Relay learns your company, you do not learn Relay

Set up a workflow directly in the editor or describe it to the assistant. Start with the service-request or laundry template, then edit the stage names, roles, deadlines and fields in your company’s words. Templates populate a draft; you review and save it. Direct setup works even when the assistant is unavailable.

General tasks can collect text, numbers, dates, choices and explicit yes/no answers. An optional step can depend on an earlier required yes/no answer. Use a counted handover where quantities matter, a claimed task where one person takes responsibility, and a completed stage when the work is done. Completion does not require an invoice.

1. Open relay.destesi.io and sign in.

2. Answer its questions in your own words. Use your own names for things: a company that says bodega gets a stage called Bodega.

3. Read the stage table it proposes. Say what you want different — “the workshop is only for lots that need presilla”, “Kenia does the definition” — and it changes it.

4. Say yes. The board appears.

Later, edit the workflow in Settings or ask the assistant to change it.

Note

A stage you keep keeps its history. A stage you remove is retired rather than deleted, and Relay refuses to retire one that still holds open orders — it tells you how many, so you can move them on first. Once a stage has work or history, changing its type or field definitions requires a new stage key. Recorded answers retain their field labels in the handover history.

Relay supports one active workflow per workspace, with ordered and optional steps. Parallel branches, loops and executable automation are not supported.

Your queue, and the board

Relay opens on your queue: the lots you have taken, then the lots waiting at the stages your roles cover, late first, found by typing a number, a client or the document the lot arrived on. That is the floor’s only question — what is mine now — and one tap on a row is the hand-over itself.

The Plant view is the other question, the owner’s: one column per stage, every lot in the building. Either view is a click away and Relay remembers which one you use.

Relay’s own words are in English or Spanish — the EN / ES toggle sits in the top bar and is remembered per person. Your stages, roles, tasks and fields are never translated: they are your words, in whatever language you typed them.

Some stages are claimed before they are worked: the first tap says “I am going” and everyone else sees the lot is taken. That one behaviour is the whole fix for three drivers each assuming another went.

Some stages are outside the building — an external workshop with no user accounts. Arriving is the hand-in; the stage’s own hand-over is the collection, often by a different driver. Relay colours the card by how long it has been sitting there.

An open order’s page lets you define the work (wash steps and priced tasks from the rate cards, with the quote fixed at today’s prices), lets anyone add a note to its log (“the workshop called, ready Friday”) without moving it, and lets an admin recount it: the corrected count is recorded next to the old one, never over it.

Getting the work in front of people

Everyone tagged for a stage is notified when a lot arrives at it. Each person links their own chat under People → Link my chat; nobody can link it for them, because a pairing link is a credential for one device.

Paying for it

On a stage that pays by the piece, people take a share of a lot before working it, and a big lot is split by two people taking half each. What a share is worth is fixed when it is taken, from the price the lot was quoted at — so a price raised next month never rewrites last fortnight’s wages. The stage will not release the lot until every task on it is finished.

Reports → Payroll totals finished work per person over any window, and downloads as CSV.

Billing

The invoice is assembled from the lot: the service, each task the definer chose, and the external workshop’s own prices. Set what the service costs per unit and your tax rates under Settings → Prices and billing; leave a rate at zero and the invoice simply has no line for it. Your accountant reviews it and records the number they issued.

Everywhere else

Everything above is also dst relay in a terminal and relay_* through MCP, over the same routes. Ask the assistant, run it in a script, or tap it on a phone — it is one product.