Email Media Profile

as the name suggests, it lets the administrator add an email address as a media profile after assigning to campaign, this email media profile can be used to send and receive emails to interact with the clients create email media profile when we create email media profile, then it starts fetching the emails immediately at once if no routing rule is created to add the fetched emails to a particular campaign or a particular queue, then these fetched emails will not be displayed in the system also, the rule to route the emails can be created only after creating the media profile therefore, it is suggested to create an incomplete email media profile by some steps such as provide a wrong username or password after it, create a routing rule in "rule engine" → "routing" by selecting this email media profile and select the required both queue and campaign after creating the rule, correct the issues in media profile now, the emails will be fetched and displayed in the system perform the following steps to create an email media profile click "add" to create an email media profile it shows the following pop up figure register a media profile click icon to create an email based media profile using the following pop up figure create email media profile media profile name provide a name for the new media profile user name provide the email address as the username password provide a password for the email address entered in "username" field a user can generate app specific password through its google account settings and use this app specific password as a password to its gmail account while creating an email media profile confirm password re enter the same password to confirm send from (name) provide a name of the sender all emails sent from this media profile will display this name as "sender's name" the limit of 52 characters has been applied to "send from name" field while creating or modifying an email media profile, the number of consumed character limits and the maximum character limit is displayed at the bottom of "send from name" field refer to the following screenshot if a user tries to provide more than 52 characters in "send from name" field while adding or modifying an email media profile, then it will show an error below the field that "you have exceeded the maximum character limit " send from (email address) provide a sender's email address when an agent uses this media profile to send the email, then "send from email address" will be stored and displayed as the sender's address in its ticket in "activity" prefix provide a prefix for the subjects subject preview provide the subject that will be sent with the emails sent using this profile outgoing allowed check this box to allow the sending of outgoing emails after enabling it, you have to provide the following inputs outgoing host provide the smtp address of your email provider outgoing port provide the port number for sending outgoing emails send protocol select any of the following protocols to send the emails none smtp smtps ews (exchange web services) outgoing folder provide the folder name that will store the outgoing email enable 'reply to' email check this box to provide "reply to" email address if a recipient click on reply on the received email, then the email address provided here will be the recipient after enabling it, provide the reply to email delete mail on fetch select it to delete those emails which have been fetched fetched emails will not be displayed in the system until the routing rule to direct these emails to a particular campaign and queue and the rule cannot be created until the media profile is created therefore, provide some wrong details here and create an incomplete media profile after creation of profile, create a rule in "rule engine" → "routing" the fetched emails to the particular campaign and queue and then modify this email media profile with correct details incoming allowed check this box to allow the receiving of incoming emails after enabling it, you have to provide the following inputs incoming host provide the incoming address of your email provider incoming port provide the port number for receiving the incoming emails fetch protocol select any of the following protocols to receive the emails none imap impas pop3 pop3s ews (exchange web services) incoming folder provide the folder name that will store the incoming emails fetch interval provide a value in seconds it is the time after which the system will fetch the emails from inbox of the configured media profile the default value is 10 seconds fetch for last provide the number of the last days of which emails has to be fetched here, you can perform any of the following steps click "next" to go to "ticket resolvers" page of the pop up refer to "ticket resolvers" section in this page to know which ticket resolvers have to be selected after it, you can perform any of the following steps a click "next" to go to "define signature" page of pop up refer to "signature" section of this page to know how to define the signature after it, click "submit" to save the default signature you can also click "cancel" to not save it b click "finish" to save the email media profile and to finish this process you can also click "done" to save the email media resolver protocol related information the email sender protocol such as smtp and email receiver protocols such as imap and pop, and their folders cannot be changed after creating the media profile view and modify settings of email media profile select an email media profile in the list to view its settings on the right side under "settings" tab you can modify the settings here and click "apply" to apply the same rather, you can click "refresh" to discard the changes while editing the media profile, the email sender protocol such as smtp and email receiver protocols such as imap and pop, and their folders cannot be changed if you want to change these settings, then, create the new media profile the email sender protocol such as smtp and email receiver protocols such as imap and pop, and their folders cannot be changed after creating the media profile these protocols and folders cannot be changed for the existing media profiles delete email media profile the deleted email media profile cannot be retrieved back the campaigns, queues, and users using this media profile will be disabled to use the email media profile to interact with your clients perform the following steps to delete a facebook media profile select an email media profile click "delete" to delete it it shows the following warning message click "yes" to delete the email media profile rather, you can click "no" to not delete it ticket resolver for email media profile all email media profile resolvers listed here are now improved that they will work for all email addresses available in the customer account information these ticket resolvers will also work for splitted and merged tickets this tab lets you manage how the tickets in a campaign (where the selected media profile is added) will be handled following is a screenshot for ticket resolver tab for a email media profile you can click the drop down menu titled "select ticket resolver" to select any of the following options single ticket for each customer from same source media profile select it to create a single ticket for all emails from a same source media profile it means the email coming from a same email address but to a different media profile will create a different ticket it acts quite similar to "single ticket for each customer" to create a single ticket for each customer; however, it appends the emails to a ticket after checking the media profile id suppose there are separate media profiles ids for customer care and sales team emails of the customer to the sales team will be added to a separate ticket of sales department similarly, emails to customer care will be added to the separate ticket of customer care without this resolver, all emails of the customers to both sales and customer care will be added to a single ticket only single ticket for each customer select it to create a single ticket for all emails from a customer in the campaign every new email from the same customer with same or different subject will be appended in the same ticket single ticket of same subject select it to create a single ticket for all emails having same subject all emails having same subject from same or different customers will be added into the same ticket single ticket of same subject from same customer select it to create a single ticket for all emails having same subject sent from the same customer case id based resolver a case is created for a new email all emails replied on this email thread, then these will be appended to the same ticket if a new email thread is created, a new ticket will be created single ticket with same subject from observer select it to create a single ticket of all emails having same subject from the observer who is in cc of an email received from a customer subject media profile customer interaction resolver select it to create a single ticket for all emails having same subject from the same customer for the same media profile a new ticket will be created only when the customer sends an email with another subject to same media profile or connect with other media profiles with same or another subject when you select a resolver, it gets added in the list the added ticket resolvers will be removed from the drop down menu after adding mutliple resolvers, you can move them to up or down to specify their priority see the following screenshot signature this tab will be visible only for email media profile this tab lets administrator to specify the signature for all emails that will be sent using this email media profile here, perform the following steps to create an email signature click "insert this signature before quoted text in replies" to insert the signature before the quoted text keep it uncheck if you want to insert the signatures after the quoted text you can type the signature in the textarea and use the available tools to format the text, add a hyperlink, and insert an image click "insert placeholder" to insert the dynamic placeholders from the following dialog box after creating the signature, click "apply" to apply the same now, the created signature will be displayed on all emails being sent through the selected email media profile failure mail configuration the administrator can configure failure mail settings for the email media profile when the mail id of the customer is wrong, then the mail sent to the customer is considered as failure mail the failure mail can only be configured for “customer based resolver ” if the resolver is “case id based” then a new ticket will be created for the same failure mail the failure email will get the escalation mark on the dashboard screen of the agent the agent can reply on the same ticket, and hence the ticket will handled execute the following command to login to the database psql u postgres ameyodb execute the following query for the gmail based email profile insert into ic configuration parameter (contact center id,name,value) values (\<contact center id>,'failuremailconfiguration','mailer daemon\@googlemail com'); execute the following query for the yahoo based email profile insert into ic configuration parameter (contact center id,name,value) values ('\<contact center id>','failuremailconfiguration','mailer daemon\@yahoomail com'); mapping incoming and outgoing media profile the administrator can map any incoming media profile with some other outgoing media profile example let’s assume there are two media profiles named as m1 and m2 if a ticket is coming from media profile m1, then the administrator can map the media profile m1 with m2, which means if ticket is coming from m1, then while answering on the same ticket, the media profile m2 will select automatically execute the following query to map the incoming media profile with another outgoing media profile insert into ic configuration parameter (contact center id,name,value) values ('\<contact center id>','mediaprofilemapping','{"\<incoming media profile id>" "\<outgoing media profile id>"}'); in the above query, the incoming media profile id is the id of the incoming media profile and outgoing media profile id is the id of the outgoing media profile id with the help of the above query, you can define multiple mappings for multiple set of media profiles if do not have the media profile id, then run the following query and copy the respective media profile id select from media profile; handling the email server error messages and retry sending policies in ameyo ameyo introduces the handling to manage the error messages thrown by the email provider server of an email address and the following four different policies have been introduced to handle such error messages default retry select it to retry sending the email just after the failure it's configuration code is "default entry" "maxretrycount" variable is used to define its value and its default value is 3 rate limit retry select it to retry sending the email when retry rate limits of the server are breached by default, the retry is tried to be attempted after 24 hours it's configuration code is "rate limit retry" "ratelimitretrytime" variable is used to define its value and its default value is 86,400 seconds (that is 24 hours) progressive retry select it to attempt the retry in the progressive intervals such as every 5 minutes, 10 minutes, 15 minutes, and 20 minutes it's configuration code is "progressive retry" "progressiveretryinterval" variable is used to define its value and its default value is 300 seconds (that is 5 minutes) no retry there are some error messages for which the retry sending should not be tried again it's configuration code is "no retry" these policies come preconfigured in ameyo and apply automatically upon detecting their relevant error codes for example, the following table illustrates the gmail error codes and the corresponding ameyo email error handling policy for them gmail error codes ameyo email error handling policy unidentified error default retry addressing error no retry mailbox error progressive retry mail system error progressive retry network routing error rate limit retry mail delivery protocol error no retry message content error no retry security policy error progressive retry no such provider no retry connection error progressive retry unknown host no retry internal error no retry working of policies with default configuration the following will be the result of applying the default configuration using the above policies all the errors corresponding to "default retry" policy should get retried immediately all the errors corresponding to "no retry" policy will not get retired all the errors corresponding to "rate limit retry" policy should get retried after 24 hours all the errors corresponding to "progressive retry" policy should get retried at intervals of 30 minutes, 1 hour, and 1 5 hours same can be verified from "s message send info" and "failed message send info" working of policies with customized configuration perform the following steps run the following query to customize the configuration insert into media profile configuration(media profile id, contact center id, media profile type, media profile properties) values ('\<media profile id>,\<contact center id>,'email', '{"maxretrycount" "3", "ratelimitretrytime" "86400", "progressiveretryinterval" "300"}') refer to the following table to know the definition of variables and their default value variable definition default value linked policy maxretrycount is the maximum count of retry attempts its default value is 3 default retry ratelimitretrytime it is the retry late limit of the email server after which the email can be retried to send it's default value is 86,400 seconds that is 24 hours rate limit retry progressiveretryinterval it is the progressive retry interval after which the email can be retried to send it's default value is 300 seconds progressive retry run the following curl command to reload the configuration curl x post http //localhost 8888/ameyorestapi/media/messages/reloadmediaprofileconfiguration h 'sessionid \<administrator session id only>' the following will be the result of applying the customized configuration using the above policies all the errors corresponding to "default retry" policy should get retried immediately all the errors corresponding to "no retry" policy will not get retired all the errors corresponding to "rate limit retry" policy should get retried after configured time all the errors corresponding to "progressive retry" policy should get retried at intervals of configured time same can be verified from "s message send info" and "failed message send info"