Back to Use Cases
AI Suite

Bot & Flows

Visual automation builder

Used byAutomation & AI

Visual builders that turn your docs and channels into working AI bots, forms, and IVRs.

Bot & Flows is the AI Suite's visual automation studio: three React-Flow builders (Bot Flow for AI agents, Keyword Flow for WhatsApp forms, and Call Flow for voice IVR) that you assemble from typed nodes instead of code. It solves the problem of shipping reliable, grounded conversational automation across chat, voice, and social channels without an engineering project for every change. A RAG knowledge base, an If-Condition and User-Approval logic layer, HTTP and MCP integration nodes, and a built-in chat and voice simulator let teams design, test, and bind bots to nine channels from one canvas.

8 use cases

Documented use cases

01

RAG Support Agent Grounded in Your Own Docs

Customer support lead
Problem

Frontline support drowns in repetitive how-do-I questions while the answers already sit in help docs and PDFs. Generic chatbots either parrot scripted FAQs or hallucinate confident-but-wrong answers, which erodes trust and forces agents to clean up afterward. Keeping a bot's knowledge current with every documentation edit becomes its own manual chore.

How BOL7 solves it

In the Bot Flow builder, wire an AI Agent node to a Chat Model and a Vector Database node backed by the RAG knowledge base, which ingests content via URL crawl, sitemap, file upload, or Google Drive. A Guardrails node keeps responses on-policy so the agent answers strictly from your sourced material rather than improvising. Re-crawl or re-upload to refresh the knowledge base whenever docs change.

Outcome

Customers get accurate, source-grounded answers around the clock, and agents are freed to handle the genuinely complex cases instead of repeating documentation.

RAGSupportAI AgentKnowledge base
02

Branch the Conversation on What the Customer Says

Conversation designer
Problem

A one-size-fits-all bot script treats a refund request, a sales question, and an angry complaint identically, which frustrates customers and buries the right path. Without branching, teams end up maintaining several near-duplicate bots or routing everything to humans by default. The result is slow resolution and inconsistent handling.

How BOL7 solves it

Drop an If-Condition node into the flow to read the customer's reply or a captured variable and split the path accordingly, sending each branch to its own AI Agent, message, or downstream node. Because branching lives on the same canvas, designers can see and adjust every route visually instead of editing code.

Outcome

Each customer is steered down the path that actually fits their intent, so conversations resolve faster and feel personal rather than scripted.

BranchingIf-ConditionRouting
03

Human Sign-Off Before Sensitive Actions

Operations manager
Problem

Fully automated bots that issue refunds, change accounts, or send commitments are a liability when they get an edge case wrong. Most teams react by disabling automation entirely for anything risky, which throws away the speed benefits on the very workflows that need them most. The alternative, hoping the bot never errs, is not a control anyone can sign off on.

How BOL7 solves it

Insert a User-Approval node at the decision point so the flow pauses and routes the proposed action to a human for review before it executes. Combine it with an If-Condition node so approval is only required above a chosen threshold, keeping low-risk paths fully automated. The rest of the flow continues automatically once a person approves or rejects.

Outcome

Teams keep automation on the fast paths while a human stays in the loop for anything sensitive, satisfying compliance without grinding everything to a halt.

ApprovalsGovernanceCompliance
04

Keyword-Triggered WhatsApp Lead-Capture Form

Demand-generation marketer
Problem

Leads who message a brand on WhatsApp expect to be qualified right there, but static reply templates can't collect structured details, and pushing people to an external web form bleeds drop-offs. Worse, prospects who start answering and wander off are simply lost, with no way to bring them back. Marketing ends up with thin, half-captured records.

How BOL7 solves it

Use the Keyword Flow builder to launch a WhatsApp form the moment a customer sends a chosen keyword, collecting fields conversationally inside the chat. A resume-if-abandoned prompt re-engages people who started but didn't finish, so partial sessions are recovered rather than discarded.

Outcome

More inbound WhatsApp interest converts into complete, structured lead records, and prospects who stall get a nudge instead of slipping away.

WhatsAppLead captureForms
05

One Flow, Bound to WhatsApp, Instagram, and Telegram

Conversational marketing lead
Problem

Customers reach out on whichever app they already use, so brands feel pressured to maintain a separate bot per channel. That means triple the build effort and answers that drift out of sync as each copy is edited independently. Inconsistency across channels makes the brand look disjointed.

How BOL7 solves it

Build the conversation once in Bot Flow and attach multiple Trigger nodes to bind it to WhatsApp, Instagram, and Telegram (and other supported channels) from the same canvas. The channel binding spans WhatsApp, Telegram, Instagram, Discord, Facebook, SMS, Email, RCS, and a generic webhook, so one source of truth serves them all.

Outcome

Customers get the same quality of experience on every channel they prefer, and the team maintains a single flow instead of several diverging copies.

Multi-channelWhatsAppInstagramTelegram
06

Inbound IVR with Voicemail Detection and Queue Transfer

Contact-center manager
Problem

Legacy phone trees are rigid, expensive to change, and frequently strand callers when no agent is free. Calls that hit an unattended line either ring out or get no graceful fallback, so the caller's intent is lost entirely. Reworking the menu usually means a ticket to a telecom vendor and a wait.

How BOL7 solves it

Use the Call Flow builder to design an inbound IVR visually, with a node to detect voicemail, an option to transfer callers into a queue, and a path to capture a voicemail when no one can take the call. The WhatsApp Call and HTTP nodes are available on the same canvas to extend the voice experience further.

Outcome

Inbound callers are routed intelligently and never hit a dead end, while the team adjusts the IVR itself instead of filing a request and waiting.

IVRVoiceCall routing
07

Simulate, Inspect Traces, and Ship with Confidence

QA and conversation tester
Problem

Pushing an untested bot to live customers is how brands discover broken branches and bad answers in production, in front of real users. Reproducing what went wrong is hard when there's no record of how the bot reasoned through a conversation. Teams either over-test manually or cross their fingers at launch.

How BOL7 solves it

Use the built-in chat and voice simulator to run the flow as a chosen persona and language before publishing, exercising every branch safely. Trace logs show the path the bot took step by step, and you can copy them for sharing or debugging, so issues are caught and documented prior to go-live.

Outcome

Bots launch already validated against realistic personas, and when something needs fixing the trace makes the cause obvious instead of a guessing game.

SimulatorTestingTrace logs
08

Call an External API Mid-Conversation and Branch on the Result

Automation engineer
Problem

A bot that can't reach your systems is just a brochure: it can't check an order status, validate a customer, or look up live data. Bolting that integration on usually means a custom service and a developer in the loop for every new call. That dependency slows down every iteration.

How BOL7 solves it

Drop an HTTP Request node into the flow and import an existing cURL command to configure the call in seconds, then feed the response into an If-Condition node to branch on what the API returns. For richer integrations, MCP and Web Search nodes are available on the same canvas to bring external tools and live results into the conversation.

Outcome

Bots act on real data from your own systems and react to it in the moment, so automation extends end to end instead of stopping at the edge of the chat.

HTTPAPIIntegrationcURL