Referral handoffs should not fail silently.

Relay makes every referral acknowledged, progressed, and closed — with a shared timeline both teams can trust.

Private pilot now open
Built for high-volume specialist teamsFits current workflowsDesigned for real clinic pressure
Specialist ReferralShared status timeline
Active
Referral SentReferring Clinic
AcknowledgedSpecialist Team
Triage CompleteClinical Lead
Patient BookedBooking Team

From assumption to certainty.

See the same referral through two lenses: the general email inbox everyone wrestles with, and the Relay workspace where every task is owned, timestamped, and closed.

General email
No ownerMissing updates
Everything hides inside the inbox.
  • Looks tidy, but every referral is just another subject line with no owner.
  • Status lives in people’s heads — nothing shows who replied or when.
  • Referrers and Specialists chase blindly because there’s zero proof anything was acknowledged.
inbox
PrimaryUpdatesPromotions
DGDr Lucy Grant
Referral — attachment.pdf · “Patient ready for implant consult…” · No reply recorded
6d
MBMax Bowen
Re: Referral status? · “Did we ever respond to Dr Grant?” · No owner
8d
Inbox confusion·Still zero assignment, zero accountability.
Relay
AcknowledgedShared Status
The same referral is visible, accountable, and done.
  • Every referral becomes a trackable card with owner, SLA, and audit trail.
  • Status changes ping referrers and specialists automatically.
  • Seen, acknowledged, and closed — with exportable proof if anyone asks.
FromDr Lucy Grant·lucy.grant@smiles.com
John Smith · Implant
2mAuto-tracked · Mar 12 · 9:41am

Specialist confirmed imaging; booking call locked for Thursday.

2attachments·Receipt sent
AcknowledgedBooked · Trail ready

Ready to retire the referral inbox?

Show both teams a shared, timestamped record with Relay.
Request access

How Relay turns a referral into a shared record.

Relay becomes the shared system of record the referrer and specialist can both see, so every state, receipt, and handoff is trackable instead of living inside someone’s inbox.

FromDr Nguyen·nguyen@lakeside.dent

Diego Ramos

Urgent CBCT review request

1d13 Nov 2024 · 4:15 pm
2 attachmentsReceipt confirmed
Status

Referral history

  • Receipt acknowledged

    Relay issued RL-2048 back to Dr Nguyen as soon as the referral landed.

  • CBCT requested

    Kelly (specialist) requested the latest CBCT + STL inside Relay — visible to both sides.

  • Files uploaded

    Referrer uploaded CBCT-final.zip and consent.docx; Relay pinned them to the case.

  • Ready to book

    Relay nudged the team: “Awaiting imaging review · book by Thu 2:30pm”.

A safeguard against silent referral breakdowns.

Relay reduces missed handoffs by making ownership and status explicit to both teams.

  • Every referral receives confirmation
  • Every action is timestamped
  • Every state change is visible
  • Every loop can close cleanly
Not another inbox. A shared operating layer for referral handoffs.

Designed for real referral pressure

Schedules compress. Threads fragment. Attention shifts. Relay keeps referrals moving when work gets messy.

Core metric: referrals that move forward and close — not dashboard activity.

Need proof every referral is acknowledged?

Relay shares live status with partners without changing their tools.
Request access

Built for teams that handle referral volume.

If you receive referrals, Relay makes them harder to lose without forcing major workflow change.

Specialist practices

Keep incoming referrals visible, trackable, and closable with less chasing and fewer dropped handoffs.

Hospital departments

Create shared status across triage, booking, and clinics with clear timestamps and ownership.

Subspecialty teams

Keep progression clear under load and close loops with a consistent trail.

Referral handoffs should not rely on inbox memory.

Every stalled referral is a waiting patient.Relay keeps the handoff moving.

Give both teams shared status, clear ownership, and a reliable close state for every referral.

Limited private pilot spaces available.
v1.0.0-dev.101