Clients Can Now Book Services Inside the CRMX Client Portal
CRMX clients can now discover, book, reschedule, and manage enabled services inside one portal. Learn the setup, limits, and booking QA path.
Clients can now discover, book, reschedule, and manage enabled services inside the new CRMX Client Portal.
Instead of sending a separate booking link for every service, a business can place selected Services booking pages in the portal's Appointments area. Clients can browse those services, choose an available date and time, complete the configured booking steps, and return later to view eligible appointments.
The improvement was announced in the official product changelog on October 29, 2026. The current official setup guide confirms the subaccount path, client journey, visibility controls, appointment-management behavior, and current limitations.
The most important boundary is in the name: this is available in the new Client Portal and uses Services booking pages. It does not make every service visible automatically, replace your service policies, or prove that reminders and workflows ran.
What changed in CRMX
The Client Portal appointment catalog can now include both meeting calendars and enabled Services booking pages.
For a client, that means one signed-in place to:
- find services the business has chosen to expose;
- select one service, or multiple services when the setup permits it;
- choose an available date and time;
- review and complete configured forms or payment steps;
- submit the booking or appointment request;
- see meeting and service appointments under Upcoming and Past;
- reschedule or cancel eligible service appointments when the business's rules allow it.
For the business, visibility remains controlled at the booking-page level. One Services booking page can appear in the portal while another stays private.
Two settings must work together:
- Allow booking from client portal must be enabled for each Services booking page that should appear.
- Appointments must be enabled in Client Portal App Permissions.
That separation is useful. It lets an administrator enable the appointment area without exposing every service, or prepare selected booking pages before opening the Appointments experience to clients.
Why this matters operationally and financially
Separate booking links create small handoff problems that add up. A customer may have to search an old email, ask the office which link applies, repeat contact details, or move between the portal and a public booking page.
Putting selected services in the portal can reduce those link-management steps and give the customer one familiar place to review upcoming work. It can also make the business's own booking path easier to explain: sign in, open Appointments, choose a service, and follow the configured steps.
The operational value is not only convenience. The new surface creates a clearer checkpoint between interest and the work that follows:
- Which service did the client select?
- Was the appointment confirmed or submitted for review?
- Which staff member or location owns the next step?
- Are forms or payment details complete?
- Are confirmation, reminder, reschedule, and cancellation rules correct?
- Does a reply or exception have a real human owner?
A cleaner path can protect staff time and reduce avoidable back-and-forth. It does not guarantee more bookings, lower costs, higher revenue, successful payment, or better show rates. Those outcomes still depend on the offer, availability, booking-page setup, client behavior, and the follow-up system around the appointment.
The businesses most likely to benefit are:
- home-service companies offering defined appointments such as tune-ups, inspections, maintenance visits, or consultations;
- coaches and consultants offering paid sessions, reviews, intensives, or other appointment-based services;
- teams already using Client Portal for customer access or ongoing delivery;
- businesses managing several Services booking pages that should not all be public in the same places;
- operators who want customers to view and manage eligible appointments without asking the office for another link.
Use the CRMX LIST booking-control method
The release supplies the booking surface. The CRMX LIST method turns it into a controlled client journey.
1. Limit what the portal exposes
Start with the Services booking pages a signed-in client should actually see.
For each page, review the client-facing name and short description. Those details appear in the portal booking catalog, so they should help a client distinguish one service from another without internal shorthand.
Do not enable every page simply because the setting is available. Separate public services, client-only services, seasonal offers, staff-only scheduling paths, and booking pages that still need configuration.
2. Invite clients into one booking path
Enable Appointments in Client Portal App Permissions, then explain the path in plain language:
- Sign in to the new CRMX Client Portal.
- Open Appointments.
- Select Book Appointment.
- Open Services or the combined catalog.
- Choose the correct booking page and service.
Test that path with an authorized contact before making it part of an onboarding message or support script. Confirm the client can sign in, see only the intended pages, and understand the choice presented.
3. Set the policies that govern the appointment
Portal visibility does not replace Services configuration.
Review the settings that shape what the client can do:
- which services appear on the page;
- whether multiple services may be selected;
- available staff, locations, dates, and times;
- whether forms or payment details are required;
- whether new appointments auto-confirm or remain requests;
- when rescheduling is permitted;
- when cancellation is permitted;
- what confirmation page or acknowledgment appears after submission.
This is where the customer promise becomes real. If the screen says the request is awaiting confirmation, the business needs a review owner. If the booking is confirmed immediately, the confirmation and reminder path should match that state.
4. Trace the full result
Run one real test journey from the customer's side and one review from the team's side.
On the client side, confirm:
- the correct service pages appear;
- the available service, date, time, staff, and location are accurate;
- prefilled client information is correct;
- required forms or payment steps behave as configured;
- the final screen accurately says confirmed or requested;
- the appointment appears in the expected Upcoming view;
- eligible reschedule and cancellation actions match policy.
On the business side, reopen the appointment and confirm the status, contact, service, staff, location, submitted information, payment state when applicable, and next owner.
Then inspect the actual notification and workflow evidence. A visible appointment does not by itself prove that an email, SMS, internal notification, task, or AI-employee action ran.
Example 1: an HVAC company gives maintenance clients one place to book
An HVAC company uses the CRMX Client Portal for maintenance-plan customers. It has Services booking pages for seasonal tune-ups, indoor-air-quality consultations, and replacement estimates.
The administrator enables the tune-up and consultation pages for the portal but leaves the replacement-estimate page out because that path begins with office qualification.
Clients can sign in, open Appointments, choose an enabled service, and select an available visit. The tune-up booking page is set to confirm automatically. The consultation page is set to create an appointment request for office review.
The company tests both paths separately:
- the confirmed tune-up must appear in Upcoming and enter the approved confirmation and reminder path;
- the consultation request must stay visibly unconfirmed until the office reviews it, and a named team member must own that review.
After the appointment is in the correct state, the business can apply its home-service booking follow-up system. The portal makes booking easier; it does not replace the confirmation, show-up, reschedule, or exception workflow.
Example 2: a consultant centralizes client sessions and intensives
A business consultant uses the Client Portal for active clients. The portal already holds program resources, and the consultant now enables booking pages for monthly strategy sessions and half-day intensives.
The monthly session page allows one service and follows the normal availability calendar. The intensive page requires additional intake and remains an appointment request until the consultant reviews the scope.
Clients no longer need to search for two different booking links. They open Appointments and choose the correct service from the catalog.
The consultant still verifies the differences:
- monthly sessions should confirm immediately only when the calendar and capacity rules allow it;
- intensives should show the request state clearly and route the review to the consultant;
- rescheduling and cancellation windows should match the engagement agreement and the configured Services rules;
- a submitted intake form should be visible to the approved owner before preparation begins.
This creates a useful bridge between the coach and consultant experience and the booking stage of the CRMX Revenue Flywheel, without treating portal access as proof that the service has been approved or delivered.
How to enable service booking in the CRMX Client Portal
Use the intended CRMX subaccount and begin with one Services booking page.
Enable the booking page
- Open Calendars.
- Select Services, then Booking Pages.
- Open the booking page you want clients to find.
- Select Client Portal in the booking-page settings.
- Turn on Allow booking from client portal.
- Review the booking-page name and short description clients will see.
- Save the page.
Repeat this only for the other Services booking pages that should be visible.
Enable Appointments in the portal
- Open Memberships.
- Select Client Portal.
- Open Settings, then App Permissions.
- Turn on Appointments.
- Save the permission.
Test the client journey
- Sign in to the new Client Portal with an authorized test contact.
- Open Appointments.
- Select Book Appointment.
- Open the Services catalog and choose the enabled booking page.
- Select a service, date, and time.
- Complete any configured form or payment steps.
- Submit the booking.
- Record whether the result is a confirmation or an appointment request.
- Reopen Upcoming appointments and test any eligible management action.
- Verify the business-side record and downstream follow-up evidence.
Limits and rollout notes
The official changelog presents Service Booking as currently available in the new Client Portal. The dedicated help guide documents the current subaccount setup and does not state a beta, Labs, phased, regional, agency-only, or plan restriction.
Important boundaries remain:
- The new Client Portal is required. The sources do not promise identical behavior in legacy portal experiences.
- This uses Services booking pages. The official guide distinguishes them from the older Calendar Service Menus feature.
- Each page needs its own visibility setting. Enabling Appointments does not expose every Services booking page automatically.
- Multiple-service booking depends on configuration. The Services Global Settings control whether clients can select more than one service.
- Submission does not always mean confirmation. Auto-confirm settings can leave a booking as an appointment request that needs review.
- Rescheduling and cancellation are conditional. The relevant Services policies decide whether the actions appear and when their permitted windows expire.
- Forms and payment steps depend on the booking page. The client sees the requirements configured for that service journey.
- Disabling Appointments removes portal access, not the underlying records. Existing appointment records remain in CRMX.
- A portal appointment is not execution proof. Reopen the record and inspect notification, workflow, payment, and ownership evidence separately.
Where CRMX AI employees fit
A service booking can give an approved CRMX AI employee useful context: the contact, selected service, appointment state, requested time, and next expected action.
That context can support confirmation, qualification, preparation, reschedule assistance, or exception handling only when the role, tools, permissions, knowledge, entry rules, and human escalation path are configured and tested.
The new portal surface does not train an AI employee, grant it access, authorize outreach, or prove a workflow ran. Keep the booking state as the source event and require evidence for every downstream action.
Client Portal service-booking QA checklist
Before rolling the feature out broadly, confirm:
- The test uses the intended CRMX subaccount.
- The new Client Portal is active for the tested client journey.
- Appointments is enabled in Client Portal App Permissions.
- Only intended Services booking pages have portal visibility enabled.
- Each visible page has a clear client-facing name and description.
- Service, staff, location, duration, date, time, and availability are accurate.
- Multiple-service selection is on or off deliberately.
- Required forms and payment steps appear as configured.
- Prefilled client information is accurate.
- The final state clearly says confirmed or requested.
- The appointment appears under the expected Upcoming or Past view.
- Reschedule and cancellation actions match the configured policies.
- The business-side appointment record contains the expected details.
- A human owns any appointment request or exception.
- Confirmation and reminder delivery are checked separately.
- Workflow execution history is checked separately.
- AI-employee action is authorized and tested separately.
- Mobile and desktop client journeys both complete without confusion.
Frequently asked questions
Can every client now book services inside CRMX?
Clients using the new Client Portal can book from Services booking pages the business has explicitly enabled, provided the Appointments application is also enabled for the portal.
Does enabling Appointments expose every service?
No. Each Services booking page has its own Allow booking from client portal setting. The business chooses which pages appear.
Can a client book more than one service at a time?
Yes, when the relevant Services configuration permits multiple-service selection. Otherwise, the client follows the single-service path.
Is every portal booking confirmed immediately?
No. Services settings determine whether new appointments auto-confirm or remain requests for review. Read the final screen and verify the saved appointment status.
Can clients reschedule or cancel from the portal?
Eligible service appointments can expose those actions, but the business's configured rescheduling and cancellation rules determine whether they are available and when the allowed window closes.
Does turning off Appointments delete existing bookings?
No. The official help guide says disabling the Appointments application removes access to that portal area without deleting the underlying appointment records.
Does a portal booking prove reminders and workflows ran?
No. The appointment proves the booking state. Check notification delivery, workflow execution history, tasks, assignments, payment state, and AI-employee actions in their own evidence surfaces.
Make the portal booking path easy to trust
The best portal experience is not the one with the most services visible. It is the one where the right client can find the right service, understand the state they created, manage the appointment within clear rules, and reach a real owner when something changes.
Limit the catalog. Invite the client. Set the policies. Trace the outcome.
That is how the new service-booking experience supports the CRMX platform: it brings discovery, booking, appointment state, and follow-up context into one lead-to-customer system without confusing visibility with verified execution.
If you want help designing the booking, confirmation, reminder, reschedule, and AI-employee handoffs around your services, request a live CRMX strategy demo.