29,270
edits
Changes
m
→Example of use case: Using Emailcollector for a support center
Line 68:
Line 68:
- Declare the email support@mycompany.com as a possible sender email for each employee (but uncheck the checkbox "alias" if using Gmail). So it will be possible for every employee to send/answer emails as the sender support@mycompany.com. So if the customer answer email of any employee, the answer will be sent to support@mycompany.com (so the n employee will also receive it).+- Once this is done, it is recommended to create another email account, for exemple *follow@mycompany.com* and include it as another member of the mailing list support@mycompany.com. So follow@mycompany.com will receive any emails and answers inside the Inbox.+- Enable the module EmailCollector and the module Ticket.+- Create one EmailCollector entry with credentials (IMAP login or OAuth) of the *follow* user and Inbox as the input directory. You can set the output directoy as "Processed emails" (you must create the directory or label before the first run). As the inbox is dedicated to support@mycompany.com email, no need to set filters. +
== Example of use case: Using Emailcollector for a support center ==
== Example of use case: Using Emailcollector for a support center ==
You have a support center with n employees. The email of you support center is support@mycompany.com, that is a mailing-list that dispatch any entering email to the n employees. You must:
You have a support center with n employees. The email of you support center is support@mycompany.com, that is a mailing-list that dispatch any entering email to the n employees. You must:
−* Declare the email support@mycompany.com as a possible sender email for each employee (but uncheck the checkbox "alias" if using Gmail). So it will be possible for every employee to send/answer emails as the sender support@mycompany.com. So if the customer answer email of any employee, the answer will be sent to support@mycompany.com (so the n employee will also receive it).
−* Once this is done, it is recommended to create another email account, for exemple *follow@mycompany.com* and include it as another member of the mailing list support@mycompany.com. So follow@mycompany.com will receive any emails and answers inside the Inbox.
−* Enable the module EmailCollector and the module Ticket.
−* Create one EmailCollector entry with credentials (IMAP login or OAuth) of the *follow* user and Inbox as the input directory. You can set the output directoy as "Processed emails" (you must create the directory or label before the first run). As the inbox is dedicated to support@mycompany.com email, no need to set filters.
Imagine that the received emails are formated by a web form and content is in the body
Imagine that the received emails are formated by a web form and content is in the body
+
Organization: My customer name
Organization: My customer name
Email: mycustomeremail@example.com
Email: mycustomeremail@example.com