Operations OS

One queue for orders, SLAs, and handoffs.

Relay is the shared system of record for multi-site teams. Route work across plants, keep SLA clocks honest, and pass a shift without a Slack scavenger hunt.

Sites, not silosEvery plant sees the same ticket.
Clocks that escalateAt-risk work surfaces before breach.
Handoffs with contextNotes, owners, and next action.
app.relayops.example / workspace / north-loop

Today · North Loop

12 on track 3 at risk 1 breached
Incoming 4
ORD-1842
Inbound kit, Dock 2
On track18m
ORD-1840
Wave 3 pick release
Plant B41m
In progress 3
ORD-1836
Pack-out, line 4
At risk6m
ORD-1831
Label reprint batch
On track27m
Handoff 2
HAN-882
Nights → QC sample pull
OpenA. Ruiz
HAN-879
Dock 3 notes for AM
OpenK. Novak
Closed 5
ORD-1822
Carrier pickup window
Met SLAdone
ORD-1819
Short-ship exception
Misseddone

What Relay holds

The work, the clock, the pass.

Three primitives. Enough to replace the spreadsheet, the group chat, and the whiteboard by the supervisor office.

01 / Orders

Site-aware queues

Every order is a ticket with a site, an owner, and a next action. Route across plants without losing the thread when work leaves the building.

02 / SLAs

Clocks that escalate

Define windows per order type. Relay marks on-track, at-risk, and breached — and pages the next owner before the customer does.

03 / Handoffs

Shifts with a record

Structured pass-downs: what moved, what’s blocked, who owns the morning. No more reconstructing the night from DMs.

Pricing

Start with a site. Add the rest when the queue is real.

Three plans. Monthly or annual. No seat minimums on Starter.

View plans