Product · Team

Collaboration that stays quiet.

HAL's team features exist so customers never feel the seams: no double replies, no lost context, no "wait, who owns this?"

Members and roles

Invite teammates from Settings → Team by email. Roles control what each member can change; per-user project permissions control which projects and areas (support, sales, knowledge, settings) they can work in. Seat limits scale by plan — see pricing.

Ownership in the inbox

Assignment — route conversations to a person or team; auto-assignment can distribute by availability.
Snooze — park a conversation until it's actually answerable; it returns to the assignee when due.
Internal notes — @mention a teammate for context without the visitor ever seeing it.
Presence — availability status shows who's actually picking up.

A setup that scales

One project per product or brand — widget, KB, pipeline, and team permissions are project-scoped.
Default assignment to a team, not a hero — coverage survives vacations.
Notes before escalations — a three-line note beats forwarding threads.

HQ for founders

Running several projects? HQ rolls every workspace up to one view: which project needs attention first, aggregated focus, and per-project health. Founders see the whole operation without living in each inbox.

Notifications that respect attention

Email and push are debounced and preference-driven: new visitor messages, note mentions, unsnoozed conversations, and AI priority escalations. Each can be toggled per user (dashboard, Settings → Notifications; iOS app mirrors the same preferences). High/urgent AI-priority escalations can push straight to your phone.

API

GET    /api/team                  # members
POST   /api/team/invitations      # invite
PATCH  /api/team/users/{id}/role  # change role
DELETE /api/team/users/{id}       # remove