Nothing answers a customer untested. The release gate

Company · About

About Rouxwe started with the ending

OriginWe started with the ending

Why this exists

Every product in this category starts from the same place: the call is a cost, and the job is to make it cheaper. Deflect it, shorten it, script it. We started from the other end, from the sentence every support team says and no system remembers: someone will call you back.

That silence is not a staffing problem. It is a systems problem: the promise lives in nobody's queue, attached to nobody's name, with nobody's deadline. So we built the boring part first. A record of promises. A real ending for every conversation. A watchdog that does not share the team's incentives. Then the agents, good enough to make most of the promises unnecessary, because they resolve instead of deferring.

Roux is the cooking kind of roux: the unglamorous base you make first, patiently, because everything else in the dish depends on it. That is what we think trust is in customer contact. It is made at the start, at low heat, and you cannot add it at the end.

PrinciplesOn the wall, and in the product

What we hold

Endings over interactions

We do not count conversations. We count how they end. Resolved and handed-over-clean are the only two endings we ship.

Proof over assurance

Where a claim can be a mechanism, it must be. The gate refuses on its own, the record remembers on its own, the watchdog never sleeps. None of it is a paragraph in a deck. And where we have no proof, we make no claim.

Manners at scale

Quiet hours, consent, suppression, disclosure. The rules are not overhead; they are what being worth answering sounds like.

Working on the first cohortdesign partners, selected for 2026

What a partner gets