Skip to content
Solution Blueprint

Tour-booking deal-stage automation on HubSpot Sales Hub

A national early learning and childcare provider tracked a family's move from enquiry to enrolled child across 47+ campuses, but a tour booked by phone or at the front desk left no property confirming it had happened. We built a deal-stage workflow keyed to the Tour Date property, then rolled matching per-campus pipeline views out to the full network. A later request to repeat the same logic on rescheduled tours ran into a HubSpot platform ceiling that Support confirmed couldn't be lifted.

Executive Summary

context-header-icon

Context

The provider ran deal pipelines for a network of 47+ campuses, each generating its own stream of tour requests and enrolments. One HubSpot Sales Hub instance held tour-to-enrolment tracking, built around two custom objects, Campus and Children, alongside the standard Contact and Deal pair.

what-we-built-header-icon

What We Built

We built a deal-stage workflow that advances a family from New Lead through Pre-Tour Engagement the moment the Book a Tour form confirms a date. A fallback task catches every tour booked by phone or in person, and matching per-campus pipeline views rolled out across the 47+ campus network.

tech-stack-header-icon

Tech Stack

  • HubSpot Sales Hub
  • deal-stage workflows
  • custom properties
  • custom objects
  • per-campus pipeline views

Not a fit if your CRM data isn't already clean at the location level. This design assumed deduplicated Campus and Children records, and a prior import here had duplicated most of both before the pipeline could be trusted. It also assumes a genuine multi-location structure, since a single site has no reason to model campuses as their own object.

the-challenge-header-icon

The Challenge

A family moved from enquiry to enrolled child at whichever of 47+ campuses they toured, and each campus needed its own view of its own deals. When a family booked online, the Book a Tour form gave the pipeline a reliable signal.

A tour arranged by phone or walk-in left the Tour Date property unset, so nothing moved the deal off New Lead.

A harder request followed. The client wanted the same contact re-enrolled every time a tour was rescheduled or cancelled, not only the first time.

our-approach-header-icon

Our Approach

We built the deal-stage advance around the Tour Date property, checked when the Book a Tour form is submitted. A known date moves the deal out of New Lead or Pre-Tour Engagement. An unknown one routes a task to the Enrolment Enquiries queue instead.

Per-campus pipeline views (Tours Today, Tours This Week and All Deals) carried the same logic outward, reaching 26+ campuses nationally and 21 more around Melbourne.

For the reschedule request, we tried a workflow that re-enrols the same contact on every meeting-outcome change, keyed to HubSpot's built-in Meeting outcome property. HubSpot Support confirmed that those values can't be edited, so the workflow can only re-enrol once. We kept the single-fire version rather than risk a duplicate enrolment.

Solution: HubSpot Administration & Support · Industry: Education & Training

impact-header-icon

Impact

check-icon

A tour booked online moves the family forward without a manual check

A deal in New Lead or Pre-Tour Engagement advances the moment the Tour Date property is set from a submitted Book a Tour form. A family that booked online moves towards enrolment without anyone reviewing the record by hand.

check-icon

A phone-booked or walk-in tour still lands with a person

When Tour Date stays unknown, the workflow sends a task to the Enrolment Enquiries queue instead of leaving the deal stalled in New Lead. A tour arranged by phone or at the front desk still gets picked up by a staff member.

check-icon

Campus teams work their own tours instead of a national queue

Tours Today, Tours This Week and All Deals filter to one campus at a time. The rollout reached 26+ campuses nationally, then 21 more around Melbourne, so a campus manager sees only their own location's deals instead of a list built for the whole network.

check-icon

Reschedules stay with a person where the platform stops

HubSpot Support's confirmation that Meeting outcome values can't be edited meant we declined a workaround. A workflow that could only re-enrol once was safer than one that risked duplicating a family's record on a second reschedule.

Technical Blueprint
1

The deal-stage advance checks the Tour Date property on Book a Tour form submission. A known date moves the deal out of New Lead or Pre-Tour Engagement. An unknown one leaves the stage alone and hands the record to a person instead.

2

A deal with no Tour Date generates a task in the Enrolment Enquiries queue rather than advancing automatically. A phone-booked or walk-in tour is worked by a staff member instead of disappearing into an unadvanced stage.

3

Tours Today, Tours This Week and All Deals are filtered views of the same pipeline, rolled out per campus rather than built as one shared list. The rollout reached 26+ campuses nationally before extending to 21 more around Melbourne.

4

A workflow keyed to the built-in Meeting outcome property can re-enrol a contact once per trigger. HubSpot Support confirmed the outcome values can't be edited, so a repeat reschedule or cancel doesn't restart the sequence a second time.

Book a Tour form checking Tour Date to advance a deal or task a queue, with per-campus views and a blocked re-enrolment path.

A tour booked by phone or walk-in used to leave "Tour Date" unset, so nothing moved the deal off New Lead. Now the workflow checks "Tour Date" when the Book a Tour form is submitted. A known date advances the deal, and an unknown one sends a task to the Enrolment Enquiries queue. Re-enrolment stays single-fire, because HubSpot Support confirmed Meeting outcome values can't be edited.

FAQ

Why doesn't every booked tour advance the deal automatically?

The workflow advances a deal once the Tour Date property is set, which happens automatically on a submitted Book a Tour form. A tour arranged by phone or in person leaves that property unset, so the deal routes to a person in the Enrolment Enquiries queue instead.

Why can't a family be re-enrolled every time they reschedule a tour?

The requested automation would have used HubSpot's built-in Meeting outcome property as its trigger, but HubSpot Support confirmed those values can't be edited. So a workflow keyed to that property can only re-enrol a contact once. Repeat reschedules and cancellations are handled by a person instead.

Continue reading

209049082794

National childcare provider: Campus and Children objects plus CRM dedupe

209049082794

National childcare provider: Family Support tickets routed in Service Hub

209049082794

K-12 Catholic diocese: 80 schools on one HubDB lead system

209049052787

Family-owned aged care provider: deal pipeline built around the family

209049052787

Not-for-profit aged care provider: leads routed by age and postcode

footerCTA footerCTA-mobile
Spice up your inbox
Sign up for our newsletter
Don't worry - we only average, like, two emojis per subject line.