Product · Platform
Roux answers your line, and makes the calls promised on it. Both read the same record of the customer before they speak, and both pass the same decision before they reach anyone.
Answers on voice and web chat, works from the policies your team wrote, acts against your connected systems, and when it can't finish, escalates with context or schedules a callback. A conversation ends resolved, or with a named person. Never in between.
Nothing is dropped →Inbound
Two good endings
Reminders, renewals, early attrition signals, reactivation, and the callbacks inbound promised. Every attempt passes the contact decision first: consent, quiet hours, suppression, frequency. A scheduled contact either fully exists or it doesn't; there are no half-made calls.
One customer, not four inboxes →Outbound
Checks before dialing
The relationship record holds memory, consents, suppressions and open items, per customer, not per channel. The release gate tests every version as the exact one that goes live. Both are things you can watch working, which is the point.
You can prove any of it →By construction
Not by policy
The gate is the honest part: a release that refuses to activate without a passing test of exactly that configuration. Rollbacks pass the same check.