Skip to main content
Demystify OS

Services

Demystify OS for Travel

Travel: Travel agencies and tour operators: package sellers, domestic tour operators, inbound operators, corporate travel desks and ticketing agencies.

Demystify OS lists 5 workflows for this industry, each step with the proof you check, and 1 of them are available today.

Every status on this page is shown as recorded: available, in beta, early access, on the roadmap, or on request.

Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST.

Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.

Ask what OS runs for TravelAll industries

The moment that matters

A traveller has paid an advance for a trip, and the owner needs to know what that trip will really earn once the hotel and transport bills are in.

What Demystify OS runs for Travel

Counted on 2 November 2026. A job we have not built is shown as on the roadmap, never as live.

Workflows

  • Enquiry follow-up list

    Early access

    Follow every enquiry to a booking. Keep each traveller enquiry on a board by stage, from enquiry to booked or lost.

    Proof: Enquiries are kept on an enquiry board.

    Done by: Finocket

  • Trip-tagged supplier bills

    Early access

    Tag supplier bills to a trip. Put a trip name on each hotel, transport or other supplier bill and see all bills for that trip in one list.

    Proof: Supplier bills are tagged to the trip they belong to.

    Done by: Finocket

  • Trip margin sheet

    Early access

    See what a trip earned. Read a trip profit line: money billed for the trip less the supplier bills tagged to it.

    Proof: Trip margin is read from the books. Only as good as the bills you tag.

    Done by: Finocket

  • Traveller dues list

    Available

    See what travellers still owe. Read the outstanding list for advances and balances still due from travellers and agents.

    Proof: Dues still owed are listed in one place.

    Done by: Finocket

  • Advance receipt with TCS line to confirm

    Early access

    Get a dated TCS suggestion on the receipt. When you record an advance for an overseas tour, the receipt screen suggests a TCS line based on the date. Your CA confirms it.

    Proof: A dated TCS suggestion appears on the receipt.

    Done by: Finocket

Routines

  • Four-week baseline, then a monthly read

    Early access

    Cadence: Four weeks first, then every month

    You receive: Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Skills

  • Enquiry follow-up listOn the roadmap
  • Trip-tagged supplier billsOn the roadmap
  • Trip margin sheetOn the roadmap
  • Traveller dues listOn the roadmap
  • Advance receipt with TCS line to confirmOn the roadmap

Integrations and distribution channels

  • CRM

    Early access

    Hold each traveller enquiry on a board by stage. The enquiry board is built but sits behind the travel pack switch, which is off by default.

    Through: Finocket

  • Web

    On the roadmap

    A traveller page for dues and invoices exists on the client link. An agency's own public site with packages and an enquiry form is not built and is planned.

    Through: Industry pack

  • Email

    On the roadmap

    Through: Connector Hub

You approve

Approvals themselves are in beta, invite-only. Each card approves the work of an agent that is on the roadmap for this industry, so each is shown as planned.

  • On the roadmap

    Approve or reject a supplier bill tagged to a trip

  • On the roadmap

    Approve or send back an advance receipt before the TCS line is saved

Memory and governance

One memory for every agent, and the controls around it.

Each agent would need to remember once your trip names, your supplier list, your traveller and agent records, and your own follow-up rule, so a bill, a due and an enquiry all point to the same trip.

  • Memory fabric

    Built, not launched to customers

    One memory shared by every agent: your parties, items, price lists and decisions are held once, with where each came from, so an agent does not ask you the same thing again.

  • Approvals

    In beta, invite-only

    Anything with a consequence waits for you. You tap approve or reject on your phone, and Mysty acts only after you do.

  • Evidence ledger

    Built, not launched to customers

    Every action leaves a receipt, and the receipts are kept in one ledger you can check later, for your own auditor.

  • Guardrails

    Built, not launched to customers

    Each agent has one role, a limit on what it may do and a named checker. Nobody marks their own work done. Money, publishing and outreach stay a person's decision.

Time and errors back: how you will see it

Measure first, then compare. Your own four weeks are the only baseline that counts. We print no promised saving.

  • Time

    Enquiries, trip bills and dues sit in one system.

  • Errors

    A trip tag on each bill and a dated TCS suggestion are in Finocket.

  • Cash

    One outstanding list shows advances and balances still due.

  • Control

    Trip margin is read from the books once supplier bills are tagged to trips.

Before you start
For four weeks before you switch on, count in a sheet: enquiries received and how many ended as a booking, overseas tour receipts whose TCS charge was reversed or re-entered, and invoices with a credit note for a wrong SAC or tax line.
Every month after
Each month, read the same counts again and compare them to your four-week baseline.
Who reads it
Owner
Where it shows
Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Metrics to adopt: how the business runs

  • Enquiries booked

    What it is
    Of the enquiries received in the period, the share that ended as a booking.
    Formula
    enquiries that ended as a booking / enquiries received x 100
    Where the number comes from
    Finocket enquiry board by stage (built, behind a pack switch)
    How often
    monthly
    Better is
    higher

Errors: count them as errors over transactions

  • Receipts corrected for TCS

    What it is
    Share of the overseas tour receipts raised in the period whose TCS charge was reversed or re-entered afterwards, each receipt counted once.
    Formula
    overseas tour receipts with a TCS charge reversed or re-entered / overseas tour receipts raised x 100
    Where the number comes from
    manual count: not captured today
    How often
    monthly
    Better is
    lower
    One error is
    One overseas tour receipt reversed or re-entered to correct its TCS charge counts as one error. A correction for another reason, such as an address, does not count, and neither does a receipt that is not for an overseas tour. Count only receipts raised in the period you are measuring.

  • Invoices with a wrong tax line

    What it is
    Share of the invoices raised in the period that carry a credit note tagged as a wrong SAC or tax line.
    Formula
    invoices with a credit note for a tax line / invoices raised x 100
    Where the number comes from
    Finocket invoices and credit notes; counted by hand from the list
    How often
    monthly
    Better is
    lower
    One error is
    One invoice with a credit note raised to correct a wrong SAC or tax line counts as one error, however many credit notes touch it. Count only invoices raised in the period you are measuring.

Start with a four-week baseline

  1. Step 1. For four weeks, count enquiries and bookings, corrected TCS receipts and credit notes for a wrong tax line in a simple sheet.
  2. Step 2. Pick your next trip, name it, and tag every supplier bill for it with that trip name.
  3. Step 3. Record traveller advances in Finocket, check the TCS suggestion with your CA, and read the outstanding list every week.

What OS does not do for you yet

OS does not yet build itineraries or costing, run group departures or manifests, store traveller documents, hold cancellation rules or reconcile airline BSP, so those stay outside OS.

Readiness table row for travel says READY, the same as the other verticals, but its own use-case map says travel is a second-wave vertical: its pack is held at preview and switched off by default, so trip bills, trip profit and the enquiry board are built but gated (BUILT, not LIVE). The readiness row also shows planned for data store, analytics and launch bar, and blocked for pricing/admin. Claims for travel: none approved. Tax statements, including the TCS rate, are not verified against primary text, so no rate is stated. Gaps (itinerary, departures, documents, cancellation, BSP) are not offered as jobs.

Sources: art:finocket-usecase-map-travel-1028, art:vertical-readiness-live.

The mix for your business

Pick what fits. Each product keeps its own site, and each link below says where it goes.

Free Demystify Tools for Travel

Start with the Diagnostic

Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.

Demystify OS Cloud is from ₹14,999 a month for 25 people. Invite-only beta; public from 1 January 2027.

Ask what Demystify OS runs for Travel

Questions

What does Demystify OS do for Travel?
It lists 5 workflows, such as Follow every enquiry to a booking and Tag supplier bills to a trip, and shows each one's status, so you can see which are available and which are on the roadmap.
What is available today and what is not?
Each workflow, routine and integration carries a status chip: available, in beta, early access, on the roadmap or on request. A job we have not built is never shown as live.
What does it cost?
Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST. Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.
When can I start?
Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.
How does this connect to Finocket?
Finocket has a vertical kit for this industry on finocket.com, linked from this page. Demystify OS works alongside it: Finocket keeps the books and stock, OS runs the routines around them.
Who sees my data?
Connectors start read only, anything with a consequence waits for your approval, and every action leaves a receipt in a ledger you can check. Demystify is DPDP-aligned and has SOC 2 on the roadmap.

Next to this industry

Looking for the wider picture? Industry view by Demystify Systems (opens a different site)