Skip to content
Adoptiv

Bulk Actions

Act on the rows you have ticked, now, where every row already carries its own verdict on whether you may touch it. The ones you may not are skipped and counted rather than failing the whole attempt.

A bulk action over a partial selection

9 selected
Action
Page 1 of 115 · 100 rows a page
  • Dana WhitlowS. Bhatt
  • Ben OseiS. Bhatt
  • Priya RamanA. Kwan
  • Alan ReyesD. Whitlowskip
  • Nina KaurA. Kwan
  • Tomas IversenP. Ramanskip
  • Ruth BelloS. Bhatt
  • Ken AdachiA. Kwan
  • Grace OyelaranD. Whitlowskip
  • Marcus BellS. Bhatt
  • Aisha KhanA. Kwan
  • Tom AlvarezS. Bhatt
9 selectedclear
Reassign
Before it commits

Reassign 6 contacts? 3 will be skipped, outside your access.

What the server answered

6 contacts updated; skipped 3 outside your access.

Scoped per row

Every row arrives carrying what this reader may do to it, so the buttons that cannot act on anything are not offered at all.

The server does the scoping again rather than trusting the browser, so the number in the result is what the database actually changed. Where the two counts differ, the second one is the truth.
0
actions on the lead selection bar
0
rows in a selection by default
0
ways to undo one afterwards

Product figures from the platform’s own defaults - not customer averages

The mechanism

How it works.

01

The selection is the page in front of you

Ticking rows works on what is loaded, a hundred at a time by default. There is deliberately no select-everything-matching-this-filter, so nobody reassigns forty thousand records by ticking one box.

02

Each row arrives with its own answer

The leads list hands back, per record, whether you may edit it and whether you may delete it. The bar acts on the permitted subset and tells you the number it left alone, which is what makes a mixed selection safe to make.

03

The server does not take your word

Reassigning leads is intersected against what you are actually allowed to write, and the reply says how many it declined. Deletions are authorised again one record at a time, so the count you are shown is what really happened.

04

Export is the ticks, not the query

The file is built from the rows already in the browser, with the record identifier dropped. It is a copy of your selection, which is a different thing from an export of everything the filter matches.

Where it sits

One moment in every record.

Every record passes through the same seven. Bulk Actions is the lit one, and everything either side of it is a different page in this category.

  1. 01
    Capture

    how it arrives, and from where

  2. 02
    Shape

    the fields and stages it carries

  3. 03
    Find

    getting back to the right ones

  4. 04
    Work

    what happens against it day to day

  5. 05
    Advance

    moving it towards a decision

  6. 06
    Protect

    who may see it, and staying clean

  7. 07
    Report

    what the floor is judged on

The specifics.

8 facts
On leads
Reassign, delete, export, and enrol into a sequence if you hold workspace settings
On deals
Reassign, delete and export, judged on your profile rather than row by row
Scope
Whatever is loaded, a hundred rows by default. No select-all across pages
Per record
Edit and delete verdicts are computed server-side and travel with each lead
Mixed selections
Records beyond your reach are skipped and counted, not turned into an error
Second check
On leads the identifiers are re-tested server-side and the shortfall reported
Deletion
Immediate and permanent. There is no undo step and no archive to restore from
Trail
Editing one lead stores before and after values. Reassigning many stores nothing

More in Leads & Sales CRM

11 capabilities

The system of record the phone writes to directly - no sync job.

Deals & Pipelines

Unlimited pipelines, each with its own stages, win probability, colour and temperature. Seven seeded, and every stage change writes itself onto the deal.

Lead Stages

Create the stages your floor argues about, colour them, order them and rate them hot, warm or cold, while six fixed categories keep the reporting stable.

Lead Sources

Ten sources seeded and sealed, your own added beside them, each with a colour and a live count, and one stamped across a whole import rather than per row.

Custom Fields

Eleven field types, all of them on the picker, with options, defaults and a section of their own, on leads, deals, products and vendors. No cap on how many.

Field Groups & Layouts

Sort the fields you add into named sections with their own colour, order and table visibility, then grant or withhold a whole section per permission profile.

Bulk Import

Upload, map, review. Headers auto-map against the full field catalogue, imports stream so memory stays bounded, and a failed row never stops the run.

Duplicate Detection

Matched on normalised email then phone, at the moment a record is written, so the duplicate is caught on the way in rather than found in a report later.

Activities & Timeline

Every field change on a record with both values, beside the notes, mail, tasks and deal links against it, assembled as it happens rather than typed up later.

Touchpoints

Calls, voicemails, emails and texts merged into one chronological history per lead, attached by the number they reached, with duration and the wrap-up code.

Tasks & Reminders

Tasks with assignees, reminders, comments and templates, raised by hand or by a sequence, and the only CRM object that leaves the app to find someone.

Goals & Leaderboards

Ten measures over six windows, with attainment read from won deals and logged work the moment you open the target rather than filed by hand or overnight.

Leads & Sales CRM

See bulk actions on your own floor.

Thirty minutes, your numbers and your data. We will set bulk actions up live and you can decide from the thing itself rather than from this page.

14-day trial · no card · migration included