4.6

Your no-code chatbot builder.

Most questions answered, the rest routed to the right person.

Kai Support answers from your knowledge, buttons collect the details, and every other conversation reaches the right teammate.

7 days free. No credit card needed.

Trusted by 4,500+ teams

  • A visual canvas

    Connect messages, data collection and routing without code.

  • Kai Support answers

    A Let Kai answer step replies from your help center, snippets and files.

  • Routed to a person

    An assignment step hands the ticket to your team with its customer context.

  • Draft until published

    Run a draft in your messenger and inspect it before rollout.

Start from a use case.

Book demos in your messenger, ask for feedback after a ticket closes or collect bug details first.

Start free trialPick a use case. Make the steps your own.

Build the conversation path.

A no-code chatbot builder connects messages, data collection and routing on a visual canvas, without writing the conversation logic in code. In Gleap, a Let Kai answer step replies from your help center, snippets and files, and an assignment step hands the rest to your team. Workflows are available on every Gleap plan, from $29 a month billed annually.

  • Choose the starting event

    Start on a conversation event, for the channels and audience you set.

    See live chat
  • Answers from your knowledge

    A Let Kai answer step replies from your help center, snippets and files, with the sources listed.

    Meet Kai Support
  • Hand-off with a summary

    Questions Kai Support cannot answer go to your team.

  • Route to your team

    An assignment step hands the ticket over with its customer context.

    See the shared inbox

“If they want AI chatbot functionality combined with a knowledge base and ticketing system, all integrated, then Gleap is for them.”

Peter Müller System Engineer & Head of Support, Lywand. Lywand's AI support was trained on its product documentation, with teammates handling complex follow-ups.

50%

Lywand's customer inquiries resolved by AI chat

Read Lywand's story

Pricing

Plans from $29 a month.

Hobby

$29per month, billed yearly

For one person.

  • 1 seat, 1 project
  • Live chat and inbox
  • In-app bug reporting
  • Kai Support and Kai Copilot
Start free trial

Growth

$99per month, billed yearly

For a support team on every channel.

  • 4 seats included
  • Every channel and integration
  • Help center, roadmap and surveys
  • Investigations and Kai Code
Start free trial

Pro

$299per month, billed yearly

Everything in Growth, plus control.

  • Unlimited seats
  • Advanced reports
  • SLA policies and custom roles
  • LLM model choice
Start free trial

7-day free trial. No credit card needed.Compare all features

Questions

About support workflows

What is a no-code chatbot builder?

A no-code chatbot builder lets you connect messages, data collection and routing without writing the conversation logic in code. Gleap adds Kai Support for answers from your product knowledge, and routed tickets reach your team in the shared inbox.

Which plan includes workflows?

Workflows are available on every Gleap plan. A Let Kai answer step costs the same as Kai Support, about $0.05 per conversation (estimate).

Escalating a conversation for Kai Support to investigate, or passing it to a custom agent, needs Growth or higher. See Gleap pricing.

Do I need to write code?

No. You build conversation workflows in the visual editor. Custom API actions and starting a workflow from your own application may need developer setup. The available action types are listed in the workflow action guide.

Can I build an FAQ chatbot with Gleap?

Yes. Start a workflow on new conversations, add Buttons for your most common questions and a Let Kai answer step, and Kai Support answers frequently asked questions from your help center, snippets and files, with the sources listed.

Questions it cannot answer go to your team through an Assign ticket step. Unlike a scripted FAQ bot, Kai Support writes each answer from the matching content, so newly published help articles are used without editing the flow.

See Kai Support, the AI support agent. Shops use the same setup as an AI chatbot for ecommerce, with order lookups from Shopify or WooCommerce.

What can start a workflow?

Supported triggers include conversation start, ticket creation, reopening or closure, status changes, customer or agent comments, and no-response conditions. You can also start a workflow manually through the SDK. Set the channel, audience, and priority for the intended use case.

Can I test a workflow before publishing?

Yes. Save and run the draft as a guest or selected contact, then inspect the execution timeline. The test creates a real conversation in your messenger, so use test data and check each branch.

Does saving a workflow make it live?

No. A workflow remains a draft until it is published. Run it in the messenger and inspect its execution before rollout.

All 13 questions
Can multiple workflows use the same trigger?

Yes, but overlapping published workflows can compete. For triggers that select one workflow, the highest priority wins; equal priorities can produce an unpredictable choice. Review the editor’s conflict warnings and test the intended path.

How do workflows differ from custom agents?

A workflow follows the actions and conditions you define. A custom agent, on Growth and up, uses instructions and configured tools for a task, and can also use an existing workflow as a tool.

From Growth, Kai Support itself can use tools your team adds, such as API calls and MCP servers. Choose based on the task, and keep access and consequential actions within your team’s intended scope.

Can a workflow call an API or send data to an integration?

Yes. The editor includes custom API and integration actions.

Configure the connection and inspect the result for your specific system. An available integration does not mean every action in that system is automatically enabled.

See the integration directory.

Who controls API access?

Your team configures the endpoint, authentication and data used by a custom API action. Enable only the access the workflow needs and test the response before publishing.

How do workflows connect to self-driving development?

A support workflow can collect the context that starts a broader product improvement. Self-driving development connects customer signals to investigation, reviewable changes and follow-up.

Does a chatbot workflow automatically ship code?

No. A chatbot workflow defines conversation actions. Kai Code handles coding sessions and reviewable pull requests as a separate part of the customer feedback loop.

Most questions answered.

The rest with the right person.

7 days free. No credit card needed. 4.6

Book a demo

See Kai answer your own customers' questions, live.

Talk to us

Pricing

Plans, seats and what AI costs, on one page.

See pricing