See when important work did not happen as expected.

Identifies when an expected business outcome has not happened, creates a tracked exception, and gives a person a private Inbox in which to review, resolve, and record what happened.

Relay is a V0.1 release candidate. It is not currently deployed or generally available, and its first controlled pilot has not been activated.

Discuss a controlled pilot

The problem

Silence can look like success.

A workflow can complete without the expected business outcome happening. When no one can see that gap, an unanswered enquiry or another time-bound obligation may sit unnoticed until somebody finds it manually.

Checks for a defined expected outcome.
Creates one exception when attention is required.
Keeps ownership, status and deadlines visible.
Records human decisions in an append-only history.

How it works

From missed outcome to a visible human decision.

Input
Receive a structured event
Relay receives a bounded event from the dedicated source configured for the pilot.
Policy
Evaluate the expected outcome
A versioned rule checks whether the required outcome was recorded by its deadline.
Attention
Create one tracked exception
If attention is needed, Relay creates a deduplicated exception and records any planned next action.
Human decision
Review and resolve
Human review step
A named operator acknowledges, resolves, or dismisses the exception while Relay keeps the audit history.

Product evidence

A working local Exceptions Inbox—not a concept dashboard.

The interface below is the implemented V0.1 release candidate running with deterministic fictional Lead Rescue records. It shows the active queue, named ownership, deadlines, safe metadata, resolution controls and recorded history.

Full LOATY Relay Exceptions Inbox with two fictional active Lead Rescue exceptions and one selected exception detail. — Product evidence
Exceptions Inbox · fictional Lead Rescue data
Captured from the local release candidate. No customer data is shown.

First planned pilot

Lead Rescue, tightly bounded.

The pilot is intended to test whether Relay is useful for a business with a defined lead-response deadline. This audience and value remain hypotheses until tested with a real participant.

Participants: One small business; one primary and one backup named operator.
Pack: Lead Rescue only.
Access: A private, single-tenant Exceptions Inbox.
Mode: Action planning only; Relay does not execute notifications.
Duration: Thirty days after a seven-day fictional-data rehearsal and approval gate.
Current state: Pilot not activated; no customer onboarding or real data authorised.

Current limits

Relay makes exceptions visible. People remain responsible for the response.

No email, SMS, Slack or Teams notification executor
No autonomous action or customer contact
No live email, CRM or forms connection
No public or multi-tenant deployment
No customer data in the current release candidate
No approved pricing or general-availability date

Pilot hypothesis

A defined, deadline-bound lead-response workflow.

The first pilot is intended for one small business that assigns inbound enquiries to named people and can define what counts as a qualifying response. This fit is not yet customer-validated.

Not the current product

Not a workflow builder or autonomous agent.

Relay does not replace an automation platform, read inboxes, contact leads, connect directly to CRM systems or forms, or carry out the planned response. Those boundaries are part of the V0.1 release candidate.

Frequently asked questions

Controlled-pilot enquiry

Discuss whether your lead-response workflow could fit the first pilot.

Please do not submit customer records, enquiry content or other operational data through the website form.