function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
vikashlohiavikashlohia 

email to case - through the email agent

Hi,

I have a requirement to configure email to agent but the client doesnt want to set a forwarding rule from *@company.com to *@salesforce.com. Hence looks like the email to agent (using the email agent) may be the right chcoice. I am trying to make sure that the forwarding rule will not be needed. The documentation doesnt mention that the forwarding rule is needed. hence good so far. Still can someone please confirm I understood this correctly?

Also where I get confused is  - the tool still needs the routing address to be configures. So how will the tool know which routing address to use?

Thanks,

Vikash 

Abi DuthuAbi Duthu
Hi,

As per our understanding, your requirement is to create an routing address for creating a case. You can achive this by configuring an On demand Email to case(If you do not need to accept attachments larger than 10 MB from customers). Else go with Email to case agent.

While creating an On demand Email to case we specify an Email Id. For this salesforce itself generates routing address(service address) which has to be verified through a mail sent to the specified Email address. Once this is done, whenever we send mail to generated routing address a case will be generated in the corresponding org. 

Steps to follow setting Up On-Demand Email-to-Case
The following high-level steps outline how to set up On-Demand Email-to-Case:
1. Determine the email routing addresses that your customers can use to submit cases to your support team. Emails are automatically converted to cases based on the settings specified for each routing address.
2. Set up assignment rules, escalation rules, and auto-response rules.
3. In Salesforce.com, enable Email-to-Case and configure your email routing addresses.
You need to add a new email routing address, verify the new email routing address, and enable Email-to-Case:
Click Setup ➤ Customize ➤ Cases ➤ Email-to-Case. (More information available on top portion of this page)
4. From the Routing Addresses related list, click the ‘New’ button to create a new Routing Address. A routing address is activated after Email-to-Case is enabled.
From the Email-to-Case Settings page, you can also:
Click Edit to edit an existing routing address.
Click Del to delete an existing routing address.
Click Verify to confirm and verify the email address used in an existing routing address. A verification email is immediately sent to the new routing address, which includes a link, that when clicked, completes the verification process.
5. Enter the routing address settings and click on Save.
6. Check the inbox for that Routing Address to verify the email address
7. Add email related list to Case page layouts. Click Setup ➤ Customize ➤ Cases ➤ Page Layout and select a page layout and click on Edit. On top, click on ‘Relates Lists’ on the left panel and drag and drop the ‘Emails’ field to the page layout and click on Save
8. Configure your email system to forward case submissions to the email services address provided to you by Salesforce.com. This step varies depending on what email client do you use. You can forward them directly from your Exchange server or setup a forwarding rule to reroute these emails.
For more information, see your email system's documentation.
9. Test your email routing addresses:
a. Manually send emails to the routing addresses.
b. Verify that the emails convert to cases based on their routing address settings.

Hope this helps you !!




vikashlohiavikashlohia
Hello,

Thanks for your response. My question is on the email to case (the one where email agent is installed). In the method, will step 8 (which you have listed above) be still needed? Hence will there be a need to set email forwarding rule? If yes, the doesnt this beat the purpose of the agent whic is suppsoed to ensure that the email stays within the company;s firewall?

Thanks,
Vikash