ScheduleOnce 5.8 is live – Tags, No-shows, and Secure booking pages

December 8, 2013 · 1 comment

We are happy to announce ScheduleOnce 5.8 with support for MeetMe page tags, No-show tracking, and secure booking pages.

MeetMe page tags: ScheduleOnce 5.7 enabled the categorization of MeetMe pages, allowing customers to use a hierarchical structure to navigate the customer interface. ScheduleOnce 5.8 further strengthens our customer interface and allows customers to filter MeetMe pages by tags.

For example, you have several team members who need to accept customer appointments in a show.  Each team member is assigned different tags according to their areas of expertise. When all team members are grouped under one booking page, customers are able to use tags to filter the team member list and only see team members that match their tag selection.

See a live example that uses both categories and tags

No-shows: It is now possible to track No-shows and get a deeper understanding of your customers’ routines. Any activity in Completed status can be changed to No-show with a single click. You can track the No-show status in all reports, allowing you to view No-show statistics by various reporting dimensions.

Secure booking pages: Https adds an extra layer of security and secures all customer interaction with your booking page. Https is already available by default when a booking page is embedded in your website. With ScheduleOnce 5.8, it is now possible to use https in your standard customer links. For example, if you have two booking pages, meetme.so/scott and booknow.so/teams, you can use https://scheduleonce.com/scott or https://scheduleonce.com/teams. You can now rest assured that all customer communication with your booking page is secure.

To learn more about this new release please see the What’s new in version 5.8 article.

As always, if you have any questions or feedback we would love to hear it. You can add a comment to this post, email us or schedule a time to speak with us.

Post by 

Previous post:

Next post: