Your integrations fall in two kinds. Some carry each request to where your team works; your customer never sees them. The others are buttons your customer gets in the card, at the moment they are useful.
Buttons in the card
| When | What the customer sees | Set up under |
|---|---|---|
| They open your plug-in's menu | A row Reach with your WhatsApp, booking, directions, review and social media buttons | Chat, booking pages, directions and reviews, social media |
| They look at availability or open times | Or book directly: a button to your booking page, next to the times | Calendars and booking pages |
| They ask for your contact details | Your details, with the same buttons | All of the above |
| They have just sent a request | Pay online, and Message on WhatsApp with the reference filled in | Payment pages, WhatsApp |
The assistant is told which buttons you have, so it can point to the right one when a customer says they want to book, pay, message, find, review or follow you.
What happens with a request
- 1The customer fills in a short form in the card and sends it. They get a reference.
- 2The request goes at once to every place you set up: your inbox, Slack or Teams, HubSpot, Notion, Trello, Airtable, your Google Sheet, your Google Calendar, your webhook.
- 3You confirm it with the customer. Nothing is booked, held or charged in ChatGPT.
What you can measure
The Traction page of your plug-in counts how often each button is pressed and where each request was delivered. See See how your plug-in is used.
The buttons on the menu and next to availability show from plug-in version 0.7.0. If your plug-in runs an older version, press Upgrade on your plug-in page. A button leads to your own page: what happens there is in your own tool.
Last reviewed 16 November 2026