Short answer: HubSpot chat is a component of a CRM and marketing platform. Its value comes from everything around it, contacts, deals, email, workflows, reporting. If you want the ecosystem, take the chat as part of it. If you just want your website to stop losing enquiries and you have no intention of running a CRM, a standalone lead-capture widget like Clerkzo does that job with far less around it.
Platform components are priced in trust, not features
When a chat widget ships inside a CRM, you are not really evaluating the widget. You are deciding whether to run your business inside that platform. The chat is a doorway. Its real payoff is that every conversation becomes a contact record, feeds a workflow, appears in attribution reporting, and connects to deals.
That is a coherent and often excellent proposition. It is also a commitment. Data model, processes, and eventually team habits all shape themselves around the platform. Fine if you want that. Heavy if you do not.
For what HubSpot includes at each tier today, check their site. Platform packaging changes regularly and I am not going to characterise it from memory.
Do you actually need a CRM?
Answer four questions honestly and the decision usually makes itself.
Does an enquiry pass through more than one person before it becomes a customer? If someone captures it, someone else quotes, and a third person closes, you need shared records. If it is you from first message to invoice, you need a list.
Do you follow up more than twice? A sales process with sequences, reminders and stages needs a system. A process of ring them back, then ring them once more, does not.
Does anyone ask which marketing produced which customer? If the answer is a genuine yes and someone will act on it, attribution has value. If it is a vague wish, it will not survive contact with data entry.
Is there a person who will keep the data clean? This is the one that decides it. A CRM with stale records is worse than a spreadsheet, because people trust it slightly and should not.
Most five-person service firms answer no, no, not really, and no. That is not disorganisation. It is a correct read of what a small business needs.
Who should go all in on the platform
Buy into a CRM platform if:
- You want contacts, deals, email marketing, and reporting in one system and are willing to work in it daily.
- You run a real sales process with stages, forecasts, and follow-up sequences.
- Attribution matters to you, knowing which page or campaign produced which deal.
- You have, or will hire, someone who owns the system and keeps the data clean.
- You plan to grow into marketing automation rather than just capturing enquiries.
If that is the direction, adopting the platform's own chat is sensible. Bolting a third-party widget onto a platform you are committed to just adds a seam.
What most small service businesses want instead
The other very common case: you are not going to run a CRM. Not because you are disorganised, but because a five-person firm with a phone, a calendar, and an email inbox does not need one. Every attempt to adopt one has ended with a half-populated database nobody trusts.
What you actually want is embarrassingly simple:
- The widget answers questions from your own website content, all day and all night.
- It collects details when someone is interested, either conversationally or via a short in-chat form with your custom fields.
- You find out immediately, by email, webhook, or Telegram.
- There is one list with a simple pipeline, New, Contacted, Qualified, Won or Lost, that you can clear in five minutes each morning.
- Nothing else. No workflows to design, no properties to define, no data hygiene project.
That is Clerkzo's entire remit. The leads inbox is deliberately a light pipeline, not a CRM, because the moment it becomes a CRM you stop using it.
And if you do run a CRM, the webhook pushes leads straight in, so the widget can feed a platform without being one. There is a plain description of the flow on how it works.
The categories, and who each one is for
People searching for HubSpot chat alternatives are usually standing in one of four aisles.
CRM and marketing platforms. HubSpot's own category. For businesses running a real sales process who want conversations, contacts, email and reporting in one place, and who have someone to run it.
Conversational marketing and sales tools. Built around routing website visitors to sales reps and booking demos, usually B2B. Powerful if you have reps to route to, and pointless if you do not. The Drift comparison sets out that shape.
Chatbot builders. You design the flows yourself. Total control, and a maintenance job that quietly falls to whoever has least to do that week.
AI website widgets trained on your own content. The widget learns from your existing pages, answers in your own words, captures the enquiry with the fields you chose, and delivers it. No platform underneath. This is where Clerkzo sits.
The mistake is comparing across aisles on feature count. A platform will always list more. The relevant question is which one matches the way your business actually runs this week.
What a captured lead should look like
This is the practical test, and it is more revealing than any demo.
A good captured enquiry arriving in your inbox at 8pm contains a name, one contact route that someone will actually answer, what the person wants in their own words, when they are available, and a link to the full transcript. That is enough to ring them at 9am and sound informed.
A poor one contains an email address and the word interested.
The difference is not AI quality, it is whether the tool was designed around capture or around record-keeping. Platforms are excellent at record-keeping. Ask the vendor to show you the actual notification a real enquiry produces, not the dashboard.
Speed matters as much as content. The reason is unglamorous arithmetic rather than theory, and it is set out in speed to lead. The related failure, where enquiries are captured properly and still evaporate before anyone rings, is covered in why you lose leads between website and inbox.
How to evaluate any alternative
Answer quality. Test with three questions from your own inbox, including one your site cannot answer. Watch for invention. Clerkzo trains by crawling your site, has guardrails and human handoff, and a corrections loop for the answers you want changed.
Setup time. Distinguish the widget's install from the platform's onboarding. A widget can be live in ten minutes, a CRM implementation is a project. Neither is wrong, but pick knowingly. Clerkzo also offers done-for-you setup.
Lead capture. Ask what a captured lead looks like and where it lands. Fields you control, delivered fast, visible in one place, is the bar.
Billing model. Platform pricing tends to step up by tier and by contact volume, which is fine at scale and awkward for a small firm. Clerkzo is flat from nineteen dollars a month with a fourteen-day free trial and no per-conversation billing. See pricing.
Design control. Check colours, copy, launcher icon, position, and CSS isolation. Clerkzo uses Shadow DOM and a Widget Studio so it does not fight your theme.
What to check before you commit
- Does the plan you are pricing actually allow the widget on your live site, or is the cheap tier a sandbox?
- Is the thing you came for, capturing enquiries, included, or is it an upgrade?
- Does the price rise with contacts, conversations, or seats? All three grow whether or not you get more value.
- Can you cancel monthly, and can you export your leads if you do?
- Who installs it, and is it one script tag or a project?
- Does it work properly on a phone, where most evening traffic comes from?
The mistakes people make choosing here
Adopting a platform for one feature. If the chat widget is the only part you will use, you are paying for the other nine tenths in money and in habits.
Assuming you will grow into it. Sometimes true. More often the platform sits half-configured for a year and gets cancelled. Buy for the business you have, and keep the exit cheap.
Ignoring the seam. Running a third-party widget on top of a platform you are committed to means two places where a contact can exist. Pick one system of record and let the other feed it.
Confusing richer records with more customers. Better data about the enquiries you already get is not the same as getting more enquiries. Be clear which problem you are buying for.
Never reading the transcripts. Whatever you choose, the first fortnight of conversations tells you exactly what your website fails to explain. That is free research and almost nobody looks.
Choose them if, choose Clerkzo if
Choose the CRM platform's chat if you are committing to that ecosystem, you want conversations to become contact records and feed workflows, and you have the appetite to run the system properly.
Choose Clerkzo if you want a widget, not a platform, you want it live today, and your success measure is more named enquiries rather than richer contact records. If you later adopt a CRM, send leads there by webhook and keep the widget. See compare for the category map, or lead capture if you want the term defined plainly.
Honest limitation: Clerkzo does not do email marketing, deal management, or attribution reporting. If those are on your roadmap, plan for a CRM eventually and treat the widget as the front door rather than the whole house.
Frequently asked questions
Can I use Clerkzo alongside a CRM?
Yes. The webhook sends each captured lead wherever you want it. Plenty of customers run a CRM and use the widget purely as the capture layer.
Is the leads inbox a CRM?
No, deliberately. It is a short pipeline so enquiries do not get lost. If you need forecasting and deal stages, use a CRM.
Do I lose attribution data?
You will not get full multi-touch attribution from a widget. You do get the transcript, which often tells you more about intent than a source field does.
Is there a per-user cost as my team grows?
No, because there are no agent seats to buy. That is a deliberate limitation as much as a saving: there is no multi-login, no roles, no assignment. If your team needs separate logins and permissions, that is a genuine reason to look at a platform.
What if I already have a form and it works?
Keep it. Then add a widget and compare the numbers for a month. The reasoning behind why conversations tend to outperform forms is in chatbot vs contact form.