Close the loop with the customer

How Novix gets involved

Every completed Novix run.

No trigger and no setting. The reply stage is the ninth stage of every run, and it is the only stage whose output is meant for somebody outside your team.

How the agent handles it

Customer and teammate updates stay separate
RespondDrafts the reply for a person to review and send: support voice for a customer, an engineering note for a teammate. When a teammate reports something a customer hit, it drafts a second reply for the customer.
A customer gets at most 120 words in a support voice. A colleague gets at most 60, no greeting, with the file paths and the specific change said out loud. The two never share a code path.
Internal details are removed in code
Every url, path, stack frame, secret, environment assignment and internal identifier is stripped out of the customer draft on the way past. It runs over the deterministic fallback too, so it cannot be skipped by a stage that never called a model.
Copy rules are enforced after generation
A deterministic pass rewrites em dashes out of every parsed answer, by declared field name, so it can never touch a diff or a path. A prompt is a request; this is a gate.
When a colleague relayed a customer
The same call answers whether there is a customer behind the report and what in the text shows it. A judgment that cannot name its evidence in a dozen words is refused, and no second draft is written.
A person clicks send
Nothing in this stage or below it sends anything, on any channel. A person still decides what reaches the customer.

What your team gets

A customer reply, scrubbed of every internal detail
An engineering note when the reporter was a colleague
A second draft for the customer behind a relayed report, with the reason it was written

The AI is pointed at your engineers, not at your customers

Novix has no deflection bot and no auto-send. Every customer-facing string is a draft, and the one path that reuses a drafted reply without a person refuses an internal one outright rather than scrubbing it.

Works with

Zendesk
Intercom
Help Scout
Front

Try it on a real customer problem.

Connect the place reports or product signals already arrive. The same agent takes it from evidence to a tested pull request.

Start free Chat with the founder

How the agent handles it

Customer and teammate updates stay separate

A customer gets at most 120 words in a support voice. A colleague gets at most 60, no greeting, with the file paths and the specific change said out loud. The two never share a code path.

Internal details are removed in code

Every url, path, stack frame, secret, environment assignment and internal identifier is stripped out of the customer draft on the way past. It runs over the deterministic fallback too, so it cannot be skipped by a stage that never called a model.

Copy rules are enforced after generation

A deterministic pass rewrites em dashes out of every parsed answer, by declared field name, so it can never touch a diff or a path. A prompt is a request; this is a gate.

When a colleague relayed a customer

The same call answers whether there is a customer behind the report and what in the text shows it. A judgment that cannot name its evidence in a dozen words is refused, and no second draft is written.

A person clicks send

Nothing in this stage or below it sends anything, on any channel. A person still decides what reaches the customer.