HouseCall Pro Integration in Alivo
How Alivo settings map to HouseCall Pro Customers, Leads, and Estimates.
The HouseCall Pro integration connects Alivo to your HCP account so leads and booked inspections flow into Customers, Leads, and Estimates automatically. HouseCall Pro uses a different object model than roofing-first CRMs, and Alivo maps to it directly. This guide explains every setting and which HCP records Alivo creates.
HouseCall Pro Objects Alivo Works With
| HCP Object | When Alivo Creates It | What It Holds |
|---|---|---|
| Customer | New lead (optional) or booking | Name, phone, email, address, lead source |
| Lead | Booking | Lead details linked to the Customer |
| Estimate | Booking | Scheduled inspection with assigned employee, or unscheduled if no host is mapped |
Connection and Integration Type
API Key
Connect with your HouseCall Pro API key from Account Settings → API.
Integration Type
- Both. Creates HCP records and reads the HCP calendar for availability.
- Calendar Only. Reads calendar only. No Customers, Leads, or Estimates are created.
- CRM Only. Creates records but does not read the HCP calendar.
Configuration Settings
- Job Type. Selects from your HCP job types. This is required during setup. It is stored in Alivo and used for validation (for example, requiring a Fallback Host).
- Fallback Host. The HCP employee assigned to the Estimate when the booked event has no mapped Alivo team member. Required when CRM sync is enabled.
- Sync contacts on every new lead. Creates or updates a HCP Customer as soon as a lead arrives, before any booking.
- Sync cancellations and reschedules from HouseCall Pro. When on, Alivo listens for Estimate changes in HCP and updates the matching Alivo appointment. A webhook URL appears after you save so you can register it in HouseCall Pro.
User Mapping
Map Alivo team members to HCP employees. The mapped host becomes the assigned employee on the Estimate. If no host is mapped, the Fallback Host is used instead.
Calendar Sync
HouseCall Pro uses All Events for calendar blocking. Alivo reads HCP events, estimates, and jobs for mapped employees to block availability. There are no additional type filters.
Custom Field Mappings
Two fields appear in the Custom Fields step:
- Lead Source. Maps Alivo values to HCP lead source names. Applied to Customer, Lead, and Estimate records during sync. Notes are required.
- Job Type. Appears in the custom fields step for mapping, but is not sent to HCP during sync. Use the Configuration Job Type dropdown for your HCP job type selection.
When Data Syncs
| What Happens in Alivo | What Happens in HouseCall Pro |
|---|---|
| New lead (sync on new lead is on) | Customer created or updated |
| Lead details enriched after arrival | Customer name, phone, and email updated |
| Appointment booked | Customer confirmed → Lead created → Estimate created (scheduled or unscheduled) |
| Appointment canceled in Alivo | Estimate option declined |
| Appointment rescheduled in Alivo | Estimate option schedule updated |
| Estimate declined or rescheduled in HCP (inbound sync on) | Matching Alivo appointment canceled or rescheduled |
Heads up: HouseCall Pro is one of two native integrations (along with JobNimbus) that support two-way cancel and reschedule sync. Turn on the inbound sync toggle and register the webhook URL in HCP to keep both systems aligned.
Still have a question this didn't answer? Reach out to our support team support@alivo.ai and we'll be glad to help.