Web lead to owner: six checks in order, with synthetic leads

How to use this order

Take one form path and check six things in order, stopping at the first that fails. Use leads you invented, and make sure that no test lead can email, task or notify a real person. This is an authored review sequence, not a HubSpot procedure, and it assumes you can see the form settings, the workflows and, if used, the Salesforce integration. Record expected and actual results side by side.

Checks one to three: capture, matching, ownership

Check 1, capture: does the lead arrive at all? Submit one synthetic lead and find the contact. Check 2, matching: the same email twice should give one contact; two people at one domain should give two contacts and one company; two people on one browser should stay two contacts. See the duplicates guide for the four routes and the cookie risk. Check 3, ownership: each synthetic lead should reach the owner your written rule table names, a lead matching nothing should reach the named fallback with an alert, and a pool change should be tested again.

• 1: one synthetic lead creates one contact.
• 2: counts of contacts and companies match the expectation.
• 3: owner equals the rule table, including the fallback.

Checks four to six: sync, alert, weekly check

Check 4, sync: for each mapped field, edit on the side that should win, wait the agreed window, and confirm the value holds and Sync Health shows no new error; read the sync-rules guide first. Check 5, alert: cause a deliberate failure on a copy of the path and confirm that a shared place and two named people are told. Check 6, weekly check: put a saved view of unowned new leads, new duplicates and sync errors in front of a named person on a schedule, because a lead without an owner produces no owner notification.

• 4: the sync rule matches who edits the field, and the value holds.
• 5: a deliberate failure reaches two named people.
• 6: a weekly view of unowned leads, duplicates and sync errors.

What to buy, if anything

One broken stage: the matching one-off outcome, whether duplicates on one form path, routing for one workflow, or one mapped field pair. Several broken at once: the project tests up to three paths from form to owner. Keeping it true: the standing weekly check, with repairs on a copy or with synthetic records. None promises how fast a lead is contacted, and none changes real records without your approval.