AnhoraSite Chat guide
A practical order for turning website content into grounded answers, useful product claims, and a restrained sales conversation.
Start with pages, FAQs, policies, and product documentation. Run Sync and check the committed item count before generating a draft. Website content is the evidence layer; the assistant configuration decides how that evidence is used.
Keep only claims supported by a source. Mark planned, limited, and unavailable items explicitly. Disable a claim when it should not be used in answers. Generated facts are a draft: review the status, summary, source, and enabled switch before saving.
Product facts
Enabled claims are available to the assistant
WordPress integration
Source attached
Shopify integration
Source attached
Private beta access
Source attached
Use Auto language for multilingual sites. Choose the sales approach, then tune response length only when the default is too short or expensive. Auto language responds in the visitor's language; locale patterns help greetings and short conversational turns without tying the assistant to one market.
Decide when contacts are requested, add fit terms only when useful, and connect a webhook only if another system needs the lead payload. Start with the default consultative approach and change cooldowns only after reviewing real conversations.
Conversion behavior
Advance only qualified conversations
Sales approach
Ask for contacts
Qualification
Optional fit signals
Fit roles
Fit use cases
Test factual questions, planned integrations, a greeting, and an off-topic request. Save the reviewed draft before publishing the deployment key.
