Leads & Handoff
Use lead capture and handoff together when visitors show buying intent, request pricing, ask to book time, or need direct follow-up.
Lead capture
When a visitor shows clear intent, the agent opens an in-chat lead form. Name and phone are required; email and a note are optional. Collected leads appear in Operations center → Customer leads.
Human handoff
The agent can escalate a conversation to your team — when the visitor asks for a person or when the request needs one. Handoff conversations land in the agent-side inbox at Operations center → Human handoff, where your team replies in real time.
The waiting policy is configurable per agent:
- Wait notice — a message shown while the visitor waits for a human to join.
- Timeout message — shown if no one joins in time, inviting the visitor to leave their question.
- Expiry — an inactive handoff request times out and the conversation returns to the AI agent.
Notifications
Configure per-agent notification channels in Settings → Notifications so your team hears about events immediately:
- Slack (connect via OAuth or an incoming webhook)
- Microsoft Teams
- WeCom, Feishu, DingTalk
- Generic webhook
Each channel subscribes to one or both events: Human handoff requested and Lead created.
Site webhooks
For your own integrations, add endpoints in Settings → Webhooks. siteaiagent delivers lead_created, human_handoff_requested, and conversation_ended events (plus a webhook_test event when you test an endpoint). Every delivery is signed with HMAC-SHA256: the X-SiteAiAgent-Signature header contains sha256=<hex digest> computed over <timestamp>.<body> with your endpoint secret, and the timestamp is sent in X-SiteAiAgent-Timestamp.