Configure your first assistant

Turn a created assistant into a reliable assistant

Onboarding creates a usable baseline, but final quality depends on three separate areas: company information, knowledge sources and behaviour rules. Changing colour does not fix an inaccurate answer; adding a document does not automatically change tone.

Work in this order so you know which change causes which effect. After each group of changes, wait for saving and test a small repeatable question set.

Editorial safety principle
The assistant must rely on sources and public context. It must never invent a missing price, URL, lead time, warranty or order status.

Stabilize the profile and brand voice

Open Assistant and review Company, Appearance and Behaviour separately.

1. Factual company profile

   Enter name, business type, website and description with verifiable facts. The description should explain the offer and audience, not provide secret instructions to AI.

2. Name and short line

   The name is limited to 30 characters and the short line to 50. Check localized versions in languages actually used by visitors.

3. Selected tone

   Standard suits most uses, Friendly adds warmth and Professional favours more formal wording. Additional instructions are only visible if the plan allows them.

Build a useful first knowledge base

Start with questions that cost your team time or block a purchase. A large quantity of weak pages is less useful than a clean core set.

1. Commercial priorities

   Add main services or products, public prices, terms, service areas and contact methods. For ecommerce, connect the store instead of manually copying a live catalogue.

2. Support priorities

   Import shipping, returns, refunds, warranties and support procedures. Clearly separate a public policy from an internal note that must not be disclosed.

3. Training status

   A saved source that is still queued or failed does not immediately feed answers. Wait for processed status, then retrain after a major change.

Configure conversion, privacy and human handoff

These options change what visitors see and what Wavize may collect.

• Contact at start or automatic detection

  Start-of-chat collection asks for details before the conversation. Automatic detection records only details explicitly written by the visitor; it is not external enrichment.

• Privacy notice

  Add clear wording and an HTTP or HTTPS policy URL. Check that the link belongs to your organization and explains the purpose of contact data.

• Human handoff

  If the plan allows, enable handoff always or on a schedule. Choose timezone and morning/afternoon slots for each day, then test a request outside opening hours.

Recommended acceptance test

Keep questions and expected outcomes in a document so the test can be repeated after every change.

• Documented question — The answer correctly uses the fact from an active source.
• Unknown question — The assistant acknowledges the limit or offers handoff, without inventing.
• Contact request — The form, notification and configured recipient work.
• Mobile display — The widget, welcome campaign and cookie banner do not overlap.