PRODUCT 01 · OPERATIONS
IN PRODUCTIONMANAGED OR SELF-HOSTEDAP-SOUTH-1
TRAVEL CRM — PIPELINE, PRODUCTION TENANT
0
Modules in the standard tenant
0
Enquiry sources into one record
0
Weeks of standard onboarding
0
Record from enquiry to voucher
WHY IT EXISTS
We ran the agency first, then wrote the software.
A travel quote carries suppliers behind it, a hold date on the payment, and a voucher that has to exist before anyone flies. General-purpose CRMs model the sale and stop, so the second half ends up in spreadsheets.
MODULES
What the tenant includes.
01
Pipeline
02
Quotations
03
Payments
04
Suppliers
05
Vouchers & docs
06
Reports
STEP 01
The enquiry arrives
WhatsApp, the web form and the phone all create the same record. Duplicate detection links a returning traveller to their history before an agent opens it.
STEP 02
The quote is priced
Choose the route template, set nights and pax, and the margin rule prices it against the contracted supplier card.
STEP 03
The booking is held and paid
A payment link with a hold date goes out on WhatsApp. Reminders run on a schedule, and the deal reaches Confirmed when the gateway settles.
1Unified enquiry inbox
2Live pipeline value
3Stage moves logged to the deal
INTEGRATIONS & STACK
It plugs into what the agency already pays for.
Everything is API-first. If a supplier can send a rate file, we can read it; custom integrations are quoted separately.
MESSAGING
WhatsApp Business APIGmail / OutlookSMS gateways
PAYMENTS
RazorpayStripeBank transfer reconciliation
SUPPLY
TBORate-card importsCustom DMC feeds
STACK
PostgresNode & TypeScriptReactAWS ap-south-1
QUESTIONS