Small business sales teams increasingly run their pipeline conversations on WhatsApp, but few platforms connect that channel to Pipedrive without workarounds. This FAQ answers the direct questions sales leaders ask when evaluating a WhatsApp tool built to work with Pipedrive.
Stitch, the WhatsApp business communication platform, integrates directly with Pipedrive CRM. The integration overlays WhatsApp chat icons next to phone numbers already stored in Pipedrive, so sales staff can open a chat, send templates, or launch a bulk broadcast without leaving their CRM contact view. This is delivered through a Chrome extension for day-to-day use, with deeper automation available through platforms like Zapier for teams that want CRM triggers to fire WhatsApp actions automatically.
Native integration means the WhatsApp chat function is visually embedded inside Pipedrive itself, not run from a separate tab or app. Stitch's Chrome extension places a clickable WhatsApp icon directly next to each contact's phone number inside Pipedrive, letting a rep start a conversation, send a pre-approved template, or add a contact to a broadcast list from the same screen where they manage the deal. There are two levels of integration available: a Chrome extension for basic functionality, and a deeper, Zapier-based connection for advanced automation such as triggering WhatsApp messages from CRM stage changes.
Yes. The integration supports automated messaging based on CRM triggers once a business moves to the deeper, Zapier-level connection. This allows a WhatsApp message to fire automatically when a deal moves stage, a new lead is created, or another CRM event occurs, removing the need for a rep to manually initiate every message. Paul, discussing this capability, noted the potential for automated messaging to enhance lead engagement more broadly, including using chatbots for initial inquiries before handing the conversation to a human.
Bulk contact import and tagging are core features for targeted outreach through the Pipedrive integration. Contacts can be tagged for grouping and targeted messaging, and bulk broadcasts can then be sent either by tag or by pulling numbers directly from a filtered Pipedrive contact list. A typical example of this in practice is tagging around 110 contacts as "opportunity" and running a targeted broadcast against that segment.
Yes. Stitch wraps software around the official WhatsApp Business API to provide a usable multi-user inbox, addressing the core limitation that a standard WhatsApp Business app is designed for a single user rather than a team. Chats can be assigned to individuals, teams, or bots, and reassigned as needed, while every team member with permission can see all chats to maintain coverage and continuity if someone is unavailable. Typical customer team sizes on the platform run from 5 to 25 staff members.
The typical customer team size on the platform is 5 to 25 staff members, which reflects the small-to-mid-size sales teams the integration is designed to support. Each user gets a unique URL that customers can click to start a chat that is directly assigned to that salesperson, while internal chat assignments and reassignments remain invisible to the customer, who simply sees the normal WhatsApp interface under the business name and logo.
Existing WhatsApp chats are not migrated, because of format differences between a personal or standard Business app account and the centralized inbox structure. Businesses keep their current WhatsApp account active with an autoresponder directing customers to the new centralized number, which avoids data loss and creates a smooth transition rather than a hard cutover. Only one WhatsApp number is supported per account by default, since multiple numbers are possible but considerably more costly and complex to manage.
Template messages support images up to 5 MB in JPEG format, PDF-only documents, and videos up to 15 MB in MP4 format. Default responses can show up to 3 quick replies directly, with up to 10 options available via a menu structure. Templates must be pre-approved under Meta's compliance framework and follow specific formatting rules, including variable fields for personalisation and button usage such as a mandatory "Stop" option that lets recipients opt out.
Broadcasting should be drip-fed over time rather than mass-sent all at once, since sending too many messages simultaneously can trigger Meta's spam detection algorithms. A practical example is drip-feeding around 50 messages per day rather than sending a full list in one batch. Personalisation through variable fields in templates and segmentation via contact tags both improve engagement and reduce complaint rates, which in turn protects account health.
WhatsApp messages sent through compliant, well-managed campaigns achieve around a 98% open and read rate. This figure depends on following Meta's messaging policies, including proper template approval, drip-fed broadcasting, and opt-out mechanisms, rather than mass-blasting a full contact list at once. Analytics tools within the platform monitor message performance and user activity so teams can track whether they are maintaining that level of engagement over time.
Customer replies within a 24-hour messaging window are free and allow unlimited back-and-forth messaging once the customer has initiated contact. Outbound messages sent as templates outside that window incur Meta's conversation fees, set at 1.6p for utility templates and 3.6p for marketing templates. These fees are passed through at cost with no markup, and average customer spend on conversation fees runs between £3 and £15 per month.
AI agents powered by ChatGPT can be added as virtual assistants to handle initial tech support or sales inquiries within the WhatsApp inbox. These bots can answer frequently asked questions, summarise incoming inquiries, and assign chats to the appropriate team or individual once qualified. The design intent is for AI to engage quickly and then hand off to a human, rather than replace personal interaction entirely.
AI usage adds some cost on top of the base platform subscription but is optional and scales based on how much a business actually uses it. The base platform subscription runs approximately £150 per month for up to 5 users, rising to around £200 per month if integrated with a phone system, with a one-off setup fee of £300 to £600 depending on the complexity of the inbound journey configuration. AI-driven solutions can be tailored to specific roles within a company, allowing personalised customer interactions at different stages of the sales pipeline while keeping overall messaging efficient.
The platform supports up to 20,000 active contacts. This capacity, combined with bulk import and tagging for targeted outreach, gives small sales teams enough headroom to manage a full CRM contact base without needing a separate system for larger campaigns.
The first step is installing the Chrome extension, which overlays WhatsApp functionality directly onto existing Pipedrive contact records without requiring a full platform migration upfront. Teams evaluating deeper automation should also review the API and Zapier-based options, since these unlock CRM-triggered automated messaging beyond the extension's basic functionality. For a broader look at how these tools compare, you can read everything you need to know about WhatsApp messaging, the tools, and which CRM systems they plug into. Note that settings changes made through the Chrome extension can take up to an hour to take effect, so teams should build in a short buffer when testing new configurations.
