Get started
Quickstart
The path from a fresh account to your first agent-built pull request is short, but a few things are worth knowing before you start so nothing feels like it's stuck when it's actually just working as designed.
- A theme needs a handful of similar signals before it forms - a brand-new account with light traffic may show individual signals for a bit before real themes appear.
- Connectors sync on a schedule, but every one has a manual Sync now if you don't want to wait.
- GitHub is optional but load-bearing - feasibility checks, grounded PRDs, and build agents all depend on it being connected.
- The manual Add feature button (for typing in an idea directly, rather than promoting a theme) currently requires GitHub to be connected first.
- Nothing ever merges itself. Every agent-built change stops at a pull request for you to review.
1. Connect a feedback source
In Settings → Connectors, connect whichever tool your team's customer feedback already lives in - Slack, Zoho Desk, Nolt, or Granola. Start with just one; see Connecting your stack for what each is used for.
2. Connect GitHub
This is the one worth not skipping. Without it, themes get ranked on signal volume alone; with it, VocxAI checks what's already built, grounds PRDs in your real codebase, and build agents can actually open pull requests. Full walkthrough: Connect GitHub.
3. Give it a little time to cluster
Once signals are flowing, VocxAI groups related ones into themes automatically - but a theme only forms once several similar signals show up, so a quiet connector might take a while to produce its first real theme. See Signals & themes for how clustering actually works.
4. Review your first theme
Open a theme to review the signals behind it and, if GitHub is connected, its feasibility spike - a quick automated check of how much of it might already exist in your codebase and how much effort the rest would take. If you're tracking any competitors, you'll also see whether one of them already ships it. When one's worth pursuing, promote it to a feature.
5. Review the plan, then approve
Promoting a theme just adds it to the backlog - nothing gets drafted until you ask for it. From the feature's page, Generate PRD kicks off the in-depth architectural plan and product requirements behind it, grounded in your codebase if GitHub is connected. Review the decisions it raises, then generate specs and detailed build-agent tasks the same way - each stage is something you choose to move forward, not something that happens on its own. When you're satisfied with the full plan, Approve for build is what actually starts the agents. See Approval gates for what's checked before you can.
6. Review your first pull request
Watch progress live on the Build agents board. Once a build job finishes, a normal pull request shows up in your repo, ready for the review it would get from any other contributor - nothing merges on its own. See Agents & jobs for the full pipeline this comes from.