WhatsApp leads, straight into HubSpot.

Every qualified lead from Zatio creates — or updates — a HubSpot contact + deal in the right pipeline stage, assigned to the right owner, with the full conversation transcript attached. No duct-tape Zaps, no missing UTMs, no orphaned contacts.

Book a 15-min demo See pricing

The HubSpot gaps we see every week

WhatsApp leads don’t land in HubSpot

Without a purpose-built integration, your best WhatsApp enquiries live in a chat app while your worst web-form submissions get VIP treatment in the CRM.

Deal stage is always ‘New’

Your AE has to manually move the deal after reading the conversation. Zatio can set stage by qualification outcome: booked / needs-nurture / disqualified.

Custom fields come back empty

Postcode, service, budget range, preferred timeframe — Zatio captures them and maps them to HubSpot custom properties. Your reports finally work.

What gets pushed to HubSpot

Contact + deal

Created or updated on every qualified lead. Dedupe by email or phone, whichever HubSpot has set as unique.

Transcript as an engagement

The full conversation attached as a note on the contact timeline, timestamped. Your AE walks in to context, not a 200-message scroll.

Custom properties filled

Map any WhatsApp-captured field to a HubSpot property — postcode, property type, EPC, budget, source campaign.

Pipeline stage by outcome

Qualified-and-booked → demo-scheduled. Qualified-needs-nurture → lead-nurture. Disqualified → closed-lost with reason.

Owner assignment

By postcode, service, team rotation, or HubSpot’s native routing. The right AE gets the lead within seconds.

Two-way sync (roadmap)

Today it’s one-way Zatio → HubSpot. Two-way (HubSpot changes flow back to Zatio conversations) is on the roadmap for Q3.

Questions we hear a lot

What HubSpot plan do we need?

Starter and above. The integration uses standard HubSpot APIs — nothing that requires Enterprise.

Will it overwrite existing contacts?

No — dedupe by email or phone, merge on create. Existing contact properties are never overwritten without explicit mapping rules.

How fast are leads delivered?

Within 10 seconds of the conversation being marked qualified. For most workflows this is real-time — an AE gets the HubSpot task notification before the prospect has put their phone down.

Can we route leads differently by service?

Yes. You set the rules: solar leads to one pipeline/owner, heat-pump to another, with postcode overrides if you want.

What about marketing consent / GDPR?

Zatio captures lawful-basis consent in the conversation and passes it as a HubSpot consent record. Double opt-in is supported for marketing lists.

Let’s wire up your HubSpot

15 minutes. Share your HubSpot pipeline structure and a typical lead shape. We’ll show you exactly what lands in the CRM.