Not templates — different operational models on the same PlexWizz core. Each business runs the workflow it actually lives, under its own brand, on its own domain.
Same infrastructure underneath — a different operating model per business.
Not a theme and not a template — the sequence of steps the business actually lives, wired into its portal: what a lead becomes, what gets scheduled, what gets paid, and what comes back.
The deepest model in production: inquiries from ads and forms land in the business's own mailbox, conversations become offers with day-by-day itineraries, bookings carry deposits and balances paid into the business's own accounts, travelers get a members area with their trips and group invitations — and repeat guests come back through their own door.
Inquiry to appointment to follow-up to recall: the model turns one visit into a returning patient — scheduled recalls and settled payments. Clinical records stay where they belong: in the clinic's own systems.
Dates and vehicle class in, availability check, reservation confirmed, payment secured — and a customer record that makes the second rental one message long.
Requests become offers with rooms and rates, bookings become stays, stays settle their folio, and the follow-up asks for the review while the trip is still warm.
Your client's industry not on this list? These are starting models, not limits — the same core bends to the workflow the business actually lives.
Whatever the industry, the shape is the same: a business portal where the owner and team operate, and a booking portal where their customers serve themselves — both on the business's own domain, in the business's own name.
Leads and conversations in their own mailbox, bookings, payments into their own accounts, their own team and roles.
Their customers book and pay online, see their reservations in a members area, and get confirmations instantly — all under the business's brand.