Build Your First AI Agent Step by Step
A step-by-step guide to creating and deploying your first AI customer support agent in under 30 minutes. No coding required.

Ready to deploy your first AI agent? According to Gartner, by 2029 agentic AI will autonomously resolve 80% of common customer service issues — making now the right time to start. This step-by-step guide will take you from zero to a production-ready customer support agent in under 30 minutes.
TL;DR:
- This tutorial walks you through 7 steps: create an agent, add knowledge sources, customize behavior, test, deploy the widget, set up escalation, and monitor analytics.
- The entire process takes under 30 minutes and requires no coding — just a Chatsy account and some documentation or FAQ content to train on.
- You can add knowledge via website crawl, file upload (PDF, DOCX, TXT), or the built-in CMS.
- After launch, use the continuous improvement loop (review analytics → identify gaps → update knowledge → test → deploy) to keep your agent getting smarter.
What You'll Build
By the end of this tutorial, you'll have:
- ✅ An AI agent trained on your content
- ✅ A chat widget embedded on your website
- ✅ Automatic ticket creation for complex issues
- ✅ Analytics to track performance
Prerequisites
- A Chatsy account (sign up free)
- Some content to train your agent (documentation, FAQs, etc.)
- A website where you'll embed the widget
Step 1: Create Your Agent
- Log into your Chatsy dashboard
- Click "New Chatbot"
- Give it a name (e.g., "Support Agent")
- Choose your primary color to match your brand
💡 Tip: Choose a name customers will see. "Support Agent"
feels more professional than "Bot 1".
Step 2: Add Your Knowledge
Your agent is only as good as its knowledge. Let's give it something to work with.
Option A: Crawl Your Website
- Go to Sources tab
- Click "Add Source" → "Website"
- Enter your website URL
- Click "Crawl"
The crawler will automatically find and index all pages. This typically takes 2-10 minutes depending on site size.
Option B: Upload Documents
- Go to Sources tab
- Click "Add Source" → "Upload"
- Drag and drop your files (PDF, DOCX, TXT, CSV)
Supported formats:
- PDF (including scanned with OCR)
- Word documents (.docx)
- Text files (.txt, .md)
- Spreadsheets (.csv, .xlsx)
Option C: Use the Knowledge Base CMS
- Enable the Knowledge Base module (Growth+ plans)
- Go to Knowledge Base in the sidebar
- Create articles directly in our editor
This is ideal for maintaining living documentation that you update regularly.
Step 3: Customize Your Agent
System Prompt
The system prompt defines your agent's personality and boundaries. Go to Settings → Behavior.
Example prompt:
You are a helpful customer support agent for [Your Company].
Key behaviors:
- Be friendly and professional
- Only answer questions based on the provided knowledge base
- If you don't know something, say so honestly
- Offer to create a support ticket for complex issues
Never:
- Make up information
- Discuss competitors
- Share internal processes not in the knowledge base
Choose Your AI Model
Different models have different capabilities:
| Model | Best For | Speed | Cost |
|---|---|---|---|
| GPT-4o Mini | Simple Q&A | ⚡⚡⚡ | $ |
| GPT-4o | Complex reasoning | ⚡⚡ | $$ |
| Claude 3.5 Sonnet | Long conversations | ⚡⚡ | $$ |
| GPT-4 Turbo | Maximum capability | ⚡ | $$$ |
Start with GPT-4o Mini and upgrade if needed.
Step 4: Test Your Agent
Before going live, test extensively:
- Click "Preview" in the top right
- Ask questions your customers would ask
- Try edge cases and unusual phrasings
- Verify answers are accurate
Common test scenarios:
- ❓ "What are your business hours?"
- ❓ "How do I cancel my subscription?"
- ❓ "I have a problem with..." (should offer ticket creation)
- ❓ "Tell me about [competitor]" (should decline politely)
Step 5: Deploy to Your Website
Get the Embed Code
- Go to Settings → Widget
- Make sure your agent is marked as "Public"
- Copy the embed code
html<script src="https://chatsy.app/api/embed-script/YOUR_CHATBOT_ID" async defer ></script>
Add to Your Website
Paste the script before the closing </body> tag:
html<!DOCTYPE html> <html> <head>...</head> <body> <!-- Your website content --> <!-- Chatsy Widget --> <script src="https://chatsy.app/api/embed-script/abc123" async defer ></script> </body> </html>
The widget will appear in the bottom-right corner automatically.
Platform-Specific Instructions
WordPress: Add to your theme's footer.php or use a plugin like "Insert Headers and Footers"
Shopify: Go to Online Store → Themes → Edit code → theme.liquid, add before </body>
Webflow: Project Settings → Custom Code → Footer Code
React/Next.js:
tsximport Script from 'next/script' export default function Layout({ children }) { return ( <> {children} <Script src="https://chatsy.app/api/embed-script/abc123" strategy="lazyOnload" /> </> ) }
Step 6: Set Up Escalation
When your agent can't help, it should create a ticket.
- Enable the Mailbox module (Growth+ plans)
- Go to Mailbox → New Mailbox
- Add your support email
- Verify your email address
Now when the agent escalates, you'll receive tickets with full conversation context.
Step 7: Monitor & Improve
Analytics Dashboard
Check your analytics regularly:
- Conversations: Total chats over time
- Resolution Rate: % resolved without escalation
- Common Topics: What customers ask most
- Satisfaction: How customers rate interactions
Continuous Improvement Loop
Review Analytics
↓
Identify Gaps (common questions with low satisfaction)
↓
Add/Update Knowledge
↓
Test Changes
↓
Deploy
↓
Repeat
Next Steps
Now that your agent is live:
- Add custom actions: Connect to your CRM, check order status, etc.
- Enable live chat: Let humans take over when needed
- Set up the knowledge base: Create a public help center
- Invite your team: Collaborate on responses
Common Issues
Agent says "I don't know" too often
- Add more content to your knowledge base
- Check that your content covers the questions being asked
- Lower the confidence threshold in settings
Widget doesn't appear
- Check browser console for errors
- Verify the chatbot is marked as "Public"
- Clear your browser cache
Answers are inaccurate
- Review and update your source content
- Add clarifying information for ambiguous topics
- Consider using a more capable model
Need Help?
Our AI agent is trained on this very documentation. Ask it anything! And yes, a human can take over if needed.
Related Articles
- The Complete Guide to Building AI Chatbots in 2026 — a deeper dive into model selection, RAG architecture, and testing
- How to Train Your AI Chatbot on Documentation — optimize your knowledge base for better AI accuracy
- 10 Common AI Chatbot Mistakes to Avoid — sidestep the pitfalls that trip up first-time builders
Frequently Asked Questions
How long does it take to build your first AI agent?
The entire process takes under 30 minutes. You'll create an agent, add knowledge sources (via website crawl, file upload, or CMS), customize behavior, test, deploy the widget, set up escalation, and start monitoring analytics. You only need a Chatsy account and some documentation or FAQ content to train on.
Do I need coding skills to build an AI agent?
No. This tutorial requires no coding—just a Chatsy account and content to train your agent on. You add the embed script to your website (a simple copy-paste before the closing </body> tag), and the widget appears automatically. Platform-specific instructions exist for WordPress, Shopify, Webflow, and React/Next.js.
What are the best platforms for building AI agents?
Look for platforms that offer no-code setup, multiple knowledge source options (website crawl, file upload, built-in CMS), customizable system prompts for personality and boundaries, and built-in escalation to human support. The tutorial uses Chatsy as an example—choose a platform that fits your budget and integrates with your existing tools.
How do I test my AI agent before going live?
Click "Preview" in your dashboard and ask questions your customers would ask. Try edge cases and unusual phrasings. Verify answers are accurate. Test scenarios include: "What are your business hours?", "How do I cancel my subscription?", "I have a problem with..." (should offer ticket creation), and "Tell me about [competitor]" (should decline politely).
What are common first-build mistakes?
Skipping the escalation setup (always provide a path to human support), training on outdated or contradictory content, and "set and forget" deployment. Other pitfalls: overpromising what the bot can do, ignoring mobile experience, and not establishing a continuous improvement loop (review analytics → identify gaps → update knowledge → test → deploy).