Your CRM knows the moment a new lead comes in. It logs the timestamp, assigns the stage, and sits there — waiting for a human to act. The lead waits too. Sometimes for hours. Sometimes forever.
The fix is not a new CRM. It is a text message sent automatically the moment your pipeline moves. Here is how to build that connection using Make (formerly Integromat), without touching a line of code — and what to know before you decide whether to build it yourself or let someone else handle it.
Your CRM Is Built for Tracking, Not Contacting
Franchise CRMs — FranConnect, GHL, Salesforce, HubSpot, ClientTether, and others — are excellent at organizing pipeline data. They store lead records, log activity, and generate reports. What they are not designed to do is reach out to a candidate the moment something changes.
SMS texting is typically a bolt-on feature in these platforms, and it shows. You get basic sequences or manual sends. You do not get an AI-driven conversation that reads the candidate's reply, answers a question about territory size, and offers three available times to book the intro call — all before your rep opens their laptop.
That gap is where Make comes in. Make is a no-code automation platform that lets you watch for events in one system and trigger actions in another. In this case: a lead moves to a new CRM stage, Make sees it, and fires a text through your SMS layer. No developer required.
What a Basic Make Scenario Looks Like
The core flow has three parts: a trigger, a filter, and an action.
Trigger: Make watches your CRM for a specific event — a new lead is created, a pipeline stage changes, a field is updated. Most franchise CRMs surface these events through webhooks or a native Make integration. GHL, HubSpot, and Salesforce all have published Make connectors. FranConnect and others can connect via webhook.
Filter: You do not want every pipeline event to fire a text. A filter tells Make to only proceed when the conditions match — for example, stage equals "New Inquiry" and lead source equals "FranConnect Portal."
Action: Make calls your SMS tool's API to send a text. If your SMS tool is also in Make's library, you connect it directly. If not, you use the HTTP module to call the API manually with a JSON payload.
A basic scenario in Make looks like this:
- Module 1: Watch CRM — trigger on new lead or stage change
- Module 2: Filter — check the stage name matches your target
- Module 3: Send SMS — pass the lead's name, phone number, and a pre-written message
Build this once, activate the scenario, and every qualifying lead gets a text automatically.
Building Stage-Specific Scenarios for Each Pipeline Phase
One automation covering every stage is a blunt instrument. The message you send a new inquiry is different from what you send a candidate who just received their FDD. Franchise development has a specific, sequential sales process — and the engagement should match each phase.
The canonical order matters here: lead capture, then intro call, then application, then FDD issuance and the 14-day review window, then franchisee validation, then Discovery Day, then signing. Each stage has different candidate questions, different urgency levels, and different goals for the conversation. Build a separate Make scenario for each stage transition you want to cover.
For a new inquiry, the text should be personal, fast, and ask a question. For an open application, it should follow up on what is missing and what happens next. For the FDD window, it should check in on questions about territory, fees, and royalties. For Discovery Day, it should confirm logistics and send a reminder at the right interval before the meeting.
Each scenario in Make watches for its specific trigger, filters to the right conditions, and fires the appropriate message. You end up with a set of parallel scenarios — one per stage — rather than a single flow trying to handle everything.
"73% of franchise brands never used SMS at all — even as a backup channel." — FranFunnel Franchise Lead Response Time Study · 530 brands · fielded March–April 2025
Where the DIY Build Gets Complicated
The Make setup described above works. The limitations show up when you try to handle anything beyond a one-way text.
Conversations, not just texts. If a candidate replies — and they will — something needs to handle that reply. Make can route an inbound SMS to a notification or log it, but building a system that reads the reply, understands what was asked, and responds intelligently requires an AI layer on top of your SMS tool. That is a separate integration, a separate prompt to write, and a separate surface to maintain.
Calendar booking. Getting a candidate from "texted" to "meeting booked" is the actual goal. Offering a booking link is one approach — it works, but it pulls the lead out of the text thread and into a form. Offering specific available times directly in the conversation converts better. Building that in Make means querying your calendar API, parsing open slots, formatting the times as a reply, and handling the response when the candidate picks one. This is several additional modules and significant edge-case handling.
CRM writeback. Activity should sync back to the CRM so your team can see what happened. Make can do this, but each field that should update — last contacted, last reply, booking status — requires its own mapping and its own error handling.
Maintenance. Every time your CRM provider updates their API, your Make scenarios need a review. Every time you add a new lead source or a new stage, the filters need updating. Someone owns this — and that someone is usually you.
What FranFunnel Does Instead
FranFunnel is what you end up with when you build the Make scenario above — and then spend six years refining it specifically for franchise development.
The platform connects to your CRM through native integrations and webhooks. When a lead moves to a new stage, a stage-specific agent activates automatically — an intro call agent for new inquiries, an application agent for pending applications, an FDD agent during the 14-day review window, a Discovery Day agent for confirmed attendees. Each agent is built by the FranFunnel team to match your actual sales process. You approve it. It goes live in 48 hours.
The meeting concierge scans your rep's calendar and surfaces the next three available times directly in the text thread. When the candidate picks one, FranFunnel books the meeting and sends the calendar invite. Reschedules, reminders, and buffer gaps between meetings are all handled inside the same conversation — no one touches it manually.
Activity syncs back to your CRM. Your rep can step into any thread at any moment — the moment they send a manual message, the agent for that stage shuts off and the rep drives the conversation. The next agent activates when the CRM stage transitions again.
You are not replacing your CRM. You are adding the engagement layer it was never built to be.
FAQ
What is Make (formerly Integromat) and how does it work with franchise CRMs? Make is a no-code automation platform that connects different software tools by watching for events in one system and triggering actions in another. For franchise CRMs, it typically works by listening for a webhook or API event — like a new lead being created or a pipeline stage changing — and then sending a command to a separate SMS tool to fire a text message. No custom code is required for most franchise CRM and SMS tool combinations.
Which franchise CRMs work with Make? GHL (Go High Level), HubSpot, Salesforce, Zoho, and Pipedrive all have native Make integrations. FranConnect, ClientTether, FranchiseSoft, and platforms without published Make connectors can typically connect via webhook — when the CRM fires a webhook on a stage change, Make receives it and continues the scenario from there.
How fast can Make trigger an SMS after a CRM stage change? Make checks for new trigger events on a polling interval — typically one to fifteen minutes depending on your Make plan. For true under-60-second response, you need either a real-time webhook trigger (which Make supports when the CRM sends one) or a platform built specifically for instant first contact. Polling-based scenarios are not fast enough to meet a 60-second speed-to-lead standard reliably.
Can Make handle a two-way SMS conversation, not just a one-way text? Make can route an inbound reply to another system or log it, but it does not natively understand and respond to natural language. For a genuine two-way conversation — where a candidate asks about territory, fees, or next steps and gets a useful answer — you need an AI layer connected to your SMS tool. Building that in Make is possible but requires significant additional configuration and ongoing prompt maintenance.
How do I send stage-specific SMS messages for different parts of the franchise sales funnel? Build a separate Make scenario for each pipeline stage transition you want to cover — one for new inquiries, one for open applications, one for FDD issuance, one for Discovery Day. Each scenario filters on its specific stage name and fires a message written for that moment in the sales process. Using one generic scenario for every stage produces messages that feel out of context and reduce reply rates.
Can Make book a meeting directly in a text thread? Not natively. Make can send a booking link inside an SMS message. But offering specific available times directly in the conversation — without sending the lead to a separate form — requires a calendar-connected platform that reads open slots and handles the reply when a candidate picks a time. That functionality goes beyond what Make is designed to orchestrate without significant custom development.
Does activity logged by a Make SMS scenario sync back to the CRM? It can, but you have to build that sync as a separate step inside your Make scenario. For each field you want updated — last contacted date, last message sent, booking status — you need a CRM update module at the end of the scenario with explicit field mappings. Errors in the webhook or API call can cause records to fall out of sync, so the writeback needs its own error-handling logic.
What happens when my CRM updates its API and my Make scenarios break? You troubleshoot and rebuild the affected modules. Make surfaces errors in its scenario history, but identifying which step broke and why requires someone who understands both the CRM's API changes and the Make scenario structure. This is one of the ongoing maintenance costs of a DIY integration that does not exist with a dedicated platform.
How many franchise brands actually use SMS to follow up with leads? According to the FranFunnel Franchise Lead Response Time Study (530 brands, fielded March–April 2025), 73% of franchise brands never used SMS at all — not even as a backup to email. That means the majority of candidates submitted an inquiry, received an email acknowledgment or nothing, and never got a text. First contact by SMS, if it arrives fast, is a meaningful differentiator simply because almost no one else is doing it.
Is it worth building the Make integration myself, or should I use a dedicated platform? The Make approach works and is a reasonable starting point if you want to test SMS engagement before committing to a platform. The tradeoffs are real: polling delays make true speed-to-lead difficult, two-way conversations require additional AI configuration, calendar booking requires custom development, and ongoing maintenance is your responsibility. A dedicated platform like FranFunnel is built specifically for this use case, connects to the same CRMs through native integrations, and is live in 48 hours with a team that handles everything after setup.
What does it cost to build this with Make versus a dedicated tool? Make's pricing is based on scenario executions, with free and paid tiers. The platform cost is low, but the real cost is setup time, maintenance, and the AI and calendar layers you still need to build separately. FranFunnel is $249 per month, per seat, with unlimited messaging, white-glove setup, and ongoing support included. For franchise development teams where a single signing is worth $250,000 or more in fees and royalties, the comparison is straightforward.
Can FranFunnel trigger stage-specific agents the same way Make would trigger a scenario? Yes — and with more precision. When a CRM stage changes, FranFunnel activates the agent built for that stage: intro call agent, application agent, FDD agent, Discovery Day agent, and others. Each agent is custom-built to your process by the FranFunnel team. The trigger can come from a CRM stage change, a webhook, a button inside FranFunnel, or another notification signal. The result is the same: the right message, from the right agent, at the right moment in the candidate's journey.
If you want to see what under-60-second SMS engagement looks like when it is built specifically for franchise development — stage-specific agents, in-thread calendar booking, and full CRM sync — book a demo at franfunnel.com. We will show you exactly how it maps to your current pipeline.