Overview:

Description	Allow bulk editing of invalid lead data based on lead ID from CSV import.
Mockup	https://www.figma.com/proto/RYEKuQTupAh9gxvhQEnPSl/LEADS---Bulk-Edit?node-id=9%3A2&starting-point-node-id=9%3A2 https://www.figma.com/proto/T3I7ucj3zthqonjwxDpMVU/LEADS---Listing---Bulk-Edit-V2?node-id=504%3A2&scaling=scale-down&page-id=0%3A1&starting-point-node-id=504%3A2
Assets	https://drive.google.com/open?id=1q4U8yms4Rh0GkpU88WANOhgSWzXYJZUy&authuser=amish%40convertr.io&usp=drive_fs

Quantitative Data:

Data driven justification for ux/ui changes, especially necessary for organic changes that do not originate from client requests or roadmap features.

Link

Date Range

Item

Metric & Value

Assumption

N/A

HYPOTHESES

REASONING

Competitor Research:

Function

Findings

Image

Takeaways

EMBRACE

REJECT

TO DISCUSS

Proposal Feedback:

Stakeholder	Date	Changes
Product	11/01/22	DONE Form select dropdown (first step in dialog), needs to be able to search by form ID Mapping step, add new row to have lead ID Last step change wording from ‘edited in the background’ to 'processed in the background' Add confirmation dialog with the ‘452 LEADS’ confirmation On leads > view > notes, have a row to say what data has changed REJECTED NEED MORE INFO TO DISCUSS TO DO
Product	12/01/22	DONE CSV download template will have ‘lead id’, ‘field name', ‘field value' Mapping step to map to 3 mapping row items ‘lead id’, ‘field name', 'field value’ REJECTED ‘Form’ dropdown not required on first step, as bulk edit is not tied to campaign in any way NEED MORE INFO TO DISCUSS TO DO
Client - Future B2B	25/01/22	NO FEEDBACK
Product	25/01/22	DONE Add more text to helper card on first step to say ‘Leads will only be processed if they have a status of ‘Invalid’ and have been generated by you/your organisation.’ Done REJECTED NEED MORE INFO TO DISCUSS TO DO
Client - Cyberrisk	25/01/22	NO FEEDBACK
Client - SWZD	26/01/22	NO FEEDBACK
Client - Intentsify	27/01/22	NO FEEDBACK
Client - Oracle	31/01/22	NO FEEDBACK
Client - HP	31/01/22	NO FEEDBACK
Product	08/02/22	DONE REJECTED NEED MORE INFO TO DISCUSS TO DO V2 allows Admin, agency, call center to edit data regardless of status, e.g. They select valid data (that is undelivered, if delivered already then they have to mark as undelivered) Toggle at the end, which if turned on will reprocess data (with warning to say we recommend this before editing)
Product	28/04/22	DONE New UX similar to lead import (previous flow did made it difficult to bulk edit from an already existing lead export report) Publisher user > new button on campaign table Admin/agency/call center > button above table on leads page Dialog Step 1 - Import Form select and csv upload (same as lead import) Step 2 - Mapping No template stuff Field mapping for all fields set to ‘Do not change' as default Include ‘lead id’ field as first option with ‘lead id’ automapped Step 3 - Preview Show table preview similar to export REJECTED NEED MORE INFO TO DISCUSS TO DO
Product	03/05/22	DONE For CSV example screenshot, include Excel logo somewhere to make it extra clear that this is the file/import Done On the saving confirmation dialog messaging, change from ‘XX rows’ to ‘XX leads’ Done On campaign > admin, change toggle wording to ‘invalid lead data’, and include information about which user roles will see this Done Leads > lead profile > notes > add exact output format Done REJECTED NEED MORE INFO TO DISCUSS TO DO First step, add form dropdown Mapping step > lead id mapping to ‘id’ Add page, email that gets sent (example of deleted, valid, invalid)
Product	04/05/22	DONE Import step > added form dropdown Done Mapping step > lead id mapping to ‘id’ Done Add page > show example of email that gets sent (with example of deleted, valid, invalid lead changes) Done REJECTED NEED MORE INFO TO DISCUSS TO DO
CS Team	04/05/22	DONE REJECTED NEED MORE INFO TO DISCUSS On ‘upload’ step, remove the csv template download and change the wording to encourage the ‘lead export’ file upload journey as this will be the main use case for publisher users Maybe change wording to something like ‘For best practices on generating and uploading your CSV file’. TO DO

Retrospective:

To be completed after this features release. The retrospective should allow a basis for further improvements to this feature.

User Feedback

Stakeholder	Date	Description

Quantitative Data

Source	Link	Description	Findings
N/A	N/A	N/A	N/A

Leads - Bulk Edit Data