Group travel is where agencies make their margin and lose their weekends. A single enquiry — forty people, one budget, one weekend, forty opinions — turns into weeks of quoting, chasing venues and rebuilding the itinerary every time somebody changes their mind.
HeyMandy is built around that specific job. A group brief goes in, an itinerary and a client-ready proposal come out, and the agency can see at a glance which groups are moving and which have gone quiet.
The pipeline, not the inbox
Every enquiry becomes a group with a brief: destination, month, headcount, budget per person and what the client actually wants out of the trip. Groups move through draft, proposal sent, booked and completed, so nothing sits forgotten in somebody's email.
- One record per group, carrying the whole brief
- Pipeline status from draft through to completed
- Groups allocated to a lead agent
- A view of what has stalled and for how long
Itineraries built against graded venues
Itineraries are assembled day by day from a venue library that carries more than a name and a rate. Each venue holds a grade, a sentiment score and its recurring issues, so an agent can steer a group away from the property that photographs beautifully and disappoints on arrival.
- Day-by-day itinerary construction
- Venue grading, review scores and recurring-issue tracking
- Per-day base cost and premium upgrade options
Proposals the client can actually respond to
The proposal carries the narrative, the itinerary and the pricing broken down per person, and it goes to the client inside the platform rather than as a PDF attachment that gets lost. Client feedback comes back against the proposal, so the revision history stays with the group.
- Draft, sent, revised, accepted and declined states
- Pricing summary per person and in total
- Client feedback captured against the proposal
- PDF generation for the client who still wants one
White-label, multi-agency
Each agency runs on its own branding, its own domain and its own subscription. Tenant isolation is enforced at the middleware layer — a user without an agency cannot hold a session at all.
- Per-agency branding, colours and custom domain
- Subscription plans with usage limits
- Strict tenant isolation, enforced centrally
About this demo
You will be signed into the real platform against a sandbox agency — seven travel groups spread across the pipeline, with itineraries and proposals already built. It is read-only: every screen is open, but anything that would send, save or confirm is declined with a note explaining what the live system would have done.
Where to start
Start as the Agency Owner to see the whole pipeline, then move to the Agent to see a single consultant building a trip. Finish as the Client — the narrowest view in the product, and the one that shows how tightly the platform scopes what each person can see.
- The whole pipeline — draft, proposal sent, booked, completed
- Every agent and their groups
- White-label branding and agency setup
- Subscription, usage and invoices
- Groups across the team and where each one has stalled
- Proposals awaiting a client response
- Venue grading to steer agents away from the weak ones
- My own groups and their briefs
- Day-by-day itinerary building against graded venues
- Proposal drafting, pricing and client feedback
- My proposal and itinerary
- Pricing broken down per person
- Nothing belonging to any other client