Skip to Content
Author's profile photo Natalia Goyenechea

Those annoying Out of Office emails! Automatic email responses that updateTickets in Hybris Service Cloud – Employee Central Service Center

When enabling email-to-ticket functionality in Hybris Service cloud, a small but still very important setting is often overlooked: How to prevent automatic email responses from customers, or employees (in the Employee Support scenarios) to update tickets or worse, re-open completed tickets.

The Problem: The service agent replied via email to a Customer support ticket (Customer support or Employee support is the same in this case) and set the ticket status to Completed, but the recipient was out of the office and their inbox is sending automatic replies. The Out of Office reply is received by the support email address, then automatically forwarded to the C4C Technical address, where it will update the referenced ticket by saving a new ‘Last customer interaction’ date/time, adding a check in the ‘Customer updated’ checkbox and also setting the status back to in process.

The Solution: First make sure you are familiar with Email Response Management in C4C, this series of fantastic Blogs from the Cloud for Service Expert Corner will explain everything you need to know to configure the email-to-ticket process for Hybris Customer Service and Employee Central Service Center scenarios.

(For a complete overview of the blog posts in the Cloud for Service Expert Corner, you can start here:  Introducing the C4C Service Expert Corner Blog Series. )

The basics come down to these simple steps:

  1. Decide which email support addresses will be exposed to end customers (or employees).  There is no limit on the number of channels which can be exposed.
  2. Review the 3 possible email-to-ticket flows, and decide which one to use for each support channel (based on the master data involved).  It is quite common to use the same flow for all support channels.
  3. In the C4C tenant, enable the flows (in Scoping) and configure the channels (under Administrator).
  4. In the company’s mail server, configure email forwarding from each support channel to the technical address exposed by the C4C tenant.

In this last step, when setting up the forwarding rule in the company’s mail server an exception can be made to exclude automatic replies.


Process example in and Employee Support scenario:


This way all of the Out of Office automatic responses sent by employees or customers won’t impact the Hybris Customer Service solution.

I hope this was helpful!



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Jameel Qureshi
      Jameel Qureshi


      Fanstastic blog Natalia 🙂

      Author's profile photo Former Member
      Former Member

      You have to full of knowledge about email, If you are part of a support team then you have to full of the knowledge of that domain in whiv=ch you are support member, If we talk about Rediffmail server it is the best email server, Where you are connected with Rediffmail Customer Service team that is always available for you on call as well.

      Author's profile photo Former Member
      Former Member

      Hi Natalia

      This is for some customers not a correct way to prevent ticket creation via Out of Office emails. As agent you want to know if you contact is on holiday or sick leave. So basically C4C should only allow an Out of Office one time to inform the agent and then the Out of Office mails should not create any tickets.

      Kind regards, Daan

      Author's profile photo Ronald van Beurden
      Ronald van Beurden

      Hi Natalia,

      Great blog! I do notice however that this Outlook rule is not working in all scenarios. When sending an automatic reply from GMAIL as an example, it is not recognized in Outlook as such.

      From the headers GMAIL adds Auto-Submitted: auto-replied, where Outlook adds Auto-Submitted: auto-generated. It seems the rule only acts on the latter.

      Do you have any recommendation to solve this?

      Thanks, Ronald