How to Set Up AI Customer Support in Under an Hour
Updated · July 3, 2026
You’ve been meaning to do this for months. A customer emails at 11pm asking about your return policy, nobody answers until morning, and they’ve already left a one-star review by the time your inbox opens. The fix doesn’t require a developer or a week of configuration. Here’s exactly how to go from zero to a working AI support bot today — we’ll use Tidio as the primary tool because it’s the fastest to set up, though we’ll flag where Intercom or Freshworks make more sense for your situation.
What you’ll build: a chatbot that answers common questions automatically, captures contact info when it can’t help, and routes harder conversations to a human. What you’ll need: a website where you can paste a script tag or install a plugin, an email address for signup, and about 55 minutes of uninterrupted time.
1. Pick the right tool for your setup (5 minutes)
Not every AI support tool is worth the same setup time. Spend five minutes here to avoid redoing this later.
Use Tidio if you run an e-commerce store, a small SaaS, or any site where repetitive questions are the problem — “where’s my order?”, “how do I reset my password?”, “what’s your refund policy?”. The free tier handles 50 Lyro AI conversations per month, enough to prove value before you pay anything. Lyro, Tidio’s AI engine, pulls answers from your FAQ content and handles multi-turn conversations without much configuration.
Use Intercom if you’re a SaaS company with a product users log into, and you need the bot to know who the user is, what plan they’re on, and what they’ve done inside the app. Intercom’s Fin AI handles complex workflows well, but setup takes longer and pricing starts around $39/month for the plan that includes meaningful AI features.
Use Freshworks if you want ticketing and live chat in one system. Their AI assistant sits inside a full helpdesk — useful if you’re currently managing support across scattered email threads. Pricing is comparable to Intercom’s mid tier.
One honest counter-take before you go any further: if your site gets fewer than 25 support contacts a week, a well-structured FAQ page and a contact form will handle the problem just as well — with zero maintenance overhead and no risk of a bot confidently producing a wrong answer. Add a chatbot when you have the volume to justify it, not because it feels like the right year to have one.
The rest of this walkthrough uses Tidio. The underlying concepts apply to any platform — the specific clicks will differ.
2. Create your account and install the widget (10 minutes)
Go to Tidio’s site and click Get started free. The signup flow asks for your email, a password, and your website URL. Enter the URL accurately — Tidio uses it to pre-populate some settings and auto-detect your platform.
After signup, you land in an onboarding wizard. Skip it for now by clicking I’ll do this later in the bottom left. You’ll move faster going directly to settings.
To install the widget, navigate to Settings → Channels → Live Chat. You’ll see your unique widget code — a single script tag. Copy it, then install it based on your platform:
- WordPress: Install the free Tidio plugin from the WordPress plugin directory. Paste your API key when prompted — it’s on the same settings page, labeled Public Key.
- Shopify: Install from the Shopify App Store. Authentication is automatic, no code needed.
- Webflow, Squarespace, or anything else: Paste the script tag before the closing
</body>tag in your site’s custom code section.
Once installed, open your site in a browser. The chat widget should appear in the bottom-right corner within about 30 seconds. If it doesn’t, hard-refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). If it still doesn’t appear, confirm you pasted the code before </body>, not inside <head>.
3. Configure Lyro AI settings (10 minutes)
In the Tidio dashboard, go to Lyro AI in the left sidebar. Set these four things before you add any content:
- Default language: Lyro defaults to English. If your customers commonly write in Spanish, French, or Portuguese, set it here. Lyro will respond in the visitor’s detected language, but this defines the fallback.
- AI confidence threshold: This controls how certain Lyro needs to be before it answers on its own. The default is “medium.” Leave it there for now — you can raise it later once you see what it’s getting wrong.
- Bot name and avatar: Under Settings → Appearance, name your bot something that doesn’t pretend to be human. “Support Bot,” your brand name plus “Assistant,” or a clearly synthetic name all work. Visitors trust bots more when they know they’re talking to one.
- Greeting message: Keep it short. “Hi there — I can answer most questions right away. What do you need help with?” Don’t list capabilities in the greeting. Just invite the question.
Don’t spend more than five minutes on the greeting message. Real conversations will show you what phrasing works. Set something reasonable and keep moving.
4. Build your knowledge base (15 minutes)
This is the most important step, and the one people overthink. Most guides tell you to write 100+ FAQ answers before launching your chatbot. Don’t. That advice delays your launch by days, and most of those answers will never get asked. Start with 10 questions and let real conversations tell you what to add next.
Here’s how to find the right 10:
- Open your email inbox or helpdesk tickets from the last 30 days.
- Filter for subjects containing “how do I,” “where is,” “can I,” or “what is.”
- Pick the 10 questions that appear most often. These are your first 10 knowledge base entries.
In Tidio, go to Lyro AI → Knowledge Base. You have two options: paste a URL (Tidio crawls the page and extracts FAQ content automatically) or add Q&A pairs manually.
The URL crawler works well for existing help pages. Paste your /faq or /help URL, click Sync, and review what it pulls in.
Delete anything outdated or incorrect before moving on. Lyro will use whatever’s there — including wrong information if you imported it without reviewing.
For manual entries, write the question the way a customer would ask it, not the way a marketing page would phrase it. “What’s your return policy?” performs better than “Returns and Refunds Policy Overview.” Then write a complete answer — include any links to relevant pages, and give specific details (timeframes, dollar amounts, exceptions) rather than vague summaries.
We set this up for a small e-commerce client in late June 2026. We pulled 12 questions from their support inbox, imported their existing /faq page (which added 8 more entries automatically), and the knowledge base was live in under 15 minutes. First evening live, Lyro handled 7 out of 9 incoming conversations without human intervention.
5. Set escalation and handoff rules (10 minutes)
An AI bot with no escalation path is a dead end for frustrated customers. Set up handoff rules before you go live — this is non-negotiable.
In Tidio, go to Automation → Flows. Create a new flow and select When Lyro can’t answer as the trigger. Then set the actions:
- Send a message: “I’m not sure about that one — let me get you to someone who can help.”
- Add action: Assign to operator if your team is currently online, or Ask for email if it’s outside business hours.
- If you choose Ask for email, follow up with: “We’ll email you back within [X hours]. What’s the best address to reach you?”
Also configure business hours. Under Settings → Operating Hours, define when your team is available. Lyro adjusts its handoff behavior automatically — during hours it routes to a human, after hours it captures the email and queues the conversation for morning.
One optional step worth the 5 minutes: connect Tidio to Slack using Zapier. A simple Zap that fires when a new unanswered conversation is created means your team gets a notification without checking the Tidio dashboard all day.
6. Test it before you go live (5 minutes)
Open your website in an incognito window so you appear as a new visitor rather than the account owner. Start a conversation and work through these four checks:
- Ask one of your top 10 FAQ questions word-for-word. Lyro should answer correctly and completely.
- Ask the same question with different phrasing. “Do you accept returns?” and “What’s your return policy?” should both trigger the right answer.
- Ask something completely outside your knowledge base. The bot should escalate gracefully, not invent an answer.
- If you set business-hours rules, verify that the after-hours flow shows the email-capture message rather than trying to connect to an operator.
Expect to make 3-5 small fixes during this phase. If Lyro gives a wrong answer, edit that knowledge base entry. If it fails to recognize a question it should handle, add an alternate phrasing to the Q&A. This is normal and quick to address.
What to do if it doesn’t work
Widget isn’t showing up: Confirm the script tag is before </body>, not inside <head>. If your site has a Content Security Policy (CSP) header blocking external scripts — common on developer-built sites — ask your developer to whitelist code.tidio.co.
Lyro says it doesn’t know the answer, even for things in your knowledge base: The confidence threshold may be set too high, or your knowledge base entries may be too brief. Try lowering the threshold one notch under Lyro AI → Settings, or rewrite the relevant Q&A entries to be more specific.
Conversations are routing to the wrong person: Check Settings → Team. Each operator needs an assigned department if you’re using department-based routing. If everyone’s in one group, confirm the default department is set and that all active operators have their status set to online.
Taking it further
After your bot has been live for a week, go to Lyro AI → Analytics and open the unanswered questions report. This is the most useful data you’ll get — a real list of what customers are asking that your knowledge base doesn’t cover. Add those entries before expanding anywhere else.
After 30 days you’ll have a clear picture of whether the free tier is enough or whether you need more capacity. Tidio’s $29/month Starter plan bumps Lyro to 100 conversations per month and adds more automation options — usually the right upgrade once you’ve validated that the bot is actually deflecting tickets.
Frequently asked questions
Do I need a developer to set this up?
No. WordPress and Shopify are handled entirely by plugins. On other platforms you’re pasting one script tag — something any site admin can do through their platform’s custom code settings without touching any code directly.
How does Tidio compare to just pointing customers to ChatGPT?
ChatGPT isn’t a support platform — it has no chat widget, no ticketing, no handoff rules, and no knowledge base scoped to your specific content. Lyro stays within what you’ve trained it on and won’t fabricate answers the way a general-purpose LLM might. For raw conversational intelligence on complex questions, GPT-4o is probably sharper — but that’s not the comparison that matters when someone’s asking where their order is at midnight.
What if my customers ask questions that are too complex for AI to handle?
That’s what the escalation rules in step 5 are for. A well-configured bot doesn’t need to answer everything — it needs to handle the 60–70% of repetitive questions so your team can focus on the conversations that actually require judgment. The unanswered questions report will show you exactly where the line falls for your specific business.
If you want AI support handling real questions by tonight, Tidio is the fastest path from zero to live — the free tier is genuinely usable, setup requires no developer, and Lyro stays within your knowledge base instead of improvising answers.
Try TidioThis article contains affiliate links. If you subscribe through one, we may earn a commission at no extra cost to you. It never changes what we recommend — we only link to tools we actually use. Full disclosure.
