[{"data":1,"prerenderedAt":16},["ShallowReactive",2],{"blog-post-combine-faq-and-catalog":3},{"id":4,"slug":5,"title":6,"metaDescription":7,"heroImageUrl":8,"languageCode":9,"publishedAt":10,"updatedAt":11,"contentHtml":12,"faqJsonLd":13,"keywords":14},1026633,"combine-faq-and-catalog","How to Combine FAQ and Catalog Data in One AI Assistant","Learn how to combine your FAQ and product catalog in one website assistant: what to include, how to keep prices current, and what to do when sources conflict.","https:\u002F\u002Fmedia.babylovegrowth.ai\u002Fblog-images\u002Forganization-42511\u002F1793161995672_Shop-owner-checking-a-bottle-s-product-details.jpeg","en","2026-10-29T02:30:09.381Z","2026-10-29T04:22:47.436Z","\u003Cp>To combine your FAQ and your product catalog, give the assistant both as knowledge sources, decide which one wins when they disagree, and keep the catalog on an automatic sync so prices and stock never go stale. The FAQ explains how your business works: shipping, returns, warranty, sizing policy. The catalog states what you sell right now: names, variants, prices, availability. A visitor asking “Can I return the blue one if it doesn’t fit, and is it in stock in a medium?” needs both in a single answer.\u003C\u002Fp>\n\u003Cp>This guide shows how to prepare each source, connect them, set rules for conflicts and gaps, test the result, and hand off to a human when the evidence runs out.\u003C\u002Fp>\n\u003Cdiv data-blg-cta=\"after_tldr\" data-blg-cta-layout=\"split\" style=\"margin:28px 0;font-family:-apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;box-sizing:border-box;\">\u003Cdiv style=\"border-radius:26px;padding:min(22px,3.2vw);background:radial-gradient(circle at 100% 0%,#d7f2fc 0 150px,rgba(255,255,255,0) 151px),radial-gradient(circle at 0% 100%,#d7f2fc 0 130px,rgba(255,255,255,0) 131px),linear-gradient(180deg,#e4f6fd 0%,#f2fbfe 100%);\">\u003Cdiv style=\"background:#ffffff;border-radius:18px;box-shadow:0 12px 34px rgba(0,0,0,0.13);overflow:hidden;\">\u003Cdiv style=\"display:flex;flex-wrap:wrap;\">\u003Cdiv style=\"flex:1 0 36%;min-width:220px;box-sizing:border-box;padding:30px 76px 30px 26px;color:#ffffff;background:linear-gradient(104deg,#0b3f51 0%,#041a21 82%,rgba(0,0,0,0) 82.15%);\">\u003Cdiv style=\"margin:0 0 14px;\">\u003Cspan style=\"display:inline-block;max-width:100%;box-sizing:border-box;border-radius:999px;padding:6px 13px;font-size:12px;font-weight:800;letter-spacing:0.1em;text-transform:uppercase;line-height:1.3;background:#ffffff;color:#0e556e;\">Konvuno\u003C\u002Fspan>\u003C\u002Fdiv>\u003Cdiv style=\"font-size:12px;opacity:0.75;\">konvuno.com\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv style=\"flex:999 1 300px;min-width:0;padding:30px 28px;\">\u003Cdiv style=\"font-size:23px;font-weight:800;line-height:1.2;letter-spacing:-0.01em;color:#1f2937;margin:0;\">Answer Product and Policy Questions Together\u003C\u002Fdiv>\u003Cdiv style=\"width:56px;height:6px;border-radius:3px;background:#1FB8EF;margin:12px 0 14px;\">\u003C\u002Fdiv>\u003Cdiv style=\"font-size:15px;line-height:1.55;color:#64748b;margin:0 0 22px;\">Konvuno answers from your FAQs and product catalog, with automatic catalog syncs from WooCommerce or Google Merchant and Facebook feeds.\u003C\u002Fdiv>\u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002F\" style=\"display:inline-flex;align-items:center;gap:9px;border-radius:10px;font-weight:700;font-size:15px;text-decoration:none;padding:13px 22px 13px 26px;background:#1FB8EF;color:#ffffff;\">Explore Konvuno\u003Csvg width=\"17\" height=\"17\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"#ffffff\" stroke-width=\"2.6\" stroke-linecap=\"round\" stroke-linejoin=\"round\" style=\"display:block;flex:0 0 auto;\">\u003Cpath d=\"M5 12h14\"\u002F>\u003Cpath d=\"m12 5 7 7-7 7\"\u002F>\u003C\u002Fsvg>\u003C\u002Fa>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2 id=\"tldr\" tabindex=\"-1\">TL;DR\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Treat the FAQ as the source for policies and the catalog as the source for product facts, prices and stock. Write that split down before you connect anything.\u003C\u002Fli>\n\u003Cli>Feed the catalog from a live source (WooCommerce, or a Google Merchant or Facebook product feed) so prices and availability update on their own. Keep the FAQ for things that change rarely.\u003C\u002Fli>\n\u003Cli>Set a source hierarchy. When two sources conflict and neither clearly wins, the assistant should say so and hand off, not guess.\u003C\u002Fli>\n\u003Cli>Test with real visitor questions that need both sources, in every language you serve, before the widget goes live.\u003C\u002Fli>\n\u003Cli>Review the questions the assistant could not answer every week, and fix the source, not just the reply.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"table-of-contents\" tabindex=\"-1\">Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"#what-combining-faq-and-catalog-actually-means\">What combining FAQ and catalog actually means\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#decide-what-belongs-in-the-faq-and-what-belongs-in-the-catalog\">Decide what belongs in the FAQ and what belongs in the catalog\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#connect-the-sources\">Connect the sources\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#keep-prices-and-stock-current\">Keep prices and stock current\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#set-a-source-hierarchy-before-conflicts-happen\">Set a source hierarchy before conflicts happen\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#hand-off-to-a-human-at-the-right-moment\">Hand off to a human at the right moment\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#test-the-combined-knowledge-before-visitors-do\">Test the combined knowledge before visitors do\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#our-perspective\">Our perspective\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#try-it-on-your-own-faq-and-catalog\">Try it on your own FAQ and catalog\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#faq\">FAQ\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#sources\">Sources\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"what-combining-faq-and-catalog-actually-means\" tabindex=\"-1\">What combining FAQ and catalog actually means\u003C\u002Fh2>\n\u003Cp>Most small sites keep these two kinds of content apart. The FAQ is a page of questions and answers someone wrote once. The catalog lives in the store or in a product feed and changes daily. A basic chatbot reads one or the other.\u003C\u002Fp>\n\u003Cp>Combining them means the assistant can pull from both within one conversation and build one coherent reply. Take a shopper who asks whether a jacket ships to Canada and whether it comes in black. The shipping answer comes from your FAQ or shipping policy. The color and stock answer comes from the product record. If the assistant only has the FAQ, it can’t confirm black. If it only has the catalog, it can’t explain the shipping rules. Shoppers don’t separate these questions, so your assistant shouldn’t either.\u003C\u002Fp>\n\u003Cp>There are three practical layers:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Policy knowledge:\u003C\u002Fstrong> FAQs, shipping and returns pages, warranty terms, uploaded documents such as PDFs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Product knowledge:\u003C\u002Fstrong> the catalog, with titles, descriptions, variants, prices, availability and images.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rules:\u003C\u002Fstrong> which source wins, what the assistant does when it finds nothing, and when it passes the conversation to a person.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The third layer is the one most owners skip, and it causes most of the wrong answers.\u003C\u002Fp>\n\u003Ch2 id=\"decide-what-belongs-in-the-faq-and-what-belongs-in-the-catalog\" tabindex=\"-1\">Decide what belongs in the FAQ and what belongs in the catalog\u003C\u002Fh2>\n\u003Cp>The cleanest setups avoid duplicating facts. If a price appears in your FAQ and in your catalog, one of them will be wrong within a month.\u003C\u002Fp>\n\u003Cdiv class=\"kv-doc-table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Information\u003C\u002Fth>\n\u003Cth>Put it in\u003C\u002Fth>\n\u003Cth>Why\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Price, sale price\u003C\u002Ftd>\n\u003Ctd>Catalog\u003C\u002Ftd>\n\u003Ctd>Changes often; the feed keeps it current\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Stock and availability\u003C\u002Ftd>\n\u003Ctd>Catalog\u003C\u002Ftd>\n\u003Ctd>Changes with every order\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Sizes, colors, variants\u003C\u002Ftd>\n\u003Ctd>Catalog\u003C\u002Ftd>\n\u003Ctd>Each variant has its own price and stock\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Materials, dimensions, compatibility\u003C\u002Ftd>\n\u003Ctd>Catalog (product description or attributes)\u003C\u002Ftd>\n\u003Ctd>Belongs to one product\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Shipping rules and delivery times\u003C\u002Ftd>\n\u003Ctd>FAQ or policy page\u003C\u002Ftd>\n\u003Ctd>Applies across products\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Returns and refunds\u003C\u002Ftd>\n\u003Ctd>FAQ or policy page\u003C\u002Ftd>\n\u003Ctd>Same\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Warranty terms\u003C\u002Ftd>\n\u003Ctd>FAQ, plus a line in the product record if it differs\u003C\u002Ftd>\n\u003Ctd>Policy, with exceptions per product\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>How to care for or set up a product\u003C\u002Ftd>\n\u003Ctd>FAQ or uploaded manual\u003C\u002Ftd>\n\u003Ctd>Often long and shared by a product line\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>A good rule: if the answer changes when the product changes, it’s catalog data. If it changes when your business policy changes, it’s FAQ data.\u003C\u002Fp>\n\u003Ch3 id=\"write-the-faq-from-real-questions\" tabindex=\"-1\">Write the FAQ from real questions\u003C\u002Fh3>\n\u003Cp>Don’t invent questions. Pull them from support emails, returns, reviews, pre-sales chats and your site search. \u003Ca href=\"https:\u002F\u002Fkovmere.com\u002Fresources\u002Fhow-to-add-faqs-and-detailed-specs-to-product-pages-for-ai-answers\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Kovmere’s guide to product-page FAQs\u003C\u002Fa> recommends exactly this, with short factual answers and honest statements of what a product is not suited for. \u003Ca href=\"https:\u002F\u002Fwww.paz.ai\u002Fglossary\u002Fproduct-qa-ai-shopping\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Paz.ai\u003C\u002Fa> lists fit and sizing, compatibility, materials, care, shipping and returns as the questions shoppers ask again and again, so start there.\u003C\u002Fp>\n\u003Cp>If you need a process for this, we wrote one: \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fwrite-effective-faqs\" target=\"_blank\" rel=\"noopener\">writing effective FAQs from customer data\u003C\u002Fa>. For a list of what visitors typically ask, see \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fchatbot-top-questions\" target=\"_blank\" rel=\"noopener\">what customers ask a chatbot and how to answer\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"make-product-facts-complete\" tabindex=\"-1\">Make product facts complete\u003C\u002Fh3>\n\u003Cp>The assistant can only repeat what exists. For each product, the Kovmere guide suggests covering the full name, model number or GTIN, dimensions and weight, materials, compatibility, variants, box contents, certifications, care, warranty and who the product is not for. You don’t need all of them for every item, but gaps are where the assistant either says “I don’t know” or, worse, fills in something plausible.\u003C\u002Fp>\n\u003Cp>If your product pages also use FAQ markup so search engines and language models can read them, this \u003Ca href=\"https:\u002F\u002Fbabylovegrowth.ai\u002Fblog\u002Ffaq-schema-seo\" target=\"_blank\" rel=\"noopener\">five-step FAQ schema playbook\u003C\u002Fa> covers how to structure that content. The same clarity helps your assistant.\u003C\u002Fp>\n\u003Ch2 id=\"connect-the-sources\" tabindex=\"-1\">Connect the sources\u003C\u002Fh2>\n\u003Cp>The catalog side should never be typed in by hand if you can avoid it. Konvuno syncs product catalogs automatically from WooCommerce or from any Google Merchant or Facebook product feed, so the assistant reads the same data your store and ad channels already use. The FAQ side can be pasted in, pulled from your website content, or uploaded.\u003C\u002Fp>\n\u003Cp>A typical setup runs like this:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Install the widget.\u003C\u002Fstrong> One script tag on your site; the rest is configured in the hosted dashboard.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Connect the catalog.\u003C\u002Fstrong> Point it at your WooCommerce store or your feed URL.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add policy knowledge.\u003C\u002Fstrong> Import your FAQ and key pages, and add any PDFs such as size charts or manuals. \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fupload-pdf-to-chatbot\" target=\"_blank\" rel=\"noopener\">What works and what breaks when uploading a PDF\u003C\u002Fa> is worth reading first.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set source priorities.\u003C\u002Fstrong> More on this below.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preview and test\u003C\u002Fstrong> before you publish.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>For a longer walkthrough of each connection type, see \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fconnect-data-to-chatbot\" target=\"_blank\" rel=\"noopener\">how to connect your data to a website chatbot\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"what-a-good-feed-looks-like\" tabindex=\"-1\">What a good feed looks like\u003C\u002Fh3>\n\u003Cp>Feed formats share a common shape. Stripe’s \u003Ca href=\"https:\u002F\u002Fdocs.stripe.com\u002Fagentic-commerce\u002Fconcepts\u002Fcatalog-feed\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">catalog feed documentation\u003C\u002Fa> describes each product or variant as a row with structured titles, descriptions, identifiers, pricing, fulfillment details and media. The point for you: every product and variant needs a stable ID. Without IDs, updates can’t be matched to the right item, and the assistant may quote an old price for a new variant.\u003C\u002Fp>\n\u003Cp>Variants deserve special care. A shirt isn’t one product when it comes in five sizes and three colors, each with its own stock. Our guide to \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fchatbot-product-variants\" target=\"_blank\" rel=\"noopener\">getting size, color and price right in chatbot product variants\u003C\u002Fa> goes through the common traps. If your store sells apparel, also read \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fsize-guide-chatbot-answers\" target=\"_blank\" rel=\"noopener\">how fresh feeds and honest fit advice shape size-guide answers\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"keep-prices-and-stock-current\" tabindex=\"-1\">Keep prices and stock current\u003C\u002Fh2>\n\u003Cp>A catalog that was right on Monday and wrong on Thursday does more damage than no catalog. Visitors who are told an item is in stock and then can’t buy it don’t blame the data feed. They blame you.\u003C\u002Fp>\n\u003Cp>Three documented practices apply to any store:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Use stable IDs and partial updates.\u003C\u002Fstrong> Stripe’s documentation says inventory updates must reference IDs already in the main feed, and it recommends frequent partial updates for changed items rather than resending everything.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Match the refresh rate to how fast the data changes.\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fhelp.productsup.com\u002Fdocs\u002Ffundamentals\u002Fkeeping-data-up-to-date\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Productsup’s documentation\u003C\u002Fa> says prices and stock should refresh on a schedule that fits their rate of change, with event triggers and delta updates catching changed records sooner.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Watch the sync.\u003C\u002Fstrong> The same page recommends monitoring for failed imports, sudden changes in item count and unmapped values. \u003Ca href=\"https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fcommerce-merchant-services\u002Fuser-guides\u002Fdata-services\u002Fcatalog-sync\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Adobe Commerce’s catalog sync documentation\u003C\u002Fa> similarly describes dashboard statuses for successful, failed and in-progress syncs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For a small shop, this translates into two habits. First, make your store the single place where prices and stock are edited, and let the feed carry them everywhere else. Second, glance at the sync status regularly, and especially after a bulk price change or a product import. A sudden drop in product count is usually a broken feed, not a sold-out store.\u003C\u002Fp>\n\u003Ch2 id=\"set-a-source-hierarchy-before-conflicts-happen\" tabindex=\"-1\">Set a source hierarchy before conflicts happen\u003C\u002Fh2>\n\u003Cp>Conflicts are normal. Your FAQ says free shipping over $50, and a product record says “ships free” on an item priced at $40. Or the FAQ lists a 30-day return window and an old PDF says 14.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Fmedia.babylovegrowth.ai\u002Fblog-images\u002Forganization-42511\u002F1793162058150_Current-FAQ-and-product-sources-outrank-stale-policy.jpeg\" alt=\"Current FAQ and product sources outrank stale policy\">\u003C\u002Fp>\n\u003Cp>The guidance in \u003Ca href=\"https:\u002F\u002Fwww.aleso.ch\u002Fen\u002Finsights\u002Fknowledge-data-rag\u002Fconflicting-outdated-missing-sources\u002F\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ALESO’s article on conflicting, outdated and missing sources\u003C\u002Fa> is practical here. Define an explicit hierarchy and a version rule: when an approved current source clearly replaces an older one, use it. When authority is equal or unclear, the assistant should say the information conflicts, not guess, and the issue should go to whoever owns that content.\u003C\u002Fp>\n\u003Cp>A workable hierarchy for most small businesses:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Live catalog\u003C\u002Fstrong> for price, stock, variants and product attributes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Current policy pages and FAQ\u003C\u002Fstrong> for shipping, returns and warranty.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Product-specific notes\u003C\u002Fstrong> (a line in a product description) override general policy for that product only, for example “final sale, no returns.”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Uploaded documents and older pages\u003C\u002Fstrong> rank last, and should be removed once replaced.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Our post on \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fprioritize-chatbot-sources\" target=\"_blank\" rel=\"noopener\">prioritizing chatbot sources for accurate answers\u003C\u002Fa> shows how to apply this in practice. Whatever order you pick, write it down. Six months from now you won’t remember why the assistant quotes one figure and not the other.\u003C\u002Fp>\n\u003Ch3 id=\"when-there-is-no-answer\" tabindex=\"-1\">When there is no answer\u003C\u002Fh3>\n\u003Cp>Sometimes neither source covers the question: “Is this safe for my dog?” or “Can you ship to a PO box in Alaska?” A bounded non-answer is better than a confident guess. ALESO’s guidance treats it as the safer behavior when evidence is missing or contradictory. Configure the assistant to say what it does know, state plainly that it can’t confirm the rest, and offer a path forward.\u003C\u002Fp>\n\u003Ch2 id=\"hand-off-to-a-human-at-the-right-moment\" tabindex=\"-1\">Hand off to a human at the right moment\u003C\u002Fh2>\n\u003Cp>Handoff isn’t a failure. It is the correct answer when a question needs a person. Based on the same ALESO guidance, hand off when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>the evidence is missing or contradicts itself,\u003C\u002Fli>\n\u003Cli>the data is technically unavailable (a feed failed, say),\u003C\u002Fli>\n\u003Cli>the question needs a responsible person’s decision, such as a refund exception, a custom quote, or a complaint.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A good handoff keeps the visitor’s question and the sources the assistant used, so your team doesn’t ask the visitor to start over. In Konvuno, conversations and captured leads land in the dashboard, and the assistant can pass the visitor to a human. A handoff to a person who already sees the full exchange converts better than a “contact us” link.\u003C\u002Fp>\n\u003Cp>Shipping is a classic case, because it mixes policy with product and destination. We cover it in \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fshipping-questions-chatbot\" target=\"_blank\" rel=\"noopener\">what to answer in a shipping questions chatbot and how to set it up\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"test-the-combined-knowledge-before-visitors-do\" tabindex=\"-1\">Test the combined knowledge before visitors do\u003C\u002Fh2>\n\u003Cp>Build a test set of 30 to 50 questions in three groups:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>FAQ-only:\u003C\u002Fstrong> “What is your return window?”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Catalog-only:\u003C\u002Fstrong> “How much is the 12 oz canvas tote in olive?”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mixed:\u003C\u002Fstrong> “If I order the walnut desk today, when does it arrive and can I return it?”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Add deliberately hard cases: a product that’s out of stock, a variant that doesn’t exist, a question you’ve never documented, and a question where two sources disagree. For each, check that the answer is correct, that it comes from the right source, and that the assistant admits uncertainty instead of inventing.\u003C\u002Fp>\n\u003Cp>If you serve several languages, run the same set in each one. Product names, model numbers and technical specifications should come through unchanged, while the sentence around them is in the visitor’s language. Konvuno supports 7 languages, so test every one you’ve switched on, not just English.\u003C\u002Fp>\n\u003Cp>When a test fails, fix the source first. If the reply was wrong because a FAQ was outdated, correct the FAQ, then keep that question in your test set so it can’t quietly come back. Our guide on \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Ftest-chatbot-replies\" target=\"_blank\" rel=\"noopener\">testing chatbot replies before your visitors do\u003C\u002Fa> gives a step-by-step routine. Images raise their own questions, covered in \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fproduct-images-in-chatbot\" target=\"_blank\" rel=\"noopener\">setting up product images in a chatbot\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"our-perspective\" tabindex=\"-1\">Our perspective\u003C\u002Fh2>\n\u003Cp>We built Konvuno for owners who don’t have a support team or a developer on call, so we see the same pattern in nearly every setup: the technology is rarely the problem. The problem is that nobody decided which source is the truth.\u003C\u002Fp>\n\u003Cp>Our view is simple. Keep what changes often in the catalog and let the feed do the work. Keep what changes rarely in the FAQ, written from real customer questions. Then spend your attention on the unanswered questions in the analytics, because they tell you exactly what your site fails to explain. That list is more valuable than any feature, since each item is a customer who wanted to buy or book and couldn’t find the answer.\u003C\u002Fp>\n\u003Cp>We also think an assistant that says “I’m not sure, let me get someone” earns more trust than one that always sounds certain. That is why handoff and preview are part of the setup, not extras. You can configure everything and see how it answers before you pay.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cem>— Konstantin\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"try-it-on-your-own-faq-and-catalog\" tabindex=\"-1\">Try it on your own FAQ and catalog\u003C\u002Fh2>\n\u003Cp>Konvuno gives you the whole setup in one hosted dashboard: catalog sync from WooCommerce or a Google Merchant or Facebook feed, FAQ and website content as knowledge, a built-in CRM for captured leads, human handoff and analytics on what visitors ask. Every plan includes full conversational catalog capabilities, with no per-seat pricing.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Fcsuxjmfbwmkxiegfpljm.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fblog-images\u002Forganization-42511\u002F1786796293645_konvuno.jpg\" alt=\"Konvuno\">\u003C\u002Fp>\n\u003Cp>Plans are Starter at €29 per month, Growth at €79 per month and Business at €199 per month. You can configure and preview your assistant before paying. \u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002F\" target=\"_blank\" rel=\"noopener\">See the plans and start setting up\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"faq\" tabindex=\"-1\">FAQ\u003C\u002Fh2>\n\u003Ch3 id=\"do-i-need-to-rewrite-my-faq-to-combine-it-with-a-catalog\" tabindex=\"-1\">Do I need to rewrite my FAQ to combine it with a catalog?\u003C\u002Fh3>\n\u003Cp>Usually not, but you should trim it. Remove prices, stock statements and anything that duplicates product data, because the catalog will carry those and stay current. Keep policies and how-to answers, and rewrite vague answers into short, factual sentences.\u003C\u002Fp>\n\u003Ch3 id=\"what-if-my-store-isnt-on-woocommerce\" tabindex=\"-1\">What if my store isn’t on WooCommerce?\u003C\u002Fh3>\n\u003Cp>If your shop publishes a Google Merchant or Facebook product feed, Konvuno can sync from that feed instead. The feed is the same one your ad channels use, so there’s no separate catalog to maintain.\u003C\u002Fp>\n\u003Ch3 id=\"how-often-should-the-catalog-sync\" tabindex=\"-1\">How often should the catalog sync?\u003C\u002Fh3>\n\u003Cp>Match it to how fast your data changes. A shop with daily stock movement and frequent price edits needs more frequent refreshes than a store with a stable range. Whatever the schedule, check the sync status after bulk edits, since broken imports show up as missing or stale products.\u003C\u002Fp>\n\u003Ch3 id=\"what-should-the-assistant-do-when-the-faq-and-catalog-disagree\" tabindex=\"-1\">What should the assistant do when the FAQ and catalog disagree?\u003C\u002Fh3>\n\u003Cp>Follow your written hierarchy: the live catalog wins on price and stock, current policy pages win on policy. If the sources are equally authoritative and truly conflict, the assistant should say it can’t confirm and pass the question to a person, and you should correct the source.\u003C\u002Fp>\n\u003Ch2 id=\"sources\" tabindex=\"-1\">Sources\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkovmere.com\u002Fresources\u002Fhow-to-add-faqs-and-detailed-specs-to-product-pages-for-ai-answers\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">How to Add FAQs and Detailed Specs to Product Pages for AI Answers (Kovmere)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.paz.ai\u002Fglossary\u002Fproduct-qa-ai-shopping\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Product Q&A for AI Shopping: Conversational Attributes (Paz.ai)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.stripe.com\u002Fagentic-commerce\u002Fconcepts\u002Fcatalog-feed\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Catalog feed (Stripe Documentation)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fhelp.productsup.com\u002Fdocs\u002Ffundamentals\u002Fkeeping-data-up-to-date\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Keeping data up to date (Productsup)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fexperienceleague.adobe.com\u002Fen\u002Fdocs\u002Fcommerce-merchant-services\u002Fuser-guides\u002Fdata-services\u002Fcatalog-sync\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Catalog Sync (Adobe Commerce)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.aleso.ch\u002Fen\u002Finsights\u002Fknowledge-data-rag\u002Fconflicting-outdated-missing-sources\u002F\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">What happens when sources conflict, are outdated or are missing (ALESO)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbabylovegrowth.ai\u002Fblog\u002Ffaq-schema-seo\" target=\"_blank\" rel=\"noopener\">Five Step AEO Playbook for FAQ Schema in SEO\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"recommended\" tabindex=\"-1\">Recommended\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fwrite-effective-faqs\" target=\"_blank\" rel=\"noopener\">Small Teams: Write Effective FAQs From Customer Data, Not Guesswork\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fchatbot-top-questions\" target=\"_blank\" rel=\"noopener\">Chatbot Top Questions: What Customers Ask and How to Answer\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fchatbot-product-variants\" target=\"_blank\" rel=\"noopener\">Chatbot Product Variants: How to Get Size, Color and Price Right\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkonvuno.com\u002Fblog\u002Fconnect-data-to-chatbot\" target=\"_blank\" rel=\"noopener\">How to Connect Your Data to a Website Chatbot\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>",null,[15],"combine faq and catalog",1794110721956]