Submitted referrals

docs.json

@@ -175,7 +175,8 @@
                 "pages": [
                   "help/article/email-campaigns",
                   "help/article/messaging-partners",
-                  "help/article/program-bounties"
+                  "help/article/program-bounties",
+                  "help/article/submitted-referrals"
                 ]
               },
               {

help/article/submitted-referrals.mdx

@@ -0,0 +1,151 @@
+---
+title: "Managing submitted referrals"
+description: "Learn how to review and manage submitted referrals in Dub."
+sidebarTitle: "Submitted referrals"
+---
+
+<Tip>
+  This feature is only available on [Business plans and
+  above](https://dub.co/pricing/partners).
+</Tip>
+
+Submitted referrals let partners manually submit prospective customers to your program, even when the referral did not come through a tracked partner link.
+
+<Frame>
+  <img
+    src="/images/dub-partners/customer-submitted-dash.png"
+    alt="Submitted referrals dashboard view"
+  />
+</Frame>
+
+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 referral record, not an attributed lead event, and only become a lead or sale in Dub when you update their status. This makes submitted referrals useful for sales-assisted workflows where partners introduce prospects before a tracked signup or purchase happens.
+
+## Creating rewards for submitted referrals
+
+To create or update referral 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 referrals that reach `Qualified` status
+- **Sale rewards** for referrals 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 referral`. If this customer reaches **Qualified**, the partner then earns a reward.
+
+<Frame>
+  <img
+    src="/images/dub-partners/create-lead-submitted-referral.png"
+    alt="Create lead submitted referral"
+  />
+</Frame>
+
+### Sale reward
+
+Open the sale reward editor, and add a condition to pay out when the customer source is `closed won deal`. This will create the customer record, and the partner will be rewarded.
+
+<Frame>
+  <img
+    src="/images/dub-partners/create-sale-submitted-referral.png"
+    alt="Create sale submitted referral"
+  />
+</Frame>
+
+
+## Managing submitted referrals
+
+To view all submitted referrals, go to **Customers** in your Partner Program navigation, then click the **Partner Referrals** tab.
+
+<Frame>
+  <img
+    src="/images/dub-partners/customer-submitted-tab.png"
+    alt="Submitted referrals tab view"
+  />
+</Frame>
+
+This view shows all partner-submitted referrals in one table, including:
+
+- Lead email
+- Company
+- Submitting partner
+- Submitted date
+- [Current status](#referral-statuses)
+
+Click any row to open the referral details panel and review the submission more closely.
+
+If you want to review converted customers after a referral has been qualified or closed won, see [Customer insights](/help/article/customer-insights).
+
+## Reviewing submitted referrals
+
+When you click a referral row in the **Partner Referrals** table, a drawer view opens with the full referral record.
+
+<Frame>
+  <img
+    src="/images/dub-partners/submitted-referral-drawer.png"
+    alt="Submitted referrals drawer view"
+  />
+</Frame>
+
+This drawer is designed for quickly reviewing the submission, updating the referral 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.
+
+## Changing 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.
+
+<Frame>
+  <img
+    src="/images/dub-partners/submitted-referral-drawer-save.png"
+    alt="Submitted referrals drawer save"
+  />
+</Frame>
+
+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.
+
+<Frame>
+  <img
+    src="/images/dub-partners/referral-status-qualified.png"
+    alt="Status change modal qualified"
+  />
+</Frame>
+
+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.
+
+<Frame>
+  <img
+    src="/images/dub-partners/referral-status-closedwon.png"
+    alt="Status change modal closed won"
+  />
+</Frame>
+
+When changing to `closed won`, this creates a sale record.
+
+## Referral statuses
+
+Submitted referrals move through a simple pipeline inside Dub:
+
+| Status | What it means |
+| --- | --- |
+| **New** | The referral was submitted and has not been reviewed yet. |
+| **Qualified** | The referral is valid and worth pursuing. This also creates a lead event. |
+| **Meeting** | The referred prospect has progressed to a meeting stage. |
+| **Negotiation** | The referred prospect is in an active deal cycle. |
+| **Unqualified** | The referral is not a fit and will not move forward. |
+| **Closed won** | The referral became a customer. This also creates a sale record. |
+| **Closed lost** | The opportunity did not convert. |
+
+### Status rules
+
+- All referrals start in **New**
+- **Unqualified**, **Closed won**, and **Closed lost** are final states
+- You can move referrals forward or backward between **Qualified**, **Meeting**, and **Negotiation**
+- A referral must have an associated customer before it can be moved to **Closed won**
+
+In practice, that means you should typically mark a submitted referral as **Qualified** before marking it as **Closed won**.