MetoCRM

Bulk Patient Operations

A consultant left, a campaign ended, a status was redefined — and you have thousands of records. MetoCRM makes that change in one pass, runs it in the background, and keeps it <strong>reversible</strong>.

What can be done in bulk

  • Status change — Move the selected records forward — or back — in one pass.
  • Reassignment — Hand records to another consultant or team, together with their conversations.
  • Adding tags — Stamp a shared tag on a group so later filters and automations have something to stand on.

Select what matches the filter, or pick by hand

Two ways to select. Either you tick records in the list, or you act on every record matching the current filter — the whole filter, not the page on screen.

Before the job starts, the system shows the distribution of that selection: which statuses these records are in now, and who owns them. This small screen prevents most wrong-filter accidents — you see the difference between "I selected 3,000 records" and "2,400 of those are already closed" before anything changes.

It runs in the background

Thousands of records are not processed in a browser tab. The job is split into chunks and runs behind you while you keep working. The outcome of every single record is kept — changed, skipped or failed.

That record-keeping is what makes the next section possible.

Why reversibility matters

In most CRMs a bulk operation is a one-way street: run it on the wrong filter and the previous state of thousands of records is gone, leaving you with a restore from backup.

MetoCRM can roll a bulk operation back item by item: each record's previous status, previous owner and added tag are stored, so the operation can be reversed. The rollback runs in the background too and reports its result.

The practical effect: bulk operations stop being the button nobody dares press. The team starts using them — which is where the real gain is.

Frequently asked questions

How many records can I process at once?

The job is chunked and runs in the background, so thousands of records are fine. Your screen is not locked; the operation progresses while you work and reports its result.

What if I run it on the wrong filter?

It can be rolled back. Each record's previous status, previous owner and added tag are stored, so the operation is reversible. You also see the status and assignment distribution of the selection before starting, which catches most mistakes there.

Do conversations move with a reassignment?

Yes. When ownership changes, the record's conversations move to the new owner too — otherwise the patient would sit with one consultant and the message history with another.

Do bulk changes trigger automations?

A bulk status change is a status change in the record's normal flow. So think about the flows you have attached to that status before running one — particularly automations that send messages.

Who can run bulk operations?

It depends on permissions. Because a bulk change reaches far further than an individual edit, who holds that permission is decided when the team is set up.

Related pages

Patient StatusesTagsLead DistributionBulk Data Upload

Let's clean up the pile you have

In the demo we work out which bulk correction your own records actually need.

Request a demo Our security approach

Related apps

See all →