Let customers request the right time without turning your phone into the calendar.
Merritt Booking is part of the same account as Portfolio Builder and Link Hub: services, coverage, rules, operator review, and a publish path that stays under your control.
Built for real service schedules.
The goal is not a generic calendar widget. It is a booking flow that understands coverage, service rules, and the operator decisions that keep jobs sane.
Requests before commitments
Customers can ask for work without forcing the business into a slot that has not been reviewed.
Rules that explain themselves
Services, coverage, exceptions, and availability should be visible enough for an operator to trust before publishing.
Connected to the rest of Merritt
Booking sits beside Portfolio Builder, Link Hub, contact actions, and the operator workflow instead of becoming a separate disconnected tool.
Booking is not just an open calendar
| Feature | Generic calendar widget | Merritt Booking |
|---|---|---|
| Customer can request the right service | Yes | Yes |
| Coverage and service rules stay visible | No | Yes |
| Operator can review before confirmation | No | Yes |
| Connects to proof, contact, and business setup | No | Yes |
Booking questions
Can customers book instantly?
The first production posture is request-first. That keeps the business in control while service rules, coverage, and team capacity are still being refined.
Does this replace phone calls?
No. It catches the details that make the next call or review faster: service, location, urgency, photos, and constraints.
Can the page change later?
Yes. Booking marketing copy and page structure are editor-owned, and the app itself remains owned by the booking worker.
Start with the booking setup checklist.
Define the service, coverage, intake questions, and review rules before sending customers to a live request page.