Marsen / WhatsApp lead follow-up sprint, India
Leads going cold before anyone replies? Follow up on WhatsApp automatically.
For Indian businesses getting enquiries from a website, ads, IndiaMART or WhatsApp. In two weeks we connect one lead source, WhatsApp and your CRM, so every enquiry gets an instant reply and a follow-up sequence your team approves. Fixed ₹34,999 (excluding GST), optional monitoring ₹2,499 a month.
Already have a workflow problem? A call does not commit you to a project.
Recognise the handoff
Small gaps.
Important conversations.
You have already earned someone’s interest. The next step should be easier to see, own and follow through.
THE NEW ENQUIRY
Interest arrives. Ownership does not.
A property enquiry lands in a message. A service request arrives through a form. Make the handoff to the responsible person explicit.
THE NEXT RESPONSE
The context is in three places.
Bring the original request, relevant facts and next action into the same view. Let a person review the response before it goes out.
THE QUIET FOLLOW-UP
A shared link is not a booked call.
Keep a proposed meeting, confirmed appointment and attended call separate. Make changes and unanswered enquiries visible.
Explore the workflow
One enquiry.
A visible next step.
Walk through an illustrative service enquiry. These are sample states, not a live integration or a customer result.
01Capture
Keep the request intact.
A source, a stable reference and the original enquiry give the next person a starting point.
02Assign
Make the next owner visible.
Give the enquiry an accountable owner or agreed queue. A notification supports the handoff; it does not replace ownership.
03Review
Draft with context. Send with care.
Use approved business information to prepare a response. A person checks the details, fit and next step.
04Book
Confirm the actual appointment.
Use the calendar provider’s confirmation, retain the visitor’s time zone and reconcile later changes.
05Follow up
Know what still needs attention.
Keep unanswered requests, failed handoffs and next actions visible so someone can resolve them.
What the pilot works towards
Less searching.
Clearer responsibility.
Define the operational change before choosing the automation. These are design objectives to test, not guaranteed results.
A fragmented handoff
“Who is handling this?”
- The request is buried in an inbox.
- Ownership is assumed, not recorded.
- The next response relies on memory.
- A calendar link is treated as an outcome.
The intended workflow
“Here is the next action.”
- The request has a source and reference.
- An owner or queue is visible.
- A next action has a review point.
- Bookings and attendance are distinct.
Start with a real problem
Built around the work
your team already does.
The first pilot starts with an existing flow of enquiries and someone responsible for the next response.
Real estate teams
From property interest
to a useful conversation.
Keep the enquiry, property context and assigned agent together. Separate a viewing request from a confirmed appointment.
Enquiry → agent review → viewing handoff
Service businesses
Give each service request
a clear next step.
Capture what the buyer needs, identify missing context and route the request to the person who can respond.
Request → fit review → consultation
Established agencies & founders
Make repeated handoffs
easier to manage.
Start with one repeatable process: new-business enquiries, client intake or reviewed follow-up. Keep a named process owner.
Brief → owner → reviewed next action
A bounded implementation
Know what you are
agreeing to build.
The proposal defines the deliverables, access, acceptance checks and support. Pricing follows that scope.
01 / Workflow map
One shared picture
of the handoff.
Document inputs, decisions, tools and exceptions before building the connections.
02 / Agreed connections
Your tools.
A defined connection plan.
Review the current enquiry source, CRM and calendar. Confirm access and feasibility before promising an integration.
03 / Acceptance checks
Test the awkward
cases too.
A repeated request, a missing field, a failed sync and a changed booking belong in the test plan.
04 / Handover
Make operating it
someone’s job.
Identify owners, review points, failure handling and the support arrangement after implementation.
05 / Measurement
Agree what progress
will mean.
Choose the baseline and observation period. Report enquiries, reviewed fit, bookings and attended calls separately.
Advertising, content production, extra workflows and ongoing support are discussed separately. The pilot does not guarantee more leads or revenue.
Before a proposal
Bring one workflow.
We will start there.
Tell us where enquiries arrive, what happens next and where your team gets stuck. We will review whether a bounded pilot is a useful next step.
Request a workflow-fit callCustom-scoped. No obligation to start a project.
The gap after the click
Make the next
handoff visible.
An enquiry arrives through a form, social message or referral. Then someone has to capture it, check the context, respond and remember the next step.
When those handoffs live across inboxes and spreadsheets, it can be hard to tell what was handled and what still needs attention. Start by making that path visible.
The bounded Sprint
One workflow.
Clear responsibilities.
Define the first useful version
Agree the enquiry source, destination record, owner, next action and exception handling. Document what is included and what is outside the pilot.
Connect and test the handoffs
Build around the agreed tools. Check valid requests, duplicate events and failures before using the workflow with real enquiries.
Review what actually happened
Separate received enquiries, reviewed fit, confirmed bookings and attended calls. Agree handover and support before extending the scope.
Is this the right starting point?
Bring an existing flow
of enquiries.
- You already receive enquiries and can explain where they come from.
- Someone on your team can own follow-up and review decisions.
- You can provide access to the tools included in the agreed scope.
- You want to improve a specific operational handoff and measure it.
If you first need an offer, audience or acquisition channel, that is a different starting point.
Start here · no email needed
The five-part
lead-flow check.
Use a recent enquiry and walk through these questions with the person responsible for it.
Where does an enquiry start?
Write down each active source: form, ad, email, message, referral or call. For one recent enquiry, identify the exact source and the place the record should live. If the source is unknown, mark it unknown rather than guessing.
Who owns the next action?
Name one person or agreed queue. Identify who covers absences. Check whether another team member can see the current owner and status without searching several chats.
What information is needed to respond?
List required details, approved facts and missing information. Decide what can become a draft and what requires a person to investigate. Keep the original enquiry available to the reviewer.
How does the enquiry become a booking?
Separate response drafted, response approved, response sent, link shared, booking confirmed and call attended. Check time zones and availability. A sent link is not a confirmed appointment.
What happens when the normal path breaks?
Check a repeated event, missing field, failed connection and booking change. Name the person who can see and resolve each exception. Preserve enough information to retry without duplicating work.
Review the draft, not just the output
AI campaign scorecard.
Score each ad, landing headline and response draft separately. Zero means missing or contradicted; one needs material editing; two is usable after ordinary review. Maximum eight points per deliverable. Keep a written reason for each score. A material unsupported claim must be corrected regardless of the total.
- Factual support
- Does every important promise match an approved fact?
- Buyer specificity
- Does it name the actual customer and recognisable problem?
- Offer continuity
- Do the ad, page and next action promise the same thing?
- Handoff
- Is there a clear destination, owner and next step after interest?
Your one-workflow brief
Our enquiries arrive through ___. The record should live in ___. The next owner is ___. The repeated problem is ___. We can provide these sample inputs ___. The reviewer is ___. Success in the pilot would mean ___, measured using ___.
Repeated-work check for agencies
For reporting, content approval or client onboarding, replace ‘enquiry’ with the work item. Name its source, required inputs, reviewer, approval state and destination. Count the current effort before promising time savings. Start with one repeatable process, not every client operation at once.
Before we talk
What to expect.
Who is this for?
Indian businesses already receiving enquiries from a website, ads or WhatsApp, with someone responsible for handling them, for example clinics, coaching institutes, property consultants and service companies. Teams outside India can discuss a scoped workflow.
Do I need more leads first?
If there are no enquiries to follow up, we should first discuss the acquisition problem. The follow-up pilot is designed around an existing flow of enquiries.
Does the pilot include advertising?
Advertising and content delivery are separately scoped. The first pilot focuses on the agreed workflow.
Do we need to replace our CRM?
We review your current tools first. The proposal identifies which connections are practical and whether anything needs to change.
What does the Sprint cost?
₹34,999 one-time, plus applicable taxes, for one enquiry source, your WhatsApp Business API provider, one CRM and one follow-up sequence with a person reviewing drafts, tested and handed over. Optional monitoring and small changes cost ₹2,499 a month. WhatsApp provider and Meta conversation charges are billed to you directly by those providers. Larger scopes are quoted after a call.
Will the AI send messages automatically?
The design depends on the approved scope. The campaign demo uses drafts reviewed by a person before sending.
Is this a finished off-the-shelf product?
The campaign demonstrates a workflow approach. Actual configuration and integrations depend on your existing tools and requirements.
What happens after the pilot?
Review the agreed checks and operational results, then decide whether to extend the workflow. More enquiries, bookings or revenue are not guaranteed.
Request a workflow-fit call
Start with the handoff
that needs attention.
Share the current process, where it gets stuck and the tools involved. We will review whether a bounded pilot is a useful next step.
Your first workflow
Where does follow-up
get stuck today?
Your current workflow, where it gets stuck, the systems involved and whether a bounded pilot is a useful next step. A call does not commit you to a project.
Request a workflow-fit callShare a description of the process. Do not include customer records or sensitive information. We’ll use the details to respond to your enquiry. Privacy policy.