Most questions are answered in the documentation or the FAQ. If you can't find what you need, the channels below get you to a real person — typically same business day for Business and Enterprise plans, 24–48 hours for Team, best-effort for Free.
1. Quick start
If you're new, these are the three things to read first:
- First review in 10 minutes — connect your repo, link a ticket, and see your first verdict.
- How the 3-stage pipeline works — what codingassist.bot actually does under the hood, so the verdicts make sense.
- Acceptance criteria, mapped — the small shift in how you write tickets that makes the verdicts sharper.
2. Common questions
How do I connect my Git provider?
From app.codingassist.bot/integrations click Connect next to GitHub, GitLab, Bitbucket, or Azure DevOps and authorize the app on the repositories you want reviewed. Step-by-step screenshots are in Connect GitHub and equivalents.
Why was my verdict different from a teammate's review?
codingassist.bot reasons against the acceptance criteria attached to the ticket; if those criteria don't capture an implicit requirement, the verdict will miss it. Open the reasoning trace linked in the verdict comment to see exactly which AC was bound to which line of code.
Where do I change my plan or update billing?
app.codingassist.bot/settings/billing. Plan changes take effect at the next billing cycle; downgrades that reduce seats are refunded prorated on annual plans, credited on monthly.
How do I export my data?
From Settings → Data you can export verdicts, audit trails, and policy configuration as JSON. The export honors the retention window of your plan.
Does the self-hosted version need an internet connection?
Only for license validation (once per day) and optional reasoning offload to a managed LLM. The full air-gapped deployment with BYOM is on the Enterprise plan; see Self-host with Docker.
3. Service status
Real-time uptime and incidents are at status.codingassist.bot. Subscribe there for incident notifications by email, RSS, or Slack webhook. We post postmortems within five business days for any incident that breaches our SLA.
4. Contact us
Product help
In-app chat from app.codingassist.bot (bottom right) routes to the right team based on your plan. If you prefer email, support@codingassist.bot is monitored by engineers, not a Tier 1 desk.
Billing and invoicing
billing@codingassist.bot. For VAT, purchase orders, and W-9/W-8BEN-E forms, mention it in the subject and we'll route faster.
Sales and Enterprise
sales@codingassist.bot or book directly at /contact. Enterprise customers have a dedicated Customer Success Manager whose Slack/Teams channel is set up at onboarding.
Legal and privacy
DPAs, MSAs, SCCs, and rights requests: legal@codingassist.bot (legal) or privacy@codingassist.bot (privacy).
5. Reporting a bug
The fastest path is the in-app "Report a problem" button — it ships the verdict ID, your plan, and the recent trace so we don't have to ask. If you'd rather email, include:
- The verdict or reasoning-trace URL (visible in the comment we posted on your PR);
- What you expected vs what happened;
- The minimum repro if you have it.
We triage public bug reports on github.com/codingassist/issues. Don't include Customer Data in public issues.
6. Reporting a security issue
Please do not file public issues for security reports. Email security@codingassist.bot — PGP key at /.well-known/security.txt.
We acknowledge within 24 hours, triage within 72, and reward valid findings under our Coordinated Disclosure Program. See our security page for the scope, safe-harbor language, and current payout ranges.
7. Response-time targets
By plan, weekdays, business hours in your account's timezone:
- Free — community support; we read everything, response is best-effort.
- Team — first response within 24 hours; resolution by severity.
- Business — first response within 4 hours; P1 has a 1-hour target.
- Enterprise — dedicated CSM, 24×7 P1 paging, custom SLA in your order form.