Leads that arrive structured
An enquiry from your site lands already read: destination, dates, party, budget — each with the sentence it came from. The gaps are listed so you ask only what is missing.
The operating system for travel advisors
Triprava's agents price the trip, write the proposal, chase the signature and reconcile the commission — and show you where every figure came from before a client ever sees it.
Nothing is sent, booked or charged without you. That is a rule in the software, not a setting.
Why it is different
The question advisors actually ask about AI is not whether it saves time. It is whether it will embarrass them in front of a client. Three answers, built in rather than promised.
A held supplier quote, a published rate, something you keyed in, or an estimate — each line says which, and the system refuses to call a number a verified quote without the document behind it. You always know what you are reading out loud.
Every suggested change arrives with the line of the confirmation it read, how sure it was, and what would actually change. You approve it in a tap, or you do not. Anything that binds a reservation or moves money always asks — that one cannot be switched off.
A requested booking is not a confirmed one. An authorization is not a payment. A signed agreement is not a deposit. The software keeps those apart everywhere, because the day they blur is the day you tell a client something that is not true.
The lines it will not cross
Only a supplier's confirmation makes a reservation. A trip with an accepted quote and nothing reserved says so, loudly.
Permission to charge a card is not money in your account. They are counted separately, and the authorization carries its expiry.
Between the client signing and the sealed copy existing, the agreement is signed. You are never sent chasing someone who already did it.
A supplier who paid 620 against an expected 890 has not settled. The difference stays on the books as money owed.
What it does
One record per client and per trip, and everything hanging off it — so nothing has to be copied between tools, and nothing is only true in one of them.
An enquiry from your site lands already read: destination, dates, party, budget — each with the sentence it came from. The gaps are listed so you ask only what is missing.
Priced from live availability, written in your voice, and sent as a page a client wants to read. They accept, or ask for changes, and the agent answers the change.
Built from what is actually reserved, checked for connections that do not connect, and published only when it holds together.
Names against travel documents, confirmations on file, deadlines before they pass. When a supplier document disagrees with you, nothing changes until you say which is right.
Planning fee, terms, insurance accept-or-decline. Signed on a phone with no account to create, sealed immutably, with the evidence kept.
Send, chase and record what arrives. An invoice is paid because a payment exists against it, not because somebody flipped a status.
Expected against received, aged, with statement imports matched on confirmation number. A short payment is a documented shortfall.
A page at your own address, built from what your agency already tells us, published as an immutable version you can roll back.
And all of it on your phone — approving a draft between meetings is the task those five spare minutes actually fit.
A week with it
An enquiry arrived overnight and is already structured. You read four lines, not four paragraphs, and see the two things it does not say. You ask only those.
Three priced options, drafted. You read them against the live offers they came from, change one hotel, and send. The client sees a range, not a promise nobody made.
They ask for a swim-up room and later dates. The agent answers it with a revision while you are cooking. You approve it from the sofa.
Accepted. The planning-fee agreement goes out, is signed on a phone, and the deposit invoice follows. Four separate things, four separate states.
A supplier confirmation lands with a different arrival date. Nothing changes automatically; you are shown both and asked which is right. It takes nine seconds.
The commission comes in 270 short. It is on the screen as a shortfall with the arithmetic beside it, not quietly absorbed. You chase it, and you win.
For agencies and hosts
An advisor who works for a host and a sub-agency has two sets of clients under two sets of commercial terms. Triprava keeps them apart in the database itself — row-level security, enforced by Postgres, re-checked on every request — rather than relying on every query being written carefully.
Roles are checked on each request too, so revoking access takes effect on the next one. Which content an advisor may quote follows from the host contract, not from us.
“The agent drafts. The advisor decides. The database keeps the tenants apart.”
Three sentences that describe the architecture and the product at the same time.
Start free, bring one trip across, and see whether you trust what it tells you. That is the only test that matters.