Custom build

Qualify WhatsApp enquiries and create the lead in your CRM

Reply to every enquiry straight away, ask the few questions that tell you whether it's a real buyer, and send the lead with its answers to your CRM or a Google Sheet. Then a person on your team takes over.

Last updated 26 October 2026

Harbour Homes
Business account · example

Hi, I'm interested in listing HH-4471

Thanks, Thandi. HH-4471 is a 3-bed house in Durbanville, R2,450,000. Photos and the brochure are below.

What's your budget?
Tap one
Under R2m R2m to R2.5m Over R2.5m
Is your finance sorted?
Pre-approved Applying Cash
Book a viewing
Slots from the agent's diary
Sat 10:00 Sat 11:30 Sun 14:00
Confirm

Booked for Saturday 10:00. Your agent will message you here before then.

The chat replies in seconds, asks the questions your sales team would ask, and creates the lead in your CRM via its API; your team picks it up in the shared inbox. Euphony builds it on your own WhatsApp account, and Meta bills you directly for messages at Meta's rates.

How the conversation runs

Here is the flow for a property enquiry. The same shape fits a school, a dealership or a services marketplace, with different questions.

  1. The enquiry arrivesThe buyer taps the WhatsApp link on a listing, a QR code on a board, or a Click-to-WhatsApp ad. WhatsApp links and QR codes can pre-fill a message with the listing reference, so unless the buyer edits it, the chat knows which property they mean from the first message.
  2. An instant answerWithin seconds the chat sends what the buyer asked for: the price, photos, the brochure as a PDF, and whether the property is still available. Those details come from your listings system or CRM through its API, so they're current.
  3. A few qualifying questionsBudget, timeline, and whether their finance is pre-approved, applying or cash. We use reply buttons and lists for quick answers, or a WhatsApp Flow (a short form inside the chat) when there are more than two or three questions.
  4. Free text and voice notesIf the buyer types "about 2.3 mil, still waiting on the bank" or sends a voice note, Claude reads it (the voice note is transcribed first) and pulls out the budget and finance status. The chat confirms what it understood before it moves on.
  5. A next stepThe buyer picks a viewing slot, asks for a call back, or asks to speak to someone now. Live slots can be read from your calendar or CRM if it has an API.
  6. The lead lands in your CRMWe create or update the contact by phone number, and add the deal or lead with every answer, the listing reference and the slot. For a smaller team it can be a new row in a Google Sheet instead.
  7. A person takes overThe conversation is in our shared WhatsApp inbox with its full history. When someone on your team replies, the automation in that chat pauses, so the buyer never gets a bot message in the middle of a human conversation.
  8. Follow-upIf the buyer goes quiet, the chat can send one reminder later. After 24 hours without a message from them, that has to be a Meta-approved template.

Systems connected

The WhatsApp side runs on our platform. The conversation logic and the CRM calls are written by our engineers for your business.

PartWhat it doesHow
Conversation logicReplies, questions, branching, remindersA Program on our platform, written for your questions (build)
Buttons and listsOne-tap answers to qualifying questionsWhatsApp interactive messages
WhatsApp FlowsLonger forms in the chat, with live data such as available slotsA Flow built for you, with an endpoint that reads from your system (build)
ClaudeReads free text and voice notes, pulls out details, drafts repliesCalled from the Program. It doesn't answer from a knowledge base; facts come from your system or the script we write
Your CRMCreates the contact and lead with the answersAn HTTPS call to the CRM's API: HubSpot, Salesforce, Zoho or your own system (build)
Google SheetsOne row per leadA call to a Google Apps Script web app on your sheet (build)
Shared inboxYour team reads the history and repliesRuns on our platform; a staff reply pauses automation in that chat
What this doesn't do

We don't sell pre-built CRM connectors: each CRM link is built through that CRM's API. Our inbox doesn't assign chats to named agents, so who owns a lead is decided in your CRM, by its assignment rules or a field we fill such as branch or listing agent. A "call me back" request lands in the inbox and your person phones from their own line, because the platform doesn't place WhatsApp calls. The number runs on the API only, not in the WhatsApp Business app at the same time.

Which messages Meta charges for

Messages customers send you are free. Most of a lead conversation happens while the customer's 24-hour customer service window is open, so your replies are service messages. A follow-up after the window closes must be a template, priced by category.

MessageMeta categoryMeta rate to SA numbers (from 1 Oct 2026)
The customer's enquiry and answersInboundFree
Your replies, questions and viewing confirmation while the chat is openService1,000 free per number per month, then US$0.0095
Viewing reminder, or a marketplace "New request" alert to a provider, outside the windowUtility templateUS$0.0095
"Still looking? Here are similar homes" after the windowMarketing templateUS$0.0379

Meta decides a template's category when it reviews it. Business-initiated messages also need the person's opt-in, which the chat can ask for and record in your CRM.

Sources: Pricing on the WhatsApp Business Platform (Meta, updated 30 September 2026) · Customer service windows · WhatsApp Business Messaging Policy

Leads from Click-to-WhatsApp ads

People who tap a Click-to-WhatsApp ad on their phone land in the same conversation. When you reply within the customer service window, Meta opens a free messaging window of at least 72 hours, in which it doesn't charge for your messages. You create and run the ads in Meta's own ads tools; we build what happens once the chat starts. See the free messaging window explained.

Variants by industry

The same job in four industries

These are common patterns in the South African market, not Euphony clients. Names, places and amounts in the chats are examples.

What we need from you

  • A Meta business portfolio and a WhatsApp number you connect through Meta's Embedded Signup. Codeswop is a Meta Tech Provider, so the account is yours and Meta bills you directly. If the number is already with another provider, see switching providers.
  • Your qualifying questions: the three to five things your best salesperson asks first, and the answers that make a lead hot, warm or not a fit.
  • API access to your CRM, or a Google Sheet you own. We tell you exactly which permissions the build needs.
  • Where the answers go: which fields, pipeline or stage, and which field your CRM uses to assign the owner (branch, area, listing agent).
  • The facts the chat may share, such as listings, fees or stock, from your system's API or a list you keep up to date.
  • Template wording for any follow-up or reminder sent after 24 hours. We submit the templates to Meta for approval in your account.

What it costs

  • Meta's charge. Billed by Meta to you directly, per delivered message, at the rates above. We add nothing.
  • Our charge. A one-off build from R15,000 ex VAT, plus R7,500 per integration, depending on the number of questions, Flows and systems, and a monthly fee from R4,950 ex VAT to run and look after it.
  • Your CRM. Your CRM subscription stays between you and your CRM vendor. Check your plan includes API access.

See WhatsApp API pricing in South Africa for rand examples.

Questions

WhatsApp lead capture FAQ

Which CRMs can WhatsApp leads go into?

Any CRM with an API that lets us create records, including HubSpot, Salesforce, Zoho CRM, Pipedrive and property, school or dealer systems. A Google Sheet works too, through a small Apps Script web app. Each one is a custom build: we connect WhatsApp to your CRM via its API. We don't offer pre-built CRM connectors.

Can a new lead be assigned to a specific sales rep?

Yes, in your CRM. We send the lead with the details your CRM needs to assign it, such as the listing, branch, area or product, and your CRM's own assignment rules or round-robin pick the owner. Our shared WhatsApp inbox doesn't assign chats to named agents: anyone on your team can pick up the conversation there, and a staff reply pauses the automation in that chat.

What happens when an enquiry comes in after hours?

The automated part runs around the clock. The customer gets the details, answers the questions and can pick a viewing or call-back slot, and the lead is in your CRM by morning. Anything that needs a person waits in the shared inbox, and the chat can tell the customer when someone will be back. If you follow up more than 24 hours after their last message, WhatsApp requires an approved template.

Can I use a Google Sheet instead of a CRM?

Yes. Each lead becomes a new row with the customer's number, their answers and the time. We post it to a Google Apps Script web app that you own, which writes to your sheet. It's a good start for a small team, and the same conversation can later post to a CRM instead.

Can I keep using my WhatsApp Business app on the same number?

No. A number connected to our platform runs on the WhatsApp Business Platform only, not in the WhatsApp Business app at the same time. You can use a separate number for enquiries instead. If your number is already with another API provider, it can stay where it is and be shared with us. See switching providers.

What does Meta charge for a lead conversation?

Messages customers send you are free. Your replies while the chat is open are service messages: each number gets 1,000 free a month, then US$0.0095 each to South African numbers from 1 October 2026. A follow-up after 24 hours needs a template, at US$0.0379 for marketing or US$0.0095 for utility. Meta bills you directly; we add nothing. Source: Meta's pricing page.

Answer every enquiry first

Tell us how enquiries reach you on WhatsApp today, what your team asks, and where leads should end up. We'll show you the conversation we'd build.