Hrishikesh Tubachi
Index/Case Study/001
Live Production System

Go Pravasa

From incoming enquiries to organized customer follow-ups.

Customers explore available trips, get relevant information, and share their travel requirements. Each enquiry is organized with details the sales team can use for personalized follow-ups.

ClientGo Pravasa
IndustryTravel & Tourism
SystemWhatsApp AI Assistant & Workflow Automation
Implementation08 April 2026 onwards
TechnologiesWhatsApp · Gemini · n8n · Google Sheets
Scroll to explore the project journey
01/The Challenge

The problem wasn't just answering questions.

Go Pravasa was receiving travel enquiries through the WhatsApp entry point on its website. Customers repeatedly asked about destinations, dates, packages, and prices.

The sales team manually handled every conversation and collected requirements piecemeal. Because information was scattered across chat histories without a structured workflow, tracking enquiries and preparing timely follow-ups became an operational bottleneck.

Key Operational Bottlenecks
  • •Response latency: Hours of back-and-forth during daytime; zero coverage overnight.
  • •Scattered records: No centralized sheet or dossier for sales preparation.
  • •Repetitive intake: Sales reps spent valuable hours gathering basic trip facts.
Previous Process AnalysisThe Original Manual Enquiry Journey
5-Stage Friction
01
Initial enquiry

Customers sent unstructured queries via WhatsApp directly from the website.

Unfiltered query
02
Individual conversation

Sales reps engaged manually in back-and-forth messaging between daily tasks.

Hours of latency
03
Manual info collection

Reps gathered dates, group size, budget, and destination preferences piecemeal.

Missing basic details
04
Unstructured notes

Critical details stayed scattered in chat histories without centralized logging.

Scattered data
05
Delayed follow-up

Reps struggled to prioritize enquiries, prepare custom quotes, and track status.

Delayed follow-up
Outcome: Hours wasted collecting routine factsUnstructured Records
02/The Approach

Connecting customer conversations to the team's operational workflow.

Rather than an isolated chatbot, the system connects incoming customer conversations directly to the team's existing Google Sheets workflow. When a traveller reaches out, the assistant provides immediate answers about trip categories, dates, and packages in Kannada or English.

As the customer explores, the assistant methodically collects their travel dates, group size, destination, and budget. It organizes these details into structured spreadsheets so the sales team can review a complete dossier before stepping in for personalized itinerary planning, custom pricing, and final bookings.

Stage 01Active Stage

Start the conversation

The customer opens WhatsApp from the website and selects Kannada or English for immediate 24/7 engagement.

Main Action:Language selection & instant session greeting
Impact:Zero onboarding barrier; responds immediately even outside business hours.
01
Stage 02

Explore travel categories

The assistant presents available services (International, Domestic, Treks, Custom Trips, Visa) with package info pulled directly from Google Sheets.

Main Action:Live catalog lookup & service guidance
Impact:Answers repetitive destination and schedule queries without sales intervention.
02
Stage 03

Collect travel requirements

The assistant guides the traveller to share essential details: destination, planned dates, group size, and estimated budget.

Main Action:Structured requirement gathering
Impact:Captures a complete enquiry upfront, eliminating hours of fragmented chat back-and-forth.
03
Stage 04

Organize into team records

Customer details are logged directly into dedicated Google Sheets tabs and tracked through structured status stages in the sales pipeline.

Main Action:Automated spreadsheet entry & lead categorization
Impact:Replaces lost chat notes with a clean, centralized dossier ready for immediate sales review.
04
Stage 05

Hand over to travel specialists

When a customer requests custom itinerary tailoring, special pricing, or visa guidance, the assistant hands over with full documented context.

Main Action:Context-rich specialist handoff
Impact:Experienced sales consultants focus entirely on high-touch advice and closing.
05
03/System Architecture

Connecting the tools behind the conversation.

The architecture maps customer conversations to reliable business tools. By connecting WhatsApp, Gemini, and Google Sheets through an automated workflow, incoming enquiries are automatically organized without requiring manual data entry.

System Architecture DiagramEnd-to-End Operational Pipeline
WhatsApp · Gemini · n8n · Google Sheets
01 / Client IngestionInbound Channel

Website / WhatsApp

Direct Customer Interface

Receives incoming traveller queries in Kannada or English directly from the website entry point.

Pipeline StatusConnected
02 / Conversation IntelligenceDialogue Intelligence

Gemini AI

Context & Language Engine

Understands customer intent, translates between languages, and guides travellers step by step.

Pipeline StatusConnected
03 / Workflow OrchestrationRouting Engine

n8n Automation Engine

Workflow Logic & Routing

Coordinates conversation steps, queries catalog data, and routes completed requests seamlessly.

Pipeline StatusConnected
04 / Business InformationLive Catalog

Google Sheets

Central Service Catalog

Maintains active packages, itineraries, dates, and pricing so responses reflect live business facts.

Pipeline StatusConnected
05 / Operational OutputLead Dossier

Structured Lead Records

Categorized Enquiries

Stores complete customer dossiers sorted by service (International, Domestic, Treks, Custom, Visa).

Pipeline StatusConnected
06 / Human HandoffSpecialist Consultation

Travel Specialist Closing

Sales Team Follow-Up

Consultants take over tailored itineraries and pricing with complete conversational context.

Pipeline StatusConnected
Connected Webhook Pipeline & Active State Management
5 Services Supported: International · Domestic · Treks · FIT · Visa
04/Operational Results

A more organized way to handle incoming enquiries.

Between April 8 and October 29, 2026, the system processed 2,047 inbound enquiries. Instead of piecing together context from raw chat history, the sales team references organized dossiers when preparing customer follow-ups.

2,047 plus inbound enquiries handled, 08 April to 29 October 2026
INBOUND ENQUIRIES HANDLED
08 April – 29 October 2026
Live Operational Count
54 percent after-hours enquiriesAFTER-HOURS ENQUIRIES

Enquiries received outside regular business hours (10 a.m. – 6 p.m.).

5 travel service workflowsTRAVEL SERVICE WORKFLOWS

International · Domestic · Treks · FIT · Visa Guidance

273 hours estimated manual time savedESTIMATED MANUAL TIME SAVED

Estimated based on an average of 8 minutes of manual intake per chat.

2 languages supportedLANGUAGES SUPPORTED

Kannada · English

Workflow TransformationOperational Shift Comparison
Initial Intake Stage
Before Automation
Manual Process
  • —Manual intake across individual WhatsApp chats.
  • —Conversations stretched across hours between other tasks.
  • —Customer details scattered across raw chat history.
  • —Manual effort needed to organize and categorize enquiries.
After Connected Workflow
Active System
  • Initial conversations answered immediately by the assistant.
  • Travel dates, party size, and destination systematically collected.
  • Structured records organized directly in Google Sheets.
  • Sales team reviews clean dossiers for personalized follow-up.
  • Human experts handle requests requiring customized consultation.
*The system supports the initial enquiry capture. It is designed to assist, not replace, human travel advisors or the closing sales process.
05/What The System Supports

Collecting an enquiry is only the beginning of a sale.

The system supports initial enquiries and requirement capture, but it does not replace travel advisors. While automation organizes intake and eliminates response lag, customer booking decisions depend on nuanced human consultation.

The boundary of operational automation

This system is designed specifically for initial enquiry intake and requirement logging. It organizes the customer's request so the sales team can enter the conversation with clear context already documented.

Automated System
  • • Immediate 24/7 first response
  • • Structured requirement collection
  • • Automated spreadsheet logging
Travel Specialists
  • • Custom itinerary adjustments
  • • Complex group requirements
  • • Pricing and final sale closure

*Sales conversion and revenue impact have not been measured or attributed to this software. Final bookings depend on pricing, personal recommendations, and customer circumstances.

Real-World Factors Influencing Bookings
01Budget & financing choices
02Holiday approval & leave planning
03Seasonal travel dates
04Itinerary customization
05Flight & accommodation availability
06Specialized visa guidance

Automation streamlines initial intake; experienced advisors close the sale.

06/Broader Application

The same thinking can apply beyond travel.

Any business that receives repetitive inbound queries and needs structured information before a person follows up can benefit from this approach. Each implementation is customized to the organization's actual workflow and team tools.

01Production Case — Go Pravasa

Travel Enquiries

Gathers destination, travel dates, party size, and budget before a travel consultant prepares a customized itinerary.

Verified production system
02Potential Application

Real Estate Enquiries

Captures buyer budget, preferred localities, and property type before an agent arranges property visits.

Conceptual workflow model
03Potential Application

Appointment Requests

Pre-screens client needs, requested specialty, and availability before clinic or studio scheduling.

Conceptual workflow model
04Potential Application

Professional Services

Collects project scope, technical requirements, and target timeline prior to preparing an initial proposal.

Conceptual workflow model
05Potential Application

Customer Support Triage

Logs issue category, account details, and request urgency before routing to specialized support staff.

Conceptual workflow model
07/Next Steps

HAVE A PROCESS THAT NEEDS A BETTER WORKFLOW?

Every business has processes that can be made easier. Let's understand how yours works and explore where a better system could make a difference.

Discuss your workflow30-minute conversation · No technical preparation needed.
← Return to IndexGo Pravasa Case Study · 2026