Our current Genesys Engage setup uses POP3 to collect emails from the email server and deliver them to Genesys for routing.

Moving to Cloud, the main option from the support documentation focuses on attaching the domain directly to to the platform.
As we share the same domain for both customer-facing addresses  (i.e. support@company.com), and the employee's email addresses (joe.bloggs@company.com), this solution doesn't appear feasible.

In our lab environment, I've used email forwarding from the email server to a purecloud.com address, which so far appears to work fine.
The issue with this setup is that the customer can see the secondary Purecloud email address in the sender's details, which is far from ideal.

Has anyone come across this scenario and found a workaround?  A subdomain has been suggested, but this would be a massive change to existing business and marketing material.

Thanks

You need to setup the DNS and MX TXT files to be able to send on behalf your corporate domain.  Here is the start of how to do that.  Use the organization's email domain name - Genesys Cloud Resource Center (mypurecloud.com)

Our current Genesys Engage setup uses POP3 to collect emails from the email server and deliver them to Genesys for routing.

Moving to Cloud, the main option from the support documentation focuses on attaching the domain directly to to the platform.
As we share the same domain for both customer-facing addresses  (i.e. support@company.com), and the employee's email addresses (joe.bloggs@company.com), this solution doesn't appear feasible.

In our lab environment, I've used email forwarding from the email server to a purecloud.com address, which so far appears to work fine.
The issue with this setup is that the customer can see the secondary Purecloud email address in the sender's details, which is far from ideal.

Has anyone come across this scenario and found a workaround?  A subdomain has been suggested, but this would be a massive change to existing business and marketing material.

Thanks

Hi Robert,

Thanks for the reply.

For replies, yes I have that working.

It's our inbound emails I'm trying to find a solution to, without bringing everything to Genesys Cloud.

Paul

You need to setup the DNS and MX TXT files to be able to send on behalf your corporate domain.  Here is the start of how to do that.  Use the organization's email domain name - Genesys Cloud Resource Center (mypurecloud.com)

Our current Genesys Engage setup uses POP3 to collect emails from the email server and deliver them to Genesys for routing.

Moving to Cloud, the main option from the support documentation focuses on attaching the domain directly to to the platform.
As we share the same domain for both customer-facing addresses  (i.e. support@company.com), and the employee's email addresses (joe.bloggs@company.com), this solution doesn't appear feasible.

In our lab environment, I've used email forwarding from the email server to a purecloud.com address, which so far appears to work fine.
The issue with this setup is that the customer can see the secondary Purecloud email address in the sender's details, which is far from ideal.

Has anyone come across this scenario and found a workaround?  A subdomain has been suggested, but this would be a massive change to existing business and marketing material.

Thanks

In your Email server, you forward the @company.com addresses to the alias you create in Genesys Cloud.  For instance, if you were in US-East, you would have:
support@company.com  forwards to support.company.mypurecloud.com
joe.bloggs@company.com forwards to joe.bloggs.company.mypurecloud.com

Now, Genesys Email is NOT designed for individual emails to agents, but queue-based email.  If you are wanting to forward personal emails, you could do that with preferred agent routing to a queue with a data table to look up the Genesys user based on the alias email.  

Hi Robert,

Thanks for the reply.

For replies, yes I have that working.

It's our inbound emails I'm trying to find a solution to, without bringing everything to Genesys Cloud.

Paul

You need to setup the DNS and MX TXT files to be able to send on behalf your corporate domain.  Here is the start of how to do that.  Use the organization's email domain name - Genesys Cloud Resource Center (mypurecloud.com)

Our current Genesys Engage setup uses POP3 to collect emails from the email server and deliver them to Genesys for routing.

Moving to Cloud, the main option from the support documentation focuses on attaching the domain directly to to the platform.
As we share the same domain for both customer-facing addresses  (i.e. support@company.com), and the employee's email addresses (joe.bloggs@company.com), this solution doesn't appear feasible.

In our lab environment, I've used email forwarding from the email server to a purecloud.com address, which so far appears to work fine.
The issue with this setup is that the customer can see the secondary Purecloud email address in the sender's details, which is far from ideal.

Has anyone come across this scenario and found a workaround?  A subdomain has been suggested, but this would be a massive change to existing business and marketing material.

Thanks

Thanks Robert,

I've had that forwarding working for testing (just the main support emails, no need for personal).

The main issue is when we send a reply we cannot use the actual inbound email address as it's not attached to Cloud.
Therefore the customer sees the MyPureCloud domain in the reply - I've seen this from other Cloud users, which doesn't look great:

What I'm thinking at the moment is a subdomain on our side for the replies, which still won't match but at least it's the company's brand.

In your Email server, you forward the @company.com addresses to the alias you create in Genesys Cloud.  For instance, if you were in US-East, you would have:
support@company.com  forwards to support.company.mypurecloud.com
joe.bloggs@company.com forwards to joe.bloggs.company.mypurecloud.com

Now, Genesys Email is NOT designed for individual emails to agents, but queue-based email.  If you are wanting to forward personal emails, you could do that with preferred agent routing to a queue with a data table to look up the Genesys user based on the alias email.  

Hi Robert,

Thanks for the reply.

For replies, yes I have that working.

It's our inbound emails I'm trying to find a solution to, without bringing everything to Genesys Cloud.

Paul

You need to setup the DNS and MX TXT files to be able to send on behalf your corporate domain.  Here is the start of how to do that.  Use the organization's email domain name - Genesys Cloud Resource Center (mypurecloud.com)

Our current Genesys Engage setup uses POP3 to collect emails from the email server and deliver them to Genesys for routing.

Moving to Cloud, the main option from the support documentation focuses on attaching the domain directly to to the platform.
As we share the same domain for both customer-facing addresses  (i.e. support@company.com), and the employee's email addresses (joe.bloggs@company.com), this solution doesn't appear feasible.

In our lab environment, I've used email forwarding from the email server to a purecloud.com address, which so far appears to work fine.
The issue with this setup is that the customer can see the secondary Purecloud email address in the sender's details, which is far from ideal.

Has anyone come across this scenario and found a workaround?  A subdomain has been suggested, but this would be a massive change to existing business and marketing material.

Thanks