WhatsApp, consent and flexible calendars in HighLevel
August 25, 2026
Product updates
Chat Widget now takes colors and fonts directly from Brand Boards, and automatically keeps the existing colors in the default palette.
Existing widgets need no migration, reconfiguration or changes to the embed code. Brand colors are read-only and are managed from Brand Boards. Source: HighLevel changelog
Calendars now let you offer up to three meeting durations within a single calendar, with a default duration and availability recalculated based on the option chosen.
The change works on personal, Round Robin, collective and event calendars. Existing appointments keep their original duration even if that option is removed later. Source: HighLevel changelog
New integrations
WhatsApp lets you request the phone number from contacts who use a username, through a button in templates or an interactive message from Workflows.
The shared number is added only if no other contact has that number, and WhatsApp calls now support contacts identified by username. Source: HighLevel changelog
Compliance and phone
Chat Widget now separates the legal notice from explicit consent, with a configurable checkbox, custom text and the option to make consent required or optional.
HighLevel records in the activity whether consent was given, whether it was required and the exact text shown. Existing widgets stay unchanged until you open and save them in the builder. Source: HighLevel changelog
What to do today
Review your Chat Widgets before saving them again, especially the ones used for SMS or email consent, because saving brings the new notice and consent setup into play.
Add the contact info request to WhatsApp flows that may receive contacts identified only by username.
Consolidate duplicate calendars that differed only by duration, after validating availability, reminders and the rescheduling experience.
Set up Brand Boards in the sub-accounts where several Chat Widgets share a visual identity.