Freshworks puts two extra hurdles in front of mobile trials and demos
On mobile, "Start for free" opens behind a cookie panel. The homepage took more than nine seconds to show its main content. The demo form then asks seven questions before a 20-minute call.
Owner brief
We checked the Freshworks homepage on phone and desktop, followed the free-trial route, opened the demo form, and tested 20 public links. Three leaks stood out between first interest and a trial or sales conversation.
We also checked current public ad sources but could not tie a live paid ad to a Freshworks destination. Ad-to-page message match was not assessed.
Funnel depth tested: public homepage → product and free-trial selector → demo form displayed. We did not choose a product, start a trial, type into the form, submit details, create an account, test a confirmation page, or check email follow-up.
Highest-priority revenue leaks
The mobile trial path opens behind a cookie decision
The homepage offers "Start for free." That click does not begin a trial. It opens a product selector, where the visitor must first decide which Freshworks product fits.
On a fresh phone visit, a large cookie panel covered that selector. The page title was visible. No product choice or trial button was.
This puts two decisions between intent and action: clear the privacy panel, then choose a product. Some visitors will stop before Freshworks learns what they wanted.
Keep the privacy choices easy to find, but reduce the panel's height on phones. Leave at least one product choice and its trial action visible. FunnelWatch should open this route with fresh consent on common phone sizes and alert when the trial choices disappear below an overlay.
Phone visitors wait more than nine seconds for the pitch
The homepage has a clean promise and clear paths to a demo or free trial on desktop.
The wait is the leak. In our fresh phone check, the main content appeared after 9.1 seconds. The page downloaded about 12.8 MB through 338 requests before settling. Even desktop took 6.8 seconds to show the main content.
That is enough time for an interested visitor to decide the page is not ready. Load the headline and first action before videos, chat, tracking extras, and content farther down the page. FunnelWatch should time the homepage after every release and alert when the promise or first action takes more than a few seconds to appear.
The demo form asks seven questions before a 20-minute call
Freshworks promises a short, 20-minute conversation with a product expert. Before that conversation, the form asks for first name, last name, work email, phone, company, organization size, and solution of interest. Six are required. The fresh view also showed the marketing-consent box already selected.
Every extra answer gives a qualified prospect another reason to pause. Start with work email and solution of interest. Ask for company size during scheduling or after the first step. Leave optional marketing consent unselected so the demo request stays focused on the visitor's intent.
FunnelWatch should keep checking the complete demo route, including field count, consent defaults, submit behavior, confirmation, and follow-up email once an approved test inbox is available.
What is working
The homepage gives visitors both a demo and a free-trial path. The demo page explains what happens next and says the call lasts 20 minutes. All 20 sampled links returned successfully. Campaign details stayed attached to the homepage visit. No block or human-verification screen appeared in the published captures.
Fix this first
Make the mobile trial choice visible without forcing the visitor through a screen-filling overlay. Then cut the initial homepage load and shorten the first demo step.
These leaks can return when consent tools, videos, tracking, forms, or product routes change. FunnelWatch keeps testing the live path so Freshworks can catch a buried trial button or a heavier lead form before weeks of visitors hit it.