Connecting WhatsApp Business API to your CRM turns a manual, email-first workflow into a fast, trackable messaging channel your negotiators actually use. This guide walks through the setup process for two of the most common estate and lettings CRMs, Alto and Rex, covering credential linking, template mapping, and lead-sync configuration, and flags the configuration mistakes that come up repeatedly during onboarding.
Stitch, the WhatsApp business communication platform, is built on the official WhatsApp Business Platform (delivered via msgboxx, the WhatsApp team inbox Stitch built on the official WhatsApp Cloud API), so the setup pattern below reflects the same underlying architecture we use across CRM integrations such as Reapit.
Before touching CRM configuration, decide how your team will access WhatsApp day to day. There are three access methods available: a web browser app, a Chrome extension, and a mobile app.
For Alto users specifically, the Chrome extension is the recommended starting point because it integrates directly with the Alto CRM interface, letting staff send messages without leaving the screen they're already working in. The mobile app mirrors the web app's functionality for on-the-go access, which is useful for negotiators handling viewings out of the office.
Note: install the Chrome extension before rolling out to branch staff. Teams that skip this step and default to the standalone web app lose the in-CRM messaging convenience that drives adoption.
Once your WABA is active, the WhatsApp Business Platform gateway (delivered via msgboxx) connects across all three interfaces: the floating inbox in your web CRM, the Chrome extension, and the mobile app, with activity logged back into Alto.
At this stage, confirm your branch structure matches your Meta-side number provisioning. Multi-branch agencies need to plan number assignment and permissions carefully before activation, since the requirement is one WhatsApp number per Alto branch, not one number shared across the whole agency.
With access and numbers confirmed, the next task is making sure every inbound and outbound message actually lands in the right CRM record.
For Alto, messages sync into the CRM as notes attached to the relevant record, which is how conversation history stays visible to the rest of the team without duplicating data entry.
This is also where the integration challenge with Alto becomes most visible. Alto's limited native integration compared to CRMs like Lifecycle, Streets, and Reapit means some workflows need manual workarounds rather than fully automated syncing. A practical fix used by agencies on Alto is applying tags and auto-tagging inquiries based on property details, which helps manage property match-outs and follow-ups even where deep native sync isn't available.
For Rex, setup follows the same integration and configuration approach for WhatsApp messaging within a property lettings context, covering the equivalent credential and messaging setup steps used for Alto.
Templates are the backbone of compliant, high-response WhatsApp outreach, and they need Meta approval before use. Approval typically takes a few minutes but can run up to 48 hours, so build your template library ahead of go-live rather than on the day you plan to launch.
Template messages carry a cost of approximately 1.6p per message from Meta, and they consistently produce a significantly higher response rate than free-typed messages. This makes template quality worth investing time in during setup rather than treating it as an afterthought.
Key template use cases to map during this step: - Portal lead acknowledgement and viewing booking flows - Bulk broadcast templates for tagged contact segments — one agency example used a broadcast to 125 contacts tagged as "opportunity" - Automated notifications for new messages, assigned chats, and unresponded chats
Tip: pair booking-flow templates with a diary link tool such as Calendly, which several agencies use for viewing bookings inside the WhatsApp flow.
Inbound automation is where the integration starts doing real work rather than just relaying messages. This covers portal leads, website chat widgets, and a choice between AI-driven and non-AI response flows, alongside booking and viewing workflows.
Set up your inbound chat automation and website widget at this stage, since this is typically bundled with the broader onboarding process alongside verification and template rollout. Decide early whether missed-call handling should trigger an automated WhatsApp follow-up, since this is a common use case alongside portal leads and viewing confirmations.
Notifications should be configured for three specific triggers: new messages, chats assigned to a staff member, and chats that have gone unresponded. Getting these three notification types right early prevents the most common post-launch complaint: messages sitting unanswered because no one was alerted.
Before full rollout, complete the WhatsApp Business Account verification process, which results in the blue tick that signals a verified business account to customers. This is typically handled as part of the standard onboarding sequence alongside template setup and CRM note-syncing configuration.
Once verified, share your WhatsApp direct link and QR code across email signatures and marketing materials, which is a standard step in the onboarding process. This turns every existing customer touchpoint into a channel that funnels into the same WhatsApp inbox your team is now trained on.
Several issues come up repeatedly during onboarding conversations, and most are avoidable with the right sequencing.
If messages aren't logging correctly into Alto, check whether the workflow relies on native sync or a tagging workaround, since Alto's more limited integration compared to Reapit and Lifecycle means some note-logging behaviour needs the tagging approach rather than automatic sync. If staff aren't using the platform consistently, the root cause is more often adoption than technical failure: ensure the Chrome extension is installed for in-CRM convenience and that training on templates has actually happened. If template messages aren't sending as expected outside a live conversation, confirm you're within the 24-hour response window and that the required template was actually approved by Meta before use.
Connecting WhatsApp Business API to Alto and Rex follows the same core sequence: activate and verify your WABA, choose your access method with the Chrome extension as the recommended default for Alto, provision numbers per branch, build and get templates approved, configure lead-sync and notifications, and prepare team-facing verification assets. The technical steps are straightforward, but the pitfalls that slow agencies down are almost always about sequencing and adoption, not the integration itself. Get templates approved early, plan branch numbering before go-live, and invest in staff training alongside the technical setup, and the switch from email to WhatsApp becomes a genuine speed-to-lead advantage rather than another underused tool sitting next to the CRM.
