Fail closed.
When a check cannot complete, the safe answer is no. A gate that passes when it cannot read its own output passes exactly what it exists to catch.
Why Rachel
Built by people who assumed it would go wrong.
Rachel started as an answer to a specific problem: an AI that is genuinely allowed to sell, without any single mistake being expensive.
The demo that started it was impressive and slightly alarming.An AI that quotes, handles objections, and pushes to signature is obviously valuable. It is also an AI with your prices, your calendar, and your name on a message somebody keeps. The interesting engineering is not making it talk. It is deciding what it is allowed to be wrong about.
So the guardrails went underneath the agent, not inside it.Anything enforced in a prompt is enforced by something a prospect can argue with. The discount floor refuses in the database. Consent is checked by one function that everything else has to go through. The closing motion is enforced in the agent and again in the database. The groundedness gate fails closed, so an unreadable verdict rejects instead of guessing. These are not settings we are proud of individually; they are the reason the product is safe to hand a price list.
And the accounts stayed with the customer.The easy version of this business pools everybody's sending through one platform account. It is cheaper to build and it means one customer's bad contact list can damage everyone else's deliverability. We took the harder path: your AI key, your mailbox, your Twilio account, your number, your 10DLC brand. We are not the sender of record for anything. The reputation you build is yours, and nobody else can spend it.
How we build
Six things we decided early and have not moved on.
Enforce it where it cannot be argued with.
A rule in a prompt is a suggestion to a very persuadable reader. The floor, consent, and the closing motion all live in the database.
Say which of the three it is.
A message that is not going out is blocked, failed, or held for a channel that is not ready. Those need different people to act, so the portal never collapses them into one grey status.
Ship closed and open deliberately.
New workspaces start at meeting-only with escalation on any money question. A config surface that defaults open means the first misconfigured customer discovers the guardrail by violating it.
Measure the claims we make.
The portal shows the median time from form fill to provider accept, and the cost of every reply, because a claim about speed or cost that nobody measures quietly stops being true.
No dead buttons.
If an integration is not ready, the card says coming soon. Salesforce and HubSpot say coming soon today.
Things we chose not to do.
- Cold outbound voice calling. The legal surface is not worth it, so a call only ever goes back to somebody who rang you first.
- A shared sending pool. It would be cheaper and it would put your deliverability in somebody else's hands.
- A knowledge base that rewrites itself. Nothing becomes canon without a human approving it.
- A per-message price. Your usage is billed by your own providers, at their rates, with nothing added by us.
See her handle your hardest objection
Book a walkthrough. We will set her up against your pricing, your floor, and your objections, and you can try to talk her into a bad deal.