Troubleshooting
โ FAQ and Troubleshooting - Crafter.ai This guide contains frequently asked questions, solutions to common problems, and best practices for optimizing the...
โ FAQ and Troubleshooting - Crafter.ai
This guide contains frequently asked questions, solutions to common problems, and best practices for optimizing the use of Crafter.ai.
๐ฏ Frequently Asked Questions (FAQ)
๐ Introduction and Setup
Q: How long does it take to create the first chatbot?
A: For a basic functioning chatbot:
- Quick Setup: 15-30 minutes
- Complete Setup: 2-4 hours
- Advanced Setup: 1-2 days
The time depends on the complexity of the knowledge base and the number of customized Q&A.
Q: Can I create multiple chatbots with the same account?
A: Yes, the number depends on the plan, see the pricing page at this link
Q: What languages does Crafter.ai support?
A: Fully supported languages:
- ๐ฎ๐น Italian
- ๐ฌ๐ง English
- ๐ง๐ท Portuguese (Brazil)
- ๐ช๐ธ Spanish
- ๐ซ๐ท French
- ๐ฉ๐ช German
Q: Can I change the language of the chatbot after creating it?
No
๐ Teaching and Knowledge Base
Q: How many Q&A can I create?
A: You can create unlimited Q&As.
Q: What file formats can I upload?
A: Supported formats:
- Documents: PDF, DOCX, DOC, TXT, RTF, Excel, CSV, JSON
- Max size: 10MB per file
Q: Can the chatbot learn automatically from conversations?
A: No, Crafter.ai does not have automatic self-learning for safety and quality control. However:
- โ You can analyze "misses" (unresolved conversations)
- โ Receive suggestions for new Q&A
- โ Dashboard analytics to identify gaps in the knowledge base
Q: How can I improve the accuracy of responses?
A: Best practices:
- More utterances: Add variants of each question
- Natural language: Write as your customers speak
- Clear context: Complete and specific responses
- Regular training: Retrain after modifications
- Analyze misses: Review unresolved conversations
๐จ Customization and Preview
Q: Can I use my logo as the chatbot avatar?
A: Yes! Supported formats:
- PNG, JPG, SVG
- Sizes: Minimum 64x64px, optimal 256x256px
- Weight: Max 500KB
- Shape: Automatically rendered circular
Q: Is the chatbot responsive on mobile?
A: Yes, fully responsive with:
- โ Mobile-first design
- โ Touch-friendly interface
- โ Automatic font/size optimization
- โ Testing on all major devices
Q: Can I test the chatbot before publishing it?
A: Absolutely! In the Preview step you have:
- Integrated test widget: Interactive testing
- Demo page: Temporary URL for testing
- Team sharing: Share with colleagues for feedback
๐ Deploy and Integration
Q: On which sites can I integrate the chatbot?
A: The chatbot works on:
- โ Any website (WordPress, Shopify, custom)
- โ Landing pages
- โ Web apps (React, Vue, Angular)
- โ E-commerce (Magento, WooCommerce, Prestashop)
Only requirement: JavaScript support.
Q: Does the chatbot slow down the website loading?
A: Yes.
Q: What happens if the chatbot server goes offline?
- Fallback message: Customizable service unavailable message
- Auto-recovery: Automatic reconnection
๐ฐ Plans and Billing
Q: What happens if I exceed the message limit?
- You can purchase additional messaging packages or upgrade to the next plan. This way, you avoid service interruptions and ensure conversation continuity.
Q: Can I change plans at any time?
A: Yes:
Q: Do you offer discounts for non-profits or educational institutions?
A: Please, contact us on info@athics.ai
๐ฅ Team and Collaboration
Q: How do I add team members?
A: Only Owners and Admins can:
- Team Settings โ Invite Member
- Enter email of the new member
- Select role (Admin, Member)
- Send invite โ The user receives an email
Q: Can I restrict access to certain chatbots?
A: Currently, permissions are at the team level, not per individual chatbot. Solutions:
- Separate teams for different projects.
๐ง Technical Issues
Q: The chatbot does not respond to the questions I entered
A: Debug checklist:
- โ Training completed? Check status "Trained"
- โ Q&A Check information in the Q&A
- โ Sufficient utterances? Add variants of the question
- โ Consistent language? Same language for chatbot/questions
- โ Test with exact phrases: Try with the exact utterances entered
Q: Error "Can't deploy - survey incomplete"
A: Step-by-step solution:
- Go to the Teaching Step
- Check Survey section: All questions must have answers
- Save everything: Click save after each modification
- Retry deploy: Go back to the Deploy step
Q: The widget does not appear on my site
A: Troubleshooting:
// 1. Check code in <head>
// 2. Open Developer Tools (F12)
// 3. Check Console for errors
// 4. Verify Network tab for 404/500 errors
// 5. Test on a simple page (test.html)
Common causes:
- Incorrect Bot ID in the code
- Unauthorized domain
- Content Security Policy too restrictive
- Ad-blocker blocking the widget
๐ ๏ธ Detailed Troubleshooting
๐ Problem Diagnostics
Chatbot Not Responding Correctly
Symptoms:
- Responds "I didn't understand" to questions present in the Q&A
- Irrelevant or confused responses
- Inconsistent understanding
Diagnosis:
Step 1: Check Training Status
โโโ Dashboard โ Bot Status
โโโ Must be "Trained" (green)
โโโ If "Needs Training": retrain
Step 2: Analyze Utterances
โโโ Review Q&A with issues
โโโ Add more variants (min 3-5 per Q&A)
โโโ Use natural language of customers
Step 3: Check Conflicts
โโโ Teaching โ Improve โ Conflicts
โโโ Resolve semantic overlaps
โโโ Clarify ambiguous Q&A
Step 4: Systematic Testing
โโโ Test exact phrases of the utterances
โโโ Test progressive variants
โโโ Document failure patterns
Solutions:
โ
Utterances Expansion:
Question: "How much does shipping cost?"
Utterances:
- "Shipping cost"
- "Delivery price"
- "Shipping rates"
- "Transport charges"
- "What do I pay for delivery?"
โ
Context Addition:
Improved response:
"Shipping costs โฌ4.90 (standard 3-5 days)
or โฌ9.90 (express 1-2 days).
FREE for orders over โฌ50!"
Deployment Issues
Error: "Upgrade chatbot plan"
Cause: Insufficient plan for deployment
Solutions:
1. Check current plan: Dashboard โ Billing
2. Check usage: % messages used
3. Upgrade plan if necessary
4. Contact admin team if you are not the owner
Error: "Deploy failed - server error"
Diagnosis:
1. Retry after 5-10 minutes
Infinite deploy (>15 minutes)
Possible causes:
โโโ Very large knowledge base
โโโ Many Q&A (>500)
โโโ Server overload
โโโ Network issues
Solutions:
โโโ Optimize KB (remove duplicates)
โโโ Deploy during off-peak hours
โโโ Contact support if it persists
โโโ Check internet connection
Widget Integration Issues
Widget not visible
Debug Checklist:
โก Bot status = "Deployed"
โก Code in <head>, not in <body>
โก Correct Bot ID (no extra spaces)
โก No JavaScript errors in console
โก Test in incognito mode
โก Temporarily disable ad-blocker
Widget visible but not functioning
Diagnosis:
1. Test on official demo page
2. Compare behavior
3. Test cross-browser (Chrome, Firefox, Safari)
๐จ Urgent Problem Resolution
Chatbot Offline During High Traffic
Immediate Action:
1. Check Dashboard Status (2 min)
2. Verify system status page (1 min)
3. Contact support if confirmed outage (immediate)
4. Activate fallback message if configured
5. Notify team/stakeholder
Health Check Routine
Daily (5 minutes):
โก Bot status check
โก Error rate review
โก New conversations scan
โก Usage metrics check
Weekly (30 minutes):
โก Performance trends analysis
โก Misses review and resolution
โก Knowledge base accuracy audit
โก User feedback analysis
Monthly (2 hours):
โก Full performance review
โก Strategic content optimization
โก Team training needs assessment
โก Technology stack review
๐ก Best Practices and Tips
๐ฏ Performance Optimization
Content Optimization
โ
Q&A Quality:
โโโ 1 concept per Q&A (no multiple questions)
โโโ Complete but concise answers (<200 words)
โโโ Clear call-to-action when appropriate
โโโ Brand-consistent language
โ
Knowledge Base:
โโโ Updated and relevant documents
โโโ Removal of obsolete content
โโโ Logical and navigable structure
โโโ Format consistency
๐จ UX Best Practices
Conversational Design
โ
Natural Language:
โโโ Write as you speak
โโโ Avoid technical jargon
โโโ Use emojis sparingly ๐
โโโ Tone consistent with brand
โ
User Journey:
โโโ Clear onboarding for new users
โโโ Help easily accessible
โโโ Progress indication for long flows
โโโ Clear exit points
Error Handling
โ
Graceful Degradation:
โโโ Informative but friendly error messages
โโโ Alternative paths when possible
โโโ Human handover when necessary
โโโ Concrete recovery suggestions
๐ Growth and Scaling
Content Scaling Strategy
Phase 1: Core Q&A (0-50 Q&A)
โโโ Focus on most frequent questions
โโโ Perfect core user journeys
โโโ Establish baseline metrics
Phase 2: Expansion (50-200 Q&A)
โโโ Add edge cases
โโโ Implement advanced flows
โโโ Optimize performance
Phase 3: Advanced (200+ Q&A)
โโโ Specialization for user segments
โโโ Advanced integrations
โโโ Predictive capabilities
Team Scaling
Small Team (1-3 people):
โโโ 1 person: All-in-one (content + tech)
โโโ 2 people: Content specialist + Tech lead
โโโ 3 people: + Analytics/optimization specialist
Medium Team (4-10 people):
โโโ Content Manager
โโโ Bot Trainer/Optimizer
โโโ Technical Lead
โโโ Analytics Specialist
โโโ QA/Testing specialist
Large Team (10+ people):
โโโ Specialized teams per function
โโโ Dedicated DevOps
โโโ User research specialist
โโโ Customer success integration
๐ When to Contact Support
๐ด Immediate Support Needed
- Chatbot completely offline >30 minutes
- Data loss or corrupted knowledge base
- Suspected security incidents
๐ก Support Within 24 Hours
- Recurring deploy failures
- Significant performance degradation
- Integration issues with critical services
- Billing/account problems
๐ข Standard Support (2-5 days)
- Feature requests
- Training and best practices
- General optimization advice
- Non-critical technical questions
๐ How to Contact
Email: support@athics.ai Chat: Chatbot
Information to include:
- Account ID and team name
- Bot ID if specific issue
- Detailed description + screenshots
- Steps to reproduce
- Browser/device info
- Urgency level (Critical/High/Medium/Low)
๐ก Remember: Most issues have simple solutions. Always follow the systematic debugging process before contacting support.
