Answers

Relay is the sending layer a company builds against. It holds the numbers, the queue and the delivery receipts, and hands your own software a single endpoint to talk to instead of eleven carrier contracts.

The inbox is a finished product your support team logs into. Relay has no screen of its own: it is the pipe underneath, meant to be wired into a system you already run.

Desk is for a shop or a studio with one line and a handful of staff. Relay suits a company sending at volume from its own systems, with policy files, audit trails and a rate ceiling you set.

Three: the hosted API for teams with engineers, a signed webhook bridge for record systems that only speak HTTP, or a delivery partner who does the wiring and hands you the finished connection.

If you have engineers who own the record system, build direct. If the work would sit at the back of a long queue, a partner will usually have you sending in a fortnight and stays on for support.

Yes. Apply for a reseller key, pass the sending review, and you can open and bill client workspaces from one console. Clients keep their own numbers and can be handed over later.

A self-hosted gateway exists for regulated work where message bodies may not leave your estate. It runs behind your own firewall and reports only delivery metadata back to us.

Written support with a four-hour first reply, a named engineer for accounts over 400,000 messages a month, and a shared channel during any migration week you schedule with us.

There is no platform fee. You pay per delivered conversation, from $0.0138 in most regions, and the first 900 conversations each month are not charged at all.

Card on file with a monthly statement, invoicing on 30-day terms once you clear a review, or a prepaid balance that draws down as conversations are delivered.

Every account agrees to the sending standards: a recorded opt-in, a working stop word in each thread, no resale of recipient lists, and honest sender identity on every number you register.