Getting started
HQ & workspaces, operator loop, operating context, and widget setup get the product aligned with how your business runs.
Docs
Documentation for the operator workspace — not just the widget.
HAL connects HQ, project Overview, Work, support, CRM, knowledge, API, and hosted HTTP MCP into one system for lean teams. Start with the concepts, then move into setup.
Start here
Understand the product model first, then configure the surfaces you need. HAL is strongest when support, sales, and Work share context instead of living in separate tools.
HQ & workspaces
See how account HQ, project Overview, and Work fit together.
Operator loop
Focus lanes, recommendation runs, approvals, and feedback.
Operating context
Goals, motion, constraints, and the metric HAL optimizes around.
Widget
Install the customer-facing widget and connect inbound signals.
Widget identification
Push known visitor, contact, company, and CRM context from your app.
CRM
Pipeline, company context, and founder-led sales activity.
REST API
Integrate HAL with your product and backend systems.
MCP
Connect external AI clients through HAL's hosted HTTP MCP endpoint.
Lifecycle email campaigns
Templates, triggers, delayed sends, and run reports through MCP.
Documentation map
Product areas
Support, help center, CRM, knowledge base, and team setup work better when they share context and feedback.
Platform access
REST API for integration, hosted MCP for AI clients, and lifecycle campaign tools for onboarding email.
Product boundaries
Human approval
The operator recommends, drafts, and organizes work. External actions stay approval-gated by design.
Start in one lane
You can begin with the widget, CRM, or Work alone. The loop strengthens as more surfaces connect.