Your tour catalog site

On Pro (and the free trial), the Website page in the dashboard can run a public catalog site for your company: your tours, in your colors, with an inquiry form that lands back in the dashboard. This page walks through claiming an address, getting the site ready, the marketing fields, and working the inquiries.

Claim an address

Open Website in the dashboard.
Choose a site address — 3 to 40 characters, lowercase letters, digits and hyphens, like kestrel-tours. A handful of words Cordelle uses itself (app, help, demo and the like) are reserved, and an address another company holds is taken; the form says so in plain words either way.
Write the welcome text — the short paragraph at the top of your page — and, if you like, a public inquiry email, the address inquiries are sent to. Leave it blank and they go to the account owner.

While your site is on, its address is frozen — links you have handed out must keep working. To rename or release it, switch the site off first; the moment an address is freed, another company can claim it.

Before the site can go on

The switch refuses politely until three things are true, and it tells you which is missing:

The site has an address.
The site has a welcome text.
At least one tour has a description — an empty catalog page would be worse for you than no page, so the site won't go live without something to show.

Switching off always works — the switch never refuses — and so does editing a live site; like any edit, the public pages catch up within a few minutes. The Website page shows how many tours the catalog would list today.

Where your site lives, for now

Today, every site lives at an unlisted address: cordelle.io/s/your-address. It works the moment you switch on — put it in your email signature, your brochure, your social pages — but it is deliberately kept out of search engines while the feature is young. A named launch, with each site on its own web address, comes when subdomains ship. The Website page has a Copy the address button.

What the site shows

Every tour with a description, its upcoming departures listed soonest first. A tour between seasons stays on the site — dateless, with the inquiry form as its call to action.
A page per tour: your description, a day-by-day outline (day titles and summaries from the soonest departure's real itinerary), hotels by name and city, the packing list, and country basics — currency, language, plug type.
Your colors and logo, from the same branding as your traveler app.
Your price line and Reserve link, printed exactly as you wrote them. Booking happens on your link — Cordelle runs no checkout.

Your site shows only what the whitelist serves. The public pages are built by a server path that names, field by field, the only columns allowed out. Travelers, the guest book, documents, flights, join codes, hotel addresses and Wi-Fi, itinerary times and meeting places — none of it can appear on the site, and our tests fail the build if a stray field ever shows up in a public payload. Visitors get no cookies and no analytics from these pages, either.

The marketing fields

On each tour (Tours & departures, the tour's card): the description that puts it on the site, an optional photo address for the card picture (no photo = a generated card in your colors), and up to four short tags — "Small group," "All breakfasts" — shown as chips. Write only what is true of the tour; there are deliberately no seats-remaining counters to go stale.
On each departure (Hotels, flights & guides tab, the website listing card): the price line — one free-text line, like from $3,999 · $699 single supplement — and the Reserve link, a web address or phone link of yours.

None of these touch the traveler app or the published trip: saving them never marks the departure "edited since publish." The public page is cached for speed, so an edit can take a few minutes to appear.

Inquiries: the inbox and the guest book

The site's form asks a visitor for their name, email, phone, party size and message — and which tour caught their eye. Each inquiry becomes two things: a row in Website › Inquiries, and an email to your public inquiry email (or the account owner), with the visitor's address as the reply-to, so answering is just replying.

Work the list: each inquiry moves through new → contacted → closed. The Website link in the dashboard carries a badge with the count of new ones.
File them in: a click checks whether the sender is already in your guest book by email; one more confirms — link them if so, create their record if not — and marks the inquiry contacted.
Delete and export: inquiries keep until you delete them, row by row, and the whole inbox exports as CSV.

← Back to the Help center

What the site is and why: the tour catalog site. Questions? [email protected].