I will build an ai faq chatbot using your website content
About this gig
Help visitors find answers in your business content. I will build an AI FAQ chatbot for one website using approved information you provide.
The bot uses your content, shows source references, and directs visitors to your chosen support route when an answer is unavailable. AI can still make mistakes; testing and fallback behavior are included.
Basic: up to 20 FAQs and 3,000 words; 10 test questions. Standard: up to 10 text pages and 10,000 words; 20 test questions. Premium: Standard plus one consent-based inquiry form and one webhook destination.
Each package includes one site, one language, one AI provider, chat widget, backend source, basic rate limiting, setup notes, manual content-update instructions, and installation in one compatible existing environment.
Message me with your stack and sample content before ordering. You pay hosting and AI usage. Voice, WhatsApp, scanned files, account-specific answers, autonomous actions, new admin panels, auto-recrawling, and ongoing support are excluded. Revisions cover the agreed scope. This is not model training.
Get to know San Nimith
Software Engineer for APIs, AI Chatbots and Web Development
- FromCambodia
- Member sinceSep 2023
- Avg. response time1 hour
Languages
English
My Portfolio
FAQ
Will the chatbot always be correct?
No AI system can guarantee that. I test agreed questions, include source references, and configure fallback behavior. The bot should not make binding commitments or replace professional advice.
Are hosting and AI costs included?
No. You own the accounts and pay ongoing usage and hosting charges. We will confirm the provider and compatible environment before starting.
What content can I provide?
Approved FAQs or readable text pages within the package limits. Use material you have permission to share. Scanned documents and private customer records are outside these packages.
Can it make bookings or take payments?
These packages answer questions from business content. Premium adds a consent-based inquiry form to one webhook destination; bookings, payments, and account-specific actions need separate scoping.
