# Funnel lead routing — 1.9.0

Open **Funnels → Results & domains → Lead routing** beside a saved funnel. Routing is off for existing and new funnels until an owner or administrator saves an enabled configuration. It works independently of visit measurement, on the normal public funnel URL and verified custom domains.

## Set up routing

1. Create a sales pipeline in this client workspace if needed.
2. Turn on **Route new funnel leads**, choose the pipeline, a current non-reviewer teammate for new deals, and New or Qualified as the initial stage.
3. Set the three-letter currency for new deals. New deals start with zero value; a form submission is not a purchase or verified booking.
4. Optionally enable **Create an assigned follow-up reminder** and choose a whole-minute delay from 0 (immediately) to 43,200 (30 days). The delay starts when routing creates the task, including after a manual retry.
5. Save routing. Publish the funnel, submit a consented synthetic enquiry, and check Funnel submissions, Pipelines and Follow-ups in the same workspace.

Configuration changes apply to later accepted submissions, without republishing page content. Saving an unpublished page does not expose it. Routing creates internal sales work and in-app reminders; it does not send a DM, email, SMS or AI-generated reply, and it grants no new marketing permission. Existing installation integrations retain their own configuration.

## Existing contacts and work

The server chooses the workspace from the published funnel. Visitors cannot select a pipeline, assignee or contact ID. Contacts match by normalized email within that workspace. Existing names, fields, tags and archived status remain authoritative.

One open deal in the selected pipeline is reused. Open means New, Qualified or Booked. Reuse preserves its stage, value, currency, owner, title and notes. A new follow-up uses that deal's current eligible owner. If a deal already has open follow-ups, its earliest open task is reused and keeps its title, notes, due date and owner. Closed deals and completed/cancelled tasks are never reopened. A later enquiry can create a new deal after the previous deal closes, or a new follow-up after earlier work is completed.

Every accepted enquiry records its routing outcome and configuration revision. New deals/tasks retain their originating funnel and submission IDs. Successful routing adds sales activity. Request retries do not duplicate the submission or work; concurrent repeated enquiries for the same contact/pipeline also reuse open work. Separate accepted submissions remain visible as leads.

## Routing needs attention

Invalidated settings, revoked administrator/assignee access, archived contacts and multiple open deals in the selected pipeline leave the enquiry saved and place it in **Routing needs attention**. No partial sales work is created for these expected validation failures. The queue is paginated so older issues remain available.

Fix the setting, contact, duplicate deals or existing assignee, then use **Retry routing** as a workspace owner/admin. Retries use current saved settings and recheck permissions and references. A funnel must be published and routing enabled. Already-routed requests are safe to retry without creating more work. Routing retries do not create new leads or analytics conversions. Leads captured while routing was off, and pre-update leads, are not automatically backfilled.

Agents can read settings, outcomes and the queue. Only current owners/admins can enable, change or retry routing. If the administrator who enabled routing loses that role, another current administrator must save the settings again. Stale configuration saves require an explicit reload rather than overwriting someone else's settings.

## Verification scope

Backend acceptance uses Convex fixtures for permissions, concurrent submissions, reference removal, manual edits, closed work, review pagination/retries, immediate/delayed reminders and opt-in behavior. Browser acceptance uses synthetic hooks for configuration, stale-save recovery, role controls and desktop/phone layouts. These tests do not certify a buyer's live deployment or send customer messages.