تحديث فعّال في جميع المكاتب المشتركة في منظومة ليدين بتاريخ 02.09.2026.
The morning after an advertising weekend usually looks the same: twelve new leads in the list, each one to be opened as a card, moved to another status and closed. There is now a tick box at the start of every row, and as soon as the first lead is ticked an action bar opens above the list with the number selected: “Selected: 12”.
There are three actions: “Change status”, “Assign employee” and “Archive (irrelevant)”. Before anything happens a confirmation says how many leads the change will apply to, and archiving also asks for the reason, exactly as marking a single lead irrelevant does. Up to 200 leads can be ticked at once.
The permissions are the same as for a single action: what cannot be done to one lead will not be done to it inside a batch either. Such a lead is skipped, the rest go through, and at the end a notice shows both numbers: “Done: 9 · skipped: 3”, with the reason for skipping next to it, for example “Transition unavailable” or “Employee does not cover the segment”.
- Every change is written into the access log separately, one lead at a time, just as a manual action is. A bulk action does not become a single line in the log.
- A status change inside a batch sends the quality loop event as usual: what goes to Meta on a manual action goes here as well.
- “Assign employee” is available to the office owner and to a senior member of staff, and it also offers “Remove owner”.
The ticks are cleared once the action is done and the list reloads. A lead archived by mistake is not lost: the state is reversible, and each of them can be brought back.