Give your AI agent accurate business knowledge

Useful answers begin with clear source information. Put the facts that determine a customer decision into managed business records, then use public website imports to add supporting detail. Review the resulting answers whenever your prices, services or policies change.

For owners and authorised staff preparing and maintaining a V7 business workspace.

Start with the facts customers need

Add products or services with clear names, descriptions and prices where applicable. Include differences between options, availability information, locations or service areas, opening hours, delivery rules and contact paths. Explain when a price is fixed and when a customer needs a quote.

Use managed FAQs and business rules for important conditions and exceptions. Keep the agent tone and sales goals separate from factual promises. A friendly style must not introduce an unapproved discount, guarantee or service.

Import relevant public website pages

Save your business website as a public HTTPS address in the business profile. The website import can collect up to 20 public pages from that configured host, within its content limits. Private accounts, local network addresses and pages behind sign-in are not sources for this import.

The importer extracts page text; it does not automatically connect your shop database, authenticate customers or read private orders. Relevant excerpts supplement managed business knowledge. It is a bounded import rather than continuous synchronisation of the whole website.

Review sources and refresh changes

Check the imported pages and the answers they support. Remove or correct stale information at its source, keep important prices and policies in the management screens, and refresh the website import after publishing relevant website changes.

If two sources disagree, correct the conflict instead of expecting the assistant to guess. Test a clear factual question, a policy exception and something your information does not answer. The response should distinguish the supplied facts from missing details and offer a suitable contact path.

Use conversation memory for follow-ups

Conversation memory helps the assistant use earlier messages in the same session. The API settings provide controls for enabling memory, history message count, context budget and memory duration. These settings bound what earlier context is available; they are not permanent customer identity or a substitute for managed company knowledge.

Including more previous text can increase model input cost. Longer replies, the selected model and additional calls also affect usage. Review the usage ledger with realistic conversations before increasing context limits. Changing active memory duration does not delete separately retained conversation or audit records.

Keep a small launch checklist

Ask what the business sells, compare two real offerings, ask a follow-up and test a missing fact. Define a harmless preference in one conversation and ask about it later in the same session. Start another session to check that the previous visitor’s details do not appear.

Open an approved website button and submit an enabled enquiry form yourself. Confirm the destination and the recorded outcome. Repeat the same checks after changing knowledge, the model or an integration, and have your team review important replies.

What to check before launch

AI answers can be wrong even when source information is available. Keep private customer data out of public website content and involve your team when an enquiry needs verification or judgement.

Make an informed decision.