CRM integrations
CRM integrations that put website visits in context.
Someone on your website could be a customer, a past customer, a homeowner with an old estimate, or a lead who never booked. Your CRM connection helps put that visit in context.
PipelineOn connects eligible identified visits with supported CRM records. Review the relationship, available website activity, and customer-location context before deciding what happens next.
Explore customer matching with HubSpot and Jobber
These connections let you define current and past customers from available CRM fields or stages. The detail available depends on permissions, configuration, and the records in your account.
The connection works in two directions
Sending an identified visitor into the CRM gives your team a record to work. Reading customer context from a supported connection helps explain who that visitor already is to your business.
Configure contact creation, visit updates, and outreach separately. Existing customers may need service help, while an old estimate may belong with the original salesperson.
Know what the match means
- A person match and a household match offer different levels of identity context.
- A non-customer label does not prove that an appointment never happened. Review the underlying history.
- Same-street and nearby-customer signals describe location. Verify the properties before calling someone a next-door neighbor.
- Available data and your classification rules determine the context shown.
Working with another CRM?
Review the workflow for your system, then confirm the connection method and fields with us. A webhook or Zapier handoff can deliver a lead without importing the customer history needed for these workflows.
Check your CRM setup