Use cases
Most teams start with one of these setups and add more bots later. Each setup lists what to add and where to start.
Customer support
Answer common questions from your help content, and bring in a person when a visitor asks for one.
- Knowledge: help center pages, a sitemap, or support PDFs. See Source types.
- Actions: Live chat so the bot can offer a conversation with your team, and Suggested messages to guide visitors to common topics.
- Channels: Chat bubble on your site, or a Help page as a dedicated support page.
- Your team: agents answer handed-off chats in the Live chat inbox.
If you use Fluent Support, the Fluent Support channel drafts replies for your agents inside the help desk.
Pre-sales questions
Answer questions about plans and features on your marketing pages, and collect details from interested visitors.
- Knowledge: pricing, feature, and comparison pages.
- Actions: Collect data or Custom form to send a visitor’s details to your webhook, and Custom button to link to a demo or contact page.
- Channels: Chat bubble or Center stage.
Product documentation
Help users find answers across your docs, with links to the pages each answer used.
- Knowledge: your docs site as a Crawl or Sitemap source with a refresh schedule.
- Channels: Help page or Chat bubble.
- Improve over time: review Content Gaps and Document Usage to find missing or unused content.
WordPress stores and bookings
On a WordPress site connected through the FluentChat plugin, a bot can help with products and appointments.
- Integration: WordPress integration.
- Actions: FluentCart for product questions and FluentBooking for appointments. Each page lists exactly what the action can and can’t do.
Signed-in customers
Recognize visitors who are already signed in to your site or app.
- Developers: pass a signed token to the widget with Identity verification, or build the bot into your own app with the REST API.
- Actions: the Fluent Support tickets action can help customers with their own tickets on your WordPress site.
Running several bots
Bots in a team share the Knowledge Base, members, and billing. Each bot has its own knowledge selection, instructions, actions, channels, conversations, and analytics. A common pattern is one bot per product, each limited to that product’s sources.
Next steps
- Quick start: build and publish your first bot.
- Actions: see everything a bot can do beyond answering.
- Channels: choose where people reach your bot.