Choosing a WhatsApp platform that connects to Salesforce without custom build work is one of the most common questions we hear from UK businesses evaluating the WhatsApp Business Platform. Below, Stitch, the WhatsApp business communication platform, answers the most frequent questions on Salesforce connectivity, what "no custom development" really means in practice, and what to check before you commit.
Some WhatsApp platforms connect to Salesforce with minimal setup, while others require API-level work to get message data flowing into your CRM. CRM Dog, for example, is described as a stripped-down platform focused on visibility and CRM integration, syncing WhatsApp messages into Salesforce without managing the underlying WhatsApp settings themselves. More advanced platforms, like Message Box, support shared inboxes and team assignments as a pro-level option suited to higher-volume or shared-number use cases. The right fit depends on whether you need simple message visibility in Salesforce or a fuller shared-inbox workflow layered on top.
A lightweight sync tool typically handles visibility and message syncing only, leaving WhatsApp settings such as forwarding or out-of-office replies on the user's own phone. A full integration platform, by contrast, centralises those settings and supports shared inboxes with team-based assignment, which matters once more than one person needs to work from the same WhatsApp number. Meta itself does not provide native software for the WhatsApp Business Platform, which is why third-party platforms exist to fill this gap with varying levels of Salesforce depth. Before choosing, map your actual requirement (visibility versus full team workflow) against which tier of platform you're evaluating.
Coexistence lets a business continue using the standard WhatsApp Business app on a phone while gaining centralised visibility through a connected platform such as CRM Dog. This means a team can keep familiar day-to-day WhatsApp usage while message data still flows through to systems like Salesforce for visibility and reporting. It's a useful bridge option for businesses not ready to move every user onto a shared-inbox platform. If your Salesforce use case is primarily about capturing conversation history rather than full team routing, coexistence-based syncing is worth evaluating first.
Not necessarily, but it depends on how deep the integration needs to go. Platforms confirm they offer an API allowing message extraction and integration, but that API is designed for message flow and response handling rather than embedding directly into a third-party UI. Basic automation, such as keyword or phrase-based flows and simple AI agents configured with prompts, is available through a GUI without developer involvement. More advanced bot behaviour, such as data lookups against external systems, requires custom development via the API and sits outside what most platforms treat as core product functionality.
Most customers rely on professional services to implement automation because the technical expertise required is often beyond what an in-house team has readily available. The platform focus tends to be on simple, repeatable automation suited to distributed sales and service teams, rather than complex contact-centre-style bots. This means "no custom development" is realistic for standard message routing and keyword-triggered flows, but less realistic for bespoke Salesforce logic like automated record updates tied to conversation content. If your requirement is closer to the latter, budget for implementation support rather than expecting a pure no-code path.
Not always, and this is worth checking directly with any vendor before signing. In at least one case, a business noted the website lacked visible API documentation, even though the vendor confirmed APIs exist for message flow and response handling once asked directly. This gap between public documentation and actual capability means it's sensible to request API documentation directly during evaluation rather than assuming it's published. Ask specifically for message-extraction and response-handling documentation before assuming Salesforce connectivity will be straightforward.
A working setup typically syncs WhatsApp conversations into Salesforce for visibility while leaving day-to-day messaging on the familiar WhatsApp interface. Discussions of WhatsApp integration and GDPR compliance specifically reference CRM Dog alongside Salesforce as a paired solution for this kind of syncing. This pairing addresses two needs at once: getting conversation data into the CRM your sales and service teams already use, and keeping a compliant record of customer communication. For businesses already standardised on Salesforce, this kind of pairing avoids duplicating workflows across separate tools.
Yes. Some third parties use the available API independently, without direct involvement from the core platform provider, to build their own connections into systems like Salesforce. This is a relevant option if your business already has development resources and wants a bespoke integration rather than an off-the-shelf sync. It also means the "no custom development" question has two honest answers: a fast path using an existing connector, and a slower, more flexible path for teams who want to build their own logic on top of the same API.
WhatsApp can be integrated with Apex to improve communication and automation within a Salesforce-based workflow. This route sits closer to the custom-development end of the spectrum, aimed at businesses that want automation logic written directly against Salesforce's own development framework rather than relying on a third-party platform's built-in automation. It suits organisations with existing Salesforce development capability who want tighter control over how WhatsApp messages trigger records, workflows or notifications inside Salesforce itself.
Ask whether the integration is a full sync (messages and CRM records) or a lightweight visibility layer, since these require very different setup effort. To understand the broader landscape, you can consult a WhatsApp business tools CRM integration guide to see how different platforms handle these connections. Ask for API documentation covering message extraction and response handling specifically, since this isn't always published publicly even when the capability exists. Ask whether basic automation is available through a no-code GUI, and where the line falls before you need professional services or custom development. Ask how the platform handles shared inboxes versus single-user WhatsApp settings, since this affects whether Salesforce visibility extends across a whole team or just one number.
Scaling to larger user counts can introduce real complexity, particularly around WhatsApp's own domain and number-extension limits rather than Salesforce itself. Scaling to 200 users could require ten or more domains, which can become complex and problematic over time. Meta does offer a number-extension process to raise these limits, but it is rarely granted, with only one client reported to have succeeded. Factor this constraint into any Salesforce rollout plan that assumes rapid headcount growth on a single WhatsApp number setup.
Basic Salesforce visibility and message syncing is achievable without custom development, particularly through platforms built specifically for that purpose. Simple automation, such as keyword-based flows, is also achievable through no-code GUIs without developer involvement. Anything beyond that, such as advanced data-lookup bots or deep Apex-level workflow logic, moves into custom-development territory and typically requires either professional services or in-house development resource. Treat "no custom development" as accurate for connectivity and basic automation, and plan separately for anything involving bespoke logic inside Salesforce.
