Handle case collision warnings and avoid duplicate customer replies

Updated Wednesday, October 28, 2026 · Marcel Gravelle

Collision indicators help you notice when another agent is viewing the same case or creating a new activity. Use that signal to coordinate who will reply, avoid duplicated investigation and keep the customer’s next commitment clear. In a complex B2B case, several people may need to collaborate at once; the goal is coordinated work with a clear owner, rather than assuming that only one person may ever open the record.

At a glance

For: agents, specialists and supervisors collaborating on the same customer case. Applies to: Supportbench Core.

Start here: Open the case → case summary and activity composer

Understand the signals you can see · Before replying on a shared case · Respond to an activity collision warning · Read newly posted work without losing your place · Example: specialist and account owner work together · Understand timing and scope limits · Troubleshoot without sending twice

Understand the signals you can see

Signal	What it means	What it does not prove
Agent is viewing this Case	A current participation signal identifies an agent viewing the case.	They have accepted ownership, read every activity or are preparing the customer response.
Agent is creating a new Activity on this Case	Another agent has a qualifying new-activity composer active.	The message has been sent, delivered or approved by the case owner.
New activity added	A newer posted activity is available than the one represented by the current view.	Your unsent draft is still appropriate without reading the new information.
No visible collision	No relevant current signal is displayed.	Nobody else can have the case open or change it; participation updates can be delayed or expire.

The case summary’s Collisions area can identify participating agents. The new-activity warning is specifically about creating an activity; it is not a universal lock protecting every case field or every edit to an existing activity. Your normal case and activity permissions still apply.

Before replying on a shared case

Open the exact case and verify Company, Contact, customer impact and current owner. Similar subjects can belong to different organizations.
Read the latest visible activity and check for a New activity added notice. Use its Refresh action when present, then read the new reply or note.
Check any viewing or new-activity indicator. If another person appears to be preparing a response, coordinate before sending your own.
Confirm whether you are sending a customer reply, recording an internal note or creating another activity type. An internal technical finding and a customer update may be complementary, but their audiences and owners should be explicit.
Review recipients and the next promised update. Being present on a case does not change the recorded case owner or customer communication responsibility.

Respond to an activity collision warning

When the composer reports that another agent is creating a new Activity, pause and identify the named colleague. Do not repeatedly press the send action.
Read the case’s latest saved activity. Contact the colleague through the appropriate internal discussion or your team’s agreed channel to establish what each person is doing.
Agree who will send the customer response and who will record the technical or internal work. If one response is sufficient, avoid creating a second message with the same purpose.
Preserve any useful unsent work through the supported draft process. A detected collision does not require discarding your investigation.
If you have coordinated the work and intentionally need to proceed, choose Ignore and continue. This acknowledges the detected collision and allows your new-activity workflow to continue; it does not stop the other agent’s work.
Review the activity type, content and recipients again, then perform the intended save/send action. Confirm the resulting activity in case history before assuming the customer has received a new message.

Use Ignore and continue deliberately

Core blocks the ordinary new-activity submission while a detected editing collision remains unacknowledged. Ignoring it is an explicit acknowledgement recorded by the system, not a transfer of ownership or a cancellation of the other person’s draft. Coordinate first, especially when both agents could send different promises to the customer.

Read newly posted work without losing your place

The New activity added notice offers Refresh to load the latest reply or note. This refreshes the activity timeline; the current Core path keeps an active composer intact. After refreshing, inspect the new evidence and revise your draft if needed. Keeping a draft intact does not mean its facts or recipients are still correct.

If the latest activity cannot be loaded, the page reports the failure and preserves the prior timeline. Retry the notice’s Refresh action when appropriate and check the result. Avoid a full browser reload as your first reaction while unsaved work is open; preserve your work and use the targeted refresh workflow.

Example: specialist and account owner work together

An account owner is preparing an update about an equipment outage while a specialist is documenting a test result on the same case. The collision warning is useful because their work overlaps in time, even though both contributions are needed.

The account owner sees the specialist’s new-activity indicator and checks whether the specialist plans an internal note or a customer reply.
They agree that the specialist will save a verified technical finding internally and the account owner will send the customer update.
After the note is posted, the account owner uses New activity added → Refresh and reads the result. They distinguish a verified test outcome from any remaining hypothesis.
The account owner revises the reply, confirms recipients and states the next action and update time. They acknowledge a remaining collision only if the coordination makes proceeding appropriate.
Both check the case history so the account has one clear customer message and a traceable internal finding. The case owner remains accountable for the next commitment.

This approach preserves useful parallel work while reducing duplicate or contradictory replies. The participation indicator helps people notice the coordination need; it does not perform the handoff or decide which response is correct.

Understand timing and scope limits

Participation is refreshed periodically while the relevant case workspace is active. Background or hidden pages can stop refreshing; older signals expire. Treat indicators as recent collaboration cues, not a complete attendance log.
An agent can have several workspaces open. The participation lifecycle does not promise a permanent list of every tab the person has opened.
The warning path for a new activity differs from editing an existing activity. Use the existing edit/save conflict messages for that workflow rather than expecting this warning to cover every concurrent edit.
A viewing indicator is not customer email tracking. It describes staff participation in the case, not a customer opening a message.
Broadcast open tracking belongs to the Broadcast workflow. Even a tracked open is an engagement signal, not proof that a person read or understood a message. Use the broadcast guide for those controls.

Troubleshoot without sending twice

Problem	Checks and corrective action
Another agent appears but says they stopped working	Participation can lag or expire after the workspace becomes inactive. Check saved case activity and coordinate directly before deciding to continue.
There is no indicator but another person replied	Absence of a signal is not an exclusive lock. Read the latest activity and clarify responsibility before sending.
The new-activity action is blocked	Read the collision warning and coordinate with the named agent. Use Ignore and continue only when intentionally proceeding.
The collision could not be ignored	Check the displayed error, session/access and connection. Do not repeatedly submit the same customer reply while the state is uncertain.
New activity cannot be loaded	Use the notice’s Refresh action again when appropriate and verify the timeline. Preserve unsaved work before broader recovery.
Two messages were sent	Inspect the actual activities and recipients. Send a clear correction only if needed, and agree ownership of the next update. Deleting or editing a record does not unsend an email already delivered.
The case owner did not change	Viewing, composing and acknowledging a collision do not assign the case. Use the authorized assignment or escalation process.
I want to know whether a customer opened a case email	Do not infer that from collision indicators. This guide covers agent collaboration; the supported broadcast tracking workflow is separate.

Was this article helpful?