Estate and letting agents running AgentOS or Jupix often ask whether Stitch, the WhatsApp business communication platform, can connect directly to their existing CRM. The answer depends on which system is involved, and the picture is different for AgentOS, Jupix, and the wider CRM landscape agents are weighing up. Here's what's confirmed, what requires a manual step, and what to expect if you're planning a switch.

Does WhatsApp integrate natively with Jupix?

Native integration between Stitch and Jupix (also referred to as Dupix or Jupyx by agents using the system) is currently limited. Agencies using Jupix as their CRM have raised this directly, including cases where the agency is also considering changing CRM systems in the near future. Stitch's approach for these agencies has focused on reducing manual phone handling of portal leads and improving team collaboration and lead qualification around the CRM, rather than a deep native sync. If Jupix is your system of record, expect to rely on the Chrome overlay approach described below rather than automatic two-way data population.

Does WhatsApp integrate natively with AgentOS?

AgentOS is not named among the CRMs with confirmed native integration in the available documentation, and agencies raising Jupix/AgentOS questions have done so specifically because of integration limitations with these systems. Where a named, working integration exists, it's built for a different CRM: Reapit integrates directly, with automatic population of data and a comprehensive audit trail for compliance purposes. For AgentOS users, the same Chrome overlay workaround used for Jupix applies, letting your team work inside WhatsApp without needing a native data bridge.

What is the Chrome overlay approach, and how does it work as a workaround?

The Chrome overlay is Stitch's way of bridging WhatsApp and a CRM when a native integration isn't available. It sits alongside limitations with Dupix/Jupyx specifically, and was discussed as the practical answer for agencies whose CRM doesn't support automatic sync. Rather than pushing and pulling data automatically between systems, the overlay lets your team access WhatsApp conversation and lead context directly in the browser alongside the CRM screen. This means lead and conversation data isn't lost, even where full API-level integration hasn't been built for your specific CRM.

Which CRM does have full native integration with Stitch?

Reapit has a confirmed, seamless integration with Stitch. Data populates automatically and a full audit trail is maintained for compliance purposes. This is the clearest example of what "native integration" looks like in practice for Stitch: inbound WhatsApp activity from portal inquiries, such as Rightmove leads, can trigger instant messages and flow into Reapit without manual re-entry. If your agency is evaluating a CRM switch and integration depth is a priority, this is the benchmark other systems are measured against.

How do leads and conversations sync between WhatsApp and my CRM generally?

Lead and conversation syncing depends entirely on which CRM sits behind your WhatsApp setup. Where full integration exists, as with Reapit, data population is automatic and creates a compliance-ready audit trail. Where integration is limited, as it currently is for Jupix, the workflow instead centres on the shared/team WhatsApp inbox and an assignment model that routes conversations to individual users or a team. Inbound automation, including simple bot flows and form delivery, can still operate on top of either setup to acknowledge and qualify portal leads before manual follow-up.

Why do some CRM integrations cost more than others to build?

Integration cost varies significantly by CRM and is a major factor in what gets built. Development of a CRM integration typically costs around £20,000 in dev time, and one specific example, integrating with Alto CRM, was quoted at £40,000 per year plus usage fees, described as currently prohibitive. This cost structure explains why some named CRMs, such as Reapit, have full native integrations while others rely on the overlay workaround: the cost and complexity of building a bespoke sync isn't always proportionate to demand, especially for CRMs agencies are actively reconsidering.

If my agency is thinking about switching from Jupix, does that affect the WhatsApp setup?

Switching CRMs does not require rebuilding your WhatsApp workflow from scratch. Stitch has worked directly with agencies using Jupix that are also considering a CRM change in the foreseeable future, and the WhatsApp Business Platform setup, including the shared inbox and lead qualification workflow, was assessed independently of which CRM the agency ultimately runs. This means your WhatsApp number, team inbox, and conversation history remain intact through a CRM migration, since Stitch wraps the official WhatsApp Business Platform API rather than being embedded inside the CRM itself.

Can portal leads still reach WhatsApp automatically if my CRM has limited integration?

Portal lead automation works independently of CRM integration depth. Instant WhatsApp messages can trigger in response to inquiries from property portals like Rightmove, giving potential clients immediate acknowledgment regardless of which CRM sits behind the scenes. These messages can be personalised, for example including the client's name and specific property details, and conversational AI can extend the interaction by answering property questions and sharing listing links. The CRM sync only affects what happens next: whether that lead data lands in your system automatically, as with Reapit, or requires the overlay workflow common with Jupix and AgentOS setups.

What other capabilities are available regardless of which CRM I use?

Several core Stitch capabilities operate at the WhatsApp platform level and aren't dependent on CRM integration depth. SAR export in CSV format supports archive and compliance requirements, and agencies can run broadcasts, apply tagging, and manage bulk contact import and list cleaning directly within the platform. A mobile app is available, though with some limitations noted alongside the desktop and overlay workflows. These features mean agencies using Jupix or AgentOS aren't limited to basic messaging while waiting on deeper CRM integration; lead qualification, compliance archiving, and bulk communication tools work the same way across CRM setups.

Are there message volume or cost limits I should know about when using WhatsApp alongside my CRM?

Outbound WhatsApp messaging is capped at 1,000 messages per day per WhatsApp Business account. Real-world usage can run high: one example client sent over 1,300 outbound WhatsApp messages in a single month, which required managing volume against Meta's daily limit and quality rating considerations to avoid being flagged for spam. Lead response speed is a related benchmark worth tracking alongside these limits, since a typical WhatsApp lead response rate runs at approximately 80% within 3 to 4 minutes. These figures apply at the WhatsApp Business Platform level and are consistent whether your agency runs Reapit, Jupix, AgentOS, or another CRM behind the scenes.

What should I do next if AgentOS or Jupix is my current CRM?

Start by mapping which parts of your lead workflow need automatic CRM sync versus which can run through the shared inbox and Chrome overlay. Given that native integration with Jupix is currently limited and AgentOS isn't among the CRMs with a confirmed native build, the practical path is to deploy the shared team inbox and inbound automation now, while treating full CRM-level sync as a separate evaluation, particularly if a CRM switch is already under consideration. Agencies in this position should also factor in integration development costs, since bespoke CRM integrations run in the region of £20,000 in dev time, against the value of automatic data population and audit trails that a system like Reapit already provides.