Meeting scheduling can be an important building block of a software solution, but unfortunately it can be complicated to build. That's why we've developed the Meet.bot API in a way so you can add scheduling to any product, including your own branding. This article explains how you can do this.
Use-cases where this can make sense are for example customer engagement solutions where a conversation can lead to a meeting being booked. Think of sales automation, customer support, user engagement, and many more. Instead of leaving a conversation or relying a lengthy back-and-forth, Meet.bot can automate this step in the process. This increases conversion and provides a better customer experience.
Initial considerations
Before you start implementing, you need to consider in what way you want to include our scheduling functionality into your product. In essence, there are two ways:
You can display a user's Meet.bot scheduling page as part of your product experience and let Meet.bot handle the rest of the process. An example would be to automatically add a scheduling page link at the end of an email that is being generated, so the recipient can open the page and find a time. Or to show the embedded iframe as part of the flow the user is going through.
You can use the API to get a user's availability and then build your own UX components to show availability and book meetings. An example of this would be to provide the next 3 available slots as part of that email, which when clicked automatically book the meeting at that time.
User Configuration
The user configuration is the same in both cases, so we'll cover that first. To integrate, the user needs to have a Meet.bot account. They can create one in a few clicks by going to https://meet.bot/signup. After this, the user needs to set up an API token in the Automation menu, which they enter on your platform.
The API token is the only authentication you need. With this you can call the Get Pages endpoint to retrieve the scheduling pages the user as available, as well as the email associated with this user.
The list of pages is important because you need to allow the user to configure which scheduling page they want to use for specific workflows in your solution. Each page may have different meeting lengths and availabilities.
Showing the scheduling page
The simplest way to integrate scheduling capabilities into your product is by leveraging our existing scheduling pages. This can be done in 2 ways:
Open the scheduling page - For example in a new tab or in the previous example of the email, by adding the link in the email.
Embed the page in an iframe - You can use our embeddable iframe to load the page as part of your software. In the iframe, we don't show the scheduling page background so it's easy to keep your product experience consistent.
We recommend one of these two options as a first step, as it is a low effort way to validate that this use-case is valuable for your customers. In both cases, all you need is the page url as it gets provided by the Get Pages endpoint.
Building your own interface
If you already have a clear vision on the product experience and want to create your own interface, then there are a few more endpoints to consider:
Get Slots - This endpoint provides you with the time slots at which meetings can be booked on a given scheduling page. These are the availability slots you can share with a user. It can also provide a link that allows users to book that slot in one click.
Book Meeting - If you also want to control the booking experience, then you can use this endpoint to get the meeting scheduled.
Get Info - Gives you more information on a scheduling page, like the duration of the m meeting and how far in the future it can be booked. Typically only required in highly dynamic setups, since most of this information also comes from the Get Pages endpoint.
If we think back to the previous example of providing available slots in an email, you would use the Get Slots endpoint to get those slots. You can then decide if you'd like to use the Meet.bot direct booking link, which gets provided with that response, or if you create your own endpoint for booking where you control the full experience.
We don't have a preference for how you integrate. We offer these different options because we know different teams have different preferences and capabilities in terms of how far they want to customize.
Getting started
To get started, all you need to do is sign up for your own Meet.bot account and start developing with the endpoints mentioned above. This all works out of the box.
If you want to discuss your integration with us, send us an email at hello@meet.bot. We're always here to help.