luckpandaAnswer from your docs, not from what sounds likely
Trial users ask whether you support SSO, how the API rate limits work, and whether you integrate with the tool they already use. The chatbot answers from the docs, pricing and changelog you give it. When the docs say nothing, it says that instead of guessing.
No account needed to try it. We read the public pages of your site, build the chatbot in about a minute and delete it after 7 days unless you keep it.
- Answers only from the docs you give it
- Says so when something is not documented
- Free to set up and test
What trial users ask, and which source answers it
| Question | Source to give it | A good answer |
|---|---|---|
| Do you support SAML SSO on the Team plan? | Pricing page, security docs | The plans that include it, as the pricing page says |
| What's the API rate limit? | API reference | The number from the reference, and where to read more |
| Do you integrate with HubSpot? | Integrations page | Yes with the page, or "not listed" and a handoff |
| How do I invite my team? | Getting-started guide | The steps, in order, short |
| When did you ship the Outlook add-in? | Changelog | The release it appeared in |
| Can I be invoiced in EUR? | Billing FAQ | What the FAQ says, or a handoff to billing |
Docs, API reference and changelog: how to load each
- Docs siteAdd it as a website source. One crawl reads up to 50 pages, to a link depth of 3. For larger docs, add several website sources that start from different sections. A project holds up to 60 sources.
- API referenceIf it renders as ordinary HTML pages, crawl it. If it lives in an OpenAPI file, export it to Markdown and upload that. JSON and YAML files are not accepted.
- ChangelogCrawl the changelog page and press Re-crawl after each release. Old text keeps answering until the new crawl finishes.
- The gapsQuestions your docs do not cover, such as "do you sign a DPA", go in as FAQ entries in your own words.
The crawler does not run JavaScript and does not log in. Docs that build their text in the browser, or sit behind a sign-in, come back as skipped pages with the reason. Serve the text in the HTML, or upload Markdown instead.
"Do you integrate with X?"
A wrong yes here costs you a customer after they have paid. The bot is told never to invent features, so the answer has to come from your integrations page.
Sample conversation on a fictional scheduling app, Plotwise
It does not know who is signed in
The chat window does not know which of your users is looking at it. So "why was my card declined" or "how many seats do I have" cannot be answered from your docs, and should not be answered from a lookup that anyone could run by typing someone else's email.
- Send account and billing questions to a person: add billing, invoice, refund and cancel as handoff topics.
- If you connect a read-only API, return only what is safe to show anyone who knows the inputs, such as public system status.
- Use the support goal on your docs, so the bot saves a lead only when someone asks to be contacted or shows buying intent.
Support on the docs, sales on the marketing site
docs.yourapp.example
- Goal: customer support
- Sources: docs, API reference, changelog
- Hands over when the docs have no answer
- Tone: concise
yourapp.example
- Goal: lead generation
- Sources: product pages, pricing, security page, integrations
- Asks for work email and company early, plus your questions, such as seat count
- Steers towards a demo or a trial
Each project has its own sources, look, allowed websites and chat history, and both send leads to the same LuckPanda CRM. The Chatbot plan covers up to 10 websites for ₹249 a month. Billing is in Indian rupees today.
Limits worth knowing before you launch
- It answers from your docs as they were at the last crawl. There are no scheduled re-crawls yet, so stale docs give stale answers.
- It cannot run code, reproduce a bug or read your logs.
- There is no Slack, Intercom or Zendesk integration. Handed-over chats wait in LuckPanda with an email alert, and a signed webhook can send leads and finished chats to your own systems.
- It can still get a detail wrong in a long reference page. Test it with your real support questions, and read the chats.
Questions
How do I keep it in step with the docs?
Press Re-crawl on the source after you publish. Re-crawling is on demand; scheduled re-crawls are not built yet. The same action is available over the REST API and MCP, so a release script can trigger it.
Can it read our OpenAPI spec?
Not as a JSON or YAML file. Upload a Markdown or text export, or crawl the rendered reference pages.
Our docs are behind a login. Can it read them?
No. It reads public pages only. Upload the content as Markdown, PDF, DOCX or text instead.
Does it work with Intercom or Zendesk?
No. Handed-over chats are answered in LuckPanda. A signed webhook sends leads and finished chat transcripts to a URL you choose, so your own code can pass them on.
What does it cost?
Free to build and test. Going live is ₹249 a month or ₹2,241 a year for up to 10 websites, billed in Indian rupees, with no per-seat or per-message charge.
Related pages
- Help centre and FAQYour help articles answer most questions, but few people search them. Let the chatbot do the searching.
- Customer supportAnswer the questions your site already answers, and hand the rest to a person.
- Lead generationTurn visitors who are ready to talk into CRM leads with a follow-up task, instead of a form they skip.
- AgenciesQualify enquiries on your own site, and run chatbots for client websites from one account.
Build it with your AI agent
Give an agent your site and it can create the chatbot, read your pages and test it through LuckPanda's API and MCP. It prepares the work; going live stays with you.
Use LuckPanda's MCP server (https://luckpanda.app/mcp) to build a website chatbot for me. Ask for my website address, call chatbot_create_from_website with it, wait until the pages are learned (chatbot_source_list), then run a few test questions with chatbot_test_message and show me the answers. Do not put it live: I will do that myself.
Instructions for AI agents
Needs a LuckPanda agent key (Settings › Developers) with the chatbot.manage grant. MCP endpoint: https://luckpanda.app/mcp (Streamable HTTP, bearer key).
chatbot_create_from_website{ url }: creates a draft chatbot named after the site and starts reading it.chatbot_source_list: pages learned, failed or skipped, with a reason for each.chatbot_test_message: asks the bot a question as the owner. Test chats never email anyone.- Going live (
chatbot_updatewith status live) is a person's action; an agent gets APPROVAL_REQUIRED.
See it on your own website
Paste your address and watch the chatbot learn your pages. No account and no card.