Get started in 10 minutes.

Sign up at /register as a Google Workspace admin. Unibox will request Gmail and Directory API scopes — these let us read mail through the shared mailbox and create aliases without manual admin-console steps.

Behind the scenes we run two flows: standard OAuth for the admin's user account, and domain-wide delegation for our service account so we can manage Workspace aliases.

From Settings → Aliases, add the addresses your customers already use — support@, billing@, hello@. Each alias is a forwarding address on one shared `inbox@` mailbox; teammates see only the aliases assigned to them.

Limits: Google allows up to 30 aliases per primary user. Beyond that, use Recipient Address Mapping (Workspace Admin → Routing).

From Team → Invite member, add each person by their Google account email. Any domain works — Gmail consumer accounts included. They'll sign in with their own Google credentials and see only the conversations addressed to their aliases.

Admins see everything; members see their assigned aliases plus threads they've been explicitly mentioned in (we record those automatically).

Open any thread to see the details rail. Apply tags from a workspace-wide library (Settings → Tags), set status (open / pending / resolved / closed), assign to a teammate, or drop an internal note that customers never see.

All actions are logged to the audit trail.

Settings → Workflows ships a visual builder for trigger → AI task → condition → action graphs. Today the executor fires on `reply_received` and via a manual 'Run on thread' button. Auto-fire on inbound mail is on the roadmap (Gmail Pub/Sub).

Press ? anywhere to see the full list. The basics: ↑/↓ navigate, Enter opens, R to reply, F to forward, C to compose, / to search, Esc to close, Cmd+Enter to send, Cmd+S to save draft.