Your stack and setup
Turn email, forms and chat into tested fixes
Customer problems arrive by email, a shared channel or your product instead of a help desk.
Novix has its own intake: a chat widget you paste into your site, a hosted report form, and one address to forward mail to. No help desk to buy first.
How Novix gets involved
A forwarded email, a widget message or a form.
Three first-party doorways, none of which needs another vendor. One script tag for the widget, a hosted page you link or frame for the form, and one shared address for forwarded mail.
How the agent handles it
The form is an iframe on purpose
The markup, the styling, the validation, the token and the uploads all stay on Novix’s own origin, so nothing here can reach your page. Framing is refused until a workspace lists the sites allowed to do it.
Forwarded mail routes on who forwarded it
The sender must be a verified member of a workspace, and the message must carry an authentication result saying the domain passed. No verdict, no task. A stranger is refused and logged, never bounced.
The customer, not the colleague who pressed forward
The forwarded envelope inside the body is parsed, so the requester on the task is the person who actually reported it, and the task records which of the two addresses it used.
A message with no words but a file is still a report
Somebody posting only a screenshot makes a task, titled from the file’s own name, because nobody has read the image yet and anything describing it would be invented.
From there it is the ordinary run
ClassifyDecides whether this is actionable work on your repo, and sets its category and severity. A teammate asking for a change counts; spam and outside feedback are set aside without spending anything.The same nine stages a connected help desk gets. A first-party doorway is a way in, not a lesser lane.
What your team gets
- A task from a widget message, a form submission or a forwarded mail
- Attachments checked by extension, size and sniffed bytes rather than a declared type
- The same diagnosis, patch and pull request the connector path produces
An address typed into a public widget proves nothing
The widget is the one surface open to an unauthenticated stranger, so whatever email is typed into it always reads as a customer and never as a member of your team. That decides who the reply is written for.
Works with
- Chat widget
- Report form
- Forwarded email
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.