Embedding a chat widget on your site

Drop a Wally-powered chat widget onto any Builder site (or a third-party site) so visitors can ask questions, get instant answers, and convert into leads. The widget runs the same Wally pipeline as the in-product drawer — it just lives in the bottom-right of your public site.

To enable on a Builder site:
1. Builder → Sites → your site → Settings → Chat Widget
2. Toggle "Enable visitor chat"
3. Configure:
• Greeting message (e.g. "Hi! Ask anything about our services.")
• Personality — Standard, Concise, Sales-leaning, Support-leaning
• Lead capture — what to collect when a visitor seems interested (email, name, phone)
• Hours — always-on or only during business hours (with offline message after-hours)
4. Save → widget appears on your site within seconds

What the widget can do:
• Answer questions about your business using Wally's knowledge of your org (services, pricing, team, articles, recent events)
• Surface help articles you've made public on the site
• Collect leads — when a visitor signals interest, Wally asks for an email and the lead is created in CRM with full conversation history
• Book meetings — if the visitor wants to schedule, Wally hands off to your public booking page
• Escalate — visitors can request a human; the conversation becomes a Support Ticket

Embedding on a non-Turtini site:
• Builder → Sites → Settings → Chat Widget → "Embed elsewhere"
• Copy the snippet (single <script> tag with your org's widget ID)
• Paste before </body> on any HTML page
• The widget loads asynchronously — no impact on page load time

Costs:
• Visitor chat uses Claude Haiku, billed at the standard +15% chargeback
• Roughly 0.05 cents per typical exchange — visible on Account → Pay-as-you-go → Wally line
• Set a monthly cost ceiling under Settings → Billing → Spend Limits if you want a hard cap

Privacy + abuse:
• All visitor conversations are logged (Settings → Chat Widget → Conversations)
• Auto-flagged for prompt injection / abuse — flagged conversations end with a polite cutoff
• No PII other than email/phone/name (when offered by the visitor) is stored — everything else is conversation text
• Cookie consent: the widget respects your site's cookie banner; non-consenting visitors get an anonymous session that doesn't persist across pages