Group bookings, banquet sales, corporate accounts. Most CRMs are built for product sales, not service sales.
Group enquiries arrive by phone. No history.
Banquet quotes live in PDFs everywhere.
Corporate account managers fight over the same lead.
Each property keeps its own spreadsheet.
A pipeline for group bookings, with stages you configure.
Web enquiry forms, inline, as a popup or a hosted link, routed to a rep on submit.
One owner per lead, set by territory rules and assignment strategies.
A personal public booking page per sales manager, with the Team module.
A workspace per property, with shared staff, in one subscription.
Run group bookings as a pipeline with the stages you configure. Enquiry forms on your site publish inline, as a popup or as a hosted link, and a new enquiry routes to a rep the moment it is submitted.
Log the call as an activity on the account, so the enquiry has a history the next person can read. Duplicate detection runs on every intake, before two records exist.
Every lead has one owner. Territory rules and five assignment strategies decide who, a rep's capacity cap stops hoarding, and a manager can force a reassignment.
Several properties can run as separate workspaces in one subscription, sharing staff. Each keeps its own data, logo and document numbering unless you choose to share a module.
Guided onboarding walks you through company, details, product and AI context, then inviting the team.
We would like to count which pages people read, using Google Analytics. It tells us nothing about who you are, and the site works exactly the same if you say no.What we collect