Complete the initial onboarding

Wavize onboarding has four required stages

The current flow does not start with a simple company form. It combines plan selection, website analysis, validation of prefilled information and widget installation. A saved stage is resumed at the next sign-in.

Automatic analysis reads only a public page and may suggest a name, industry, business type and description. These suggestions must not be approved blindly: the owner remains responsible for their accuracy.

Partner exception
A demo account created from the Partner area is already marked as onboarded and opens the dashboard directly. This is intentional and does not describe standard client registration.

Stage 1 — choose capacity and billing cycle

Wavize displays active catalogue plans except the partner-demo plan. Prices and limits shown on this screen are authoritative because the administrator can update the catalogue.

1. Compare conversations and AI replies

   A real conversation and a consumed AI reply are separate counters. Assess traffic, average question volume and included features before selecting only the lowest price.

2. Monthly or yearly

   Choose the displayed cycle, review the Stripe summary and accept payment terms. An already active plan automatically advances to the next stage.

3. Interrupted payment

   If the Stripe window is closed, Wavize may retain a pending subscription. Return to the plan screen to resume or cancel that attempt before creating several.

Stage 2 — analyze the public website

Enter the official website, then choose WordPress, WordPress with WooCommerce, PrestaShop, Shopify or Other. The URL is normalized to HTTPS and linked to the future widget’s allowed domain.

1. Publicly accessible URL

   Use the canonical home page, not password-protected staging, an admin page or a shortened URL. Analysis follows at most two redirects on the same registrable domain and limits the HTML response to 500 KB.

2. Assisted prefill, not content invention

   Wavize extracts public metadata and may use AI to structure it. If AI is unavailable, the stage continues with available data; no business information should be invented to fill a gap.

3. Background crawl starts

   After website validation, Wavize saves the profile, authorizes the domain and queues a full crawl. Progress can continue while you correct the company profile.

Stage 3 — review the business and personalize the assistant

This stage turns suggestions into data actually used by the assistant. Each limit prevents overly long titles or messages in the widget.

• Company profile

  Company name and industry accept 30 characters, business type 120 and description 600. Remove vague slogans, correct outdated information and describe what the business actually offers.

• Assistant identity

  The name accepts 30 characters. Choose a hexadecimal colour and left or right position. The optional avatar must be JPG, JPEG, PNG or WEBP and stay below 5 MB during onboarding.

• Initial proactive welcome

  Wavize prepares a standard welcome campaign. It later appears under Proactive messages, counts toward campaign limits and can be edited, paused or deleted like any other campaign.

Stage 4 — install for the selected technology

The last screen provides the installation method matching the previous choice and the public domain-bound token. Completing onboarding stores the completion date and prevents accidental return to the wizard.

1. WordPress and WooCommerce

   Download the same Wavize plugin, install it under Plugins and configure the supplied token. WooCommerce then needs a separate store connection for product and order-tracking features.

2. PrestaShop

   Download the module archive, add it through Module Manager and enter the token. The PrestaShop Webservice key used for the catalogue is configured separately under Integrations.

3. Shopify or another website

   Copy the complete embed code. On Shopify, App Store installation normally automates this link; manual code remains for cases explicitly offered by the screen.

When onboarding is truly complete

The end of the wizard is not the end of quality control. Check these four outcomes.

• Active plan or valid trial — Subscription shows a consistent status and the expected quotas.
• Correct domain — The token belongs to the public domain actually tested, including the correct www variant.
• Sources queued or complete — Crawl progress is visible; wait for processing before judging answers.
• Preview then live site — Ask one question in preview and another from a private window on the live site.