Configure how Moxabot thinks, talks, and responds. This guide covers building your AI persona, populating your Knowledge Base, testing replies in the Preview tab, and setting up hand-off rules that escalate conversations to your human team at exactly the right moment.
Overview
Moxabot's AI is powered by Google Gemini 2.5 Flash — a fast, highly capable model optimised for conversational support. Every reply it generates is shaped by three things you control:
🤖
Persona config
Name, tone, greeting, and behavioural instructions you write in the AI Persona page.
📚
Knowledge Base
PDFs, URLs, and articles you upload. The AI treats this as its source of truth.
🔀
Hand-off rules
Trigger phrases that escalate conversations to a human agent automatically.
ℹ️
Note:Changes to your persona, Knowledge Base, or hand-off rules take effect immediately — no republishing or cache-clearing needed. New conversations pick up the updated config right away.
Set up your AI Persona
The AI Persona page is where you give Moxabot its identity. Everything you set here influences the tone, style, and behaviour of every AI-generated reply across all your connected channels.
Moxabot
Inbox
Contacts
AI Persona
Knowledge
Integrations
Analytics
Team
Billing
AI Persona
Define how your AI assistant thinks and responds
Persona name
Aanya
Tone
Friendly
Professional
Casual
Greeting message
Hi! I'm Aanya, your virtual assistant. How can I help you today? 👋
Instructions
You are a helpful assistant for Bloom Boutique. Always be warm and concise. If you don't know the answer, say so and offer to connect the customer with a human agent...
Save changes
Persona name
Give your AI a name that fits your brand — "Aanya", "Max", "Support Bot", or anything else. This name appears in the chat widget header, in the greeting message, and in agent-facing inbox notes when the AI replies. Keep it short (1–2 words) and human-sounding for best results.
Tone
Choose one of three built-in tones to set the overall register of every AI reply:
Tone
Best for
Example phrasing
Friendly
E-commerce, lifestyle brands, consumer apps
"Great question! Let me check that for you 😊"
Professional
B2B, finance, healthcare, legal services
"Thank you for your enquiry. I can confirm that…"
Casual
Youth brands, gaming, creator communities
"Hey! Yeah, totally — here's the deal…"
💡
Tip:You can always override the tone for specific scenarios in your Instructions field. For example: "Use a Professional tone when discussing returns or complaints, but Friendly otherwise."
Greeting message
The greeting message is the first thing a visitor sees when they open the chat widget or start a new conversation on any channel. Write 1–2 sentences that:
Introduce your AI by name
Set expectations ("I can help with orders, returns, and product questions")
Invite an action ("How can I help you today?")
You can include an emoji if it matches your brand tone. Keep it under 160 characters so it renders cleanly on SMS channels.
Instructions
Instructions are a free-text field where you give the AI behavioural rules — things the AI should always do, never do, or do only in specific situations. Think of it as a one-page brief for a new customer service hire.
💡
Tip:Good instruction patterns:
Always refer customers to the Returns Policy page for refund requests.
Never make up pricing or delivery estimates — only quote what is in the Knowledge Base.
If a customer seems frustrated, acknowledge their feelings before providing information.
When asked about competitors, stay neutral and redirect focus to our products.
Do not answer questions unrelated to our products and services.
Language
Moxabot auto-detects the language the customer is writing in and replies in the same language by default. To restrict replies to a specific language, add a line to your Instructions such as: "Always reply in English, regardless of what language the customer uses."
app.moxabot.com
AI Persona page showing the name field, tone pills (Friendly selected), greeting textarea, and instructions textarea with a Save changes button
AI Persona — name, tone, greeting, and instructions all live on one page
Build your Knowledge Base
The Knowledge Base is where you teach the AI about your business. Every time the AI generates a reply, it searches your Knowledge Base for relevant content and uses it to answer accurately. The more relevant content you add, the better — and more confident — the AI's answers become.
Adding content
Navigate to Knowledge in the sidebar. You have three ways to add content:
1
Upload a PDF
Click Upload file and select a PDF. Good PDFs include product catalogues, FAQs, return policy documents, shipping guides, and user manuals. Moxabot extracts all text and makes it searchable. Max file size: 20 MB per PDF.
2
Paste a URL
Click Add URL and paste the full link to a web page (e.g. your FAQ page, About page, or a product category page). Moxabot fetches and indexes the page content. URLs are re-crawled automatically every 7 days to stay up to date.
3
Write an article
Click New article to open the built-in editor. Write a question-and-answer style article directly in the app. This is the fastest way to add knowledge for specific topics not covered in your existing documents.
app.moxabot.com
Knowledge Base page showing three content cards — a PDF titled 'Returns Policy', a URL card for 'FAQ page', and a written article titled 'How long does shipping take?'
Knowledge Base — mix PDFs, URLs, and written articles for the best coverage
Best practices
You don't need to add everything at once. Here's a recommended starting point:
Day 1
5–10 FAQ articles covering your most common questions (order status, returns, delivery times)
Your returns or refund policy as a PDF or URL
Week 1
Top product category pages (URLs)
Shipping & fulfilment guide
Sizing or specification guides if relevant
Ongoing
New product launches
Seasonal policy changes
Any support article you notice customers asking about repeatedly
💡
Tip:Start with 5–10 FAQs. That's enough to handle the majority of inbound questions for most e-commerce businesses. Use the Preview tab (below) to test how well the AI answers before you go live — then fill in the gaps.
Writing good Knowledge Base articles
When writing articles directly in Moxabot, use a question-and-answer format. Each article should:
Have a clear, specific title phrased as the question customers actually ask ("How do I return an item?")
Open with a direct answer in the first sentence
Include any relevant URLs, timelines, or policy details in the body
Stay focused — one topic per article is better than one long article covering many topics
Avoid internal jargon the customer wouldn't use
text
Good article title: "How long does standard shipping take?"
Bad article title: "Shipping"
Good opening: "Standard shipping takes 3–5 business days for orders placed before 2pm."
Bad opening: "There are several shipping options available to customers."
Good body: Includes the cut-off time, weekend handling note, and a link to the tracking page.
Bad body: Vague — "It depends on your location and order date."
Test & preview AI replies
Before you go live, use the Preview tab to test your AI in a sandboxed environment. Replies in Preview are never delivered to real customers and don't count toward your conversation limits.
1
Open the Preview tab
On the AI Persona page, click the Preview tab at the top right. A mock chat window appears showing your greeting message exactly as customers will see it.
2
Send test messages
Type a question your customers commonly ask — for example, "What is your return policy?" or"When will my order arrive?" — and press Enter. The AI replies using your current persona config and Knowledge Base content.
3
Interpret the response
Look for three things:
Accuracy — is the answer correct according to your Knowledge Base?
Tone — does it sound the way you want your brand to sound?
Completeness — does it answer the whole question, or does it leave something out?
4
Iterate
If a reply is wrong or off-tone, go back and either add or improve a Knowledge Base article, or refine your Instructions field. Then test again. Most teams get to a good baseline in 2–3 rounds.
app.moxabot.com
AI Persona Preview tab showing a chat window with a test question 'What is your return policy?' and an AI reply quoting the 30-day returns policy from the Knowledge Base
Preview tab — test your AI in a sandboxed chat window before going live
ℹ️
Note:The Preview tab shows replies from your current unsaved draft as well. You can tweak instructions or tone and test immediately without saving — useful for rapid A/B testing of phrasings. Remember to hit Save changes when you're happy.
Common issues and fixes
Symptom
Likely cause
Fix
"I don't have information on that"
No matching KB content
Add an article covering that topic
Reply ignores your policy details
KB article is vague or missing key facts
Rewrite the article with specific details (dates, amounts, steps)
Tone feels too stiff / too casual
Tone selector mismatch
Switch tone, or add a tone note to Instructions
Reply is too long
AI over-explains by default
Add to Instructions: "Keep replies under 3 sentences unless the customer asks for more detail."
Greeting doesn't show persona name
Name field is empty
Fill in the Persona name field and save
Configure hand-off rules
Hand-off rules define the conditions under which Moxabot stops trying to resolve a conversation automatically and assigns it to a human agent. Getting this right is critical — you want the AI to handle volume, but never leave a frustrated customer talking to a bot when they need a person.
Trigger phrases
Trigger phrases are keywords or short phrases that, when detected in a customer's message, immediately escalate the conversation. Navigate to AI Persona → Hand-off and add your triggers one per line. Common examples:
"speak to a person"
"talk to someone"
"human agent"
"refund"
"complaint"
"not happy"
"this is wrong"
"cancel my order"
"legal"
"lawyer"
"sue"
"media"
⚠️
Warning:Trigger phrases are matched case-insensitively and as substrings — so "refund" also catches "I want a refund" and "refund request". Be careful with short words that could trigger false positives (e.g. "not" would match almost everything). Use more specific phrases.
Escalation flow
When a trigger phrase is detected, here is exactly what happens:
1
AI sends a hand-off message
The AI replies with a configurable hand-off message, e.g.: "Got it — I'm connecting you with a member of our team right now. Please hold on."You can customise this message in the Hand-off settings.
2
Conversation is escalated in the inbox
The conversation moves to the top of your Inbox with an orange Escalated badge. All agents with inbox access are notified (in-app and by email if enabled in notification settings).
3
AI stops replying
Once escalated, the AI goes silent. No further automated replies are sent until an agent manually marks the conversation as "Resolved" and re-enables AI — or until a new conversation is started.
4
Agent takes over
The assigned agent sees the full conversation history, including all AI replies, and responds manually. They can add internal notes (invisible to the customer) to provide context for their colleagues.
app.moxabot.com
Inbox view showing an escalated conversation with an orange 'Escalated' badge, the full AI conversation history, and an agent reply box at the bottom
Escalated conversations appear at the top of the inbox with full history intact
What happens when no agent is available
If a hand-off is triggered outside of your team's working hours or when all agents are busy, the AI sends the hand-off message and the conversation enters the escalation queue. The customer is not left hanging — the AI also sends a follow-up message configured in Business Hours settings(e.g. "Our team is currently offline — we'll get back to you within 4 business hours.").
💡
Tip:Set up Business Hours in Team settings to ensure customers always receive an accurate offline message rather than a generic "no agents available" notice.
Tips for writing great instructions and KB articles
1
Be specific, not vague
Instead of "Handle refunds politely", write "For refund requests, always apologise for the inconvenience, quote the 30-day return window from our Returns Policy, and provide the returns portal link: returns.yourbrand.com."
2
Use real customer language
Write KB article titles the way customers would ask the question — not the way you'd categorise it internally. "How do I cancel?" beats "Order cancellation procedure".
3
Tell the AI what NOT to do
Negative instructions ("Never quote delivery estimates not listed in the KB") are often more effective than positive ones, because they prevent the AI from making things up.
4
Keep instructions under 500 words
Very long instruction sets can cause the AI to miss individual rules. If you need complex logic, consider splitting it into multiple specific KB articles the AI can reference.
5
Review the Preview tab weekly
As your business changes — new products, policy updates, seasonal changes — test a few common questions in Preview to make sure the AI is still accurate. Set a weekly 10-minute review.
Limits
🚨
Heads up:50 AI replies per conversation — each conversation is capped at 50 automated AI replies. After the 50th reply, the AI stops responding and the conversation is automatically escalated to a human agent. This prevents runaway loops and ensures complex conversations always reach a person.
⚠️
Warning:Trial plan: 100 conversation lifetime cap — the free trial includes a maximum of 100 total conversations across all channels for the life of the trial account. This counter includes both AI-handled and human-handled conversations. Upgrade to a paid plan to remove this limit. See Billing & Plans for details.