Part of TripzoCRM
One link in your bio. Your whole trip catalogue.
Tripzo Links gives your travel agency a branded page on its own address — every category, every departure, every brochure — and sends each tap into TripzoCRM as an enquiry that already knows which trip it came from.
- Your own subdomain
- No app to install
- Included with TripzoCRM
Trip : Kashmir Valley
→ Tagged in the CRM
- Link to keep in the bio
- 1Link to keep in the bioOne address, however often the catalogue changes behind it.
- Taps from bio to WhatsApp
- 3Taps from bio to WhatsAppOpen, pick a trip, send. The message is already written.
- Logins for your customer
- 0Logins for your customerNo account, no app, no cookie banner in the way.
- Open while you are not
- 24/7Open while you are notBrochures, dates and payment keep working after hours.
Three steps, and it is live.
Nothing to design, nothing to host, nothing for your customer to install.
Put the link in your bio
Your agency gets its own address — yourname.tripzolink.com — built from the slug already on your organization. Paste it into Instagram, WhatsApp, Google Business, anywhere one link is all you get.
Your customer browses
Your logo, your name, your categories, your trips, with real prices and durations. They tap a trip and get the brochure, a departure date, a booking, or WhatsApp with the message already typed.
The enquiry lands in the CRM
It arrives tagged as a Tripzo Links lead with the trip attached, and it is routed and assigned by the same rules as every other lead. No export, no copy-paste, no separate inbox.
Most bio links go dark the moment WhatsApp opens.
A wa.me link carries nothing into WhatsApp but its text. No referrer, no UTM, no origin domain. Meta's referral data exists only for paid click-to-WhatsApp ads, never for an ordinary link on a web page.
So without a marker in the message itself, an enquiry from your bio page is byte-identical to one off your Meta ad — and every report that splits them is guessing.
What Tripzo Links does instead
Each trip tile opens WhatsApp with a sentence already in the composer, prefixed and keyed to that one trip. The CRM matches the phrase, reads which surface it belongs to, and stamps the lead. You get the channel and the trip, from a link that technically transmits neither.
Per trip, not per page
Every trip gets its own phrase, so the report names the trip that pulled the enquiry, not just the page.
It survives the hop
The marker rides inside the message the customer sends, which is the only thing that crosses from a web page into WhatsApp.
It never dead-ends
A trip with no phrase set, or an agency with no WhatsApp number connected, falls back to the booking page. A dead tile is worse than one that goes somewhere useful.
Trip : Kashmir Valley
Tagged in the CRM as Tripzo Links · Kashmir Valley
More than a list of blue buttons.
A link-in-bio tool holds links. This one holds your catalogue, because it is reading the same packages, departures and prices your agents are.
Your own address
Your page lives at yourname.tripzolink.com, built from the slug already on your organization, so what you paste into Instagram carries your name rather than a CRM's. Agencies without a slug stay reachable on a plain link until one is set, and nothing about the address has to be bought or renewed separately.
Categories and trips
Your trips arrive grouped the way you already group them in the CRM, each tile carrying its photo, duration and price. There is no second catalogue to maintain: the page reads the packages your agents are quoting from, so editing a trip, repricing it or retiring it changes the page the next time it is opened.
Brochures, gated
Tapping a trip's PDF asks for a name and a phone number before the download, which is instant once given. You get a contact out of a visitor who was never going to message you first, and the brochure is served fresh — re-upload it in the CRM and the old file stops being handed out.
Departures and seats
A fixed-departure trip shows its real dates rather than asking the customer to propose one, so the enquiry reaches you with a date already attached. The dates come from the same departure records your operations team works to, which is what keeps the page from offering a batch that is full or gone.
Book and pay on the page
A customer who has already decided can add a trip, open the checkout sheet and pay online without waiting for office hours or a callback. The booking lands in the CRM with the trip, the departure and the amount on it, so the first thing your team does is confirm rather than re-key.
Two layouts, one catalogue
The default layout is the catalogue: a category strip over your trips. The second is a blocks page you compose yourself — a heading, the buttons you choose, your own paragraphs, and the trips strip wherever you want it. Layout and theme are separate settings, so picking a shape never decides your colours.
Built to open fast
It is its own small deployment for a reason: no login, no database client in the browser, no analytics SDK and no cookie banner. The whole page is two unauthenticated reads, which matters when the person opening it is on a phone on a mobile network and has already decided how long to wait.
Enquiries become leads
Every form on the page files a lead as it is submitted, carrying the trip and the chosen departure that a plain lead record has nowhere to put. From there it is an ordinary lead: routed, assigned and chased by the same rules as the rest of your pipeline, with nothing to export and no second inbox to remember.
The same catalogue, arranged your way
The blocks layout, composed in the CRM. Pick it when your page is more of a front door than a shop window.
The denominator under the leads number.
You can already see how many enquiries the page produced. Without the other half you cannot see how many people had to open it to produce them — which is the number that tells you whether to change the page or change the traffic.
And it is measured without following anyone
- No cookie, so no banner to put in front of your customer.
- No IP address is stored anywhere in this path.
- The session id lives in sessionStorage and dies with the tab — it can turn views into a conversion rate among the same visit, and cannot recognise anyone who comes back.
- Device, source and country are derived from the request, never asked of the browser.
01Page opened
Somebody followed the link. Counted once per visit, so a customer who reloads is still one person.
02Category opened
They went looking rather than bouncing — the step that tells you whether the page or the traffic is the problem.
03Trip tapped
They picked a trip, by name. This is the enquiry, and this is the row the lead is matched back to.
The things agencies ask about this one.
Is Tripzo Links a separate product we pay for?
No. It is part of TripzoCRM. Your packages, departures, prices and WhatsApp number are already in the CRM, and this page is a second surface onto them rather than a second place to maintain them.
Do we need the WhatsApp Business API for this?
For the WhatsApp button on a trip, yes — the enquiry has to land in an inbox the CRM can read, and we set that up with you during onboarding. Everything else on the page works without it: brochures, the departure picker, booking and payment all file an enquiry on their own.
What happens to a trip we have not set a phrase for?
Its WhatsApp button is hidden and the tile opens the booking page instead. That is deliberate: a button that opens WhatsApp with an empty message produces an enquiry nobody can attribute, which is the one thing this page exists to avoid.
Can we change how the page looks?
Yes. There is a theme — backdrop, gradient, palette — and a separate choice of layout: the catalogue, or a blocks page you compose yourself. The two are independent, so you can have the catalogue in your own colours or a different shape in the same ones.
Our customers are on slow connections. How heavy is the page?
It is built as its own small deployment for that reason: no login, no database client, no analytics SDK, and the whole page is two unauthenticated reads. It is the lightest surface we ship.
What if we already have a website?
Keep it. This is for the one link Instagram gives you, where a homepage is the wrong thing to send someone — they came from a reel about a trip, and this puts that trip two taps away instead of five.
Your bio link is doing one job. Give it the whole catalogue.
Tripzo Links comes with TripzoCRM. If your packages are already in the CRM, your page is a slug and an afternoon away.
Set up with you during onboarding, on every plan that includes it.
