How long should a first onboarding take?
Most teams complete setup and first validated scan the same day when URL scope, ownership and alert recipients are defined upfront.
FAQ
Find concise answers to common product, rollout and operational questions from end-user and enterprise teams.
What this solves
Answers recurring operational questions quickly so teams can unblock themselves without waiting for manual support.
Who is this for
- •New users learning platform behavior
- •Operations teams validating rollout decisions
- •Stakeholders comparing plan and governance impact
Prerequisites
- •Identify your role and target workflow
- •Collect relevant project or run context
- •Use linked deep-dive pages for advanced cases
Step-by-step
1. Search by outcome
Start from the expected outcome (scan, alert, workflow, analytics) and read the matching FAQ cluster.
2. Validate with docs page references
Open linked runbooks for implementation detail and operational outputs.
3. Apply your plan context
Cross-check answer scope with plan availability and guardrails.
4. Escalate if unresolved
Use escalation path when your scenario is outside FAQ coverage.
Operational outputs
- •Faster self-serve resolution for common questions
- •Reduced repetitive support load for teams
- •Consistent answer language across departments
Plan availability
- •FAQ guidance applies across all plans
- •Feature-specific depth is linked through plan-aware docs pages
- •Enterprise-only surfaces are clearly marked in related pages
Limits and guardrails
- •FAQ is summary guidance, not a replacement for runbook details
- •Use troubleshooting flow for active incidents
- •Escalate for contract or compliance-specific requests
Expected outcome
- •Teams answer common questions without delay
- •Docs adoption increases through clear entry points
- •Support escalations become higher quality and lower volume
Troubleshooting paths
- •If answer is missing, jump to troubleshooting page
- •If answer depends on plan, review pricing & limits page
- •If answer depends on integration topology, review integration runbook
FAQ
Do we need separate tools for visual testing and analytics?
No. Crawlens supports both surfaces, but advanced analytics and operational depth are plan-dependent.
How do we reduce alert noise quickly?
Use smart grouping, threshold tuning and ownership mapping together. Troubleshooting page includes the decision sequence.
What should we validate before scaling scan volume?
Check queue lag trends, worker capacity policy, and baseline quality before increasing cadence or target scope.
Can we integrate CI triggers safely?
Yes. Use scoped credentials, idempotent trigger contracts and callback verification with retry handling.
How should we present results to leadership?
Share operational outputs: incident groups, trend deltas, SLO snapshots and decision logs with plan-aware context.
Escalation
Still blocked after FAQ review?
Contact the team with your scenario details and the pages already reviewed.