Schedule, customers, reminders — booking as a first-class app. Slots become rows in Tables; confirmations go out over Mail and Connect. Everything AI can already reason about, plus a public booking page for your customers. Ships within a week.
Calendly, Cal.com, SavvyCal — all of them live outside your customer database. Bookings sync back to your CRM via a brittle Zapier chain. Reminders go out from the booking tool, not from your mail server. The AI running your business can't see any of it.
Each Slot is a row on the same substrate as your Customers. Public booking pages render from a Tables view. Reminders go out over the same Mail server that already knows your DKIM keys. Confirmations post to Connect. The AI reasons about the whole graph.
Slot rows link to Customer rows automatically. New booking = new row on Deals with the AI-suggested next step already in the assignee column.
Any Tables view can front a public booking page — same public-form primitive Tables already ships. Bookings drop as rows.
Reminder emails go out from your DKIM-signed Mail server, not from a booking vendor's relay. Deliverability follows your domain.
New bookings post to the channel of your choice. AI workers can react — pre-brief the assignee, prep a doc, block prep time in the calendar.
Same activation model as every other Elastbiz app: pay per org, free to self-host under Elastic License 2.0. Waitlist orgs get the first 6 months at Team tier for free.
Get the launch alert and we'll email you the moment TapSlot is live. Slot rows on your Tables substrate, booking pages public, reminders on your DKIM.