Skip to content
Verified Wavize guide

Recover a password or 2FA code

Restore access without bypassing account security checks.

Updated 7 August 2026

First identify account type and blocked step

Wavize separates client, team-member and partner/affiliate accounts. They do not always use same form or 2FA. A reset sent from client area does not fix program password.

Do not bypass code by creating a new account: you would separate subscription, assistant, conversations or attribution. Recover existing identity with exact address.

Never requested
Support should never receive password, full 2FA code or API key. Ownership proof uses non-secret information and official process.

Recover client password

Use Forgot password from client login.

  1. Exact address

    Enter actually registered owner or member address. Check typos, aliases and old company domain.

  2. Latest link

    Open latest message before expiry. Used or old link is rejected; restart flow without reusing URL.

  3. New secret

    Choose at least eight characters and confirm. Sign out shared sessions according to process and update password manager.

Recover program account

Partner area has its own forgot-password routes.

  1. FR/EN partner form

    Open program login in desired language then Forgot password. Received link keeps locale.

  2. Temporary link

    Wavize stores token with email and rejects invalid or expired link. Use same address in final form.

  3. 2FA after reset

    New password does not remove mandatory email code. On next login, wait for separate six-digit code.

Resolve missing or expired email code

Validity is ten minutes for documented flows.

  1. Check inbox

    Spam, quarantine, forwarding rule, full mailbox and provider delay. Search Wavize subject at test time.

  2. Resend once

    Wait displayed delay, request new code then ignore old ones. Do not mix signup verification code and login code.

  3. Clock and entry

    Enter six digits without spaces. Expired code requires a new message; changing browser clock does not extend server.

When inbox is no longer accessible

This is identity recovery, not simple delivery troubleshooting.

  • Do not create duplicate

    A new account does not recover old data, subscription or commissions.

  • Open ticket from controlled channel

    Provide account type, masked old address, company, approximate date and requested non-sensitive references.

  • Follow verification

    Wavize may request additional proof before change. Do not proactively send full identity documents unless requested.


After recovery

Address cause that made access fragile.

  • Current email — Owner has durable control of inbox.
  • Unique password — Stored in manager and not shared.
  • Team access — Each collaborator has distinct account.