Summary & Overview
In the 2026.2 (May 2026) core platform release of Mercury, the following Contact & Client Experience Improvements item was released:
| Product Improvement Number | Headline | What / Why / How Description |
| 105329 | Preserve Client Context for Activities | What: Records the client a person was associated with at the time an activity was completed, ensuring the original client context is retained. Why: Contacts can move between clients over time. Without this context, historical activities can appear disconnected or misleading. This improvement ensures recruiters can always see activity history against the correct client, even if a contact later changes employers. How: When an Email, Appointment, or Phone Call activity is completed, the system captures and stores the contact’s current client. That activity will continue to display against that client’s record, preserving accurate historical reporting and visibility. |
Clarification & Additional Information
The Product Improvment item above was to deliver functionality that explicitly links an Activity to the Client, where a Client contact was working at the time the activity was completed.
Some customers have reported that the implementation of this feature for email records, can appear as though outbound emails have been sent to an additional recipient.
What the customer sees is that the Client associated with a Client Contact record has been automatically added as a Bcc recipient on the email. This additional “recipient” is visible in both the Mercury and MercuryAdmin apps, as well as in email clients, such as Outlook and Exchange Online.
This behaviour is by design. It does not mean that the email was actually sent to the Client, although we recognise that it can appear indistinguishable from an email where that has happened.
The process that appends this additional data runs only after the email has been marked as completed. For outbound emails, this means after the email has been successfully sent by the email server. For inbound emails, it also means after the email has been received and processed by the Microsoft Power Platform (that powers Mercury).
We do this because, natively, the Microsoft Power Platform shows activities against Contacts and Client records only where those records are directly associated with the Activity, so for example, as a Sender or Recipient.
By adding the Client directly to the list of recipients, the activity remains visible against the Client record even if the underlying Client Contact later moves to a different Client.
This behaviour is being further constrained in the next version of Mercury (2026.3) and will only be invoked if the activity is marked as "As a Client Contact".
For Mercury internal reference
Related to PROB-00382 - Client records are automatically Bcc'd into Emails.