Documentation

Everything you need to run Closr.

Start with the quickstart, then go module by module. Every reference page describes what ships today — anything still in development is labelled.

Quickstart

From signup to first booking

01

Create the account

Sign up with email, Google, or Microsoft — the 7-day Pro trial starts with your account. No card, no payment details, and nothing charged: after seven days the trial ends and you pick a plan if you want to keep going.

02

Connect your calendar

Settings → connections. Google Calendar, Microsoft Outlook, Lark, and Zoom connect over OAuth and sync two ways.

03

Build an event type

Duration, buffers, notice period, locations, and the questions you want answered before the slot is held.

04

Share your booking link

Your handle resolves to aiclosr.ai/your-name. Share the page, link a single event type, or embed the flow on your site.

05

Connect a mailbox

Optional, but it unlocks campaigns, sequences, and email sync onto the contact timeline. Gmail or Outlook, over OAuth.

06

Turn on the AI

The note taker works from day one. The voice agent needs a knowledge base, a persona, and guardrails before it goes live.

Concepts

How the pieces relate

One contact record

Bookings, meeting notes, emails, messaging threads, and form submissions all resolve to the same contact. Nothing needs syncing between modules because there is nothing to sync.

Events drive automations

Bookings, form submissions, deal stage changes, and inbound messages publish to a shared event bus. Automations and analytics both read from it.

Draft and live knowledge

Knowledge-base documents have a draft and a live state. Agents read live at runtime, so a half-finished edit never reaches a customer. Promote when it's ready.

Plans gate features, tokens meter AI

Feature access comes from your plan; the note taker and voice agent additionally draw on a monthly AI token allowance shown in the sidebar.

Projects and organizations

Voice configuration is scoped per project, and organization accounts share one agent, one knowledge base, and one set of guardrails. Admins edit; members use.

Attendance is a field

A booking being confirmed and a meeting being held are different states. Analytics count the second one, resolved from evidence after the meeting.

Build on Closr

Embeds, webhooks, and API keys

Three supported ways to connect Closr to something you own.

Embed

The site snippet

One script on your site covers visitor tracking, click capture, and form embeds. Copy it from the growth page; it is scoped to your portal so multi-site accounts stay separated.

Embed

The AI chat widget

A second script puts an AI support chat on any site, answering from the knowledge base of whichever AI project you point it at, in your own colours. See the install guide for WordPress, Shopify, Webflow, GTM, and React.

Webhooks

Outbound webhooks

Automations can call an endpoint you control when an event fires, so Closr can push into systems it doesn't integrate with directly. Available on Sales and Enterprise.

API key

Voice integration

An API key lets you drive the voice agent from your own IVR or web surface instead of the built-in widget. Available on Sales and Enterprise.

Need something not covered here — a specific integration, a data export, or a rollout across several teams? Ask us directly and we will tell you honestly whether it exists yet.

Still have a question?

Support, sales, and partnerships each have their own page, and the person who answers is the one who builds this.

Replies within one business day.