# Leads Everyone who submits a funnel or books an appointment, in one place: status, owner, history, notes and retention. Source: https://docs.getridian.com/leads/ Language: en Reviewed: 2026-11-03 Under **Leads** you find everyone who submitted one of your [funnels](https://docs.getridian.com/funnels/) with contact details or booked an appointment. For each person you see answers, status, owner and history. ## How a lead is created - **Submission:** someone submits the contact details step of a funnel. - **Booking from a funnel:** if the funnel ends on **Book an appointment**, lead, submission and booking are created together. The lead is then **Booked**. - **Booking without a funnel:** every booking through a booking page, a single-use or package link, an embed, the API, an AI assistant or Alvin creates a lead too, for courses and groups one per booker. The source shows **Booking page** with the event type. The lead is then **Booked**. One lead per email address and workspace: if the same person submits again later, the new submission goes into the same lead's history. If the funnel does not ask for an email, every submission becomes a separate lead, without merging. If the name is missing, the list and detail show the email or phone. ## Status The statuses are fixed: **New**, **Contacted**, **Qualified**, **Booked**, **Customer** and **Lost**. New leads start as **New**. A booking sets **Booked** if the lead was New, Contacted or Qualified before. Everything else is changed by you, a team member or Alvin. If the booking is rescheduled, the history shows "Booking rescheduled" with the old and new time. If the booking is cancelled, the history shows "Booking cancelled". The status falls back to what it was before the booking, unless someone changed it by hand in the meantime. ## History and notes The history shows each submission with questions and answers, the path through the funnel and the outcome. Custom fields from the contact block appear in the detail; if someone submits again, the newest value per field applies. It also shows bookings with time, tier and a link to the booking, status changes and notes. All workspace members see notes. ## Owner For team event types, the lead gets an owner: for Round Robin the assigned host, for Collective the first host. An existing owner stays, even if a later booking goes to someone else. In the lead detail, change the owner under **Owner** or set it to nobody. **My leads** above the list shows only leads you own. ## Who sees leads All workspace members see all leads and can change status and notes. Admins and owners can delete them. ## Retention and deletion - We delete leads without a booking and without a note 6 months after their last activity. This period is fixed and cannot be changed. Submissions, status changes, edits and notes count as activity. The list and detail show under **Retention** when a lead will be deleted. - Leads with a booking or a note stay until someone deletes them. - **Delete lead** removes the lead with all answers, notes and history. Its bookings are anonymized: name, email, answers and cancellation reason are removed, while event type, time and status stay for your overview. Entries in the host's calendar remain. This cannot be undone. ## Search and export Search by name, email or company and filter by status or **My leads**. **Export CSV** downloads the filtered list, even if the view only shows the most recently active leads. Custom fields go into the `custom_fields` column, the owner into `owner`. The top of the list shows how many new leads per month your plan includes. Team workspaces have 5,000 new leads per month for the whole workspace. Beyond that, we still accept every lead and only show a notice. ## With Alvin and your AI assistant - **Alvin** summarizes leads, answers questions about them and drafts follow-ups, in the app and in WhatsApp. By default, Alvin changes status and notes as a proposal that you confirm. Under **Execution** in the Alvin chat you can switch to **Execute automatically**. "Set them to qualified and note …" works that way too, as one card with both changes. - **AI assistants via MCP** (Claude, ChatGPT and others) read leads and funnels and change status and notes if you allow it when connecting. Deleting is only possible in Ridian. ## For developers (team workspaces) Team workspaces have a REST API for leads and the `lead.created` webhook. You turn on access per developer project under **Developer > API projects**, **Access** tab; **Leads > API** shows the status. The project gets an app token with the scopes `leads:read` and `leads:write` via `client_credentials`; the dialog under **Leads > API** shows the exact call. - `GET /v1/funnels`: funnels with status, address and leads in the last 30 days. - `GET /v1/leads?status=&q=&limit=` (up to 100) and `GET /v1/leads/{id}` with history and answers. - `PATCH /v1/leads/{id}` with `status` and/or `note`. - `DELETE /v1/leads/{id}`. If the funnel has no email field, `email` is empty (`null`); custom fields come as `custom_fields` with `label` and `value`, in the webhook too. Leads carry `owner` (`user_id`, `name`) or `null`. `lead.created` also fires for leads from bookings without a funnel. `source` says where the lead comes from: `funnel` with `funnel` and `submission`, or `booking` with `booking` (`booking_id`, `appointment_type_id`, `appointment_type`, `start`). The other object is `null` in each case. For `waitlist` (an entry on a waitlist), all three are `null`; `waitlist.joined` reports the details. In the REST API and over MCP, leads from waitlists appear with `source.type` `appointment`. Since 2 November 2026, `funnel` and `submission` can therefore be `null`; check `source` first. Errors are returned as Problem Details. The `lead.created` webhook is signed with HMAC-SHA256 and reports only new leads, not every further submission by the same person. You set up webhooks under **Developer > Webhooks**, with a delivery log.