Relay
Every inbound message — email, chat, SMS, forms — ingested, normalized, and threaded into one conversation model.
In the constellation
Relay highlighted in the live map — hover or tap any node to explore.
Why it exists
Messages arrive everywhere — email, chat, SMS, web forms — and each channel comes with its own inbox, its own format, and its own parser. Stitching them into one coherent conversation is work every team redoes, badly.
The result is a fractured view of every customer and contact: the same thread scattered across tools, with no single place that says “here is the whole conversation.”
What Relay is
Relay is the inbound side of communications, unified. It ingests messages from every channel, normalizes them into one shape, and threads them into a single conversation model your app can read from one place.
It’s the missing inbound half of the system: where the marketing and sales engines push messages out, Relay takes them in — and never tries to guess what a message means or how to answer it.
What it does
Every channel, one path
Email, chat, SMS, and web forms ingested through a single uniform pipeline.
Threading
Messages stitched into coherent conversations across channels and time — deduped, ordered, complete.
One conversation model
A single queryable inbox surface your app reads, instead of a parser per channel.
State tracking
Read/unread, open/closed, attachments, and retention tracked mechanically.
The line between judgment and machinery
AccelMars draws one hard line through every product: what an AI decides, and what runs deterministically. Relay sits on the deterministic side.
Deterministic by design
- ▪ Channel ingestion across email, chat, SMS, forms
- ▪ Normalization to a uniform message shape
- ▪ Threading, dedup, and ordering
Relay shapes the conversation; it never judges it. Intent, triage, and what to do about a message are the app’s call — the engine just delivers a clean, threaded inbox to decide over.
Planned — designed, not yet built. It will power the unified inbox in Aide and future support apps — the inbound counterpart to the outbound marketing and sales engines.
Open-core, like Anchor and Booster — the mechanical engine in the open.