FAQ
37 answers to what buyers ask.
Concept, onboarding, security, playbooks, knowledge base, channels, and common workflows — grouped by where you are in the buying journey.
Concept & positioning
- What is BeforeQuery?BeforeQuery is an agent platform grounded in your knowledge and your context. It answers employee and customer questions, runs playbooks across your systems, and shows the source paragraph plus the entity path that justified every action.
- How is BeforeQuery different from a traditional ticketing system?Coming in Phase 1.
- What kinds of requests is BeforeQuery designed to handle?Coming in Phase 1.
- What auto-resolution rate can I expect from BeforeQuery?Coming in Phase 1.
- How do we measure auto-resolution?Coming in Phase 2.
Onboarding & setup
- How do we get onboarded and ship our first live workflow?Coming in Phase 1.
- How do we add our first admin and operators to BeforeQuery?Coming in Phase 1.
- How do we build our first playbook?Coming in Phase 1.
- Is BeforeQuery a fit for startups?Coming in Phase 1.
- How does BeforeQuery scale to enterprise?Coming in Phase 3.
Playbook operations
- How do we write effective playbooks?Coming in Phase 1.
- How does BeforeQuery handle exceptions and edge cases?Coming in Phase 2.
- How do we run AI-first workflows with human escalation?Coming in Phase 2.
- How do we reduce escalations with tier-zero and tier-one automations?Coming in Phase 2.
- How does the auto-categorization schema work?Coming in Phase 2.
- How does BeforeQuery route requests automatically?Coming in Phase 2.
- How does BeforeQuery help with SLA management?Coming in Phase 2.
Security & access
- How does BeforeQuery enforce approvals and MFA?Every write action can be gated by an approval chain — one or more reviewers, a deadline, a step-up MFA challenge on the reviewer, and an automatic escalation if the reviewer is out. Read-only actions default to autopilot; destructive ones require MFA by default.
- How does BeforeQuery prevent unauthorized actions?Every write goes through an identity-bound action pipeline: the requester is verified through their chat platform's SSO, the action is checked against your approval matrix, a reviewer (or a fresh MFA challenge) must sign off, and only then does the write execute — with the entire chain logged.
- How does BeforeQuery secure integrations?Credentials are AES-256-GCM encrypted at rest and never rendered in a log or read back through the API. Every outbound URL is SSRF-checked at every redirect. Idempotency headers make retries safe. Optional per-workspace IP allowlists and BYO-VPC connectors for regulated buyers.
- How do we set up audit logs and review agent actions?Audit logs are on by default in every workspace — every action, approval, and credential change writes an immutable row. Review them in the dashboard's Reports → Audit & Access page, export via API on any tier, or ship to your SIEM on Enterprise.
- How does the BeforeQuery access model work?Coming in Phase 2.
- How do we manage access to sensitive workflows?Coming in Phase 2.
- How do we create an intake workflow for high-risk requests?Coming in Phase 2.
Knowledge base
- How does BeforeQuery automate knowledge base upkeep?Coming in Phase 1.
- How do we write knowledge articles BeforeQuery can use effectively?Coming in Phase 1.
- How does BeforeQuery unify IT and HR knowledge bases?Coming in Phase 3.
- How do connected apps, knowledge, and playbooks work together?Coming in Phase 2.
Workflow walkthroughs
- How does BeforeQuery resolve tickets end-to-end?Coming in Phase 2.
- How does BeforeQuery answer employee questions?Coming in Phase 2.
- How does BeforeQuery troubleshoot laptop and account access?Coming in Phase 2.
- How does BeforeQuery grant and remove app access?Coming in Phase 2.
- How does BeforeQuery handle lost-laptop reports?Coming in Phase 2.
- How does BeforeQuery manage Google Groups?Coming in Phase 2.
- How does BeforeQuery manage Slack channels?Coming in Phase 2.