AI chatbot guide

Build an AI chatbotwith AI.

A real chat UI on your domain backed by OpenAI or Claude, with conversation history, optional knowledge-base retrieval, and an embeddable widget. Skip the $99/month chatbot vendors.

helpdesk.webtwizz.app

Built for you

  • ✓OpenAI · GPT-5 or GPT-4o behind the chat
  • ✓Anthropic · Claude as an alternative or fallback model
  • ✓Supabase · Conversations
  • ✓Resend · Email escalation when the bot gets stuck
  • ✓Hosting · Live at helpdesk.webtwizz.app

5 steps

From a sentence to a live app.

Step 01

Describe the chatbot you want

Prompt WebTwizz: "An AI chatbot for my SaaS that answers questions using my product docs, asks for an email if the user is stuck, and escalates to support via Resend." WebTwizz builds the chat screen and the backend behind it.

Step 02

Connect OpenAI or Anthropic

One-click integration. Paste your API key and WebTwizz stores it safely in your app. Replies appear word by word as they are written, like ChatGPT.

Step 03

Connect Supabase for conversations + (optional) knowledge base

Conversations and messages are saved per user. For a knowledge base, WebTwizz can set up AI search in Supabase. Paste your docs, the AI splits them into small pieces and indexes them, and the chat finds the most relevant pieces for each question.

Step 04

Style the chat UI

The chat bubble, message input, suggested-question chips: all editable visually. Match your brand colors. Word-by-word replies, auto-scroll, and code formatting work out of the box.

Step 05

Embed it on your site (optional)

WebTwizz generates a short snippet you paste into any site to add a chat bubble. Or use the standalone page at chat.yourdomain.com.

What you can build

Steal a prompt.

Each one opens the builder with the prompt filled in.

Why it works

The parts other AI builders skip.

Replies that type out live, not "thinking…" spinners
Replies appear word by word as the model writes them. Feels like ChatGPT.
Conversation history per user
Each user’s chats persist in Supabase. Switch between conversations, search past messages, delete what you don’t need.
Optional knowledge base
Add your docs as a knowledge base. AI search over your docs gives the chatbot answers based on your content, without training a custom model.
Use any model you want
GPT-5, Claude, Gemini, Llama. Switching providers is a small change. Or use several and pick one by question type.

Integrations

Wired up. One click each.

OpenAI vs Claude vs both: which AI model your chatbot should use

OpenAI (GPT-4o / GPT-5). Default pick for general-purpose support and lead-gen bots. Cheaper per use, quicker to start replying, broadest model selection (4o-mini for cheap routing, 4o for quality, o1 for reasoning). The right default if you don't already have an opinion.

Anthropic Claude (Sonnet 4.6 / Opus 4.7). The right pick when conversation quality matters more than cost, sales chatbots, in-app product help, anything where tone and how it declines requests affect the experience. Claude also handles very long inputs (200K tokens), so it shines for "talk to my docs" use cases where you put a large knowledge base into the prompt.

Both, with routing. The mature pattern for serious chatbots: send short, simple questions to GPT-4o-mini at $0.15 per million tokens, and send complex or high-stakes questions to Claude Sonnet at $3 per million. WebTwizz builds the routing if you ask for it: you describe the rule ("if the message is over 500 characters or mentions account or billing, use Claude"), and the AI writes it.

Both integrations are ready in WebTwizz. Connect once and the keys are stored safely in your project, ready for your app to use.

Knowledge bases and "talk to my data": what actually works in 2026

If your chatbot needs to answer questions grounded in your own data (docs, support articles, product specs), you need AI search over that data, not just a long prompt.

The setup WebTwizz builds: your content is stored in Supabase in a searchable form, re-indexed whenever it changes, and before each answer the chat pulls the few most relevant pieces and hands them to the AI model. This is called retrieval-augmented generation, or RAG. It's how every serious doc chatbot is built.

For most B2B chatbots under 10K documents, keeping the search inside Supabase is the right call: one fewer service to run, and the search sits next to your logins and user data. Past that, you move to a dedicated search service like Pinecone or Qdrant. WebTwizz can connect either; Supabase is the default because it's simpler.

What you should NOT do: put your entire knowledge base into the chatbot's instructions on every message. Even with Claude's 200K token limit, you'll burn money and quality. Search first, then ask.

FAQ

The honest answers.

The questions founders actually ask before they commit to a tool.

You can. They’re great if you want plug-and-play. The trade-off is per-conversation pricing, generic UI, and limited control over the model and prompt. WebTwizz gives you a chatbot you own: same AI models, your prompt, your data, fixed cost.

Yes. Replies appear word by word as they arrive, using OpenAI’s and Anthropic’s official tools. Feels exactly like ChatGPT or Claude.ai.

Two ways: (1) put your docs straight into the chatbot’s instructions, which works for short docs (up to about 20k tokens), or (2) use a knowledge base with AI search. WebTwizz sets up the indexing and the search for you.

OpenAI or Anthropic usage costs (variable by model + usage), plus your WebTwizz hosting. For most chatbots, $5–50/month covers thousands of conversations. Way cheaper than $99–500/month per-vendor pricing.

Yes. WebTwizz generates a short snippet that adds a chat bubble to any web page: Wix, Webflow, Shopify, your existing site, anywhere.

Keep reading

Start with one sentence.

Describe it, and watch the real app get built. Free to start, no credit card.