![]() ![]() ![]() AUTOTASK OUTLOOK ADD IN UPDATEIf you update who’s assigned to the call, it will update your HaloPSA and regular calendars. If your calendar account is synced with your Smartphone, your entry will be injected automatically, so your HaloPSA appointments are in with all your other appointments. HaloPSA will inject your Agent appointments to the specified calendar, and all of the ticket data you specified as well. Add to Exchange, Office 365, MDaemon or Google Calendar If you update the appointments in the ticket, it will then update both your HaloPSA and regular calendars. So, if you update the calendar time/date in your calendar, it will update your HaloPSA calendar. You control what information comes out of the ticket and into the HaloPSA calendar entry using $variables of multiple data fields from the database.The intelligent 2-way updating allows you to update in one place, to update the other. HaloPSA has its own centralised calendar, where each Agent can have their own calendar, or you can group Agents appointments together, with personalised colour selection to identify. These can be viewed separately, or collectively in a group HaloPSA calendar from the main screen. Each Agent has their own HaloPSA calendar in the help desk software. This amazing, intelligent 2-way functionality works with both Exchange Calendars on your domain, Office 365 or Google Calendar. HaloPSA will then push your appointments out to your Agents’ calendars. Add the Subject for the appointment, start date and time, end date and time, indicate if confirmed with the relevant parties, and which Agent it is applicable to. Whatever the reason, schedule your multiple appointments from within the ticket. Note: This feature also does not work unless you have the paid edition of Google G-Suite.Whether it’s to call your end user back, schedule actions internally, or site visits. Under “Console” > “Apps” > “G Suite” > “Settings for Gmail” :ġ) Single recipient > Specify envelope recipients > do I confirm it working? Google admin > Gsuite > Gmail > Default Routing Ok, I have the paid edition of Google G-Suite What about groups with an external Autotask email address? The forwarding options can be found with this link Yes, you can set up a dedicated support mailbox within GSuite so that you can forward from GSuite to the incoming email processing mailbox in Autotask, from the original sending email that your customer used. This solution produced funky results in our own Legacy G-Suite environment. How about using a forwarder from the support mailbox? I repeat, AUTOTASK EMAIL PROCESSING WILL NOT WORK FOR LEGACY GOOGLE G-SUITE USERS. This service, albeit very well advertised on the G-Suite console for any edition the business owns does not support S-suite legacy users. in our example below, it should be your for your business and the recipient further down the page should be the Autotask email address that processes your email for ticket creation, updates, etc. Well, maybe… Follow the straight forward steps illustrated below. Here are Google (G-Suite) Mail steps for configuring a rule to re-route the incoming emails to a different recipients, all the information is detailed in the following Help Center Article. Google G-Suite Steps to Processing Autotask Email Setup Email Channel – Zoho Desk Knowledgebase.Are you redirecting other service desk customer service systems?.Redirect emails from your organization to an external email processor.You can head over to Autotask KB if you are lacking a basic understanding of the Autotask email processing workflow. Autotask email processing works if you have a solid best practice setup and the right email hosting packaging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |