Back to home
Case StudyMay 20258 min read

How we automated 100% of trek bookings on WhatsApp without a second number

A trekking company was spending 3 to 4 hours every evening answering the same WhatsApp messages. What trek is available this Saturday? What is the price for two people? Can I pay online? We fixed that in two weeks. Here is the full story.

200 identical messages every week

Trekking companies live on WhatsApp. That is where customers ask questions, negotiate, and eventually book. The problem is that every single conversation starts the same way. Route options, pricing, how hard is it, what to bring, are slots available for next weekend.

The operator we worked with tracked their inbox for one month. 214 incoming messages. 31 unique questions total. The rest were repeats. Every reply was typed manually, often at 11 PM after a full day on the trail. Bookings that came in overnight went unanswered until morning, and customers had already moved on.

Why not just build a website booking form

We asked that question too. The answer was simple: customers do not trust a new website from an operator they found through word of mouth. They message on WhatsApp because that is where the relationship started, usually from a friend's recommendation or an Instagram post. Moving them to a form breaks that trust.

WhatsApp has a 98% open rate. A booking confirmation sent on WhatsApp gets read in minutes. The same email sits unread for days. The goal was to keep customers exactly where they were and make the business respond at machine speed.

The number problem everyone gets wrong

Most WhatsApp automation tools need a separate business number. You set up automation on a new SIM and ask customers to message that number instead. This never works. Customers have saved the owner's personal number. A message from an unfamiliar number gets ignored or marked as spam.

Sociovio runs on the existing number. Personal conversations with the owner's contacts continue exactly as before. The automation layer handles incoming business inquiries through the WhatsApp Business API in parallel. Customers see no change. The bot just responds faster than any human could.

What happens when a customer messages the number

Customer sends "Hi, I want to book a trek for this weekend." The bot picks up the intent, asks how many people, and shows available routes with dates, difficulty, and pricing. Customer picks a route. Bot shows available dates and remaining slots. Customer confirms their date.

Bot sends a Razorpay payment link inside the same chat. Customer pays on Razorpay and returns to WhatsApp. Payment confirmation hits a webhook. Bot reads the confirmation and immediately sends a booking receipt with all details, the meetup point, what to pack, and an emergency contact number.

Start to confirmed booking: under 5 minutes. Zero human involvement. The owner sees a new row appear in the dashboard with full booking details and payment status.

Week one was all mapping, no code

We spent the first week going through six months of WhatsApp chat history. Every question customers had ever asked, every objection, every booking that fell through, every edge case like group discounts or last-minute cancellations. We built a map of every path the conversation could take.

The bot needed to handle slots filling up mid-conversation, payment failures, customers asking about treks in a language mix of English and Hindi, and questions outside the booking flow entirely. Each edge case got a specific response path, not a generic "I did not understand that."

What changed after 60 days

100%

Bookings completed by bot

0

Manual replies for standard queries

24/7

Response availability

1

Number for personal and business

The operator stopped doing evening WhatsApp duty. Bookings that came in at 2 AM now confirm automatically. Payment collection happens inside the chat at the moment a customer decides, not a day later after chasing UPI screenshots. The owner opens a dashboard each morning to see everything that came in overnight.

Same setup works for any service business

The trekking use case is specific, but the pattern is not. Any business where customers ask the same questions before every purchase is a candidate. Clinics getting the same appointment questions fifty times a week. Coaches fielding program inquiries through personal WhatsApp. Restaurants taking reservations through chat.

The specific flow changes depending on what you sell. The outcome is the same: customers get an answer in seconds, payment happens in the same conversation, and you stop spending your evenings on WhatsApp.

Want the same for your business?

Message us on WhatsApp with your use case. We will map your flow and tell you exactly what automation looks like for your business.