Chatterbox field notes

What should your website say when you’re away?

Practical guidance for answering customer questions after hours, without plugins, guesswork or a developer.

“How much does delivery cost?”

Your website should answer from your real pricing—or ask for a number when the answer isn’t there.

  1. TemplateA home cleaning key handover FAQ templateA home cleaning key handover FAQ should explain whether an unattended visit is possible, how an access arrangement is confirmed, who may receive a key, and how it comes back. Keep door codes and addresses out of a public FAQ. A request for unattended access is not permission to enter; a person must confirm the specific plan.
  2. TemplateA pet grooming matted-coat FAQ template that leaves the decision to the groomerA pet grooming matted-coat FAQ should tell owners how to flag tangles before an appointment, what the groomer needs to assess in person, and when the service and charge will be confirmed. Do not promise to brush out every coat or quote a final price from a photograph. Give the owner a clear route to a human decision.
  3. TemplateA photo studio image selection FAQ template for your websiteA photo studio image selection FAQ should tell clients how they will see proofs, which images they may choose, when selections are due, and what happens next. Separate a client's selection from the studio's confirmation and final delivery. Fill in your package terms before publishing; an unanswered request should go to a person, not become an assumed edit.
  4. TemplateAn event venue overtime fee FAQ template for your websiteAn event venue overtime fee FAQ should distinguish the booked end time from the time guests must leave and the time the room must be cleared. State how extra time is requested, how it is charged, and who must confirm it. A request to stay later is not an approved extension.
  5. TemplateA guesthouse quiet hours FAQ template for a peaceful stayA guesthouse quiet hours FAQ should name the actual time window, the spaces it covers, what guests should do about noise, and how to reach the person on duty. Write the rule for your own property, not a borrowed cutoff. A general FAQ can explain expectations; staff must respond to a particular disturbance.
  6. TemplateA guesthouse luggage storage FAQ template for early arrivalsA guesthouse luggage storage FAQ should say whether bags can be left before check-in or after checkout, during which hours, where guests ask, and who confirms each request. Do not treat a general storage rule as a receipt for a particular bag. Publish your actual process; staff must confirm the drop-off and collection arrangements.
  7. TemplateA tailor alteration fitting FAQ template for your shopA tailor alteration fitting FAQ should explain whether a fitting is needed, what garment and shoes to bring, when the tailor can quote, and when sewing begins. Publish the normal process, but leave the fit and feasibility of a particular garment to the person examining it. Adapt the sample answers to your shop's real practice.
  8. TemplateFlorist flower substitution policy FAQ templateA florist's substitution FAQ should say which flowers might change, what may replace them, when the shop asks for permission, and how the customer hears about a change. A bouquet photograph is not a guarantee that every stem is available. Use the wording below only after your florist decides the actual rule and who checks each order.
  9. TemplateA guesthouse late check-in FAQ template for your websiteA guesthouse late check-in FAQ should state the normal arrival window, how guests request a later arrival, and who confirms access arrangements. Do not publish a universal promise that every late arrival is accepted. A website chatbot can repeat the published rule, but a person must confirm the arrangements for a particular booking.
  10. TemplateA laundry stain-removal FAQ template without a removal guaranteeA laundry stain-removal FAQ should explain what the shop needs to inspect, what its standard process includes, and when a customer will hear whether treatment is possible. Do not promise that every mark will disappear. Publish the process you can stand behind; let a person examine the garment before making a promise about its result.
  11. TemplateA print-ready file FAQ template for small print shopsA print-ready file FAQ should say which file types your shop accepts, how customers should set up size and bleed, what to send with the artwork, and who checks a file before printing. Publish your shop's actual specifications, not generic numbers. A submitted file is not a promise that it can be printed unchanged.
  12. TemplateA salon patch-test FAQ template for color appointmentsA salon patch-test FAQ should say which services your rule covers, when and how the test is arranged, who checks the result, and what happens if a client cannot complete it. Use your salon's approved process rather than a borrowed waiting period. A website answer can explain the rule; staff must decide what it means for an individual appointment.
  13. TemplateA pet boarding medication handover checklist for your websiteA pet boarding medication handover checklist should separate the business's general acceptance policy from instructions for one animal. Publish what owners must bring and how to request a review, then have a person confirm the individual instructions before accepting the stay. A website chatbot can explain the published policy; it cannot approve a medication plan.
  14. TemplateA tuition center batch change policy FAQ template for parentsA tuition center batch change policy FAQ should say how a family requests a permanent move, what the center checks before agreeing, when the new schedule begins, and who confirms it. A request is not a seat in another batch. Publish your real rules, and leave each student's availability and level check to staff.
  15. TemplateCustomer-supplied parts: a repair shop FAQ templateA repair shop FAQ about customer-supplied parts should say whether the shop considers them, what information it needs before accepting one, who checks suitability, and which charges and responsibilities must be agreed before work starts. A part brought to the counter is not automatically approved for installation. Use the sample wording below only after your team sets its own policy.
  16. TemplateA bakery preorder cutoff FAQ template for ordinary and late requestsA bakery preorder cutoff FAQ should name the eligible bakes, the exact request deadline, the calendar rule behind it, and the point at which staff confirm availability. Separate routine orders from holiday and late requests. A visitor who meets the deadline has asked in time; they have not reserved a bake until the bakery says yes.
  17. TemplateA repair estimate approval message template for small shopsA repair estimate approval message should identify the item, quote the proposed work and price, say what is not yet authorized, and give the customer a clear way to accept or decline. If inspection changes the scope, send a revised quote for fresh approval before proceeding. Use the template below with your shop's actual terms.
  18. TemplateA course completion certificate FAQ template for training centersA course completion certificate FAQ should explain which course and attendance conditions qualify, who checks the learner's record, when a certificate can be collected, and how errors or missing records are handled. Publish your center's actual rules, not a blanket promise. Chatterbox can surface those rules; a person must confirm an individual learner's result.
  19. TemplateA tuition center waitlist FAQ template for full classesA tuition center waitlist FAQ should tell parents which class is full, how to request consideration, how a place is offered, and when that offer expires. Being on a list is not enrollment. Publish your actual order and deadlines; a person must check the class and confirm a place.
  20. TemplateA bakery allergen FAQ template that does not promise too muchA bakery allergen FAQ should separate known ingredients from the risk of shared equipment and from questions your team must check for a particular order. State your actual handling practices, not a blanket safety promise. Chatterbox can repeat published bakery information, but a customer's individual allergy question needs a person to verify it.
  21. TemplateA salon late-arrival policy FAQ template for your websiteA salon late-arrival policy FAQ should tell clients when to notify the salon, whether a shorter service is possible, who decides if the appointment must move, and what happens to any fee or deposit. Publish only the rules your team has approved. A website chatbot can repeat the policy, but a person must confirm what can happen with today's slot.
  22. TemplateA repair turnaround time FAQ template for your workshopA repair turnaround time FAQ should say when the estimate starts, which jobs it covers, what can change the window, and how the shop confirms collection. An estimated window is not a ready notice. Publish the ordinary rule, then let a person check the timing of an individual repair.
  23. TemplateA parent progress update FAQ template for tuition centersA parent progress update FAQ should say when families hear from the center, what an update covers, who can receive it, and how to ask about a particular child. Publish the routine process, not a child's results. Chatterbox can explain that process from your approved content; an individual progress question belongs with a teacher.
  24. TemplateA home service call-out fee FAQ template for your websiteA home service call-out fee FAQ should separate the cost of sending someone to the customer's address from inspection, parts, and repair. State the covered area, when the visit charge becomes payable, and what happens if access or cancellation changes the trip. Publish your actual terms; leave job-specific prices to the team.
  25. TemplateAn appointment rescheduling policy template for a small businessAn appointment rescheduling policy should tell customers how to request a change, when notice is due, what happens to any advance payment, and who confirms the new time. Publish the standard rule without implying that a requested slot is reserved. Leave unusual cases for a person to decide.
  26. TemplateA tuition fee installment FAQ template for your center's websiteA tuition fee installment FAQ should say which courses offer installments, what each payment covers, when each payment is due, and what happens if a family cannot pay on time. Use your center's approved terms rather than borrowing another center's schedule. Chatterbox can repeat those terms, but a person must decide an individual account question.
  27. TemplateA missed-class makeup policy FAQ template for tuition centersA missed-class makeup policy FAQ should tell families how to report an absence, whether a replacement lesson is offered, which deadline or class type changes that rule, and who confirms an individual request. Publish only your center's approved terms. Chatterbox can surface those terms and request contact details when the supplied material does not settle the case.
  28. TemplateA device intake checklist for a repair shop counterA repair shop intake checklist should record the device, reported fault, accessories left behind, visible condition, and a way to contact the owner. Keep the inspection charge and permission to begin repair separate. Publish the general drop-off instructions; have a person confirm the details of an individual device at the counter.
  29. TemplateA trial class FAQ template for a tutoring centerA trial class FAQ should tell parents which lesson they can observe or attend, whether it costs anything, how to request a place, and what happens afterward. Use your center's real rules. Chatterbox can answer from those published terms, but a person must confirm an individual child's place and suitability.
  30. TemplateA customer pickup policy FAQ template for repair shopsA customer pickup policy FAQ should say when an item can be collected, where to go, what proof the collector needs, and what happens if someone else arrives. Publish only the rules your shop actually follows. Chatterbox can repeat those rules from your content, but a person should confirm whether one particular repair is ready.
  31. TemplateQuotation validity wording for a small-business websiteA quotation validity notice should name the quote's expiry date, what work and materials it covers, and what happens when a customer accepts after that date. Publish the general rule, but let a person check an individual expired quote. Chatterbox can repeat the written rule without promising that an old price still stands.
  32. TemplateA repair diagnostic fee FAQ template for your websiteA repair diagnostic fee FAQ should say what inspection costs, what that fee covers, when it is payable, and whether it is credited against a repair. State who authorizes the work after a quote. Chatterbox can repeat your published terms, but an unusual fault or disputed charge still needs a person.
  33. TemplateA gift card terms FAQ template for your business websiteA useful gift card terms FAQ explains where the card can be used, how long it remains valid, what happens to a remaining balance, and which cases need a person. Replace every bracketed prompt with an approved rule. Have the final terms reviewed for the laws that apply to your business.
  34. TemplateA print artwork approval checklist for customer ordersA print artwork approval checklist should name the file supplied, the checks your team performs, what the proof represents, who may approve it, and which changes require a new proof. Record approval before production begins. Publish the ordinary process clearly, while leaving file-specific quality and deadline decisions to a person.
  35. Use caseAnswering location and directions questions on your websiteChatterbox can answer location and directions questions from details your business has published, including an address, entrance, landmark, or parking instruction. If that material does not settle a temporary route change or an unusual access question, it asks for contact details instead of inventing directions.
  36. TemplateA holiday opening hours FAQ template for your websiteA useful holiday opening hours FAQ names the date, location, open or closed status, exact hours, and when normal timings return. Publish the exception before customers travel. If a date or branch is not covered, leave the decision with a person instead of letting a general hours page imply an answer.
  37. TemplateA custom order FAQ template for your business websiteA custom order FAQ should explain what customers may change, what information you need, how approval works, and which requests require a quote. Keep standard options separate from exceptions. Chatterbox can answer from the rules you publish and collect contact details when a request still needs a person to decide.
  38. TemplateA website chatbot privacy notice template for small businessesA website chatbot privacy notice should explain what visitors may type, which contact details the widget requests, why a person receives them, and where to find the full privacy policy. Verify retention, sharing, cookies, and visitor-rights wording for your own setup instead of copying promises your business cannot confirm.
  39. TemplateA product care instructions template for your websiteProduct care instructions should identify the exact item or material, explain routine cleaning, name what to avoid, and separate ordinary care from damage that needs inspection. Publish one approved version. Chatterbox can answer from those instructions and collect contact details when a customer's case is not covered.
  40. Use caseAnswering product compatibility questions on your websiteChatterbox can answer product compatibility questions when your business's supplied material names the exact products, models, sizes, or conditions that work together. If the content does not settle a visitor's combination, it asks for contact details instead of turning a similar model into a fit guarantee.
  41. Use caseAnswering size and fit questions on your websiteChatterbox can answer size and fit questions from dimensions, size guides, and measurement rules your business has supplied. It can show the source behind a published measurement. When that material does not settle whether an item fits a particular person or space, it asks for contact details instead of turning a general guide into a promise.
  42. TemplateA minimum order quantity FAQ template for your websiteA minimum order quantity FAQ should state the smallest standard order, the product or variation it applies to, whether samples are available, and which lower quantities need a separate quote. Chatterbox can surface those published rules and collect contact details when a buyer's request still needs a person to decide.
  43. Use caseAnswering advance payment and deposit questions on your websiteChatterbox can answer advance payment and deposit questions from terms your business has published. It can repeat the stated amount, due date, purpose, and refund rule. When the material does not settle a particular order or exception, it asks for contact details instead of inventing a payment commitment.
  44. Use caseAnswering stock availability questions on your websiteChatterbox can answer stock availability questions only when the business's supplied content settles them. It can surface a published availability rule or product statement. When a visitor asks whether an item is available right now and the material does not confirm that, it asks for contact details instead of inventing a stock promise.
  45. TemplateHow to follow up website chatbot leadsFollow up a website chatbot lead by reading the unanswered question before you call, checking the current business information, and answering that question first. Record whether it was a one-off case or a gap worth fixing on the website. Do not make the visitor repeat the whole conversation.
  46. TemplateA pre-appointment instructions template for your websiteA useful pre-appointment instructions template tells a customer what to bring, what to do beforehand, when to arrive, and which exceptions need confirmation. Keep requirements separate from suggestions. Publish one approved version so a website chatbot can repeat the instructions without turning a standard step into advice for every situation.
  47. TemplateA course eligibility FAQ template for your training websiteA course eligibility FAQ should state the required age or class level, prior knowledge, equipment, documents, language, and attendance rules. Keep each condition beside the course it applies to. Chatterbox can answer from those published rules and collect contact details when a learner's situation still needs a person to decide.
  48. Use caseAnswering what-is-included questions on your websiteChatterbox can answer what-is-included questions from service or package details your business has published. It can repeat the stated scope and conditions. If the material does not settle whether an add-on, custom request, or unusual case is included, it asks for contact details instead of turning a standard package into a promise.
  49. Use caseAnswering delivery-time questions on your websiteChatterbox can answer delivery-time questions from estimates your business has published. It can repeat the stated dispatch window, delivery range, and conditions. If the material does not settle when a particular order will arrive, it asks for contact details instead of turning a general estimate into a promise.
  50. Use caseAnswering shipping and delivery questions on your websiteChatterbox can answer shipping and delivery questions from terms your business has published. It can surface stated areas, charges, dispatch times, and delivery estimates. When the material does not settle a particular address, delay, or order, it asks for contact details instead of inventing a delivery promise.
  51. TemplateHow to trace a wrong chatbot answer back to its sourceTo trace a wrong chatbot answer, preserve the visitor's question, reply, and displayed source passage as one incident. Decide whether the source is stale, irrelevant, incomplete, or stretched beyond what it says. Repair that cause, then replay the question and a boundary case the chatbot should refuse.
  52. TemplateHow to verify a website chatbot answer against its sourceVerify a website chatbot answer by opening the source passage shown with it, reading the surrounding rule, and checking that the page is current. If the source does not support the reply, correct or remove the source, refresh the chatbot knowledge, and test the question again.
  53. Use caseAnswering warranty questions on your websiteChatterbox can answer warranty questions from terms your business has published. It can surface the stated period, coverage, exclusions, and claim steps. If the material does not settle whether a particular fault or purchase qualifies, it asks for contact details instead of approving or rejecting the claim.
  54. Use caseAnswering GST and tax invoice questions on your websiteChatterbox can answer GST and tax invoice questions from information your business has published. It can repeat whether a listed price includes GST and whether you provide a tax invoice. If the website does not settle a rate, exemption, invoice detail, or unusual transaction, it asks for contact details instead of inventing tax advice.
  55. Use caseAnswering payment method questions on your websiteChatterbox can answer payment method questions from information your business has published. It can repeat whether you accept UPI, cards, cash, bank transfer, or another stated option. If the website does not settle a deposit, surcharge, or exception, it asks for contact details instead of inventing a payment promise.
  56. Use caseAnswering opening-hours questions on your website after closingChatterbox can answer opening-hours questions from times your business has published. It works outside business hours without anyone attending the chat. If the website does not settle a holiday, appointment, or exception, it says it cannot find the answer and asks for contact details instead of guessing that you are open.
  57. TemplateWhen to re-crawl website content for your chatbotRe-crawl website content after you change a fact the chatbot may repeat, such as a price, opening time, service area, or policy. Update the primary source, remove stale copies, run the crawl, then test the changed answer and one edge case. Chatterbox allows each source to be re-crawled once a day.
  58. IntegrationHow to connect a website chatbot to an AI tool with MCPConnect an AI tool to Chatterbox through its MCP server at https://chatterbox.cbrspn.cloud/api/v1/mcp/. The endpoint accepts JSON-RPC 2.0 requests over HTTP POST and uses a bearer token. Keep that token private, add the endpoint and authorization header to your MCP client, then test the connection before using it with business information.
  59. TemplateHow to update a website chatbot after your content changesAfter changing a price, policy, service area, or opening time on your website, refresh the matching chatbot source and test the changed answer. Chatterbox can re-crawl a website source once a day. Check the source passage, then ask an edge-case question that should still reach a person.
  60. TemplateWhat to check when robots.txt blocks your website chatbotIf a website chatbot crawl fails or returns nothing, check robots.txt before changing the chatbot. ChatterboxBot obeys that file, and a rule that blocks it—including a blanket block for all crawlers—stops the crawl before it starts. Add a specific allow rule, then run the crawl again.
  61. TemplateHow to build a chatbot knowledge base from your website contentBuild a website chatbot knowledge base from four sources: crawl the pages customers already read, upload useful documents, paste details that need a stable home, and type direct question-and-answer pairs for common gaps. Remove contradictions first, then re-crawl a source when its information changes.
  62. TemplateHow to give a website chatbot information that is not on your siteGive a website chatbot information that is not on your public pages by uploading a file, pasting text, or adding hand-written question-and-answer pairs. Use one clear source for each fact. If the material still does not settle a visitor's question, the chatbot should leave it for a person.
  63. Use caseHow to capture leads with a website chatbot when an answer runs outA website chatbot can capture a lead when it cannot answer a visitor's question. Chatterbox admits the gap, collects the visitor's name, phone, and email, then sends the lead to the dashboard and inbox so a person can follow up with the answer.
  64. Use caseA Hindi AI chatbot that also handles the Hinglish people actually typeIndian customers rarely pick one language per sentence. Chatterbox replies in English, Hindi and Hinglish out of the box, in whichever the visitor used, and paid plans translate the knowledge base into further languages. Answer quality still depends on what your site published.
  65. Use caseA white-label chatbot web agencies can sell under their own brandChatterbox's agency plan is ₹3,000 a month flat. It replaces the widget credit with your own brand on every client site, gives each client its own isolated knowledge base, and takes 15% off every client tenant's plan price so the margin stays with you.
  66. IntegrationAn AI chatbot for a PHP website you would rather not rebuildChatterbox runs on a PHP website as one script tag in the footer template. Nothing runs in PHP, so there is no Composer package, no PHP version floor, no model key in your config file and no queue to babysit. The AI stack stays off your server.
  67. IntegrationAn AI chatbot for a Shopify store, installed with a script tagChatterbox goes on a Shopify store as one script tag in theme.liquid. There is no Shopify App Store listing and no live product or inventory sync today. It answers policy, shipping, returns and pre-sales questions from the pages it has crawled, and captures the lead when it cannot.
  68. Use caseAn AI chatbot for a small business in IndiaAn AI chatbot for a small business in India has to answer from what the business has published, take a phone number when it cannot, and cope with customers who type in Hinglish. Chatterbox does those three things, installs with one script tag, and starts free.
  69. Use caseAnswering cancellation and refund policy questions on your websiteChatterbox can answer cancellation and refund policy questions from terms your business has published. When the website does not cover a visitor's situation, it says it cannot find the answer and asks for contact details instead of inventing an exception.
  70. PostChatbot cost for a small business in India: what actually creates the billSeven things drive what a chatbot costs: model usage per answer, how the vendor counts a conversation, indexed pages, re-crawls, extra languages, WhatsApp platform fees and per-seat charges. Knowing which ones apply to you is how you compare two quotes that look nothing alike.
  71. PostHow a web agency can offer AI chatbots to clients without building AI infrastructureThe billable work in an agency chatbot service is the content, not the install. Package it as a setup fee plus a line on the maintenance contract, fix the client's published answers first, and write down where your support ends before the first client asks you to answer their customers.
  72. TemplateHow to add an AI chatbot to an existing PHP websiteFind the one footer template every page includes, paste the script tag before the closing body tag, allow the crawler in robots.txt, crawl your content, and test on staging first. The install is ten minutes. Preparing what the bot answers from takes the afternoon.
  73. Use caseWebsite chatbot pricing in India, and what Chatterbox chargesChatbot pricing in India comes in four shapes: per seat, per resolution, per conversation and flat. Chatterbox is flat and in rupees. Free is ₹0, Starter ₹999 a month, Pro ₹2,999, and the agency plan ₹3,000. Every plan is capped, so the bill cannot spike.
  74. PostWhat a chatbot should do when it doesn't know the answerA chatbot that doesn't know the answer has four honest moves: refuse, ask a clarifying question, show the source it did find, or take contact details for a person. A confident guess is the only genuinely expensive option, because the customer acts on it.
  75. PostWhat crawling a business website reveals about its chatbot knowledge baseA crawl audit reads every public page, extracts the questions each one answers, then clusters them. What surfaces is rarely a knowledge base. It is duplication, prices that disagree with each other, policies nobody has updated, and the customer questions the site never answered at all.
  76. PostWhatsApp chatbot vs website chatbot: which should a small business choose?A website chatbot catches the stranger who found you on Google and has not decided to contact you yet. A WhatsApp chatbot serves the customer who already has your number. They solve different halves of the funnel, and the setup, rules and costs are nothing alike.
  77. PostWhy AI chatbots on websites hallucinate, and what source-backed answers fixA language model produces the most plausible continuation, and plausible is not the same as true. Grounding an answer in passages from your own content and showing them cuts the failure rate a long way. It does not reach zero, because a real source can still be summarized wrong.
  78. Use caseAnswering service-area questions on your websiteChatterbox can answer a website visitor's service-area question from coverage details your business has published. If your pages do not establish whether you serve that location, it says it cannot find the answer and asks for contact details instead of guessing.
  79. TemplateHow to test a website chatbot before launchTest a website chatbot with questions it should answer, questions it should refuse, and questions your site answers badly. A safe launch means correct published information is used, missing information is not invented, and the visitor has a clear route to a person.
  80. TemplateWhat a website chatbot should say when it does not knowWhen a website chatbot does not know, it should say so plainly, avoid filling the gap with a guess, and offer a clear next step. Ask for the visitor's contact details so a person can answer the question.
  81. Use caseRunning one chatbot account across many client sites without mixing up their dataAn agency managing multiple client sites with Chatterbox keeps every client's chatbot answers separate. Each client's knowledge base stays isolated from every other client's, and agency controls let one person manage all the sites together.
  82. Use caseWhen a visitor asks Chatterbox to book an appointmentChatterbox does not book appointments itself. It answers scheduling questions using whatever your website has already published — hours, service days, typical lead times — and when a visitor needs an actual slot, it asks for their contact details instead of guessing one for you.
  83. TemplateA checklist of what to publish before you turn on a chatbotA chatbot answers from what your website already says, so publish the answers first. Write down the twenty questions customers actually ask, check that each one has a real answer somewhere on the site, and delete the pages that contradict each other. Then install it.
  84. Use caseAdding a chatbot to a shared-hosting websiteIf you manage your website through cPanel or a shared-hosting file manager, you can add Chatterbox without a plugin or build step. Paste one script tag before the closing body tag. The widget is under 15KB.
  85. Use caseAnswering customer pricing questions after hoursA customer may ask about price long after you have closed for the day. Chatterbox replies using pricing published on your website. If the answer is not there, it asks for contact details so you can follow up yourself.