innkept
Log in Start free

Your first lead

What happens the moment a guest hits Submit — and where everything ends up.

A walkthrough of what happens between Submit and the lead landing in your CRM. If something looks broken, this is the page that helps you isolate where in the pipeline it stalled.

The instant the guest clicks Submit

  1. The widget POSTs the full configuration to POST /api/widget/v1/submit with your publishable key.
  2. We validate the publishable key, the origin (if you've set an allowlist), and the GDPR consent.
  3. A Lead record is created with status new.
  4. A Quote record is created with status sent, including every selected item, every applicable pricing rule, and a freshly minted proposal token.
  5. If the guest booked a viewing, a Viewing record is attached to the lead.
  6. A queued job — PushLeadToDestinations — fires for every active integration on your company. Each push is isolated; if HubSpot is down, your webhook still delivers.
  7. The widget swaps to a confirmation screen with a link to the proposal page (/p/{token}). We don't email the guest from our side by default — the assumption is that the operator owns the relationship and will reach out from their own tools.

What you see in the dashboard

  • Dashboard home — the new lead appears in Recent leads.
  • Leads — full row with name, email, event date, guest count, status.
  • Quotes — the matched quote, ready to open with the breakdown.
  • Lead detail page — combines lead info, quote(s), viewing slot, and a free-text notes field.

What the guest sees

Their proposal at https://quote.innkept.com/p/{token} (or your custom domain on Pro+). The page shows everything they configured, with toggle controls on optional items, a comments section, and a deposit button (if you've enabled deposits).

The first time they open the proposal, the quote status flips from sent to viewed and you see a Viewed badge in the dashboard.

What's pushed to your CRM

A single canonical payload, the same shape across every connector. The HubSpot connector maps it to a Contact, the Pipedrive connector maps it to a Person, the Webhook connector forwards the raw JSON. Full reference in Webhook payload v1.

If nothing arrives

  • Open the lead in the dashboard. If it's there, the widget is fine — the issue is downstream.
  • Check Integrations. Each card shows last pushed at and the most recent error message.
  • Check the obvious: is your HubSpot token still valid? Is your webhook returning 2xx?
  • Still stuck? Troubleshooting or email hello@innkept.com.

Something missing or wrong? Tell us.

Updated regularly. UK English. No AI slop.