Troubleshooting guide
Leads do not provide enough job detail: A Practical Diagnostic Path
Leads do not provide enough job detail can have several causes that look identical from the outside. Use this path to gather useful evidence without making the original problem harder to reproduce.
Record the symptom before changing it
Capture the exact screen, user role, time, device, and sequence that produces the issue. Note whether slow response costs good projects occurs at the same time.
- Save exact error text
- Record the last known working date
- List recent code, content, vendor, DNS, or account changes
Separate reachability, data, and behavior
First confirm whether the affected system can be reached. Then confirm the expected record or content exists. Only then test the behavior supported by mobile-first lead and quote forms.
- Reachability check for scheduling and notification workflows
- Data or content check related to contractor and home-service websites
- Behavior check for service-area and local landing pages
Use stop conditions
Stop and preserve evidence if a test could overwrite data, invalidate logs, lock out users, or remove the only working copy. Recovery work needs a known restore path before intrusive changes.
- No confirmed backup
- Unknown production ownership
- Security or payment data may be involved
Verify the repair in the real journey
A green technical check is not enough. Repeat the original journey, test a nearby edge case, and confirm the result from the perspective of contractors, home-service companies, landscapers, hvac, electrical, plumbing, roofing, cleaning, and similar trades.
- Contractor and home-service websites
- Quote request and estimate intake systems
- CRM, email and SMS integrations