Set up Answers and live product information
Open SmartCloud → Answers → Run setup. Setup stages your changes until Finish setup. Existing detailed settings remain available and are preserved.
Start with your business
Choose Site guide, Services and enquiries, Product discovery, or Customer support. Enter your business name and describe what visitors should achieve in one or two sentences. Audience and main topics are optional.
For a sports shop, topics might be “Snowboards, winter sports equipment, product selection and care.” Describe your actual offering; do not enter sample prices or claim stock levels here. Live prices and availability belong to the catalog.
Select Preview assistant profile, review the suggested role, tone and tasks, then apply the reviewed profile to your draft. A preset supplies behavior; it does not connect a service or provide verified product facts.
Choose the information sources
- WordPress content: select public content types for the knowledge base. Synchronization and backend indexing must finish before that content can support answers. See Knowledge Sync.
- Live catalog: choose an optional supported catalog connection.
- Approved web pages: add specific public HTTPS sections that the assistant may read. This is page retrieval, not unrestricted web search.
These sources complement each other. WordPress can provide usage guides and detailed descriptions while the external catalog supplies current product data. When setup proposes an evidence-policy change, review its effect before approving.
Connect a Shopify catalog
- Select Shopify product catalog.
- In Shopify administration, open Settings → Domains and copy the original
your-store.myshopify.comdomain. Enter the domain only, withouthttps://, an admin path, or a product path. - Optionally enter a two-letter market code and a fallback language tag. Visitor-language support sends the selected reply language; it does not change market or currency. Catalog translations must exist in Shopify.
- Keep the Public catalog agent profile filled from your configured AI Kit backend. An override is for an independently hosted compatible profile.
- Select Check connection and available reads. Review the server identity, endpoint and operations, then explicitly approve read-only access.
- Add the reviewed connection to the draft. It is saved with Finish setup.
This connection check lists supported schemas. It does not execute a product search, save a profile, or change the store. A connection already configured in detailed settings is recognized, so setup will not add the same endpoint twice.
No catalog JSON export is required. Advanced MCP JSON describes reviewed tool names, schemas and policies, rather than exporting products. Its remote schemas come from the service, and the site owner supplies the purpose and approval.
Send visitors to your WordPress product pages
A compatible backend can resolve a catalog product to your own public page. The original product ID, price, variants and availability remain catalog data.
Choose a link policy for the connection:
| Policy | Destination |
|---|---|
| Original store links | The approved catalog product URL |
| Prefer WordPress pages | Your matching page, otherwise the original product URL |
| WordPress pages only | Your matching page; no external product link when unmatched |
Search the live catalog and select a product. Search your published WordPress pages and select the page dedicated to that product. Review and add the pair to your draft; you do not need to look up the external product ID yourself. Finish setup or Save profile saves the rows.
Only published, public pages without a password are offered. Selecting a page does not create or publish content. A collection page that lists products does not automatically become a dedicated page for each one.
An optional language tag identifies a localized page. Resolution uses an exact visitor-language match, then its base language, then a row without a language. Explicit pairs take precedence over reviewed integration suggestions. You can store up to 50 rows per connection.
Some installed integrations can supply verified product identities. Review their page suggestions before adding them. Other integrations use the manual picker; recognition is not assumed from a product name, SKU, generic block ID or URL slug. The presence of WooCommerce page identities does not itself enable a live WooCommerce catalog connector.
Review saved pairs after moving or unpublishing a page. Discovery does not automatically rewrite the profile. If several sites share one backend profile, choose the public site intended for those clients.
Test before enabling visitor answers
Try a known product, its price and variants, a missing product, and a comparison. Repeat in the visitor languages you expect. Inspect the source references and local page links, including an unmatched product under each selected policy.
“Orderable” does not necessarily mean immediately in stock. The assistant should not invent quantities, unavailable attributes, or variants missing from a bounded result. Missing catalog information should remain explicit.
These settings enable read-only discovery and product-page links. Cart, checkout and order changes are not enabled.