Chatbot Templates for Lead Generation, Support, Booking, and E-Commerce

Most business chatbots solve the same handful of problems: capture a lead, answer a support question, book an appointment, or rescue a sale. You do not need to invent a flow from scratch for each one — you need a reusable template you can adapt. A chatbot is essentially an interactive flowchart, so the same logic applies every time: a clear entry point, a sequence of choices, and no dead ends. This guide breaks down four proven templates by use case, with the conversation steps and the kind of prompts that make each one work, so you can copy the structure and fill in your own details.

A note on designing flows

Before the templates, one principle ties them together. Sketch the flow before you build it — pen and paper first — and make sure every path leads somewhere. The most common chatbot failure is a conversation that runs into a wall: an option with no response, a question with no follow-up. Keep each flow simple and single-purpose; if it sprawls, split it into separate flows rather than cramming everything into one. Use consistent prompts, offer quick-reply buttons where choices are finite, and always give the user an escape hatch to a human. With that foundation, the templates below become reliable rather than brittle.

Lead generation template

A lead-gen bot trades a small bit of value for contact details, conversationally, without feeling like a form. The art is collecting data in a way that does not detract from your brand — natural tone, one question at a time, and a clear reason the visitor should answer.

The rule of thumb: ask for the email only after you have given a reason to share it.

Customer support template

A support bot exists to resolve common questions instantly and around the clock, escalating anything it cannot handle. It improves trust precisely because it is available at any hour.

• Open with scope: tell the user what the bot can help with so they do not ask the impossible.
• Offer top topics: surface your most common questions as quick replies — billing, shipping, account.
• Answer or search: pull the answer from your knowledge base; never invent one.
• Confirm resolution: ask "Did that solve it?" to capture a real resolution signal.
• Escalate cleanly: if unresolved, hand off to a human with the full transcript attached.

The escalation path is not optional — it is what keeps the bot from trapping a frustrated user.

Booking and appointments template

A booking bot turns interest into a scheduled commitment. It works best when it connects to a real calendar and shows live availability rather than promising to "get back to you."

The reschedule and reminder steps quietly do the most work, because they reduce no-shows and the support tickets that follow them.

E-commerce template

E-commerce bots earn their keep at two moments: helping shoppers find the right product, and recovering carts that are about to be abandoned. A classic cart-recovery flow detects the user leaving the page and reminds them what is in the basket, sometimes with an incentive.

• Product finder: ask a few preference questions, then recommend matching items.
• Order status: let returning customers check shipping without a human.
• Cart recovery: nudge a leaving visitor about basket items, optionally with a discount.
• Post-purchase: confirm the order and offer related items or support.

Match the incentive to the margin — a discount that recovers the sale should not erase the profit it was meant to protect.

Bottom line

You rarely need a bespoke bot; you need the right template, adapted. Lead-gen earns contact info conversationally, support resolves and escalates, booking turns interest into a calendar slot, and e-commerce finds products and recovers carts. Sketch the flow first, kill every dead end, and keep a human handoff one tap away. Start from one of these structures, swap in your own prompts and integrations, and you will ship something useful far faster than building blind.

Sources and further reading