Bulk Operations

Bulk Operations let you apply actions to many clients at once.

Use them to send messages, assign or remove tags, mark chats as read, or transfer chats for a filtered group of clients.

Bulk Operations Page

The Bulk Operations page shows every created bulk run.

Item Counters

Each operation shows detailed item counters.

Use these counters to understand whether the operation finished cleanly or needs review.

Create a Bulk Operation

1. Open Bulk Operations.
2. Click Create Bulk Operation.
3. Configure the Filters tab.
4. Configure the Actions tab.
5. Click Create.

Creating the record saves its filters and actions. An immediate operation must build a recipient snapshot before it can run. A scheduled operation builds and runs at the configured time.

Operation Lifecycle

The snapshot fixes the recipient set for an immediate run. If the subscription recipient limit truncates it, GChat shows a warning.

Filters

Filters define which clients will be included in the operation.

Schedule Bulk Run

Enable Schedule bulk run when the operation should run automatically at a selected local time.

When scheduling is enabled, set:

Example:

Client Creation Date

Use Created Clients At From and Created Clients At To to include only clients created during a specific date range.

Leave these fields empty if the operation should not filter by client creation date.

Last Message Date

Enable Use Last Message Date to filter clients by the date of their latest message.

Use this when you want to target clients who were recently active, inactive for a period, or last contacted during a specific time window.

Tags

Use tag filters to include or exclude clients.

Tag filters are useful for avoiding repeated outreach or targeting a specific client segment.

Integrations

Use Integrations to include clients from selected connected channels or sources.

Leave it empty if the operation can include clients from any integration.

Changing filters or actions on a scheduled operation returns it to a draft state and requires a new snapshot.

Actions

Actions define what the bulk operation will do to the filtered clients.

Click Add action to add another action. Use the delete icon to remove an action before creating the operation.

Available action types:

Send Message Action

Choose Send message when the operation should send a message to every matching client.

The message editor supports text and attachments. Use it for announcements, follow-ups, reminders, or reactivation campaigns.

Bulk message text can use message variables to personalize each message with client, chat, operator, or custom field data.

Example:

Hello {client.name}, your client ID is {client.id}.

When the operation sends the message, GChat replaces the variables separately for each matched client.

Before creating the operation, check:

1. The message text is correct.
2. Attachments are added if needed.
3. Filters match only the intended clients.
4. The operation is scheduled only if it should run later.

Recommended Workflow

1. Start with a narrow filter.
2. Review the expected client segment.
3. Add one action first.
4. Use scheduling only when timing matters.
5. Build the snapshot and check the target count before an immediate run.
6. Click Run Operation only after the audience and actions are correct.
7. After the run, check Processed, Sent, Send failed, and Skipped counters.

Best Practices

• Use tag filters to avoid sending the same message to the same clients repeatedly.
• Schedule large operations during a predictable working window.
• Keep bulk messages short and clear.
• Test a new message on a small segment before running it for a large audience.
• Review failed and skipped items after every important operation.
• Avoid combining too many actions in one operation unless the workflow is already tested.

Troubleshooting

Operation Has Send Failures

Check whether the target integration is active and whether clients can receive messages through that channel.

Operation Skipped Items

Skipped items usually mean the client did not match the final rules or the selected action could not be applied.

Wrong Clients Were Included

Review the filters, especially tags, integration, client creation dates, and last message date.

Scheduled Operation Did Not Run at the Expected Time

Check the selected run date, run time, and time zone.