Manage contacts and notifications

A contact is created from voluntarily supplied information

Name, email and phone may come from a form or visitor text when detection is active. Wavize fills missing fields without blindly replacing an existing value.

Notifications signal an event—contact, handoff, ticket—but do not replace the contacts list or inbox. A missing email does not imply the record failed.

Data minimization principle
Collect only details necessary for the stated purpose and export them only to authorized people or tools.

Configure capture before measuring

Review Behaviour, privacy notice and recipient.

1. Actually necessary fields

   For email follow-up, a phone number is not always required. Fewer fields improve completion and reduce protected data.

2. Understandable consent

   Explain the purpose and link the privacy policy. Wording should match actual processing, including Klaviyo or Mailchimp synchronization.

3. Monitored recipient address

   An unmonitored inbox creates leads without follow-up. Use a team address and test delivery.

Review and qualify contacts

The table is a work source, not automatic proof of marketing consent.

• Email format

  A valid format may still be false or temporary. Do not launch campaigns without your own consent and quality checks.

• E.164 phone for Klaviyo

  Klaviyo phone sync requires international format such as +33123456789. A local number may remain in Wavize but not be sent.

• Source and page

  Use origin to understand intent and prioritize follow-up, without inferring sensitive data visitors did not declare.

Separate Wavize notifications and external sync

Each channel may succeed or fail independently.

1. In-app notification

   It belongs to the account and may be marked read. Check it when email was filtered.

2. Request email

   Check spam, sending DNS and recipient inbox. Do not resend repeatedly before confirming the contact exists in Wavize.

3. Klaviyo or Mailchimp

   The sync job uses the active integration, configured audience and profile-only or double-opt-in mode. Wavize contact remains the initial source even if the marketing API rejects it.

Controlled capture test

Use a team-owned address and document its deletion.

• Single creation — The contact appears with supplied fields, without an obvious duplicate.
• Notification — The expected channel receives the event once.
• Marketing — In double opt-in, status remains pending until the address owner confirms.