Wireframe — HCP Customer Match Modal

Triggered by clicking Complete on any estimate detail tab. Searches the org's HousecallPro account for matching customers (by phone, email, or name) and lets the user confirm the match — or create a new customer if none of the candidates fit. Critical for Phase 1.5 because mismatches in HCP are awkward to undo.

{{ name }} — Estimate Review

D Dan ▾

↑ underlying estimate page (faded behind modal)

Match logic

SEARCH n8n hits HCP's customer search endpoint with phone, email, and name. Returns up to 5 candidates.
SCORE Confidence scoring is server-side: exact phone OR email match = 95%+, name + ZIP match = 70-80%, name only = 30-50%. Candidates ranked by score.
DEFAULT If the top candidate is ≥95%, it's pre-selected (as shown). Otherwise no pre-selection — Dan must explicitly choose.
CREATE NEW The "Create new" path opens a second modal with editable fields pre-filled from the estimate.

Failure modes & edge cases

HCP API down → modal shows "HCP unreachable. Estimate is saved here; we'll auto-retry on your next sync."
OAuth token expired → modal redirects to Settings · Integrations to reconnect.
Org has no HCP connection → "Connect HCP first" CTA → Settings · Integrations.
Estimate already pushed (idempotency) → modal warns "This estimate already exists in HCP as Estimate #1234. Update it instead?"