WhatsApp-led intake
The customer journey starts in a familiar channel, capturing service requirements and location before creating an opportunity.
Case study · Home Services / Vendor Operations
A WhatsApp-powered operating system helps Sofa Doctor capture service requests, allocate them to eligible vendors with failover, and keep management informed after assignment.
See it work, step by step
Follow one enquiry through the system. Tap any step, or let it play.
Step 1 of 6
A WhatsApp flow where the customer describes the repair and shares their area.
Customers can start a service request on WhatsApp, and the team can review it in the agreed workflow.
Step 2 of 6
Rules that pick vendors who offer that service in that area and are active.
Jobs go to someone who can actually do them, without manual phone-arounds.
Step 3 of 6
Round-robin allocation: if one vendor declines or does not respond, the next eligible vendor gets it.
A “no” or silence no longer ends the customer’s request.
Step 4 of 6
A queue for the admin when no vendor takes the job.
Stuck requests are surfaced for a human decision instead of disappearing.
Step 5 of 6
A follow-up asking the customer whether the vendor actually contacted them.
The owner knows work is really moving, not just “accepted”.
Step 6 of 6
One operational view of requests, vendors, assignments and exceptions.
Management sees the whole service operation in one place.
What they got

Sofa Doctor × ScaleYukti · WhatsApp · CRM · Business workflows
The challenge
Requests needed to reach vendors with the right service capability and local coverage. Allocation needed structure, and an accepted opportunity did not by itself prove that a customer had been contacted.
Our approach
ScaleYukti designed an operations layer around customer intake, routing, vendor actions, exception handling and customer confirmation, supported by a custom CRM and mobile-first vendor experience.
What ScaleYukti built
The customer journey starts in a familiar channel, capturing service requirements and location before creating an opportunity.
Location, service capability, operational status and access rules determine which vendors are eligible.
Round-robin routing distributes opportunities across eligible vendors. Declines or timeouts can trigger further allocation rather than end the journey.
Unresolved allocation cases reach an administrator-controlled queue for attention.
A mobile-first experience supports vendor actions, while subscription and credit controls govern access without publishing private commercial details.
Follow-up with the customer adds an independent signal of whether accepted work is actually progressing, alongside centralized owner and admin visibility.
Before & after
Tap a card to flip it from the old way of working to what was implemented.
The operational outcome
Customer requests, vendor eligibility, assignment states and exceptions can be managed through one workflow. Management gains a clearer view of operations, supported by customer-side accountability after acceptance.
“What we expected and what you delivered is way beyond our expectations.”

More implementation stories
We set up the follow-up workflow and manage it with you, within an agreed scope.
See how it works

Let's talk about your business
Tell us where enquiries, handoffs or follow-ups get difficult. We'll discuss a practical scope around your business.
Prefer to review the options first? Explore Solutions