RRatiba
Itineraries

Sharing proposals

Links, password protection, expiry, custom domains.

Once a proposal is published, the Share tab gives you the link and the controls around it.

https://<your-subdomain>.ratiba.io/proposal/<id>

The ID is a long unguessable string, so the link is effectively private as long as you don't share it widely.

You can copy the link, send it by email, send it on WhatsApp, or embed it in a Calendly follow-up.

Email send

Click Email proposal to send the link from Ratiba. The email:

  • Has your branding.
  • Includes a short cover note you can edit.
  • Tracks opens and clicks.

If you'd rather send from your own inbox, copy the link and paste it.

Password protection

You can optionally require a password to open the proposal. Set it in the share tab. The client receives a separate email or message with the password.

Most operators don't bother — the unguessable URL is enough — but it's there for high-value or sensitive bookings.

Expiry

You can set the proposal to expire on a date. After expiry, the URL shows "this proposal has expired, please contact us for an updated quote".

Expiry is useful when supplier rates change frequently and you don't want stale quotes circulating.

Custom domain

On paid plans, you can use your own domain (e.g. proposals.yourcompany.com) instead of <subdomain>.ratiba.io. Set this up from Settings → Branding. Requires a DNS CNAME pointing at Ratiba.

Once configured, all proposal URLs use your domain.

Tracking

Every share method (email, link copy, WhatsApp share) is recorded. The activity timeline on the itinerary shows who shared when, and what the client did next.

You'll also see:

  • First open time.
  • Total views.
  • Last view time.
  • Time spent reading (rough estimate based on scroll and time on page).
  • Devices used.

This is how you know whether to follow up tomorrow or wait another day.

Forwarding

Clients sometimes forward proposals to a spouse or to a corporate buyer. Ratiba tracks each unique device, so you'll see multiple viewers even though one link was sent. We don't try to identify them individually beyond what the URL fingerprint reveals.