Quick Actions

Quick actions are the primary interaction buttons displayed in the Beacon panel. Each action routes visitors to a specific destination — chat, a booking link, a community room, an external URL, or through a wallet verification gate.

Action Types

open_chat

Opens a chat interface for the specified lane (support, sales, or community).

{
  "id": "help",
  "label": "Get Help",
  "icon": "help",
  "lane": "support",
  "type": "open_chat"
}

book_call

Redirects to a calendar booking link. Only available for the sales lane.

{
  "id": "book-demo",
  "label": "Book a Demo",
  "icon": "calendar",
  "lane": "sales",
  "type": "book_call"
}

The booking URL is set in the handoff.calendar config section.

join_room

Joins a Dial community room by room ID. Only available for the community lane.

{
  "id": "community",
  "label": "Join Community",
  "icon": "users",
  "lane": "community",
  "type": "join_room",
  "roomId": "my-community-room"
}

open_link

Opens an external URL. Works with any lane.

{
  "id": "docs",
  "label": "View Documentation",
  "icon": "file",
  "lane": "support",
  "type": "open_link",
  "url": "https://docs.example.com"
}

verify_then

Triggers a wallet verification gate before proceeding to another action. This is lane-independent.

{
  "id": "verified-support",
  "label": "Verified Support",
  "icon": "shield",
  "type": "verify_then",
  "nextActionId": "help"
}

The nextActionId must reference another action’s id. After successful verification, that action is executed automatically.

See Verify with Dial for details on the verification flow.

Lanes

Each action (except verify_then) belongs to a lane — a category that determines how the action is grouped and routed:

Lanes must be enabled in the config for their actions to appear:

{
  "lanes": {
    "support": { "enabled": true, "label": "Support" },
    "sales": { "enabled": true, "label": "Sales" },
    "community": { "enabled": false, "label": "Community" }
  }
}

Action Properties

Limits

A maximum of 5 quick actions can be configured per project.

Analytics

When a user clicks a quick action, a quick_action_clicked event is fired with the action ID in the metadata. See Analytics for details.