AI receptionist for small business. Honest answers.

Most accounts are live within 30 minutes of checkout. Ava starts monitoring inbound channels as soon as the integration handshake completes; Max, Sam, and Kai come online behind her on the same initialization pass. Rex and Nova activate once your first lead row is written to the pipeline.

Connect at least one inbound channel (email forwarding, a web form, or a chat channel), confirm the inbox Ava replies from, and map your CRM fields so qualification signals land in the right columns. You can change any of these later from the dashboard — nothing is locked at signup.

Yes. Every outbound AI reply — Ava’s first response, Max’s follow-ups, Rex’s re-engagement email, Kai’s support reply, even Sam’s booking proposal — lands in your CRM approval queue before it sends. You green-light the drafts you like and edit the ones you don’t. Nothing goes out unless a human signs off.

Yes — back up to 90 days of historical leads can be imported on request during onboarding. Rex uses that history to set his first 14-day sweep window, so cold prospects in your existing pipeline get the same treatment as fresh ones.

All leads, conversation transcripts, AI replies, booking rows, follow-up sequences, and operations logs are stored in Neon PostgreSQL on encrypted-at-rest infrastructure in the us-east region. Backups are retained for 30 days. No lead data is replicated to a third-party datastore outside the platform.

No. Anthropic API usage is zero-retention under our enterprise terms — your prompts and completions are not used to train any third-party model, ours or anyone else’s. The agents rely on Anthropic for reasoning but the conversation history stays in your Neon store.

You and anyone you grant CRM access to. The human-in-the-loop approval queue shows every outbound AI draft before it leaves the platform, so accidental sends are structurally impossible. Server logs are scoped to the operations account only.

There’s no data lock-in. On cancellation you can export your full lead, conversation, and booking history as CSV or JSON from the dashboard. After 30 days your tenant is purged from Neon and the export is the only remaining copy. Stripe keeps the billing records required for tax compliance — that’s it.

No. The $99/month is the only line on your Stripe invoice. Onboarding help is built into the dashboard; if you need hands-on migration support from a real human, that’s quoted separately and only when you ask.

No. Monthly Stripe subscription, cancel any time. There’s no minimum term and no auto-renewal trap — the Stripe Customer Portal treats it like a Netflix subscription, not an enterprise SaaS contract.

Open the Stripe Customer Portal from your billing settings, click cancel subscription, done. The platform stops processing new leads within 60 seconds. Your data export remains available for 30 days. No support ticket is required, no retention team is involved.

Stripe retries the card on its standard schedule over the next 7 days. We email you at each retry. The agents keep running for the grace window — we don’t shut off Ava mid-inbound-lead because of a transient card decline. After 7 days the subscription pauses; no data is deleted during the pause.

Ava is the Lead Response agent — she replies to inbound leads in under 90 seconds. Max is the Follow-Up agent — he runs smart multi-touch sequences on leads that didn’t convert. Sam is the Booking agent — she proposes three time slots and confirms calls one-tap. Rex is the Reactivation agent — he sweeps cold leads every 14 days with a fresh-angle email. Nova is the Operations agent — she sends a plain-English morning digest at 7am ET. Kai is the Support agent — he handles tier-1 tickets for billing, how-to, bugs, and cancellation attempts.

The handoff is data-driven, not chatty. Ava qualifies the lead and writes a row to Neon with the engagement signals she observed. Max reads that row and decides whether to start a follow-up sequence, bump the lead to Sam, or leave it alone. Sam writes the booking row, which Ava and Rex read so they stop touching an already-booked prospect. Kai operates on the same Neon store with channel=support so support tickets never get confused with leads. Everyone shares the same source of truth; nobody pays token latency for a direct message to another agent.

Yes — Rex sweeps the pipeline every 14 days, drafts a re-engagement email with a fresh hook (not a boilerplate nudge), and caps each lead at 2 attempts. If the lead doesn’t respond, Rex archives the conversation. Cold leads don’t get churned into spam.

A short paragraph: how many new leads came in yesterday, how many follow-ups went out, how many calls got booked, how much revenue closed, plus one concrete recommended action. Sent at 7am ET from ops@relay by Postmark. Nova does not send the digest to your customers — only to the team.

Not from the dashboard today — the platform ships as a pack of six on purpose, because the hand-offs above only work when every agent is online. If one of them doesn’t apply to your business, the human-in-the-loop review queue means that agent’s drafts simply don’t get approved and they cost you nothing operationally.

Kai triages inbound, but the founding team reads every reply that’s flagged urgent and ships improvements weekly — yes, really, see the changelog. For billing, the Stripe Customer Portal cancels in one click. For everything else, reply to any Relay email and a real person gets back to you within one business day.