Quickstart

Open /signup, create your account, and name the workspace after the team that owns the queue. Beamdesk uses the workspace name in internal routing labels, audit exports, and default notification copy.

Choose forwarding or widget. Forwarding is fastest for email teams: create a forwarding rule from your support mailbox to the Beamdesk inbound address shown during onboarding. The widget is better when your first test should happen from a website session.

For forwarding, send one test email from an address outside your company domain and wait for it to appear in the queue. For the widget, install the script snippet on a staging page and send a short message as a visitor.

Open AI Personas after onboarding and configure the default support persona. Start with a short role, a tone rule, two refusal rules, and the knowledge sources it may use.

A practical first persona says what the agent can answer, how it should sound, and when it must hand off. Add tool access only after the first knowledge-only answer looks correct.

Send a realistic customer question: a pricing question, order status question, refund question, or setup blocker. Avoid a synthetic "hello" test because it does not exercise knowledge retrieval, confidence scoring, or escalation rules.

In the inbox, inspect the ticket timeline. You should see the inbound message, classification, retrieved knowledge, drafted reply, confidence score, and any automation actions.

Create a narrow rule in Automations: when the default support persona answers with high confidence, no restricted topic is detected, and the customer does not ask for a human, send the reply and resolve after a short delay.

Run the rule in dry-run mode first. If the preview shows the correct reply, tag, and audit event, enable it for the test queue. Your first auto-resolved ticket should include a full audit trail and the exact knowledge sources used.