Skip to content
debarko.deproductspherahome services

Home services CRM · powered by Phera

Two truck rolls become one, because dispatch can see the whole property

A homeowner requests a roof quote, then a gutter cleaning two months later — Phera notices it's the same address before a second truck gets sent.

~1,750 monthly searches — the largest cluster found, across construction, field-service and landscaping CRM terms

Marcus fills out a roofing-quote form after a storm. Six weeks later his gutters need clearing, so he fills a completely different form on the same site. Different service line, different crew, different Pipeline — but the same Contact, and Phera's routing engine can see he already has an open Deal in the roofing Pipeline at the same address.

Every quote, site visit, and crew note from both jobs lands on one Contact timeline. When a warranty dispute comes up eight months later — "what did you actually promise us in March?" — it's a query against an immutable audit log, not a search through two separate paper trails.

Bundling two jobs into one truck roll

A workflow triggers on form submission: if the new form opens a Deal in a different service Pipeline, and the same Contact already has an open Deal in another Pipeline with a matching postal code, dispatch gets flagged to bundle the site visit. One truck, two jobs, instead of two separate dispatches to the same driveway two weeks apart.

How it maps to Phera

Pipelines

Roofing

Quote requested → Site visit → Quote sent → Won / Lost

Gutter & Exterior

Quote requested → Site visit → Quote sent → Won / Lost

Emergency Repair

Reported → Dispatched → Resolved

Channels

  • Voice — emergency calls, L1→L2 overflow after hours
  • WhatsApp — photo estimates
  • Email — formal quotes

Workflow

trigger — form.submitted opens a Deal in a new service Pipeline, and the Contact has an open Deal in another Pipeline at the same postal code

action — flag the site visit for dispatch as a bundling opportunity

Ownership — pipeline_centric

Each service line is its own crew (PipelineTeam), assigned by least-open-load so no single crew gets buried while another sits idle.