bluegill

a bluegill chatbot answers visitor questions in your voice 24/7. the setup is one page — name, hours, services, faqs — and you're live.

the bluegill widget is a small launcher that lives in the corner of your site. visitors click it to chat — it expands without leaving the page.

every visitor chat is logged with the full transcript. promising ones get flagged "ready" — the bot caught lead intent (asking about pricing, requesting a callback). convert them into marigold leads in one tap.

the first version of the bot won't be perfect. when you spot a wrong or weak answer, edit the faqs and re-publish.

your bluegill chat lives at a wymzy url by default. for a more polished look, point a subdomain like chat.yourbusiness.com at it through heron.

the public chat page can use one of 13 animated backgrounds from the shared catalog — a nicer first impression than a flat color.

the first thing a visitor sees is your bot's name in the header and its greeting in the chat window. these set the tone before any answer.

the avatar is the small image inside the chat — the launcher is the floating button visitors click to open the chat. you can use your business logo, a bullfrog file, or upload something custom for each.

the faq list is the bot's primary knowledge. ten faqs cover most small businesses — pricing, hours, services, location, payment, what makes you different.

the training-sources section lets the bot answer from live data — your foxfire hours and reviews, your mockingbird services, your magpie products, your bobcat portfolio, your junebug availability. you flip the toggles for what's relevant.

the test panel lets you ask the draft bot questions without affecting the live one. great for catching weak answers before customers see them.

until you publish, your draft only answers in the test panel. publish flips the live url to whatever's in your draft.

every published bluegill chatbot has a public url at /c/{slug} on app.wymzy.ai. share it anywhere — your bio, your email signature, your magnolia site.

every visitor chat is logged. the ones with lead intent get flagged ready — the bot caught a question about pricing or a request for a callback. one tap drops them into marigold.

every conversation gets an ai-derived sentiment — positive, neutral, negative. negative conversations are where the bot probably failed. fix the underlying faq before another customer hits the same wall.

if you're running magnolia, the bluegill widget is one toggle away — no script tag, no copy-paste, no embed snippet to keep in sync.

when a visitor wants to actually book an appointment, the bot doesn't try to handle the calendar — it hands off to your junebug booking link, where they pick a slot themselves.