--- title: Pipeline Engine — native sales pipelines and stages for your leads description: A friendly guide to the Pipeline Engine. Group your lead statuses into one or more pipelines, give each stage a canonical group, switch it on gradually (Off → Shadow → Hybrid → Canonical), pick a pipeline on the leads Kanban, and read a per-stage funnel with win rate — all built on top of your existing lead statuses, with nothing changed until you turn it on. product: TSync Intelligence 11.3.6 language: en canonical: https://docs.tsync.pro/modules/tsync-pipeline-engine/ source: https://docs.tsync.pro/llms.txt --- # 🪜 Pipeline Engine The **Pipeline Engine** turns your lead statuses into proper **sales pipelines** with **stages** — so you can see where every deal is, group stages by meaning (new, offer, won, lost…), and read a simple funnel with a win rate. It is built **on top of your existing lead statuses** — a "stage" is just a lead status that belongs to a pipeline. Nothing is replaced, and **nothing changes for your team until you decide to turn it on**. Open it from **Configuration Center → Integrations → Pipelines (sales stages)**, or go directly to `/admin/tsync_pipeline_engine`. --- ## How it switches on — the four modes At the top of the console you choose an **adoption mode**. Start at **Shadow** and move up only when you are ready. | Mode | What your team sees | Use it when | |------|---------------------|-------------| | **Off** | Nothing. Works exactly like before. | You are not using pipelines yet. | | **Shadow** *(default)* | Nothing visible. The pipeline is built quietly in the background. | You want to set things up and check them first — **recommended at first**. | | **Hybrid** | The pipeline becomes visible: a **pipeline selector on the leads Kanban**, and automations can use stages. Old statuses still work. | Most live installations. | | **Canonical** | The pipeline is the main way you work the deals. | Mature setups that run everything through stages. | > In **Off** and **Shadow** the leads screen is **completely unchanged**. The selector and automations only appear in **Hybrid** or **Canonical**. --- ## Pipelines and stages - A **pipeline** is a named flow, e.g. *Default Sales Pipeline* or *Support*. You can have **several**, one of them marked **Default**. - A **stage** is one step in a pipeline — and it is simply one of your **lead statuses** (New, Contacted, Offer, Won, Lost…). - Each stage can carry a **canonical group** — a standard label (new, contacted, offer, won, lost, …) that lets reports and automations understand the stage no matter what you named it. - A stage can be marked **terminal** (won / lost / cancelled / archived) — the end of the road for a deal. When you first open the module, a **Default Sales Pipeline** is created automatically from your existing statuses, and TSync makes a best guess at each canonical group (won/lost are detected and flagged terminal). You can adjust everything. ### Create or rename a pipeline On the **Pipelines** card, click **New pipeline** (or **Edit** next to a pipeline's name). Use **Set default** to choose which pipeline new leads belong to. ### Edit a stage Click **Edit** on any stage row to set its **canonical group**, mark it **terminal** (and pick won/lost/cancelled/archived), move it to a different pipeline, or choose its **Kanban ordering**. ### Card ordering, per stage Each stage can have its own rule for how its cards are ordered on the leads board. It sits in the same **Edit** dialog, under **Kanban ordering**: | Choice | When to use it | |---|---| | **Inherit (newest first)** | The default. The stage follows the install-wide setting; if that isn't set either, cards sit **newest first**. | | **Date created** | Intake columns — a fresh lead shows up at the top of the list instead of buried among older ones. | | **Last contact** | Columns where what matters is who has waited longest: pick **ascending** and the most neglected lead rises to the top. | | **Lead value** | Quoting and negotiation columns, so the big opportunities come first. | | **Name** / **Company** | When you simply want an alphabetical list. | | **Manual (Kanban order)** | Keeps the order you dragged the cards into by hand. | You also pick the **direction** — ascending or descending — next to the column. The rule is **per stage**, not per board: "New lead" can be ordered by date while "Measurements" is ordered by last contact. Stages left on *Inherit* behave exactly as before. > If a new lead used to appear somewhere down the column instead of at the top, that was an install with no ordering rule set at all. Now, even with nothing chosen, cards sit newest first. > Tip: pressing **Regenerate default pipeline** re-attaches any lead status that isn't in a pipeline yet. It never overwrites a value you already set. --- ### Who can see which pipeline Each pipeline can be limited to certain **roles** — for example, project managers reach the *Projects* pipeline while *Logistics* stays out of their way. Open a pipeline's **Edit** dialog and use **Roles that can access this pipeline**: - **Leave it empty** and everyone sees the pipeline. That's the default, so nothing changes until you decide otherwise. - **Pick one or more roles** and only they will see it — its leads, its board columns, its stages and its part of the dashboard all disappear for everybody else. Administrators always see every pipeline. Access follows the **role**, not the person: move someone into the role and they get it automatically. > This is a real restriction, not just a tidier menu. A denied pipeline's leads cannot be reached by searching, > by a saved filter, or by opening a lead's link directly. ## On the leads board (Hybrid and up) Once you switch to **Hybrid**, open **Leads** and switch to the **Kanban** view. A **Pipeline** selector appears next to the sort options. Pick a pipeline and the board shows only that pipeline's stages as columns. Your choice is remembered for you. --- ## Automations In **Hybrid** and up, moving a lead between stages can **trigger a workflow**. Three triggers become available in the Workflow Automation builder: - **A lead moved to a different stage** (carries the new stage's canonical group). - **A lead reached a Won stage.** - **A lead reached a Lost stage.** And two new workflow actions let a rule act on the pipeline: - **Move lead to stage** — moves a lead to a stage by its **canonical group** (so the rule works on any install, with no fixed numbers). - **Assign pipeline** — puts a lead on a chosen pipeline. For example: *"When a lead reaches a **Won** stage → notify the manager and create a follow-up task."* --- ## Pipeline analytics The console shows a **read-only analytics panel** for the selected pipeline: - **Leads, Open, Won, Lost** counts, and a **Win rate** (won ÷ decided). - A **funnel**: one bar per stage, sized by how many leads sit there, each tagged with its canonical group and coloured by outcome (open / won / lost). - **Stage durations** — the average time leads spend in each stage, learned from real transitions. - **Abnormally stalled leads** — a short list of deals that have sat in their current stage **longer than that stage is used to taking**. Instead of a fixed "older than 14 days" rule, each stage learns its own typical time from history (average plus a margin), so a stage that naturally takes weeks won't raise a false alarm, and a quick stage flags a stuck deal sooner. Each row shows how long the lead has waited, what's typical for that stage, and by how much it's over — so you can see *why* it was flagged and follow the link to open the lead. It is a **read-only hint** — nothing moves on its own. It is a live read of your leads — there is nothing to configure, and it fills in as leads move through the stages. (Advanced: an administrator can tune the sensitivity with the `tsync_pipeline_stalled_sigma` option — higher means only more extreme cases are flagged.) --- ## Pipeline health A small **health** panel flags anything worth fixing — for example a pipeline with no stages, a terminal stage with no won/lost type, or stages with no canonical group (which limits analytics). These are **advisory** hints, not errors; the same checks also appear in the platform's health page for administrators. --- ## Frequently asked **Will this change my leads or statuses?** No. It only **groups** your existing statuses and adds optional labels. In Off/Shadow nothing is visible at all. **Do I have to map every stage?** No — but giving stages a **canonical group** makes the funnel and automations smarter. **Can I have more than one pipeline?** Yes. Create as many as you like and mark one as the default.