Download websites that use Salesforce Service Cloud

About Salesforce Service Cloud

Support software is bought for what happens after the sale, and most of what it does happens where a crawler cannot see it. Agents work inside a console. Cases move through queues. Knowledge articles get written and revised. None of that touches the public HTML of the company's website, which is the honest starting point for reading this record.

Salesforce Service Cloud is the CRM product Salesforce sells for customer service rather than for sales, launched in 2009 on the same underlying platform. Licensing is Commercial and per seat, so the buyers are organisations with a support headcount to justify it: contact centres, subscription businesses, hardware companies, anyone whose customers open tickets. The parts we can detect are the parts deliberately pointed at customers, which is a much smaller set. Embedded chat and messaging widgets, web-to-case contact forms, and self-service help centres and communities served from the platform are what leave a trace.

So the figure here undercounts, and not by a small margin. A company can run the entire product internally, route every case through phone and email, and expose nothing on its marketing site. A company can also serve its help centre through a custom domain and a CDN in a way that obscures the origin. What our record does capture reliably is the set of sites that have chosen to put a customer-facing support surface on the open web, which is a useful population in its own right and should never be confused with a licence base.

By September 2026 that visible population stands at 879 domains. A per-domain check tells you that one company embedded a widget. The export tells you how the visible support layer is distributed: which ecommerce and CMS platforms these sites run, whether they pair the widget with a separate chatbot or review tool, which industries expose self-service portals at all, and which domains carry support surfaces from more than one vendor at once, usually the residue of an unfinished migration.

Competitive teams at rival support vendors read a list like this as a displacement target, since a visible widget is proof of an active customer-facing deployment rather than a shelfware seat count. Integration and app vendors read it as an addressable base for connectors. Analysts read it as a way to observe enterprise software adoption without relying on vendor-reported customer numbers, which are rarely comparable between companies. In every case the value comes from the join, because knowing which sites expose Salesforce Service Cloud matters less than knowing what else those sites run beside it.