How to Open an AI Chatbot From a Button on Your Website
Why every visitor gets the same hello
Your website already tells you what a visitor wants. Someone who clicks "Get a quote" wants a quote. Someone who clicks "Pricing help" in the footer wants to understand your plans. Yet most chat bubbles open with the same welcome message whichever button was pressed, and the visitor has to explain again what they just told you with their click.
The usual workaround is a separate form or page for each purpose. That sends the visitor away from the page they were on, and the answers end up in different inboxes. A chat that starts from the right place keeps them where they are and keeps the conversation in one list.
AI Chatbot lets any button open the chat with a reason. You decide, reason by reason, what the chatbot says first, which buttons it shows, whether a card with choices appears under its first answer, and what it should keep in mind while it talks to that visitor.
Why this happens
- the chat bubble is the only way in, so every visitor starts with the same generic welcome message.
- the reason a visitor opened the chat is lost, so the chatbot asks what the button already said.
- a button opens a contact form on another page instead of the chat.
- the greeting is written once for the whole website and fits no page in particular.
- nobody can tell afterwards which button a conversation came from.
Biznsbook addresses this through data-cw-open buttons and links, Launch rules per reason, greeting, buttons and an offer card, a private instruction for the chatbot in AI Chatbot, an AI chatbot for your website or app that is sold on its own and needs no other Biznsbook app.
Unanswered website questions rarely show up in a report. They show up as visitors who left and bought elsewhere. Answering from your own content, and passing the visitor to a person when needed, closes that gap.
Step-by-step: Open an AI Chatbot From a Button on Your Website
Written for owners, marketers and support teams in small and mid-sized businesses. The steps follow AI Chatbot in Biznsbook.
- Choose a reason. Pick a short name for why the button opens the chat, for example get_quote or pricing_help. Use 1 to 40 lower-case letters, digits, underscores or hyphens. The same name is used on the button and in the launch rule.
- Add the attributes to the button. Add data-cw-open and data-cw-intent="get_quote" to the button or link. Optionally add data-cw-source with a label for where the button is, and data-cw-data with a few extra facts as JSON, for example {"plan":"pro"}. Developers can call BiznsbookChat.open({ intent: "get_quote" }) instead.
- Keep a normal link as the fallback. Give the button a normal href. If the chat is not available on that page, the link works as an ordinary link.
- Add a launch rule. Open AI Chatbot, Settings, Launch rules, and press Add rule. Enter the same reason as on the button.
- Write what happens. Write a greeting of up to 400 characters that replaces the welcome message. Choose up to three buttons from the Actions tab, an optional offer card from the Offer cards tab, and an optional instruction of up to 300 characters that visitors never see.
- Save and test. Press Save settings. Settings changes reach your website within 5 minutes. Click the button as a new visitor and check the greeting and buttons, write a first message, and check the card under the answer.
- Add an automation if you want one. With Business Automation, the Chatbot Opened From a Button trigger starts a workflow on the visitor's first message. A ready template, Chat bot: tell the team when a visitor starts from a page button, emails your team.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Inside Biznsbook, open AI Chatbot: the chatbot Dashboard shows a short checklist until the chatbot is live. This article explains the process behind those screens.
Common mistakes to avoid
- Mistake 1: The chat bubble is the only way in, so every visitor starts with the same generic welcome message. Repeating this each month usually shows up first in visitors who asked and left without an answer.
- Mistake 2: The reason a visitor opened the chat is lost, so the chatbot asks what the button already said. Repeating this each month usually shows up first in visitors who asked and left without an answer.
- Mistake 3: A button opens a contact form on another page instead of the chat. Repeating this each month usually shows up first in visitors who asked and left without an answer.
- Mistake 4: The greeting is written once for the whole website and fits no page in particular. Repeating this each month usually shows up first in visitors who asked and left without an answer.
- Mistake 5: Nobody can tell afterwards which button a conversation came from. Repeating this each month usually shows up first in visitors who asked and left without an answer.
Each of these shows up in Conversations or Leads. Fix it in the chatbot's knowledge or settings, publish, and check the next week's conversations.
Best practices that hold up as you scale
- Choose a reason — Pick a short name for why the button opens the chat, for example get_quote or pricing_help.
- Add the attributes to the button — Add data-cw-open and data-cw-intent="get_quote" to the button or link.
- Keep a normal link as the fallback — Give the button a normal href.
- Add a launch rule — Open AI Chatbot, Settings, Launch rules, and press Add rule.
- Write what happens — Write a greeting of up to 400 characters that replaces the welcome message.
Give one person the job of reading new conversations, unanswered questions and leads every day, and publish the fixes the same week.
How Biznsbook supports this workflow
data-cw-open buttons and links is part of Biznsbook AI Chatbot. It works from the knowledge you publish, so you decide what the chatbot says, and every conversation, lead and live chat stays linked in one place.
Launch rules per reason is part of Biznsbook AI Chatbot. It works from the knowledge you publish, so you decide what the chatbot says, and every conversation, lead and live chat stays linked in one place.
greeting, buttons and an offer card is part of Biznsbook AI Chatbot. It works from the knowledge you publish, so you decide what the chatbot says, and every conversation, lead and live chat stays linked in one place.
a private instruction for the chatbot is part of Biznsbook AI Chatbot. It works from the knowledge you publish, so you decide what the chatbot says, and every conversation, lead and live chat stays linked in one place.
AI Chatbot runs on its own, on the same plans as every Biznsbook app: Starter $19 a month (1 chatbot), Pro $39 (2 chatbots, with CRM and Bookings) and Business $89 (5 chatbots, your own branding). Access is permission-based: AI Chatbot Manager covers everything in AI Chatbot, AI Chatbot Agent covers live chat, conversations and leads, and Company Admin keeps full access.
Suggested implementation timeline
- Day 1: Choose a plan, create the chatbot and set up data-cw-open buttons and links.
- Week 1: Publish your main knowledge sources and test with the questions customers ask most.
- Week 2: Put the chatbot live on your website and read every conversation for the first days.
- Month 1: Add answers for the questions it could not answer, and tune intents, buttons and the lead form.
- Ongoing: Reviewing your launch rules each month.
Choosing reasons that stay useful
A reason names the visitor's purpose, not the page or the button. get_quote and pricing_help are good reasons because the same purpose can have several buttons: a header link, a product page button and a footer link can all send get_quote and use one launch rule. Use the optional source label to tell the buttons apart later, for example header, product-page or footer.
Keep the list short. Start with the two or three purposes that matter most, such as asking for a quote, getting help choosing, and booking, and add more once you see which buttons visitors really use.
Writing a greeting that fits the button
The greeting replaces the welcome message, so it should answer the question the click already asked. For get_quote it can say you can help with a quote and ask what the visitor needs. For pricing_help it can ask what they want to run and how many people will use it. Keep it to a sentence or two; the limit is 400 characters.
Choose the buttons that make sense as the next step, such as booking a visit or calling you, and keep to the three allowed. An optional offer card from your Offer cards tab shows choices from your own system under the answer to the visitor's first message, and the chatbot keeps that answer to a sentence or two and points to the card.
The instruction is for the chatbot, not the visitor. Use it to say what to ask first or what to offer, for example to ask what kind of business the visitor runs before suggesting anything. It follows your house rules and never overrides the chatbot's safety rules.
What the visitor and your team see
The visitor clicks the button and the chat opens with your greeting and the buttons you chose. They write a first message and get an answer written with the reason in mind, and the offer card if you attached one. Nothing about the reason is shown to them.
Your team sees Opened from on the conversation, and the reason travels with the lead when the visitor leaves their details. If you use Business Automation, the Chatbot Opened From a Button trigger starts a workflow on the first message, once per conversation and reason, with the reason, the button location, the extra details, the first message, the page and a link to the conversation.
Metrics to track monthly
- Conversations and AI answers this month, against your plan
- Questions it could not answer, and how many now have an answer
- New leads, and leads still to follow up
- Live chats accepted, and visitors asked for details instead
- Buttons visitors pressed, by button
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Contact forms and guesswork vs AI Chatbot
Compare a typical website without a chatbot, or with a generic one, with Biznsbook AI Chatbot and data-cw-open buttons and links.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Where the visitor starts | ❌ The same generic bubble for every button | ✅ The button that was pressed opens the chat with its own reason |
| First message | ❌ One welcome text for the whole website | ✅ A greeting per reason, replacing the welcome message |
| Next steps offered | ❌ Whatever the visitor asks for | ✅ Up to three buttons and an optional offer card for that reason |
| Guidance for the chatbot | ❌ None for a specific page | ✅ A private instruction per reason that visitors never see |
| Knowing where it came from | ❌ Guesswork | ✅ Opened from on the conversation, and with the lead |
| If the chat is unavailable | ❌ A dead button | ✅ The link works as a normal link |
Reviewing your launch rules each month
Once a month, open the dashboard and check which reasons visitors actually use. Rewrite the greeting for any reason where visitors do not reply, add a rule for any reason marked no rule, and retire buttons nobody presses.
Write the routine down so whoever covers holidays knows who reads leads and conversations, and how quickly they reply.
Frequently asked questions
Do I need a developer to add the button?
Usually not. Add data-cw-open and data-cw-intent to a button or link in your page template. Developers can also call BiznsbookChat.open with an intent from their own script.
What happens if the chat is not available on the page?
The button works as an ordinary link to its href, so keep a normal link on it.
Does the greeting replace a conversation that has already started?
No. The greeting and buttons replace the welcome message only for a chat that has not started. A chat already under way is not restarted, and a chat opened with the normal bubble is not changed.
When does the offer card appear?
Under the answer to the visitor's first message, with options that fit what they wrote. The chatbot keeps that answer short and points to the card. If it also notices an intent with its own card, that card is shown instead.
Can the reason be trusted for security decisions?
No. The reason comes from the visitor's browser, so it only steers the conversation. It never unlocks anything, and the instruction you write for it cannot override the chatbot's safety rules.
Does it work for every company, or only for Biznsbook?
It works for every chatbot. Each company chooses its own reasons and launch rules for its own website.
How this differs by industry
Retail
A shop adds a "Help me choose" button to each product category page, sends the reason help_choose, and greets those visitors with a question about what they are shopping for.
Wholesale & distribution
A distributor puts a "Request trade prices" button on its catalogue pages and greets those visitors with the details its sales team needs to prepare a quote.
Manufacturing
A manufacturer adds "Ask an engineer" buttons to product data sheet pages so the chat opens with a greeting that asks which product the visitor is specifying.