Widget Setup
Write compelling greeting messages
Write compelling greeting messages
Greeting messages appear above the bubble before the user opens the chat. Make them:
- Specific: “Questions about our pricing plans?” beats “Need help?”
- Action-oriented: Tell users what you can help with
- Brief: 1-2 sentences max per greeting card
- Varied: Use 2-3 different greetings to avoid repetition
Choose the right auto-open timing
Choose the right auto-open timing
Auto-open shows the chat frame automatically after a delay:
- Don’t auto-open on landing pages — let users explore first
- Auto-open on support/help pages — users are already looking for help
- 5-10 seconds is a good default delay
- Disable for mobile — screen space is limited, let users choose to open
Use SSO for logged-in users
Use SSO for logged-in users
If your site has authentication, use SSO to identify users:
- Agent can greet them by name
- Conversation history persists across sessions
- Support team sees who they’re talking to
- See SSO setup guide for implementation
Match your brand
Match your brand
The widget inherits your agent’s branding:
- Accent color: Set in Branding → Design. Use your primary brand color.
- Avatar: Upload a recognizable icon or team photo
- Bubble icon: Choose from 16 icons or use your avatar
- Position: Bottom-right works for most sites. Use bottom-left if you have a conflicting element.
Messaging
Be specific, not generic
Be specific, not generic
❌ “Need help?”
✅ “Having trouble with payment? I can help!”❌ “Click here for support”
✅ “Stuck on this step? I can walk you through it.”
Match your brand voice
Match your brand voice
If your brand is:
- Professional: “Need assistance with checkout?”
- Friendly: “Hey! Can I help with that?”
- Technical: “Encountering an issue? Let’s debug together.”
Invite, don't pressure
Invite, don't pressure
✅ “Questions about pricing? I’m here.”
❌ “Don’t leave! We need you!”✅ “Happy to walk you through setup.”
❌ “Sign up now or miss out!”
Training Your Agent
Include relevant knowledge
Include relevant knowledge
Your agent should know:
- Product features and pricing
- Common issues and solutions
- Policies (shipping, returns, refunds)
- Technical documentation
Write clear agent instructions
Write clear agent instructions
Instructions should:
- Define the agent’s role and tone
- State what it should and shouldn’t answer
- Explain when to hand off to a human
Test with real scenarios
Test with real scenarios
Before deploying, test:
- Common user questions
- Edge cases
- Error scenarios
- Various context combinations
Analytics & Optimization
Track key metrics
Track key metrics
A/B test variations
A/B test variations
Test variations of:
- Greeting messages
- Conversation starters
- Auto-open vs manual open
- Open style (normal vs dock)
Iterate based on data
Iterate based on data
- Low opens: Greetings aren’t compelling, or the bubble is easy to miss
- High opens, low resolution: Agent needs better training
- Long conversations: Add the missing answers to your knowledge base
Common Mistakes
- Auto-opening on landing pages - Let users explore first
- Generic greetings - “Need help?” is forgettable
- Blocking the page - Never prevent users from continuing
- Untrained agent - Answer quality depends on your knowledge base
- Ignoring mobile - Test on all devices
- No analytics - You can’t improve what you don’t measure
Checklist
Before launching, verify: Widget:- Accent color matches your brand
- Greeting messages are specific and helpful
- Auto-open timing is appropriate (or disabled)
- SSO configured for authenticated users
- Works on mobile devices
- Position doesn’t conflict with other page elements
- Trained on relevant product and support content
- Instructions define tone and escalation rules
- Tested against common questions and edge cases
- Legal/privacy requirements are met
Next Steps
Quickstart
Set up your first widget
Use Case Guides
Real-world implementations