Bulk actions on leads
How to process hundreds of leads with one action: changing status and owner, moving between projects, archiving, bulk waybills and label printing.
When there are hundreds of leads, editing them one by one is impossible. Bulk actions apply an operation to the whole selection at once: hand the no-answers over to another manager, create a hundred waybills before a shipment, archive the old rubbish.
#How it works
- 01
Filter down to the leads you need
A bulk action works with what you see. First narrow the selection with filters to the leads that genuinely need changing.
- 02
Select the leads
You can tick individual rows or the entire filtered selection — even when it does not fit on one page.
- 03
Choose the action and confirm
The system processes the leads one by one and shows a report: how many succeeded, how many failed and exactly which leads could not be changed.
#Available actions
| Action | What it does | When you need it |
|---|---|---|
| Change status | Moves every selected lead into the chosen status | Closing a batch of no-answers, pulling postponed leads back into work |
| Change manager | Assigns a different owner | An employee has left or gone on holiday and their leads must be handed over |
| Copy to project | Creates copies of the leads in another project; the originals stay | Running a repeat-sales campaign on an old base without touching the history |
| Move to project | Moves the leads; nothing stays behind | Reorganising business lines |
| Archive | Removes leads from the working space while keeping the data | Cleaning out dead leads from a year ago |
| Create waybills | Issues Nova Poshta waybills in a batch | The daily shipment from the warehouse |
| Print labels | Builds a PDF with labels for every waybill | Immediately after creating the waybills in bulk |
| Courier list | An export for handing the parcels over | Dropping off a batch of parcels |
#Bulk waybills: how not to get it wrong
The most frequently used scenario — and the one most sensitive to messy data.
- Leads with an empty city or branch will not stop the process: the rest go through, and you get a list of the problematic ones with the reason.
- The order is always the same: create the waybills first, print the labels second. Otherwise some labels will be missing.
- The label format is chosen to match your printer: compact for a thermal printer or an A4 sheet.
- Field details and error messages are covered in Nova Poshta in the CRM.
#Permissions and oversight
Bulk actions are potentially dangerous: one button can change thousands of records. That is why access to them is granted separately from ordinary editing.
- Every bulk action has its own permission. You can let an operator change statuses in bulk while forbidding archiving and exports.
- The most sensitive actions — exporting lists, printing labels, archiving, copying and moving — are written to the security log at an elevated level.
- The log shows who applied the action, when, from which address and to how many leads.
#Rules for working safely
- Check the number of leads in the selection before acting
- Test on two or three leads first, then apply to everything
- Do not move leads in bulk into a status with an SMS trigger without thinking: every customer gets a message at once
- Archive regularly and in small batches, not once a year
- Create waybills before printing labels, never the other way round
- Grant bulk permissions case by case