10. Where a Lead Goes After the Form

Right now, when a contractor fills in the Ledgerlane booking form, the answers land in the Tally dashboard and an email goes to the founder. The founder then copies the lead into the lead sheet by hand and pastes one of two follow-up emails, one for each van price. That works for three leads a month. It breaks when the search article starts sending traffic. It also breaks when the same person fills in the form twice, or when the founder is away for a week.

This chapter answers one question. Where should a lead go after the form, and how does the first reply reach the right person exactly once? The answer is a CRM. Each Tally submission becomes one HubSpot contact through Zapier. The reply then goes out automatically, but only after the sending domain is authenticated and the right people are excluded. This picks up two items we left open earlier: the duplicate-checking connection the form would need once a CRM arrived, and the follow-up email the founder sends by hand.

Moving the lead into a CRM and sending the first reply

A CRM, short for customer relationship management system, is the record of three things: contacts, deals and next actions. A contact is a person and what you know about them. A deal is a possible sale and the stage it has reached. A next action is the task someone has to do, such as calling back by Thursday. The lead sheet we built already does a rough version of this. A CRM does it with matching, history and automation built in.

For a small service like Ledgerlane, four tools are worth comparing, and the right one depends on what you need first.

If you want the lowest cost with automatic email matching and a built-in follow-up, choose HubSpot's free CRM. HubSpot matches contacts on the Email property. When a submission arrives with an email it already holds, it updates that contact instead of creating a second one. The weak spot is a person who uses two email addresses. HubSpot treats them as two people, and only you can notice and merge them. HubSpot can also store an account's data in its EU data centre in Frankfurt. That choice is made per account, so check its current conditions before you sign up.

If you want a free plan with several users and plan to grow into paid features, look at Zoho CRM Free. As of November 2026 it is zero dollars and described as forever free for three users. It lists tasks, meetings and calls, follow-up reminders and workflow automation. But Zoho's pricing page puts pipelines and web forms under its paid Standard plan, so the free tier is thinner than it first looks.

If you want a flexible, modern record and expect to shape it yourself, look at Attio Free. As of November 2026 it is zero dollars for up to three seats, fifty thousand records and three objects. Formula attributes and custom objects are not included.

If you care most about a sales pipeline and UK data hosting, look at Pipedrive. It has no free plan, only a fourteen-day trial. Published prices for its Lite plan disagree, so check Pipedrive's own pricing page before you count on a figure. Pipedrive lists hosting on Amazon's servers in Frankfurt, Dublin and London, which matters if you want UK hosting. Whether Lite includes web forms is unclear. Pipedrive ties web forms to its LeadBooster add-on, which comes with the Premium plan, so a Tally user might need Zapier or Make anyway.

For Ledgerlane, HubSpot wins on two points. Repeat submissions update one contact without extra work, and the free tier can send a simple follow-up email. Those are the two problems the founder has today.

Connecting Tally to HubSpot with Zapier

Zapier is a workflow tool. It watches one app for an event and does something in another app. Here the event is a new Tally submission, and the action is a HubSpot contact.

Sign up for a free HubSpot account and a free Zapier account first. In Zapier, create a new Zap. Choose Tally as the trigger app with the new submission event, and connect your Tally account. Pick the diagnostic call form. Then choose HubSpot as the action app with the action called Create or Update Contact. That action creates a contact, or it updates the existing one matched by email address. That single choice is the duplicate check we wrote into the fault note when we built the booking form.

Next comes field mapping, which means telling Zapier which form answer goes into which contact property. Name goes to first and last name. Email goes to Email, and this one matters most, because it is the matching key. Phone goes to phone number. For van count, trigger and the optional note, create three custom contact properties in HubSpot first, then map the answers to them. Do the same for the three hidden fields. The utm source, utm medium and utm campaign values the form already captures each get their own property. If you skip this, the campaign origin we worked so hard to keep in a test two chapters ago gets lost at the last step.

Two more properties replace columns in the lead sheet. The first is lifecycle stage, HubSpot's built-in field for where a person stands, such as lead, qualified lead or customer. The second is a custom property for the qualification reason. It follows the definition we set earlier: a qualified lead is a one- or two-van contractor with a penalty letter or a big year-end bill. Somebody with three vans, or a different reason for getting in touch, is marked not qualified, with the reason written down. Check whether the lifecycle stage field appears in Zapier's action. If it does not, set it inside HubSpot when the founder reviews the lead.

Routing stays simple. The founder owns every contact, and the next action is always the same: call. Zapier's free plan sets the limit here. As of November 2026 it includes a hundred tasks a month, and each Zap is limited to one trigger and one action. Creating the contact uses up that one action. A second step that creates a task for the founder needs a paid plan. Even then, check what HubSpot steps Zapier offers, because a plain Create Task action may not be there. The task may sit under a broader Create Engagement step. Until then, the founder's next action comes from the reply email and the owner notification Tally already sends.

One automated reply, sent from an authenticated domain

HubSpot's free tools allow one simple workflow per form, with one action: a follow-up email after the form is submitted. That is enough to replace the hand-pasted email. Higher plans allow more. Starter without Marketing Hub allows one workflow with three actions, and Marketing Hub Starter allows one with up to ten. Sequences, the timed series of one-to-one emails, need Sales Hub or Service Hub at Professional or Enterprise level, so they are off the table for now.

There is a catch to check first. This simple workflow is attached to a HubSpot form. Our contacts arrive from Tally through Zapier, and it is not clear whether such a contact triggers the workflow. Test it with one submission. If no email arrives, send the reply from Zapier instead, once you are on a plan that allows a second step.

A second catch is re-enrollment. Contacts enter the workflow again every time they submit, and the trigger cannot be changed. So a contractor who fills in the form twice gets the reply twice. That is tolerable for a factual reply, and it is the reason this workflow should never carry anything else.

Before any automated send, authenticate the sending domain. Authentication is how a receiving inbox checks that mail really comes from Ledgerlane's domain and was not forged. There are three records. SPF lists the servers allowed to send for the domain. DKIM adds a signature the receiver can check. DMARC tells the receiver what to do when those checks fail.

In HubSpot, go to Settings, then Content, then Domains and URLs, then Email Sending, and choose Connect sending domain. HubSpot gives you DKIM records to add as CNAME entries, an SPF entry and a DMARC entry, both as TXT records, in your domain's DNS settings. Your domain registrar or website host holds those settings. One pitfall breaks setups often. If your domain already has an SPF record, edit that record to include HubSpot. Do not add a second one, because two SPF records make the check fail. Back in HubSpot, the status reads Not authenticated, Partially authenticated or Authenticated. Wait for Authenticated, then check the records again with an outside checker such as MXToolbox or dmarcian.

Gmail is why this matters even at a small scale. Google's sender rules, in force since the first of February 2024, apply to every sender. You need SPF or DKIM, an encrypted connection known as TLS, valid reverse-lookup records and a spam complaint rate below three tenths of a percent. Senders of five thousand or more messages a day must also have SPF, DKIM and DMARC together, a From address that matches the authenticated domain, and one-click unsubscribe. A DMARC policy of none is allowed. Ledgerlane is nowhere near five thousand, but setting up all three records now costs nothing and covers the stricter rule later. Microsoft introduced similar rules for large senders, reportedly from the fifth of May 2025.

Keeping the reply a reply

The next question is permission. In the UK, PECR, the Privacy and Electronic Communications Regulations, applies to anyone who sends or instigates direct marketing by electronic mail. Filling in an inquiry form does not by itself give Ledgerlane permission to send marketing. Ledgerlane's audience makes this sharper. Sole traders and ordinary partnerships count as individual subscribers, the same as private people, and most one-van contractors are sole traders. So they need either consent or the soft opt-in.

The soft opt-in needs three conditions together. Ledgerlane must have got the details during a sale or the negotiation of a sale. The marketing must be for its own similar products. And the person must be offered a way to opt out when the details are collected and in every message after that. A booking for a diagnostic call may count as a negotiation, but only if all three conditions hold, so the form needs an opt-out choice at the point of collection. A newer soft opt-in for charities started on the fifth of February 2026 and is unlikely to apply to an ordinary business like this one.

So the automated reply answers what was asked and nothing more. It gives the chosen van price, the four inclusions and three exclusions, the line that penalty appeals are not included, setup in about two weeks from signing, and the one question about VAT registration. It carries no newsletter pitch, no offer and no tips series. Whether a reply like this counts as a service message rather than marketing is not settled for this case, so keeping it plainly factual is the safe choice.

Opt-outs must be free and simple, with no login. Anyone who opts out goes on a suppression list. That list is checked before any later marketing goes out, and it is acted on promptly. In HubSpot, the person's email subscription status does this job. Keep it accurate before the next chapter adds more emails.

Testing it twice with the same email

Run the test the way we ran the earlier one. Open the offer page on a phone in a private tab, using a link with source, medium and campaign all set to test. Submit the form as a one-van contractor with a penalty letter, named TEST plus today's date, using an email inbox you control. Then submit again with the same email but choose the big-bill trigger.

Then check four things. In HubSpot, search contacts by that email. You should find one record, not two, and its trigger property should now read the big-bill answer. Open the record and confirm the three campaign properties read test. In your inbox, look for the reply. Check that it came from the Ledgerlane domain and that its footer has a working unsubscribe link. You should also find a second identical reply, which is the re-enrollment risk showing itself. Finally, add a yes-or-no test property in HubSpot and set it on the record, so it stays out of every count, as the test rows do in the lead sheet.

Whether you run this now is your choice. One item still blocks launch either way: the reply-time placeholder in the booking confirmation waits for the owner. Once the test passes, every lead has one record, one owner and one correct first reply. That is the starting state for a short inquiry sequence built from where each contact actually stands.

Platform AI behind a higher tier

One platform release is worth knowing about: HubSpot's Breeze Agent Builder. It is part of HubSpot's Fall 2026 Breeze announcements in mid-September. It lets you build AI agents that act inside HubSpot's records, which sounds like a fit for the routing and follow-up work in this chapter. Two facts decide whether it is for you today. It is in public beta, so its behaviour and limits can still change. And it requires a Professional or Enterprise subscription. A Ledgerlane-sized account on HubSpot's free tools, or even Starter, cannot use it.

The way to judge a release like this is to ask which tier your account is on and which job the feature would do. Here the job is a single factual reply and a call task, and the free simple workflow already handles the reply. Make a short note in the project: Breeze Agent Builder, beta, Professional and above, to revisit if the account moves up a tier or if routing grows past one owner. Then stay with the simple workflow.

The broader habit carries over to every platform's AI. Before you plan around a new feature, check three things: the plan it needs, whether it is in beta, and what your current setup already does. A new product name does not prove the work got better.