Guidance for Testing HeavySet Tech Forms

Purpose

Use this guidance when submitting test leads through HeavySet Tech forms so tests do not create billable leads, trigger outreach to real people, or get suppressed as duplicates.

Why this matters

Test submissions can have real downstream effects if they look too much like production data in the wrong ways, or not enough like production data in the right ways.

Good test data should:

• be recognized as test traffic for billing and reporting

• avoid contacting real people by phone or email

• remain unique enough to avoid duplicate matching

• still use real ZIP codes so routing and time-slot logic behave normally

• look realistic enough to pass CRM and form validation rules

Required rules for test lead data

Email must contain "test"

Every test email must include the string test.

This helps HeavySet Tech identify the submission as test traffic so it is not billed as a real lead.

Examples:

• [e-mail]

• [e-mail]

• [e-mail]

Phone number must be fictional

Use a fictional US phone number so automations do not accidentally call or text a real person.

Recommended pattern:

• use a US-formatted number in the 555 exchange

• example: 2155550143

This is realistic enough for many validation flows while avoiding real customer outreach.

Names should look realistic, but be fictional

Do not use obvious placeholders like TestUser1, QA User, or Fake Lead, since some CRMs reject or mishandle those values.

Instead, use fictional names that have a normal first-name / last-name structure and look plausible at a glance, while still being clearly invented.

Good examples:

• Zeric Thornevale

• Lunara Vexley

• Corvin Draxen

• Velora Quenth

• Nyra Velmora

These are better than generic test names because they behave more like normal lead data in stricter CRMs.

Make every test lead unique

Test records should be unique so they do not match recent duplicate leads.

Change one or more of the following:

• full name

• email

• phone number

• street address

• ZIP code

Even when re-running the same scenario, do not reuse the exact same record repeatedly unless you are specifically testing duplicate handling.

ZIP code must be real

Use a real ZIP code.

This is important because HeavySet Tech uses ZIP-based logic for:

• serviceability

• routing

• appointment availability

• time-slot lookup

Invalid ZIP codes can cause the form flow to fail for reasons unrelated to the feature being tested.

Address should be obviously fake, but structurally valid

Use a fake street address that is clearly not a real residence, while still looking like a normal address field value.

Examples:

• 742 Not A Real Lead Ln

• 1187 Placeholder Ave

• 55 Fake Entry Rd

• 903 Example Data Blvd

• 505 Unreal Estate Blvd

This keeps the record safe for testing while still passing common address-format expectations.

Recommended structure for a valid test lead

A good HeavySet Tech test lead should look like this:

• Name: plausible but fictional

• Email: contains test

• Phone: fictional 555 number

• Street: fake but valid-looking

• City/State/ZIP: real enough for routing, with a real ZIP code

Example records

Below are sample records testers can use directly or copy and modify. Use different ZIP codes across tests when possible to reduce duplicate matching and to exercise routing and time-slot logic in multiple areas.

Name	Email	Phone	Address	City	State	ZIP
Zeric Thornevale	[e-mail]	2155550143	742 Not A Real Lead Ln	Philadelphia	PA	19103
Lunara Vexley	[e-mail]	4125550198	1187 Placeholder Ave	Pittsburgh	PA	15222
Corvin Draxen	[e-mail]	6105550127	55 Fake Entry Rd	Allentown	PA	18101
Velora Quenth	[e-mail]	7175550162	903 Example Data Blvd	Harrisburg	PA	17101
Taryn Voxley	[e-mail]	5705550189	221 No Such St	Scranton	PA	18503
Nexis Halvern	[e-mail]	8145550114	77 Test Address Way	Erie	PA	16501

Best practice when reusing examples

If you reuse one of the examples above, swap at least the ZIP code and ideally one or two other fields.

Example:

Original:

• Zeric Thornevale

• [e-mail]

• 2155550143

• 742 Not A Real Lead Ln

• Philadelphia, PA 19103

Variation:

• Zeric Thornevale

• [e-mail]

• 2155550167

• 742 Not A Real Lead Ln

• West Chester, PA 19380

Another variation:

• Lunara Vexley

• [e-mail]

• 4125550134

• 1187 Placeholder Ave

• Altoona, PA 16602

What to avoid

Do not use:

• obvious fake-user names like TestUser1

• real personal phone numbers

• emails without test

• invalid ZIP codes

• the exact same record over and over

• real home addresses unless a specific test requires them in a controlled environment

Quick checklist

Before submitting a HeavySet Tech test lead, confirm:

• email contains test

• phone number is fictional

• name is fictional but realistic-looking

• ZIP code is real

• address is clearly fake

• record is unique enough to avoid duplicate matching