Retest every quote form after changing the business email

Map the places that still use the old address

An email change can affect the account used to sign in, the mailbox shown on the contact page, the form alert recipient and the sender displayed in an acknowledgement. Make an inventory of those roles before editing. Include footer forms, campaign landing pages, callback widgets and older service pages. A visible new address on the homepage does not confirm that these routes changed.

Separate account identity from enquiry routing

Wix explicitly says that changing an account email does not automatically update form-automation recipients. The practical lesson is to inspect the destination of each enquiry rather than infer it from an account setting. Keep the old mailbox accessible during a planned transition if your existing arrangement allows it, and ask the mailbox administrator before changing domain email records.

Source checks: Wix Forms: Troubleshooting · Wix Forms: Choosing Who Gets Notified About Form Submissions

Test one form at a time

Use a test matrix with a row for every form, including forms that share the same appearance. Record the published page, form identifier, new recipient and acknowledgement behavior. The business owner should verify access to the new mailbox directly. A vendor screenshot of settings is useful evidence, but the published path still needs an actual test.

• Find every published quote, contact and callback form and list its intended staff recipient.
• Check the linked automation for each form; change only addresses involved in the handoff.
• Submit TEST-EMAIL-301, TEST-EMAIL-302 and similar distinct messages through separate forms.
• Confirm each request is saved and its owner alert arrives in the current mailbox.
• Inspect the customer-facing acknowledgement and reply route, then document remaining exceptions.

Avoid changing unrelated email settings

A copied form can retain a separate automation. A notification might reach the new mailbox while the acknowledgement asks customers to reply to an abandoned address. Do not replace mail-server records just because a website alert is missing; that can affect all business email. Escalate the specific evidence to the person responsible for the form or mailbox rather than guessing.

Track unmatched tests during the handoff

Count tested forms, successful current recipients and unresolved routes. These are operational checks, not a conversion lift. For the first few working days, compare new saved enquiries with alerts in the new mailbox. Look for customers replying to old acknowledgements, and record those replies without forcing them to start their request again.

Document the active route for future changes

Keep a small routing register with form name, notification recipient, reply address, responsible team member and last test date. Tell the person maintaining the website which forms are approved and which remain under investigation. When a staff role changes later, this register becomes the starting point; nobody has to remember which hidden widget sends to which mailbox.

Worked example: an illustrative customer journey

For example, a repair shop changes from an owner's personal mailbox to quotes@example.com. Its homepage form is updated, but a separate windshield page still alerts the old address. TEST-EMAIL-301 reaches the new mailbox; TEST-EMAIL-302 appears only in saved submissions and the old inbox.

The administrator updates the second form's recipient and repeats it with TEST-EMAIL-303. Both current routes now pass. The owner also checks that acknowledgements do not direct replies to the personal address. The result is a documented handoff, not evidence that website traffic or the underlying demand has changed.

Questions about this task