Lead capture
Require contact details before chat starts, or collect them naturally during the conversation. Your team always has the info they need to follow up.
Choose how to collect visitor information. Enable a pre-chat form to turn every conversation into a lead — visitors provide their name, email, or phone before the chat begins. Or let the AI collect details naturally during the conversation when human follow-up is needed. Either way, your team always has the contact info they need.
Require name, email, or phone before chat starts. Every conversation becomes a lead your team can follow up on.
The AI collects contact details contextually during escalation — less friction for visitors who just need a quick answer.
Visitors who already provided their details go straight to chat. No repeated forms, no friction.
Every captured contact becomes a persistent profile linked to their conversation history. Teams can review what a returning visitor discussed previously, avoiding repeated questions and providing more personalized support. Custom fields and external IDs let you map contacts to records in your own systems.
New contacts are created automatically when details are captured, and existing profiles are updated with each subsequent interaction.
View every past conversation a contact has had, including outcomes, sentiment, and escalation records, from a single profile view.
Store your own customer identifiers and business-specific metadata on contact records for seamless cross-system alignment.
When the AI determines a conversation needs human attention, it routes to an available operator or falls back to a leave-a-message form. The escalation includes the reason, a conversation summary, and any contact details collected during the exchange. This eliminates the back-and-forth that typically follows a blind transfer.
Every escalation records why the AI escalated, giving agents immediate context about the customer's need before they respond.
A generated conversation summary accompanies the escalation so agents can prioritize and respond without reading the full transcript.
Name, email, and any custom fields collected during the conversation travel with the escalation request automatically.
Keep capture practical: collect only what is needed, attach it to contact history, and pass clean context into escalation.
Use pre-chat forms for guaranteed capture, or let the AI ask when follow-up is needed.
Focus on essential contact fields to reduce drop-off and friction.
Ensure escalation and contact records include enough context to act quickly.
Pricing
Unlimited conversations. 10 seats. No credit card needed. Upgrade when you're ready — paid plans from $49/mo. Learn more about the free plan →
For teams who want live chat on their site. Your first shared inbox.
Key features included:
Unlimited live chat
Answer your customers directly, no conversation limits.
For small teams launching AI support across web chat and WhatsApp with a shared inbox and grounded answers.
All the Free features, plus:
AI-Assisted support
AI answers from your knowledge base, grounded in your docs.
For teams running support across web chat and WhatsApp with analytics, AI insight, and knowledge operations.
All the Starter features, plus:
Advanced analytics
Sentiment, resolution tracking, and knowledge gap insights.
For larger teams that need higher volume, broader workspace coverage, and deeper support operations tooling.
All the Growth features, plus:
Priority operations
High-volume support with dedicated onboarding and priority support.
FAQ
Name, email, and phone. You can require any combination via the pre-chat form, or let the AI collect details during conversations. Learn more
Contacts are available in the Contacts section with linked conversation history and summary metrics. Learn more
Escalation requests can include contact details and a conversation summary so agents can continue without repeated questions. Learn more
Unlimited conversations. 10 seats. Live chat, shared inbox, contacts, knowledge base, and AI — all included. Free forever, no credit card.