Skip to content
Verified Wavize guide

Customize appearance and branding

Match the widget to your brand while keeping it readable on mobile.

Updated 7 August 2026

Appearance combines identity, languages and position

The Appearance page controls avatar, name, short line, primary colour and display side. Text may be localized for assistant languages; this does not change the FR/EN client-area language.

The welcome message is no longer a simple appearance field: it is managed as the default welcome campaign under Proactive messages. That campaign counts, produces statistics and can be paused.

Conditional feature
Removing Wavize branding is only offered when the plan includes brand hiding. A missing setting is therefore not a display defect.

Define a readable identity in every language

Name and short line have limited space in the widget, especially on mobile.

  1. Name up to 30 characters

    Choose an immediately understandable name and avoid placing a full sentence in it. Fill localized variants only where actual adaptation is needed.

  2. Short line up to 50 characters

    Explain the role in one proposition: support, advice, tracking or booking. Do not promise human availability when handoff is not configured.

  3. Consistent fallback language

    Review the variant used when a visitor language has no text. An English fallback on a French-only site may harm the welcome experience.

Prepare avatar, colour and position

The settings screen accepts JPG, JPEG, PNG or WEBP avatars up to 10 MB, while onboarding uses a 5 MB limit.

  • Square, recognizable avatar

    Use a sharp, centered image without tiny text. Compress it before upload even under the limit to reduce load time.

  • Hex colour

    The field expects a valid hexadecimal colour. Check contrast with white, text and button states; a brand colour is not automatically accessible.

  • Left or right

    Choose the side that does not cover cart, accessibility button or cookie banner. The best choice may differ between desktop and mobile: test the live site.

Use preview without relying on it alone

Preview validates composition, but not every style, script and banner on the live website.

  1. Save before comparing

    Wait for save confirmation then reload preview. An uploading image or invalid form may retain the old value.

  2. Test several sizes

    Check the closed button, open window, a long reply and proactive campaign on a small screen.

  3. Validate on the allowed domain

    Open a private window on the public site. This reveals cache, CSP, consent and position conflicts absent from preview.


Final visual validation

Keep desktop and mobile screenshots after each major redesign.

  • Identity — Name, avatar and line match the brand and tested language.
  • Contrast — Text, button and focus remain readable.
  • No overlap — Widget, campaign, cookies, cart and navigation can all be used.

Still need help?

Our team can help from your client area.

Contact support