FACTORY ZERO

FZ-008 · SUPPORT

SupportGenius

Support answers from your docs; anything unanswered goes to your team.

In development VALIDATION FZ stackBug reports and supportOpen source
Visit supportgeni.us Launched: NOT YET
Status
In development
Pipeline stage
VALIDATION
Sector
SUPPORT
Autonomy target
LEVEL 4 · SELF-OPTIMIZING
Built with
3 live · 2 planned

The problem

Customers wait for answers that are already in your docs, and real bugs get lost in the inbox.

What it does

SupportGenius is designed to answer customers from your own docs and turn what it cannot answer into a ticket.

How it works

  1. Answers by chat, voice or phone, from your docs, tickets and files
  2. What it can’t answer becomes a support ticket, a sales lead or a GitHub issue with steps to reproduce
  3. Every ticket is checked a second time before it is filed, and the customer gets updates until it is closed

The core is free and open source (MIT) and public on GitHub.

Built to take repeat questions and ticket triage off your week.

TodayBeing built in the open: MIT core on GitHub (widget, MCP, ticketing, takeover), staging API up, waitlist open; nothing hosted yet.

The film

Support that answers.

Aims

Autonomous operation
The support desk is the automation target: answering from the company’s own docs, tickets and files, turning what it cannot answer into a ticket, a lead or an issue with reproduction steps, and keeping the customer told until it is closed. People stay on call to approve, take over and hand back; nothing is filed on one model’s say-so.
Intelligence
Two models that check each other rather than one bigger one. A drafting model turns the conversation into a structured ticket and an independent judge decides whether, where and with what priority it is filed; the agent answers only above a confidence threshold, and each correction a person makes is kept as a reviewed source for the next customer.
Growth
Resolution-led. Growth is conversations resolved without a handoff and escalations filed without a correction, counted from the first widget that runs on a site that is not the author’s.
The technical detail

A customer-support agent that answers from a company’s own docs, tickets and files, by text or voice, through a web widget, an iOS or Android SDK, a phone line, an API or an MCP server. What it cannot answer becomes a ticket for support, a lead for sales or a GitHub issue with reproduction steps for engineering: a drafting model writes it, an independent judge model checks it before anything is filed, and the customer hears back as it moves until it is closed. The ticketing and routing core is planned in Rust, open source under MIT. The MIT core is public on GitHub (widget, MCP server, ticketing and takeover) and a staging API is up; the agent, the SDKs, the phone line and the integrations are still being written. The waitlist is open, and nothing is hosted yet.

Related

From the same foundation.

All ventures