Questions, answered.

meet_ is an agent-native scheduling platform. Your AI agent looks after your calendar — protecting focus blocks, lunch and evenings, holding tier-based access so the right people get through and strangers get a polite refusal, and merging your work, personal and family calendars into one view. Humans can still book via a grid; agents book via API or MCP.

Calendly and similar tools optimise booking — sharing a link, picking a slot. meet_ optimises your week. It defends focus, lunch and evenings by default, gates access by contact tier, merges multiple calendars into one decision, and exposes the same scheduling primitives to your AI agent via API and MCP. You can still share getmeet.ai/your-namelike a Calendly link — the difference is what's behind it.

Different problem.

• Motion and Reclaim auto-schedule your own tasks and habits into the gaps in your calendar. meet_ doesn't move your to-dos around — it controls what gets in. You can use them alongside each other.
• Cal.com is open-source Calendly. Same model — human picks a slot from a grid. meet_ is built so an AI agent can negotiate on your behalf via MCP and API, and enforces tier-based access and focus blocks automatically.

Short version: Motion and Reclaim plan your time. Calendly and Cal.com share your time. meet_ defends your time and lets your agent do the talking.

Yes if you take bookings and use Google Calendar, whether you work alone or lead a team. Connect every calendar you have, set your rules and share your link. Leading a team? Book customers into your team members' diaries without seeing their calendars. Using Outlook? Leave your email on the Outlook list and we will tell you when it is ready.

Today: the getmeet.ai web dashboard works on mobile, but there's no native app yet. Coming soon: a Telegram bot — chat with your meet_ agent, get briefs and decline notifications pushed to your phone, and manage bookings without opening a browser. WhatsApp, iMessage and SMS surfaces are on the longer roadmap. Want the Telegram beta when it lands? Tick Telegram on the messaging-apps question when you join the waitlist.

Yes. Sign in with Google, connect your calendar, and share your booking page or set up a team. It is free during the trial period.

meet_ is free during the trial period. Team and personal plans are published when they are set. People who joined during the alpha keep a lifetime 50% discount on personal plans.

Yes. During the trial we switch your team on in a 15-minute call. Then add your team members by email, and once each has offered a meeting type to the team you can book customers from the team page or send three options.

Open times for the meetings they offer your team, and the bookings your team made. Nothing else: no titles, no attendees, no other bookings, no rules.

Yes. They offer different meeting types to different teams. Each team sees only its own bookings.

You do. Your organisation is the controller and meet_is the processor. We can erase a customer's data on request; see the privacy policy.

Today, yes. Outlook is on the roadmap. Leave your email on the Outlook list and we will tell you when it is ready.

Yes. Every confirmation and reminder carries a link to do so. The team member and you are told.

Teams are free during the trial period. The team price per active team member is published when it is set. The team lead's seat is free.

Yes: minimum notice, buffer between meetings and meetings per day. A team member's own stricter rule still applies.

A Google account with Google Calendar (Outlook is on the roadmap). Sign in, connect your calendar and claim your handle at getmeet.ai/your-name. No other software is needed. Developers can also connect an AI agent over MCP; the developer questions further down cover that.

About 5 minutes in your browser. Sign in with Google, connect your calendar, set your rules and share your link. The four steps are at /get-set-up. Nothing to install.

Outlook (Microsoft 365) is on the roadmap. Leave your email on the Outlook list and we will tell you when it is ready. Apple Calendar comes later.

Your Google Calendar events — read and write — for the calendars you choose to connect. We see event times, durations, attendees, and IDs. To check your availability quickly, meet_ keeps a local cache of your busy blocks — each event's start and end time, the calendar it came from, and its title where your calendar exposes one — so your agent can tell you which meeting a conflict refers to. We don't store event descriptions. Attendees from your calendar history are used to build your contacts graph on the People page.

Only you, your authorised agents (using your meet_ API key), and bookers who have your booking link see anything. Bookers see availability slots — not your events, not your other calendars. Other meet_ users see nothing about your calendar by default; if both you and another meet_user opt in to mutual-availability, the system can find a slot that works for both without either of you seeing the other's events.

Yes, at any time:

• Disconnect your Google Calendar from getmeet.ai/settings
• Revoke your API key from getmeet.ai/settings?tab=keys (this immediately stops any agent or integration using it)
• Revoke meet_'s Google access from your Google account settings
• Delete your meet_ account — clears all stored data within 30 days

Yes. Every booking, reschedule and cancellation made via meet_is fully reversible from your dashboard. The agent never deletes events you created manually — only ones it created on your behalf. If you find an action you didn't expect, hit Undo and tell the agent what happened — it learns.

Two safeguards:

1. The agent operates within your stated rules (focus blocks, working hours, tier access). It can't book against those rules.
2. Anything it does is auditable in the dashboard activity feed and reversible.

If something still goes wrong, email support or book 15 min with Harry.

No. Your booking page only goes live once you choose to share getmeet.ai/your-name. Even then, tier-based access (rolling out shortly) means only contacts you've classified can book — strangers see a polite refusal and a request-to-be-added link.

meet_'s rules — focus blocks, working hours, tier access, calendar merging — are enforced 24/7 by the platform itself, not by an LLM. Your booking page applies them automatically whether you're online or not. The agent-driven bits (chat with meet_via Claude Code, the forthcoming Telegram bot, briefs and decline notifications) need an MCP-capable AI to be running. Bottom line: your calendar is protected even when you're asleep.

No. Anyone with your booking link can pick a slot — email address, name, an optional note, done. They get a Google Calendar invite like any other meeting. Only the person being booked (you) needs a meet_ account.

Yes. By default every booking gets a Google Meet link added automatically on event creation — no extra step, no plugin. If you run meetings on Zoom, set a meeting type's Video to Zoom and add your own Zoom link: bookings then carry that link and no Meet link. Microsoft Teams isn't supported yet; if you live in Teams, tell us on the waitlist, which is how we prioritise integrations.

Yes. Get an API key from getmeet.ai/settings?tab=keys. The v1 API covers calendar read/write, bookings, availability, contacts and event types. Auth is Authorization: Bearer mk_.... Full reference at getmeet.ai/dashboard/help.

Yes. Set it up from /get-set-up/claude-code. Running npx getmeet registers the meet_ MCP server with Claude Code. Tools cover schedule, book, propose meetings, check availability, find time, look up contacts and team times. Run /meet help in Claude Code for the full list.

You do not need it. The browser setup at /get-set-up covers sign in, calendar, rules and your link. If you want the agent in your terminal, install Claude Code from claude.ai/code and follow /get-set-up/claude-code.

Yes, at the protocol level. meet_'s MCP server is HTTP-based and Claude Desktop supports remote MCP servers through its mcp.json config. Today that is a manual setup: add the server URL and your API key. The steps are on /get-set-up/claude-code. Email us if you get stuck.

Yes — anything that supports either MCP or REST API tool calling. The API is provider-neutral. Direct OpenAI / Gemini / Ollama integration is on the roadmap as native one-click installs; today it's a few minutes of wiring.