31,029
edits
Module EMail Collector: Difference between revisions
Jump to navigation
Jump to search
m
→Usage
m (→Usage) Tag: 2017 source edit |
m (→Usage) Tag: 2017 source edit |
||
| Line 65: | Line 65: | ||
A test mode is available (button '''Test'''). This mode does not cause any modification of your mailbox (just reading) nor modification in Dolibarr. On the other hand, it allows you to see the different stages of the selection of qualified email, the filter and the processing of the actions that would be applied if we were not in test mode. This is an important feature to fine-tune the configuration of the collector. | A test mode is available (button '''Test'''). This mode does not cause any modification of your mailbox (just reading) nor modification in Dolibarr. On the other hand, it allows you to see the different stages of the selection of qualified email, the filter and the processing of the actions that would be applied if we were not in test mode. This is an important feature to fine-tune the configuration of the collector. | ||
== 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: | |||
- 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 | |||
Organization: My customer name | |||
Email: mycustomeremail@example.com | |||
Set the action to "Load the thirdparty by searching name/alias/email/id" with parameters | |||
name=EXTRACT:BODY:Organization:\s*([\w\-\s]+)$ | |||
email=EXTRACT:BODY:Email:\s*([\w\.\-]+@[a-zA-Z\.\-]+) | |||
If the received email has no know format, you can't reuse contnt to guess the company name. Only the sender email can be used. | |||
Then set a second action that is "Create or complete a ticket" (no parameters). | |||
So each time an email is received to support@mycompany.com, or an answer is done, the user follow@mycompany.com receive the email and the collector will use it, trying to guess if it is a input or output email and will record a help desk ticket or complete a ticket.. | |||
=Boundary Value Analysis= | =Boundary Value Analysis= | ||