Getting started
Guide
Onboarding: first project → first signals
The minimal setup that gets CavBot watching real user journeys without over-instrumentation.
Find answers fast.
Operate with clarity.
This is the operational surface for CavBot: guides, troubleshooting, account help, and structured escalation. Search first, then use filters to move into the right lane.
A real path through support
A Help Center should feel like an operating map, not a wall of emails. Start with the guided path below.
Getting started
Onboard CavBot in three steps
This is the “first-success” loop: connect → mark routes → review signals. Keep it calm and measurable.
-
Step 01Guide
Connect your first project surface
Add CavBot to a single high-value flow so signals land in Command Center cleanly.
-
Step 02Routes
Build your route watchlist
Mark journeys that can’t fail: checkout, sign-up, and campaign landing routes.
-
Step 03Signals
Read signals, set escalation rules
Confirm what “good” looks like, then set alert thresholds that match your risk.
Browse topics
Topic routes
Open a card to get docs, examples, and the right support path.
Routes & 404s
Surface
404s as a product surface
How CavBot treats dead ends: route severity, referrers, and what “critical” means in production.
SEO structure
Signals
Structure alerts: what CavBot flags first
Title/description drift, canonical issues, crawl traps, and how CavBot summarizes structure risk.
Accounts & billing
Support
Invoices, receipts, and plan changes
Clean billing workflows for finance teams: receipts, invoices, PO notes, and subscription adjustments.
Security
Critical
Report a security concern
Responsible disclosure guidance: what to include, how to reproduce, and how we coordinate fixes.
Legal & privacy
Policy
Data requests & compliance
DPAs, privacy rights, and structured data requests (export / deletion). Keep it jurisdiction-clear.
Incidents
Escalation
Report a production incident cleanly
The fastest way to get help: route description, timestamps, what changed, and how to reproduce.
FAQs
Preview
Frequently asked questions
The FAQ is designed as a high-speed reference surface: short questions, precise answers, and language that maps directly to CavBot’s operating model (routes, watchlists, signals, and escalation thresholds).
Routing
Map
Not sure where it belongs?
Use the contact roadmap. It routes your message once, correctly — without duplicating emails across the page.
Contact roadmap
One map. Clean escalation. No duplicate loops.
This is where emails belong: a single routing surface at the bottom. Pick the lane once and move on.
General support Account access, console behavior, day-to-day questions.
Include: route (if relevant), timestamps, and a short “expected vs actual”.
Billing Invoices, receipts, plan changes, finance notes.
Include: org/workspace name, invoice ID (if available), and what you need (receipt, PO note, plan change).
Incidents Production issue on a critical flow. Escalation lane.
Include: route, time window, what changed, and reproduction steps. Keep it short and factual.
Pilots & engineering Structured pilots, rollout plans, instrumentation reviews.
Include: goal, route list, expected signals, timeline, and constraints.
Security Vulnerabilities, abuse, responsible disclosure.
Include: reproduction steps, affected surfaces, and any logs/screenshots you can safely share.
Privacy & legal Data rights requests, DPAs, contracts, compliance questions.
Include: jurisdiction (GDPR/CCPA), org name, and the exact request (export/deletion/DPA).
FAQs
CavBot FAQ preview
The FAQ is designed as a high-speed reference surface: short questions, precise answers, and language that maps directly to CavBot’s operating model (routes, watchlists, signals, and escalation thresholds). If a question requires account-specific review, security handling, or legal verification, route it through the contact map so it lands correctly once.