luckpandaAnswer the questions that stop a checkout
A shopper with a doubt about size or delivery rarely writes an email. They leave. The chatbot answers from your shipping, returns and size pages while they are still on the product. Connect your order API and it can also tell them where their order is.
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 from your policy and product pages
- Order status through a read-only connection
- Free to set up and test
What shoppers ask on a product page
| What they type | The page that answers it | If that page does not exist |
|---|---|---|
| Delivery to Guwahati how many days? | Shipping page with zones and times | It says it does not know and offers a person |
| COD available? | Payment or shipping FAQ | It does not guess yes or no |
| Chest 40 inch, M or L? | Size chart and fit notes | It does not guess a size |
| Is this pure cotton? Machine wash ok? | Product page, care guide | It does not assume the fabric or care |
| Exchange possible if size doesn't fit? | Returns and exchange policy | It hands over rather than invent a rule |
| Any coupon code? | Offers page, if you have one | It says no code is listed and never makes one up |
The third column is the honest part. The bot is told to say so when your content has nothing, not to fill the gap.
"Where is my order", from your own system
This needs a live connection. Without one, the bot knows your pages: it can explain shipping times, but not where a parcel is.
- Get a read-only endpointYour store or your developer provides a URL that returns one order's status, such as https://api.yourstore.example/orders/{order_id}?phone={phone}. An MCP server that does the same also works.
- Add it as a connectionPaste the URL template and an auth header. Each {placeholder} becomes something the bot asks the shopper for. The key is encrypted and never shown to the model.
- Describe itWrite one line on what it returns and when to use it. The bot reads the description, never your credentials.
- Test itRun Test connection with a real order number and read the response. Every call the bot makes is in the call log.
Ask for two things, such as the order number and the phone number on the order, and have your endpoint check both. An order number alone is easy to guess, and the bot looks up whatever the visitor types.
One answer from the store's system, one from its policy page
Sample conversation on a fictional clothing brand, Kapas and Co.
The bot did not start the exchange. It pointed to where the shopper can do it, and offered a person. Changing an order stays with your team.
Shopify, WooCommerce or your own code
There is no app or plugin to install. You paste one line of script before the closing body tag in your theme or template, and list your shop's address as an allowed website. Any store that lets you add a script can show the chat.
For order status, the connection is to an API, not to the platform. If your platform or your developer gives you a read-only endpoint or an MCP server for orders, the bot can use it. If not, it answers from your pages and hands order questions to your team.
A large catalogue is better as a file than as a crawl. A website crawl reads up to 50 pages, so upload a CSV of products with the details shoppers ask about: fabric, fit, care, delivery time. A CSV can have up to 5,000 rows, and the bot finds each row on its own.
Check these before a busy week
- Shipping times and order cut-offs for the sale are on the site, and you have pressed Re-crawl.
- Offer terms are written on a page. If there are no codes, the bot should say so.
- Handoff topics include refund, cancel, damaged and damage, so those always reach a person.
- Your team's hours are set, and alert emails go to whoever handles support.
- You have asked it ten real questions from last month's inbox and read what it searched for.
What a person still does
- It does not cancel orders, start returns, issue refunds or apply discounts.
- It does not take payments. It knows stock and prices only from your pages, or from a connection that returns them.
- A connection can write to your system only if you untick Read-only, and there is no approval step for each call yet. Keep order connections read-only.
- It does not chase abandoned carts or message shoppers on WhatsApp or by email.
- Pages that build their text with JavaScript in the browser may be skipped as having no readable text. The source lists each skipped page and why.
Questions
Does it work with Shopify?
Yes, as one line of script in your theme. There is no Shopify app. For order status you connect an API or MCP server that returns order data; without it, the bot answers from your pages.
Can it tell customers where their order is?
Yes, once you connect a read-only API or MCP server that returns order status. The bot asks the shopper for the values your URL needs, such as order number and phone, and calls it.
Will it hand out discount codes?
Only codes written on your site or in your sources, and it is told never to invent one. If you do not want codes shared in chat, keep them off the pages it reads.
Can it process a return or a refund?
No. It explains your returns policy and points to where the shopper starts a return. A person handles refunds and changes.
What does it cost?
Building and testing are free. Putting it on your website needs the Chatbot plan: ₹249 a month, or ₹2,241 a year, for up to 10 websites on one account.
Related pages
- Live order and account dataLet the chatbot look up an order, stock or a plan in your own system, instead of replying "please email us".
- Customer supportAnswer the questions your site already answers, and hand the rest to a person.
- After-hours enquiriesEnquiries arrive at night when nobody is there. Answer them, keep the lead, and call back in the morning.
- 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.