> ## Documentation Index > Fetch the complete documentation index at: https://dub.co/llms.txt > Use this file to discover all available pages before exploring further. # Submitted leads > Learn how to review and manage submitted leads in Dub. > [!TIP] > > This feature is only available on [Advanced plans and > above](https://dub.co/pricing). Submitted leads let partners manually submit prospective customers to your program, even when the lead did not come through a tracked partner link. ![Submitted leads dashboard view](https://mintcdn.com/dub/YZMDDkh5hoQ95qsL/images/dub-partners/customer-submitted-dash.png?fit=max\&auto=format\&n=YZMDDkh5hoQ95qsL\&q=85\&s=e77edd7af8310abbdeb52bc2201a9ee7) They are different from tracked leads since they are not created automatically by a partner link, but rather manually submitted by the partner. They start as a "submitted lead" record, and only become an attributed lead or sale in Dub when you update their status. This makes submitted leads useful for sales-assisted workflows where partners introduce prospects before a tracked signup or purchase happens. ## Creating rewards for submitted leads To create or update lead rewards, go to your program's [partner groups](/help/article/partner-groups), open the group you want to configure, and edit its rewards. This is where you create: * **Lead rewards** for leads that reach `Qualified` status * **Sale rewards** for leads that reach `Closed won` status ### Lead reward Open the lead reward editor, and add a condition to pay out when the customer source is `submitted lead`. If this customer reaches **Qualified**, the partner then earns a reward. ![Create submitted lead reward](https://mintcdn.com/dub/YZMDDkh5hoQ95qsL/images/dub-partners/create-submitted-lead-reward.png?fit=max\&auto=format\&n=YZMDDkh5hoQ95qsL\&q=85\&s=f5dfa9e860ba3067699929dfb39a4380) ### Sale reward Open the sale reward editor, and add a condition on `Customer` `Source`, and select the source that matches how your deals are closed: * **`closed won deal`**: Pay out when you mark a submitted lead as **Closed won** in Dub. This creates the customer and sale records, and the partner is rewarded. Use this if you manage the deal stage directly from the [Submitted leads](#updating-lead-statuses) page. * **`HubSpot closed won deal`**: Pay out when a deal reaches your closed won stage in HubSpot. Use this if you track your sales pipeline in HubSpot with the [HubSpot integration](/docs/integrations/hubspot#when-a-deal-is-closed-sale-event). Choosing one of these sources keeps these rewards separate from `tracked sale` rewards, which apply to sales tracked via the API or the [Stripe integration](/docs/integrations/stripe). Learn more about [sale reward conditions](/help/article/sale-rewards#customer-attributes). ![Create submitted lead sale reward](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/create-submitted-lead-sale-reward.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=a187c52bb11bc5325d0ad9b0e3a57a18) ## Managing submitted leads To view all submitted leads, go to **Submitted Leads** page in your Partner Program navigation. ![Submitted leads location](https://mintcdn.com/dub/YZMDDkh5hoQ95qsL/images/dub-partners/customer-submitted-location.png?fit=max\&auto=format\&n=YZMDDkh5hoQ95qsL\&q=85\&s=ce32d65340a04bfff9b76fcbcdaa4ac6) This view will show all partner-submitted leads in one table, including: * Lead email * Company * Submitting partner * Submitted date * [Current status](#submitted-lead-statuses) Click any row to open the lead details panel and review the submission more closely. ![Submitted leads dashboard view](https://mintcdn.com/dub/YZMDDkh5hoQ95qsL/images/dub-partners/customer-submitted-dash.png?fit=max\&auto=format\&n=YZMDDkh5hoQ95qsL\&q=85\&s=e77edd7af8310abbdeb52bc2201a9ee7) If you want to review converted customers after a lead has been qualified or closed won, see [Customer insights](/help/article/customer-insights). ## Reviewing submitted leads When you click a lead row in the **Submitted leads** table, a drawer view opens with the full lead record. ![Submitted leads drawer view](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/submitted-lead-drawer.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=12626562e656ae4c775db4b192f1b588) This drawer is designed for quickly reviewing the submission, updating the lead stage, and seeing the history of changes without leaving the table. You're also able to edit the lead details by clicking the **Edit** button on the lead details card. ## Commenting on submitted leads Use comments to keep notes on a submitted lead and share updates with the partner who submitted it. In the lead drawer, click the **Comments** tab next to **Lead Details**. ![Comments tab](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/submitted-lead-select-comments.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=961e54aae99cdaacb5bc915bef19b8da) ### Choosing who can see a comment Before posting, use the visibility selector next to the **Post** button to choose who can see the comment: | Visibility | Who can see it | | - | - | | **Workspace only** | Only members of your workspace. Use this for internal notes about the lead. | | **Workspace and partner** | Your workspace and the partner who submitted the lead, in their partner dashboard. | Comments default to **Workspace only**. When **Workspace and partner** is selected, the comment input turns orange, and the posted comment shows a **Partner visible** badge so it's easy to tell apart from internal notes. ![Comment visibility](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/submitted-lead-comment-visibility.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=1e3662c302d39826bfc4e602ef353ce8) Partner can reply to a submitted lead from their partner dashboard. Their comments are always visible to your workspace and show a **Partner** badge next to their name. ![Comment types](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/submitted-lead-partner-visibility.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=d30839f84fac70fd2cb3440101727e50) ## Submitted lead statuses Submitted leads move through a simple pipeline inside Dub: | Status | What it means | | - | - | | **New** | The lead was submitted and has not been reviewed yet. | | **Qualified** | The lead is valid and worth pursuing. This also creates a lead event + reward. | | **Meeting** | The lead prospect has progressed to a meeting stage. | | **Negotiation** | The lead prospect is in an active deal cycle. | | **Unqualified** | The lead is not a fit and will not move forward. | | **Closed won** | The lead became a customer. This also creates a sale record. | | **Closed lost** | The opportunity did not convert. | * All submitted leads start in **New** * **Unqualified**, **Closed won**, and **Closed lost** are final states * You can move submitted leads forward or backward between **Qualified**, **Meeting**, and **Negotiation** * A submitted lead must have an associated customer before it can be moved to **Closed won** In practice, that means you should typically mark a submitted lead as **Qualified** before marking it as **Closed won**. ## Updating lead statuses If you select a new stage, Dub shows **Save changes** and **Cancel** actions at the bottom of the drawer before the update is finalized. ![Submitted leads drawer save](https://mintcdn.com/dub/xqXdgfAIEtSjbep9/images/dub-partners/submitted-lead-drawer-save.png?fit=max\&auto=format\&n=xqXdgfAIEtSjbep9\&q=85\&s=7c008733b9ab490ff6a361161888fc1e) For all status change updates, the partner is notified and the status change is reflected in their dashboard. You can also include optional notes for the partner with the status update. For `qualified` and `closed won` statuses, additional information may be shown or required. ### Qualified status This change will also ask for an optional external ID. ![Status change modal qualified](https://mintcdn.com/dub/-D9XED4ZG80v4PSc/images/dub-partners/submitted-lead-status-qualified.png?fit=max\&auto=format\&n=-D9XED4ZG80v4PSc\&q=85\&s=7ba049a417728246f1d23b1f80cfec7e) When changing to `qualified`, this creates a lead event. ### Closed won status This change will also ask for a required sale amount and optional Stripe customer ID. ![Status change modal closed won](https://mintcdn.com/dub/-D9XED4ZG80v4PSc/images/dub-partners/submitted-lead-status-closedwon.png?fit=max\&auto=format\&n=-D9XED4ZG80v4PSc\&q=85\&s=8013bc7a5d266fe4d7fac257689b9cbf) When changing to `closed won`, this creates a sale record. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.