About Vroxy

Support chat has two familiar failure modes. Either a bot cheerfully invents an answer and the customer leaves angrier than they arrived, or there is no bot and a person retypes the same four answers all day.

Vroxy is built on the assumption that the second one is the honest failure, and the fix is not a smarter guess — it is a bot that only speaks from things you actually wrote.

What that means in practice

The corpus is the product. The bot answers from your documents and your tools. When it does not know, it says so and gets a person, rather than producing something plausible.

Handoff is a feature, not an apology. The bot stands down the instant an operator types and picks the thread back up with full context when you hand it back. Nobody is stuck arguing with a machine to reach a human.

Every unanswered question is a signal. The conversations where the bot handed off are the map of what your documentation is missing. We are building toward closing that loop automatically.

We run on it

The widget on this page is Vroxy, installed through our own public Ruby gem, answering from our own docs. Every rough edge you would hit, we hit first. It is not a demo instance — it is the same product, and it is how we find out what is broken before you do.

Talk to us

We are small, we read everything, and we are more interested in the thing you think is wrong than the thing you think is nice. [email protected], or just use the widget in the corner.