HubSpot and Chili Piper: what happens after the form?

When the form says thank you, the enquiry still has a journey ahead of it. The data needs validating, the contact needs creating and someone needs to qualify it and take ownership. Booking, notifications and reporting follow too. If one of those handoffs is unclear, you can end up with slow follow-up or duplicate records.

The pattern below connects a website, HubSpot and Chili Piper. How you configure it will depend on your HubSpot objects, routing rules and sales process, but it gives you the decisions to work through.

1. Decide who sees the booking router

Before showing a calendar, I'd want to know who's ready to book and what information the route needs. That might be a work email, service, company profile or use case. Once you've worked that out, you can keep the form as short as the decision allows.

The visitor should know what's going to happen. If suitable visitors can book immediately, say so. If every enquiry gets reviewed first, explain that before they meet a calendar that may reject them. It's part of the landing page journey too.

2. Keep a reliable record in HubSpot

Each website field needs a known HubSpot property to land in. Keeping service, source and lifecycle values controlled helps you avoid creating a new free-text property whenever the website wording changes.

HubSpot already maintains Original and Latest Traffic Source properties. If you need the exact first landing path as well, it can go in a clearly named custom property. Leave the native source history intact.

3. Route with rules the team can explain

Chili Piper can use submitted and enriched data to choose an owner or queue. The team should be able to explain those rules in plain English: UK enterprise enquiries go to this team; existing customers go to their owner. Unsupported requests go to a queue someone reviews.

I'd also want a route for when no rule matches, the owner has no availability or the router doesn't load. A standard booking page, confirmation email or reviewed fallback queue gives the visitor somewhere to go instead of a blank screen.

4. Keep the website journey usable

• Show an immediate confirmation before waiting on third-party scripts.
• Keep the booking experience usable on a small phone and with a keyboard.
• Do not erase the submitted message when the calendar opens.
• Provide a clear alternative if the visitor cannot find a suitable time.
• Load non-essential scripts carefully so the form remains responsive.

5. Measure the whole handoff

To see where things stop, track form start, successful submission, router shown, meeting booked and lead accepted. The website can usually capture the early events; HubSpot and Chili Piper should supply the later state. You can join those through stable identifiers or a controlled reporting workflow, keeping personal data out of general analytics.

Then look at submission to router, router to booked meeting, booked to attended meeting and submission to qualified opportunity. Those rates help you work out whether the issue is the page, routing, availability or lead quality.

Failures worth testing

• An existing contact submits with a different company domain.
• The selected owner is away or has no available times.
• The form succeeds but HubSpot rejects one property value.
• The CRM succeeds but the router script is blocked.
• A visitor returns through a different campaign before submitting.
• The same person submits twice from two website pages.
• A mobile visitor rotates the screen or closes the calendar.

Checks before release

1. Submit test leads for every important routing branch.
2. Confirm contact and company matching behaves as expected.
3. Check property values, original source fields and owner assignment.
4. Verify confirmation, booking and notification emails.
5. Test the fallback journey with the router unavailable.
6. Confirm analytics fire once and contain no personal information.
7. Give sales and marketing one place to report a routing problem.

Official references

• HubSpot: Original and Latest Traffic Source properties
• Chili Piper: Concierge router deployment
• Chili Piper: Concierge documentation

Frequently asked questions

What should a website-to-CRM lead flow include?

The flow needs agreed input fields, validation, matching rules, owner assignment, booking handoff and delivery state. I'd also keep enough evidence to trace an enquiry if it fails between submission and the receiving team.

How do I test HubSpot and Chili Piper lead routing?

Use controlled test contacts and agreed routing cases. Check the CRM record, owner, booking result and measurement. Include unmatched routes, repeated submissions and failures after part of the workflow succeeds.

What happens when no lead-routing rule matches?

Send the request to a fallback queue with a named owner and an agreed escalation time. A successful submission still needs someone responsible for replying.