Skip to content

CRM 1.2.0 — Deals, deployments, inside sales

Sales CRM — Release Notes (What’s New)

Section titled “Sales CRM — Release Notes (What’s New)”

Diagrams of how inbound, companies, deals, and deployments fit together: Inside-sales flow.

| Release version | CRM 1.2.0 — “Deals, deployments, inside sales” | | Release date | 2026-08-24 | | Applies to | Leads, Deals, Deployments, Team, Journey plan, Area lists | | Availability | GA |

  • Deals (Workspace → Deals) — the commercial pipeline now lives separately from the lead. A lead answers “is this worth pursuing?”; a deal answers “how far along is the sale?”. One pharmacy can carry several deals over time, and a lead interested in two products becomes two deals that are won and lost independently.
  • Three product pipelines, each with its own stage ladder:
    • POS — Qualified → Demo → Proposal → Negotiation → Won / Lost
    • Dead-stock liquidation — Qualified → Stock data received → Valuation & offer → Offer accepted → Agreement signed → Stock lifted & settled → Won / Lost
    • Inventory financing — Qualified → Financials collected → Credit assessment → Limit approved → Agreement signed → Disbursed → Won / Lost
  • Must-have information per stage — each stage lists the fields needed to enter it, shown as a checklist on the deal before the move is attempted. Must-haves are cumulative, so stages cannot be skipped. A deal can still be marked Lost at any point with only a reason.
  • Deal line items — POS always carries its own value, including when bundled into a liquidation or financing deal. A bundled deal cannot be won without a priced POS line. Financing limits are recorded as a facility, never counted as revenue.
  • POS deployments (Workspace → Deployments) — every won deal, whichever product was sold, automatically creates a POS go-live record: Scheduled → Data migration → Installed → Training → Live → Go-live support.
  • Delivery role — a new DELIVERY user role owns deployments. Delivery users see won deals and drive go-live; they cannot move deal stages. Sales can see deployments in their own scope but cannot drive them.
  • Lead qualification on the lead menu — New, Attempting contact, Contacted, Qualified, Disqualified (with a reason). Set to Converted automatically when a deal is created.
  • Create deal on the lead menu — convert a qualified lead into a deal for one product.
  • Won and Lost stages added to both campaigns. Neither live campaign previously had them, so no lead could be closed — every deal outcome report was empty by construction.
  • Visits are now activities — each carries a type (Call, WhatsApp, Meeting, Visit, Other) and can be linked to a specific deal. Existing visits are recorded as VISIT.
  • Field-sales surfaces parked. While the team runs inside sales, Journey plan and Area lists are hidden behind NEXT_PUBLIC_FIELD_SALES_ENABLED. Nothing is deleted — journey plans, area lists, territory rules, and all visit history remain intact. Set the flag to true to bring the field motion back.
  • 80 leads were invisible to the open-deal filter. They carried a status category (ASSIGNED) that was not a valid category and not present in any campaign’s configuration, so they were silently excluded from Deal-status filters on both Leads and Reports. The stage is now configured properly and the leads are back in scope.
  • Dashboard and Reports still read the lead’s stage, not the new deal pipeline. Deal-based reporting arrives in a later release; existing reports are unchanged and continue to work.
  • Companies and Contacts now exist (licence, else phone). The same pharmacy can appear on more than one campaign as separate leads, all pointing at one company. See Inside-sales flow.