No auto email to customers after ticket creation

Howdy!
Fairly new to ZSD and are just in the setup/config stage, for internal employee IT Support only
We have tryed several setups but cannot get the result we want so I'm asking if its even possible

 ONLY create tickets via email polling ->  'customer' is emailed the ticket has been created -> AFTER which they ONLY view/update the ticket via the portal.
-- The technician watches the dashboard for new tickets and self assigns.

RESULTS wanted:  No more email UNLESS we specifically send it.

Tried having ONLY a NoReply acct under a team layer but then other technicians aren't available for assignment.

Can we have a customer ONLY receive the initial ticket creation email and NO subsequent ones ??

many thanks.

Parents
  • 0

    NOTE: i see we can manually set customer notifications to none on the ticket. is there a NON manual way?

  • Verified Answer

    +1 in reply to 

    Welcome to ZSD and thank you for posting.

    Though there are some notification configurations in privileges, most of the "notification" settings are at the Team level.
    This is because each team may require different notifications as you mention.

    There are generic "how to" notify the Customer and Technician and when a request is created / updated / escalated / closed.

    When sending emails the system uses Templates for certain actions or states.

    Reminder - notice the drop downs while in the templates.

    • "Template" drop down, if you wish to use a preconfigured template
    • "Insert Parameters" drop down, to automatically insert different details about the request to better personalize / clarify the email.

    There are also Email Templates you can configure to when an action is taken on a request sending an email with a particular wording.

    And a hidden gem - when a request enters a particular workflow "state" you can configure that "state" to "Send a Custom Email" .
    Selecting the Lifecycle State will allow you to edit it's settings.

    A request is entered for replacing a printer cartridge that had to be ordered. 
    Once the cartridge is ordered and the request enters the "On Hold" state, an email can go out to say the order has been placed and we are waiting on the vendor. 

    Let me know if this helps resolve your email sending requirements.

    Be sure to check out the ZSD Customization Cookbook it is a compilation of Technical Information Documents (TIDs) from customers that reference different ways to configure for certain scenarios, branding and tools.

    Feel free to email me for other questions.

    Paul Pedron

Reply
  • Verified Answer

    +1 in reply to 

    Welcome to ZSD and thank you for posting.

    Though there are some notification configurations in privileges, most of the "notification" settings are at the Team level.
    This is because each team may require different notifications as you mention.

    There are generic "how to" notify the Customer and Technician and when a request is created / updated / escalated / closed.

    When sending emails the system uses Templates for certain actions or states.

    Reminder - notice the drop downs while in the templates.

    • "Template" drop down, if you wish to use a preconfigured template
    • "Insert Parameters" drop down, to automatically insert different details about the request to better personalize / clarify the email.

    There are also Email Templates you can configure to when an action is taken on a request sending an email with a particular wording.

    And a hidden gem - when a request enters a particular workflow "state" you can configure that "state" to "Send a Custom Email" .
    Selecting the Lifecycle State will allow you to edit it's settings.

    A request is entered for replacing a printer cartridge that had to be ordered. 
    Once the cartridge is ordered and the request enters the "On Hold" state, an email can go out to say the order has been placed and we are waiting on the vendor. 

    Let me know if this helps resolve your email sending requirements.

    Be sure to check out the ZSD Customization Cookbook it is a compilation of Technical Information Documents (TIDs) from customers that reference different ways to configure for certain scenarios, branding and tools.

    Feel free to email me for other questions.

    Paul Pedron

Children
  • 0 in reply to 

    Many thanks for your reply. The cookbook will be useful.

    We are slowly moving forward and need advice on:

    1- after hours? - All tkts will be created via email. ONLY the customer will get notified....BUT after hours we would like to have someone in IT emailed that a tkt has been submitted.  What are after hours best practices? can we disable/enable on a schedule the email polling?

    2- the IP address is used in the email templates for the URL to services desk so we end up hard coding it. Is there a place we can change it to the hostname instead? not https://172.16.222.111/zsd   change to https://zsd83vm.domain.ca 

    3- we would like all users (customers) to be able to resolve any of their tkts but some have option to add note and some have add note and resolve. We cant see why resolve isn't always available.?

    Thanks again.