Core concepts

A short list of the words that recur across the dashboard, the docs, and our support replies. Read this once, then refer back when something isn't clicking.

Operator

You. The venue, caterer or planner with an Innkept account. The configurator is embedded on your website and leads land in your CRM. We never market your venue to anyone — Innkept is back-office software, not a directory.

Guest

Your customer. The person filling in the configurator, looking to book an event. They don't need an account — they just need the proposal link we send them.

Configurator (the widget)

The eight-step flow your guest sees. Mounts inside an isolated shadow DOM so it can't conflict with your site's CSS. See Anatomy of the configurator for a step-by-step.

Lead

A potential booking. Created the moment a guest hits Submit. Holds contact details, event details, and a status. Statuses move through: new → contacted → viewing booked → quoted → won (or lost).

Quote

The configured proposal: every line item, the rule adjustments, VAT, and the total. A lead can have multiple quotes if you re-quote them. See Anatomy of a quote.

Proposal page

The magic-link guest view of a quote, hosted at /p/{token}. No login. The guest can toggle optional items, leave comments, and (soon) pay a deposit. Branded with your logo and colours.

Embed

The two-line HTML snippet you paste on your site. It loads a tiny loader script which then mounts the widget into your page. See The embed snippet.

Destination

Anywhere a lead gets pushed: HubSpot, Pipedrive, Salesforce, Webhook, Zapier, Email. You can have as many destinations as your plan allows — every active destination receives every new lead in parallel.

Pricing plan

A self-contained pricing world for a venue × event-type × event-date range. Six layers (base, seasonal, day-of-week, key dates, lead-time, manual overrides) stack to give you the price for any date. You can have several active plans — when more than one matches an event, the highest priority wins. See Pricing plans.

Pricing unit

How a product or menu item scales: flat, per_guest, per_hour, or per_day. The widget multiplies by guest count or duration as appropriate.

API key

Two flavours: publishable (pk_live_… or pk_test_…) — safe to put in your HTML — and secret (sk_live_…) — server-side only, used for advanced API integrations. See Publishable vs secret keys.

Magic link

The unguessable URL we generate for each proposal. No login required. The token is 48 random characters, so a guess is statistically impossible. Whoever has the link can view the proposal — so don't post it publicly.