Adding CC recipients to an agent update can be automated by having them populate based on a setting in each Category's configuration under Manage >> Categories >> edit.
The first four settings can be split in two between agent updates that are added only through HappyFox, and agent updates that can be added through both HappyFox and email notifications.
These settings would auto-populate the CC email addresses when an agent update is sent only through the HappyFox application. If the agent update is sent through an email notification, only the original contact will receive it.
With this option selected, each time an agent update is being added from HappyFox, all the CC’d email IDs that were included in each email/update of the contact, will auto-populate in the agent's reply. That is, if there were two contact updates and one agent update, the next agent update will include the CC'd email IDs from both the previous contact updates.
Let’s take the below scenario as a case:
- The contact first writes in with a third-party email ID - “email@example.com” as a CC in their message.
- A agent then replies to the contact’s update directly from HappyFox, with “firstname.lastname@example.org” CC’d in their update as well.
- The contact now writes back without “email@example.com”, but with a different third-party email ID “firstname.lastname@example.org” as the only CC in their latest update.
- Now, when the agent proceeds to add their update, they will find the CC email addresses from the first and second contact updates automatically populated.
When a ticket associated with a Category that has this CC option selected, only the CC’d email address from the last contact update will automatically be populated in the next agent update.
Considering the same hypothetical scenario as above, with this option selected, an agent’s update will only choose to include the CC’d email address from the contact’s latest update.
Since “email@example.com” is the only email address CC’d in the contact’s last reply, it’ll be the only one populating in the agent's next update. Similarly, if there were any additional email address CC’d in the contact’s last reply, all of those email addresses will populate as well.
Note: This applies only for the last contact update and not for the last staff update.
HappyFox also provides the option for an agent to reply to tickets directly from the Agent Notification emails they receive. The following CC settings, let’s an agent send their update to the CC’d email IDs in a ticket, through agent email notifications.
With this setting in place, when an agent replies to a contact’s email from their email client (Outlook, Gmail, Thunderbird etc.), the update will be sent to all CC recipients that the contact had included in their emails.
Let’s have a look at how this works:
Below, you can see that the agent has received an email notification of the contact’s update. The agent proceeds to respond to the contact’s email, directly from their Gmail notification.
Note: The email addresses CC’d by the contact in their update, will not appear in the agent's email Notification. This is because they have already been captured by the CC setting in HappyFox.
As per the selected setting, the agent's reply which was added as a update from the Gmail client, has been sent to all the CC recipients that the contact had previously included.
When an agent replies to a contact from their email client with this option selected, only the CC email address from the contact’s last update will be included as a CC recipient.
In the above screenshot, the agent replied to the contact through the Gmail client, with this setting in place, and the update included only the CC recipient from the contact’s last reply.
As the title suggests, this setting is to deactivate any CC recipient auto-population, wherein none of the contact’s CC’d recipients will auto-populate in a staff’s response. This holds true to both agent updates that are added in HappyFox or through email notifications. With this setting selected, an agent would have to manually include CC recipients in their updates.