Motion
Configured connection for customer scheduling workflows using Motion.
Product detail · Configured scheduling workflow
Let customers book an available appointment by text.
Let customers request and book available appointment times by text while keeping availability and booking ownership in the connected scheduling platform.
Confirmation matters: Conversational input can be incomplete or misunderstood. The workflow shows the interpreted appointment details before the booking is treated as complete.
From request to booking
Keep the conversation simple and the calendar authoritative.
The scheduling platform remains the source of availability. The text workflow translates a customer request into an availability check, an explicit choice, and a confirmed booking.
- 01
Receive the request
A customer asks for a day, time, or general window through an approved business-messaging number.
- 02
Check real availability
The workflow checks the connected scheduling platform and applies the configured appointment rules.
- 03
Offer eligible openings
The customer receives available choices that fit the interpreted request and current schedule.
- 04
Confirm the selection
The workflow repeats the appointment details and records the confirmed booking in the connected platform.
- 05
Use the fallback
Ambiguous requests, invalid responses, platform errors, and unsupported situations follow the customer-approved exception path.
Platform-flexible design
Connect the workflow to the scheduling system the business owns.
The agent is not tied to one calendar vendor. Heritage verifies each connection, maps the appointment rules, and tests the customer-specific workflow before routine use.
SimplyBook.me
Configured connection for customer scheduling workflows using SimplyBook.me.
Microsoft and Google
These connection paths are anticipated but are not represented as supported today.
CalDAV, including Zimbra
A generic CalDAV path is planned for compatible scheduling environments.
Configuration before launch
Define the rules the conversation must respect.
- An eligible registered business-messaging number and approved messaging use case
- A supported scheduling account with maintained availability and appointment rules
- Defined duration, availability, lead-time, buffer, confirmation, and fallback behavior
- Representative testing of ordinary requests, ambiguous language, unavailable times, and failures
Scheduling service pricing
Choose the number of connected schedules the workflow needs.
The scheduling tiers are monthly service charges. Configuration/setup, the required messaging foundation, scheduling-platform subscriptions, and separately scoped integration work remain separate.
Required SMS foundation10DLC + enabled number + message usage
All Heritage SMS services require the applicable $4 Brand registration, $40 Brand vetting, $40 Campaign vetting, $10/month Campaign, $2 per telephone number/month SMS enablement, and $7 per 500 messages.
Review messaging pricingConfiguration/setup charges apply separately. The selected platform, appointment rules, exception handling, and any custom integration determine that scope.
Common questions
Keep availability, automation, and exceptions distinct.
Which scheduling platforms are supported today?
Heritage currently supports configured connections to Motion and SimplyBook.me. Microsoft, Google, and generic CalDAV connections, including Zimbra, are planned and are not represented as currently available.
Does the agent invent appointment times?
No. The intended workflow checks the connected scheduling platform and offers eligible openings under the configured rules. Availability can still change or become unavailable, so the booking and exception behavior must be tested.
Can it understand requests such as “next Tuesday afternoon”?
The workflow can interpret natural-language date and time requests, but those requests can be ambiguous. It should present specific openings and confirm the selected appointment before completion.
Are rescheduling, cancellation, and reminders included?
The exact appointment actions, notification behavior, time-zone rules, and handoff paths depend on the approved configuration. This page does not represent every action as universally included.
Start with the appointment rules