Leads Features

Owned by Spyroulla Ioakim
Last updated: Dec 19, 2023
2 min read

LEADS

Issue Key

Summary

Description

Issue Type

Release

V5-1394

Bulk edit Leads and merge two Leads into one

Enhance Leads to provide two new options:

a) Ability to select multiple Leads and apply a bulk edit

b) Merge two separate Leads into one, retaining the relevant details

Improvement

 

V5-1290

Bulk Update for Leads

Ability to select a number of Leads from List View and perform a bulk update to change one or more details: pipeline stage, owner, expected close date. 

New Feature

Candidate Features

V5-1289

Merge Leads Feature

Ability to merge two Leads into one.

New Feature

Candidate Features

V5-1231

Leads API enhancements

Leads APIs have been revised and amended
a) Three Leads bulk edit APIs have been merged into one
b) The Lead status API has been renamed
c) Ability to track a Leads progression through a pipeline - two new APIs created

Improvement

5.4.0.0

V5-955

Create and Manage Leads

When a Lead is created, it is assigned to an Owner (user) and a Pipeline relevant to the type of business it represents. The Lead is progressed through the pipeline until it reaches the final stage, where it becomes either a Won or a Lost lead. 

Story

 

V5-904

Merge Leads

This process merges two leads into one, chooses the lead to be retained, and any details (not already specified) will be transferred from the unwanted lead before it is deleted. 

Story

 

V5-903

Bulk Edit Leads

Select and update multiple leads in one go; choose to update one or more of the following values:

  • Pipeline Stage

  • Lead Owner

  • Expected Close Date

Story

 

V5-902

Create and Manage Lead Settings

When a Lead is created, it is assigned to an Owner (user) and a Pipeline relevant to the type of business it represents. The Lead is progressed through the pipeline until it reaches the final stage, where it becomes either a Won or a Lost lead. 

Story

5.4.0.0

V5-2437

Enhancements to Leads

  1. Leads 'description' and 'notes' placeholders should be adjustable so that they are large enough to display the whole text on screen instead of 2-3 lines.

  2. Automation for Leads - trigger event 'Lead State Change' (new, in progress, won, lost)   action should be 'communicate to the system user.'

  3. Leads report

     a) Filter options: lead state (New, In Progress, Won, Lost) queue, queue stage, owner, closing date range, tags
     b) Columns: lead name, state, contact, value, queue, queue stage, owner, expected closing date, tags, custom fields (selectable)

  1. Contact screen - the ability to view the contact's leads from the activity feed

Improvement

 

V5-2263

V2 APIs - Leads to use queues and stages 

Align Leads with Orders so that they use queues instead of pipelines

Currently, Leads use:

  • Pipelines

  • Stages

  • Status  (open, won, lost)

Change to:

  • Queues

  • Stages

  • State (New, In Progress, Won, Lost)

Improvement

5.5.1.0

V5-2369

Attachments improvements 

Ability to upload attachments (links) to contacts, orders, service requests and leads

Improvement

5.6.0.5

V5-4203

Queues alignment & improvements for Orders, Service Requests, Leads

  1. Ability to provide a name (as for the ‘In Progress’ stages) for all predefined stages in a queue.

  2. Leads to additionally support ‘Won’ and ‘Lost’ stages, not just states.

  3. Service Requests queue ‘edit’ screen should copy the behaviour of the Order queue screen in ‘edit’ mode.

  4. When creating an Order queue, there should be an option to select the ‘Point of no return’, currently it can only be set when editing an existing queue. 

Improvement

5.6.8.0

Â