In this window we can pair an unknown email addresses to the existing customers/leads in Splynx. As a result, this will help to assign all received tickets from unrecognized email addresses to specific customers/leads and they will receive correct tickets' notifications to such new email addresses. Also, it's possible to unpair email address with customer/lead, edit sender name, disable pairing, ban the sender's email address and check if the email is in deny list.
The following actions can be applied in the Recipients table:
- sender email address will be banned to send message to Incoming mailbox, the next new ticket from this email address won't be created in Splynx;
- sender email address will be unbanned and the next new ticket will be created in Splynx;
- to map an unknown email address to existing customer/lead in Splynx, ticket that was created will be assign to paired customer/lead;
- Assign all tickets - toggle allows to assign, all unassigned tickets created from an unknown email to the existing customer/lead;
Tip: If unrecognized email address is paired to some customer/lead e.g. by mistake in Recipients table, we can reassign the current ticket and the future ones to other customer/lead directly from ticket, after adding new customer/lead and pressing Update, the new Change pair for recipient window will appear, press Yes to proceed. If the
Shared email option is enabled, the mass reassignment function will not work (only the current ticket will be assigned to specific customer/lead).
- Edit sender
- to edit sender's name in Tickets;
- Shared email - toggle allows to mark an unknown email address as shared one, in this case pairing will be disabled for such email, for example support team receives a lot of messages from one request form (the same email address) and we need to block
Pair Customer/Lead to requesteroption in ticket Actions list, but at the same time tickets should continue to be received. However, each ticket can be assign to specific customer separately;
- the status
in the column
in deny list- means that the email address was added to Deny list in
Config → Tickets →Inboxes. Ticket from these email will not be created in Splynx.
Example #1: Notifications to customer's emails:
Let's imagine that we have set up SMTP, Incoming mailbox (
email@example.com) and enabled Ticket notifications. In SMTP config, we use
firstname.lastname@example.org address in both Sender's email and Admin email fields.
Customer sent a message to
email@example.com from his new mail address, as a result, the new ticket will be created in Splynx. After that we paired new mail address with our customer in
Tickets → Recipients.
firstname.lastname@example.org will be sent a notification New ticket created, when administrator directly replies on this notification message, the new notifications
New ticket created (Request received)and
New message in ticket will be sent to customer's paired mail address but to customer's mailbox (
New message in ticket. To customer's
Billing emailno notifications will be sent at all.
Example #2: The relationship of the customer's message to the ticket:
We paired two mail addresses to one customer in
Tickets → Recipients: email@example.com and firstname.lastname@example.org. The customer wrote a message from email@example.com to our Incoming mailbox (
firstname.lastname@example.org), after that the new ticket was created in Splynx. If customer replies (the
subject of the message shouldn't be changed, otherwise will be created a new ticket) from email@example.com to ticket notification (e.g.
New message in ticket), the message will be added to the existing ticket's thread (created from firstname.lastname@example.org) in Splynx .
The Recipients table can be modified to display the necessary fields with