Docs: legacy Book Appointments capability visibility (VS-1342)#669
Open
haleyserrano wants to merge 1 commit into
Open
Docs: legacy Book Appointments capability visibility (VS-1342)#669haleyserrano wants to merge 1 commit into
haleyserrano wants to merge 1 commit into
Conversation
…ts visibility (VS-1342) The legacy Book Appointments capability card is now hidden for new users and auto-migrated Chat Receptionist users; it remains visible only for Voice Receptionist accounts with prior usage, shown with an Upgrade available badge. Updates the Chat and Voice Receptionist capability descriptions to lead with Book Multi-Service Appointment and adds a matching upgrade note to the Voice setup guide. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RJ11JUi3dtRc6HHHEMnXdJ
haleyserrano
marked this pull request as ready for review
July 21, 2026 19:09
Comment on lines
+228
to
+229
| - **Book Multi-Service Appointment** | ||
| Connect a Service Menu to let the AI help customers schedule one or more services in a single conversation. It offers available time slots, collects all necessary booking details automatically, and confirms the full session with a single message. See [Book Multi-Service Appointments with AI](../../../crm/My meetings/groups-and-service-menus.md#book-multi-service-appointments-with-ai) for setup steps. |
There was a problem hiding this comment.
The legacy capability has been replaced with two separate capabilities:
"Book Multi-Service Appointment (Chat)" for the Chat Receptionist
"Book Multi-Service Appointment (Voice)" for the Voice Receptionist
This documentation uses the unsuffixed name "Book Multi-Service Appointment".
@dpahuja-code, could you please confirm whether the description is correct?
Contributor
There was a problem hiding this comment.
The name of the capabilities are this what isac has mentioned:
"Book Multi-Service Appointment (Chat)" for the Chat Receptionist
"Book Multi-Service Appointment (Voice)" for the Voice Receptionist
@isac-vendasta can you please make changes in this PR and than merge it, it would be a help.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA
VS-1342: Hide old Book appointments capability for new users in Business App (Done)
Part of VS-1211: Deprecate "Book appointments" capability
Classification
Feature behavior change / UI change — capability card visibility rules for the AI Chat and AI Voice Receptionists.
Repo targeted
Business App only. This ticket is scoped explicitly to the Business App end-user experience (capability cards under AI → AI Workforce). No Partner Center changes are included — see "Assumptions & limitations" below.
Summary of documentation updates
Existing docs described the legacy Book Appointments capability as the default/only booking capability. Per VS-1342 (and the related, already-Done VS-1338), that's no longer accurate:
Updated three existing articles — no new pages created:
docusaurus/docs/business-app/ai/ai-workforce/ai-chat-receptionist/index.mdxdocusaurus/docs/business-app/ai/ai-workforce/ai-voice-receptionist.mddocusaurus/docs/business-app/crm/My meetings/groups-and-service-menus.mdWhether existing docs were updated or new docs created
Existing docs updated only. A new page wasn't warranted — the capability-visibility behavior is a detail of existing Chat/Voice Receptionist setup articles, not a distinct feature or workflow.
Placement reasoning
Kept the change embedded in the same capability sections that already described the old "Book Appointments" behavior, matching the existing pattern in
groups-and-service-menus.md(which already had a "may show two capabilities" note for Chat — Voice was missing the equivalent).Acceptance criteria coverage
Figma / images
None provided or used — updates were based on the JIRA description and the parent epic (VS-1211), which specify the visibility rules, badge name, and info-icon copy.
Skills used
pre-push-validation(frontmatter, callout pairing, and internal link checks confirmed clean on all three modified files)Assumptions & limitations
@ahnikakuse @haleyserrano @maryam6samadi
Generated by Claude Code