Calendar

I would love to see a feature in the calendar options thst is similar to Zazzle events previously known as HobNob. You can create an event with details and a cute invite. The systems sends it out to your guest list and they can RSVP yes or no they are coming as well if they are bringing anyone with them. You can also create a line up for food if you want people to sign up to bring food and post pictures from the event on the event too!

A lot of businesses run bookings where the dates are already decided, tattoo artists with flash day events, personal trainers running bootcamp weekends, makeup artists for bridal seasons, photographers doing holiday sessions. The client doesn't need to browse a calendar. There are 4 dates, just showing the available slots as buttons under each date makes much more sense than showing the entire monthly calendar. It's too cluttered and not needed at all. A simple layout, with title and date as a header, time slots as buttons, booked ones grayed out — would convert so much better for these date specific offers.

Example: we have a user who we want to have restricted access to only information/contacts they are assigned to. But they also need to be able to view calendars they are not assigned to so they can see who else is available and at what times. It would also be very important to show all users when other users have blocked off time. This information is not tied to any calendar that anyone other than the specific user who blocked it off can see unless they are a full admin. It doesn't need to go into details for privacy reasons. But being able to quickly see that X User is Unavailable or out of office at X day/time would be very useful.

When using the same calendar across multiple channels (e.g., a booking bot, an embedded widget on a service page, and an embedded widget on the main website, etc), there is currently no native way to see which channel generated a specific appointment. Requested feature: Add a native "Booking Source" field to each appointment that captures how and where the booking was made. This could include: The page URL or embed source where the booking widget was loaded The channel type (e.g., bot, inline widget, direct link, workflow) UTM parameters passed at the time of booking, surfaced directly on the appointment record Why this matters: Service-based businesses often run the same calendar across multiple touchpoints. Understanding which channel drives the most bookings is essential for optimizing marketing spend, bot performance, and website UX, without requiring manual UTM setup or workarounds.

When I'm looking at my calendar, it would be much more convenient if I can just click on the phone number in the calendar appt to take me straight to the call, as opposed to clicking on the contact's name to get into their contact card, and then calling from there. Thanks!

Summary: We would like the ability to set a shared maximum daily booking limit that applies collectively across multiple calendars, rather than only per individual calendar. Current Behavior: Currently, the daily booking limit can only be configured per calendar. If the same staff member is assigned to multiple calendars (e.g., separate calendars for different service types), each calendar enforces its own independent limit. This means the total number of bookings across all calendars can exceed the intended daily maximum. Desired Behavior: A setting that allows multiple calendars to share a single daily booking cap. For example, if the shared limit is set to 3, then once 3 appointments have been booked across any combination of the linked calendars on a given day, no further bookings would be available on any of those calendars for that day — regardless of which calendar the bookings came from. Use Case: A life coach or consultant offers multiple types of sessions — for example, separate calendars for male and female clients, or for different consultation formats (introductory sessions, deep-dive sessions, transformation programs). Unlike a hairdresser or other service provider whose limitation is primarily physical, a coach experiences significant mental and emotional fatigue. Conducting too many intensive sessions in a single day directly impacts the quality of their work and the experience of their clients. For this reason, it is essential to cap the total number of sessions per day across all service types combined — not just per individual calendar. There is currently no native way to enforce this combined limit, which means clients can inadvertently over-book a coach beyond what is sustainable. Proposed Solution: Introduce a "Calendar Group Daily Limit" option in Calendar Settings or Calendar Group settings When enabled, all calendars within the group share the same daily booking counter Once the shared limit is reached, all calendars in the group automatically block further bookings for that day

It would be extremely helpful to have a feature that allows setting a global daily booking limit for a user across all calendars they are assigned to, especially for round-robin setups. Right now, the booking limit only applies per individual calendar. This creates an issue when a team member is added to multiple round-robin calendars because they can still end up receiving far more meetings than intended in a single day. Example: A user may want to accept only 3 meetings per day total, but if they are added to 4 different round-robin calendars with a 3-meeting limit each, they could potentially receive up to 12 meetings in one day. Suggested Feature: Add a user-level or profile-level setting such as: “Maximum total meetings per day across all assigned calendars” This would help agencies, sales teams, coaches, and service providers better manage workloads and avoid overbooking while still using multiple round-robin calendars for different funnels, services, or departments. This feature would be especially valuable for: Coaches and consultants Sales teams Multi-service businesses Agencies managing multiple pipelines/calendars Teams using round-robin distribution heavily A global booking cap would make calendar management significantly more flexible and practical for real-world workflows.

Problem: There is no way to filter contacts by which service they have booked in the Contacts view in Services V2. The only place you can filter by service is in the Calendar list view, but that view does not support bulk actions like adding tags, updating fields, or enrolling in workflows. This means if you want to take action on all contacts who booked a specific service (e.g., tag them, update a field, send a campaign), there is no native way to do it. Requested solution: Add "Booked Service" and "Service Category" as filter options in the Contacts view and in Smart Lists Allow bulk actions (add tag, update field, enroll in workflow) from the Calendar list view

It would be very helpful for us if there will be an option to lock the time zone in the booking widget, its because the appointment time zone field does not really guarantee the right term for each time zone so we hard coded it to Philippine Time, because when leads booked an appointment using Ph time it shows in the email confirmation as PHT.

There is currently no way to put a service "on sale" in Services V2 and have the original price and the sale price both visible to customers on the booking page. The only way to offer a discount is through coupon codes, which require the customer to know the code, type it in, and apply it at checkout. This means if a detailing shop, med spa, salon, cleaning company, or any service business wants to run a Black Friday sale, a slow- week flash promotion, or a seasonal discount on a specific service, they have two bad options: Change the actual service price to the sale price. The customer sees the lower number but has no idea it is a deal. There is no strikethrough, no "was $199, now $149," no urgency. The original price disappears entirely, and when the sale ends the business has to remember to manually change it back. If they forget, they are undercharging every customer who books after the promotion. Create a coupon code and tell customers to use it. This adds friction to the booking flow — the customer has to find the code, remember it, and type it into a separate field. Every extra step in a booking flow reduces conversion. And for a public sale where every customer gets the discount, requiring a code makes no sense. Nobody hands a coupon to every person who walks into the store and then makes them read it back at the register. What we need: Add a native Sale Price field to each service in Services V2. When the business enters a sale price, the booking page automatically displays both the original price and the sale price — with the original price shown as a strikethrough and the sale price highlighted as the current amount. The customer sees: ~~$199~~ $149 No code needed. No extra step. The discount is applied automatically to every booking made while the sale is active. How it should work: Each service gets an optional Sale Price field and an optional Sale Start Date and Sale End Date. If no dates are set, the sale runs indefinitely until the business manually removes it. If dates are set, the sale activates and deactivates automatically — no risk of forgetting to revert the price. When a sale is active, the booking page renders the original price with a strikethrough and the sale price as the current amount. This is standard e-commerce UX that every customer already understands. The original service price is never modified. It stays stored as-is. The sale price is a separate field layered on top. When the sale ends (either manually or by date), the service automatically reverts to the original price with zero action required from the business. Sale pricing should stack with coupon codes if the business wants both. If a service is on sale for $149 (down from $199) and the customer also applies a valid coupon code for 10% off, the coupon applies to the $149 sale price — resulting in $134.10. This lets businesses run public sales AND reward specific customers (referrals, VIPs, email subscribers) with an additional code-based discount on top. If the business does not want stacking, they can simply not issue coupon codes during the sale period. The sale price should be respected everywhere the service price appears: the public booking page, the New Booking screen when staff books internally, calendar confirmations, invoices, and any workflow merge fields that reference the service amount. Why this matters beyond just convenience: Strikethrough pricing is one of the most well-documented conversion drivers in retail and e-commerce. Showing what the price was next to what the price is now creates anchoring — the customer perceives the deal relative to the original value, not in isolation. A service at $149 feels different when it is sitting next to a crossed-out $199 than when it is just listed at $149 with no context. Right now, every e-commerce platform (Shopify, WooCommerce, Square, Stripe) supports native sale pricing with strikethrough display. Services V2 is GHL's commerce engine for service businesses, but it is missing this basic merchandising capability. Adding it would bring Services V2 to parity with what every product-based commerce platform already offers and unlock seasonal promotions, flash sales, and strategic discounting for the thousands of service businesses on GHL — without adding friction to the booking flow.