The short answer
Write the process down in one page. For demo requests: acknowledge instantly, route to a named owner with a backup, spend a few minutes on context, send a personal first reply that offers times, follow up a fixed number of times, and record every outcome with a reason. For identified visits: filter for fit and high-intent pages, check for an existing contact or open deal, choose a proportionate action, and record what you did. Review both every week.
Two kinds of inbound signal
Most follow-up problems start with treating every inbound signal the same. There are two very different kinds, and they need different handling.
| Demo request or contact form | Identified company visit | |
|---|---|---|
| Who asked? | A named person asked to talk to you | Nobody: a tool matched a visit to a company |
| What you know | Name, email, company, often their question | A company name, where it can be found, and the pages read |
| How certain | High, once spam is removed | Lower: the match may be wrong, and the visitor may not be a buyer |
| Right response | A fast, personal reply from a person | A considered decision: watch, warm up an existing relationship, or reach out with something useful |
| Wrong response | A shared inbox and a generic sequence | An instant cold email saying you saw them on your site |
Why speed matters so much for the first kind is set out, with the research, in our speed to lead statistics. This page is about the process that makes speed possible.
Agree the basics first
Before you build alerts or templates, agree five things and write them down where everyone can see them.
- Definitions. What counts as an inbound lead (a demo request, a contact form, a pricing enquiry, a chat that asks for a call) and what counts as an account signal (an identified visit that meets your rules).
- Ownership. Who owns each kind, by name, and who covers when they are away. A shared inbox is not an owner.
- Hours. Your working hours, what happens outside them, and what the buyer is told.
- Response targets. A time to first reply you can meet every working day, set by you and measured, not borrowed from a benchmark.
- Outcomes. A short list of ways a lead can end, so every one is closed with a reason (see the table further down).
After a demo request: the process step by step
1. Acknowledge at once
The buyer should know immediately that the request arrived and what happens next: who will reply, by when, and, if your team can take meetings that way, a link to book a time. The confirmation page and email are part of the form, and our guide to demo request form optimisation covers them in detail.
2. Route to a named owner
Routing rules should be simple enough to explain in a sentence each. Common rules, in the order they are usually checked:
- Existing customer or open deal? Send it to the account owner, not to new business.
- Partner, supplier, job seeker or press? Send it to the right person outside sales, and close it as not a lead.
- Region, size or product line? Route by whichever one decides who would run the deal.
- Otherwise: a simple rotation, with the backup named for holidays and sickness.
The alert should reach the owner where they already work, usually the CRM and team chat, with the lead's details and a link to the record. Test the whole route once a month by submitting a request yourself.
3. Take a few minutes for context
A short check before the first reply makes it personal without slowing it down. Keep it to a few minutes:
- What did they write in the form? Answer that first.
- What does the company do, and is it in your target market?
- Is there history in the CRM: past conversations, an old opportunity, a former customer?
- Which pages did they read before submitting, if your tools show it?
- Is it real? Obvious spam and test submissions are closed now, with that reason.
4. Send a personal first reply
The first reply has three jobs: confirm a real person has read the request, answer or acknowledge their question, and make it easy to agree a time. Email and a phone call both work; many teams do both, with the call first. An example to adapt:
Subject: Your demo request, [Company]
Hi [First name],
Thanks for asking about [what they asked about]. I look after
[region or sector] at [your company], so I will be your contact.
You mentioned [their question or situation]. In short, [one or two
sentences that answer it honestly, including if it is not a fit].
Would any of these work for a 30-minute call?
[Option 1], [Option 2] or [Option 3]
Or pick a time here: [booking link]
If it helps me prepare, which tools do you use for [relevant area] today?
[Name]
[Role], [direct phone number]Avoid long qualification questionnaires before the meeting. Ask the one or two questions that change how you prepare, and save the rest for the call.
5. Follow up a fixed number of times
Buyers who asked for a demo still miss emails, go on holiday and get pulled into other work. Agree a fixed sequence so every lead gets the same treatment. One illustrative pattern, not a benchmark:
| When | Channel | Content |
|---|---|---|
| Day 1 | Phone and email | The first reply above |
| Day 2 | Phone | A second call attempt at a different time of day |
| Day 3 | A short reply to your first email, with new times | |
| Day 6 | Something useful: a relevant case study or answer to their likely next question | |
| Day 10 | A polite close: you will stop following up, and how to get back in touch |
Stop as soon as they reply, book or say no. If they ask not to be contacted, record it and respect it everywhere.
6. Hold the meeting, or close the lead
If a meeting is booked, send a short agenda and confirm who will attend from both sides. If the lead is not a fit, say so politely and, where you can, point them somewhere useful. A clear no is better for the buyer than a long silence.
7. Record the outcome
Every lead should end in one of a short list of states, each with a reason. A list like this is enough for most small teams:
| Outcome | Meaning |
|---|---|
| Meeting booked | A first call is in the calendar |
| Not a fit | Wrong size, sector, region or need, with which one |
| Not a lead | Spam, job seeker, supplier, partner, press, student |
| Existing customer | Passed to the account owner |
| No response | The sequence finished without a reply; moved to nurture |
| Not now | Interested, but with a stated later date to come back |
The reasons matter more than the counts. If a third of demo requests are not a fit, the website is attracting the wrong buyers or failing to explain who you serve, which is a website problem, not a sales one.
After an identified company visit
An identified visit is a weaker signal than a demo request. IP-based identification names a company, not a person, and it can be wrong; HubSpot, for example, describes its own visit identification as probabilistic1. The visitor may also be a job applicant, a supplier or a competitor. That makes the process slower and more selective by design.
1. Decide whether it is worth acting on
Act only when a company is both a fit and shows real interest, for example repeat visits, several people, or high-intent pages such as pricing, integrations or a comparison. Everything else goes into a weekly review. Setting up those rules and filters is covered in how to see which companies visit your website.
2. Check the context
- Is it an existing customer? Pass it to the account manager, with the pages read.
- Is there an open deal or a recent conversation? Tell the owner; it may change what they say next.
- Did a campaign just reach them? Note it, and do not assume the campaign caused the visit.
- Is it plausible? A match that does not fit the pages read may be a wrong match.
3. Choose a proportionate action
From lightest to strongest:
- Watch. Add the company to a watch list and see whether interest continues.
- Improve what they read. If several target companies leave the same page, that page is worth improving.
- Warm an existing relationship. If someone on your team already knows a person there, a normal check-in is the most natural route.
- Reach out with something useful. A relevant message to a suitable role, about a problem companies like theirs have, with no reference to the visit. Take particular care with sole traders and very small firms, where a company name can point to a person, and with tools that suggest named contacts for a visiting company.
Whether and how you may contact a person at that company, and what your privacy notice must say about identifying visiting organisations, are data protection questions. We do not give legal conclusions here; our guide to visitor identification under UK GDPR sets out the rules, and you should take your own advice on your own set-up.
4. Record what you did
Log the action and the result against the company in the CRM. After a quarter, you can see which kinds of signal led to conversations and which did not, and tighten the rules. If the signal came from a bought source rather than your own site, our guide to B2B intent data explains what each type can and cannot tell you.
An internal alert that gets acted on
Whatever tool sends it, an alert for an identified visit should give the owner enough to decide in a minute, and nothing that encourages a careless cold message. An example layout:
Account signal: [Company] ([sector], [size], [location])
Fit: target segment [yes/no]
Visits this week: [number] sessions, [number] on high-intent pages
Pages: /pricing/, /integrations/[name]/, /case-studies/[sector]/
CRM: [no record / customer / open opportunity, owner]
Suggested action: watch / tell account owner / useful outreach
Reminder: do not mention the visit in outreach.Measure the process, not just the leads
A short monthly review keeps the process honest. Track:
- Time to first reply, as a median and for the slowest tenth, in working hours. The slowest leads show where the process breaks.
- Leads with no reply at all. This should be zero, and the monthly test submission proves it.
- Contact rate and meeting rate for demo requests, from your own CRM.
- Outcome reasons, especially not a fit and not a lead, as a check on what the website attracts.
- Account signals acted on, and what came of them.
If you track demo requests in Google Analytics as well as the CRM, our guide to GA4 key events for B2B websites covers reconciling the two.
Where follow-up usually breaks
- A shared inbox. Everyone assumes someone else replied.
- No cover. Leads wait while the owner is on holiday.
- A broken route. A form change, a CRM field rename or an expired integration quietly stops leads arriving.
- A generic sequence. Automated emails that ignore what the buyer asked.
- Chasing every visit. Treating identified visits like demo requests wastes time and annoys buyers.
- No outcomes. Leads left open forever, so nobody learns which ones were worth having.
A one-page checklist
- Inbound lead and account signal are defined in writing.
- Every lead has a named owner and a named backup.
- The confirmation page and email say who replies and by when.
- Routing rules fit in a few sentences, and existing customers go to their account owner.
- Alerts arrive in the CRM or team chat, not a dashboard.
- The first reply is personal, answers the question and offers times.
- The follow-up sequence has a fixed number of steps and a polite close.
- Every lead ends with an outcome and a reason.
- Identified visits are filtered for fit and intent, and outreach never mentions the visit.
- A test request is submitted every month, and response times are reviewed.
Where Artiweave fits
Artiweave works on the pages buyers read before they reach this process, with every change approved by a marketer. Showing which companies visit is in development and not available yet; when it is ready, it will identify companies, not individual people, so the lighter process for identified visits above is the one that will apply. For the wider topic, see our guide to website visitor identification.
Frequently asked questions
How quickly should we follow up an inbound demo request?
As fast as you can reliably manage, and set a written target that the team can meet every working day, including when someone is on holiday. The research on response times, collected in our speed to lead statistics, shows the odds of reaching and qualifying a lead fall quickly, so measure your own time to first reply and work it down.
How many times should we follow up if a lead does not reply?
Agree a fixed number of attempts over a fixed period, for example five or six over two working weeks, mixing email and phone, then close the lead with a reason and move it to nurture. The point is that every lead gets the same, recorded treatment, not that one number is right.
Should we contact a company that visited our website but did not fill in a form?
Only when it is a good fit and the visit shows real interest, such as repeat visits to pricing or a comparison page, and usually through an existing relationship or a relevant, useful message rather than a cold note about the visit. Whether and how you may contact a person is a data protection question to check for your own set-up.
Who should own inbound lead follow-up in a small team?
One named person per lead, with a named backup. In a very small team that may be a founder or the one salesperson, with marketing owning routing, the alert and the weekly review of what happened to each lead.
Sources
Improve the pages buyers act on.
Artiweave continuously improves the website your B2B company already has, with every change approved by you and every outcome reported honestly. Showing which companies visit is in development. It is in private beta.