Full Sticker + Prep
- Apr 3, 2014
- First Name
This is the hard part. Getting access to appointments is one thing. Getting access to appointment capacity is another thing.
Being able to write an appointment back to the DMS is a whole other thing on top of that.
Although it's now possible with some DMS systems, it's still quite a big barrier to entry, often due to massive costs.
Before I venture into a technical framework I'm far from capable of recommending, I'll just reference that Vonage already does this for appt schedulers outside of Auto (think hair salons, yoga classes).
It's a question of who wants to own the conversation and how many systems need to talk to each other.
If the software that owns the schedule is willing to build the comms element, they can reference back to their own system. More simple than the past.
If the scheduler is separate from the conversation, the bot would need to reference an external system/database. Possible with the right connectors.
No, this is not an "integration" play. You can build the conversation/data flow yourself with natural language understanding and webhooks.
Highlighted are the pieces that would come into play for this use case.