A website customer journey is the path a visitor takes from the page they land on to the action that makes them a lead: a form, a booking or a call. If that path is unclear or unrecorded, you pay for traffic and cannot say which pages turn it into business. This article answers how to design that path on the levelpartner.ai platform, capture where each visitor came from, and report on which pages and forms actually produce booked calls.
The three parts of a website journey
Every website journey has an entry, a middle and an exit. The entry is the landing page, which should match the promise of whatever sent the visitor there. The middle is the evidence: case studies, process, pricing logic, proof. The exit is the conversion: a form, a calendar or a phone number.
Most service firm websites get the entry and the exit wrong. Visitors from a specific ad land on a generic homepage, then hunt for a contact link buried in the footer. Fixing those two ends usually matters more than redesigning the middle.
Before you start
- A list of your main traffic sources: search, paid ads, social, email, referrals.
- The pages each source currently sends people to.
- A calendar set up in Calendars for discovery or consultation calls.
- Access to Sites, Calendars, Automation and Dashboard.
How to set it up
- Pick the three traffic sources that bring the most visitors.
- Build or choose one landing page in Sites for each source.
- Match each page headline to the ad or link that sends visitors there.
- Place a booking calendar or short form above the fold on each page.
- Add a Source element to each page's form, named after the page.
- Add a Form Submitted workflow with a Create/Update Opportunity action.
- Add a Customer Booked Appointment workflow confirming by email and SMS.
- In Contacts > Smart Lists, filter by each page's contact source.
- Add Contacts Count Over Time with First Attribution, grouped by Session Source.
- Compare the two monthly and rework the weakest page first.
What the journey is for in a stalled business
A company with 60 staff and flat revenue usually has enough traffic. What it lacks is a clear route from visit to conversation. Adding a direct booking option often lifts the number of calls without any extra spend, because visitors who are ready to talk no longer wait for someone to reply to a form.
Recording the source on each booking also ends the guesswork about which channel works. You might find, for example, that paid social sends lots of visitors who rarely book, while a niche directory sends few who nearly all do.
Say all traffic goes to the homepage and produces around 40 enquiries a month. Now suppose three source-specific landing pages with an embedded booking calendar bring 38 enquiries and 26 booked valuations a month from the same traffic. Enquiries would barely move, but the share turning into a booked appointment would rise sharply, and that is the number that matters.
What it replaces
It replaces the contact form that sends an email to a shared inbox and waits for someone to respond. It also replaces the guess about which page "works". With page and source recorded on every contact, the answer sits in a widget rather than in a debate.
Weekly time it takes
Building three landing pages and their forms takes one to two days. After that, look at the page counts for ten minutes a week. Once a month, pick the weakest page and change one thing: the headline, the form length, or the placement of the calendar. Leave each change for at least four weeks before judging it.
The mistake most people make
Asking for too much on the first form. Every extra field costs submissions. Collect name, email, phone and one qualifying question. Gather the rest on the call or with a follow-up form once the visitor has committed to a conversation.
When not to use it
If your website gets very little traffic, building separate landing pages for each source spreads too few visitors too thin to learn anything. Focus on one strong page and on getting traffic first. Separate pages also matter less when almost every client comes by referral and visits only to check you are real. A clear about page and a phone number may be all you need.
The wider view of online behaviour is covered in the digital customer journey guide. To follow each visitor once they become a contact, read about customer journey tracking. For giving credit across several visits, see first-touch, last-touch and linear credit.
Troubleshooting
Attribution arrives empty. The ad links do not carry UTM parameters, or a redirect strips them. Test each link in a private browser window and submit a dummy form.
Bookings appear but no opportunity is created. The calendar is not set to create an opportunity. Add a workflow triggered by the booking that creates one in the right pipeline stage.
The page looks fine on desktop and breaks on mobile. Most visitors arrive on a phone. Preview every page at phone width in Sites before publishing.
Submissions drop after a page change. Revert the change and test one element at a time.
Frequently asked questions
Should every page on the site have a booking calendar?
No. Put the calendar on landing pages and on pages near a decision, such as pricing and case studies. Educational pages are better served by a softer next step, such as a guide download.
How do I know which page a visitor first landed on?
Give each page's form its own Source value. Platform forms also record attribution, which you can read on the contact's Activity tab.
Can an AI agent help on the website?
An AI chat agent can answer common questions on the page and offer a booking slot in the same conversation. It helps visitors who would otherwise leave rather than fill in a form.
What should I measure first?
Booked calls by landing page. It is closer to revenue than visits or form fills and is simple to read.