Contact
Who answers, and when
Four desks, a named owner on each, and the median time it takes to hear back.
Billing and accounts
Median 31 minInvoices, proration and anything Relay escalated to a person on your queue.
Dana Okonjo, billing on-call
Rollout and setup
Same working dayConnecting Stripe and a helpdesk, moving a ceiling, tuning the 0.8 threshold.
The engineer who built your connector
Security review
Two working daysScopes, sub-processors and the DPA. Most of it is already written down.
Answered against the scope ledger
Something is wrong
24 hours a dayRelay sent something it should not have, or stopped sending at all.
The on-call engineer, not a queue
31 min
Median reply on billing, last quarter
Measured from the message arriving to a person answering it, not to an autoresponder. The slowest 5% took under four hours.
Who you are contracting with
registered details- Entity
- Relay Systems Ltd
- Registered
- Company 11482996, England and Wales
- Office
- Ashby House, 4 Hoxton Square, London N1 6NU
- Data region
- eu-west-1, with three sub-processors
- Data controller
- privacy@relay.systems
Scopes, retention and the sub-processor list are on the security page.
Send it on
Ask one of them directly
Pick the desk, say what happened, and the receipt tells you who has it and how long you wait.
This is the frontend. The request is validated and receipted in the page and nothing is transmitted — point the form at your own endpoint and the same four states carry through.
- Workspace
- Coilbook, eu-west-1
- Last run
- ZD-4821 · 6 tool calls
- Kept
- 13 months, with the audit log
Put Relay on the billing queue
Connect Stripe and one helpdesk, approve its first 50 replies, then let it send.
- No card to start
- You approve its first 50 replies
- Cancel any month