• Skip to primary navigation
  • Skip to main content
  • Skip to footer
  • Skip to custom navigation
HaloPSA

HaloPSA

  • Features
  • Pricing
  • Integrations
  • Resources
    • Demo On Demand
    • Roadmap
    • ITIL Alignment
    • Guides
    • HaloPSA Academy
    • Onboarding Partners
    • Distributors
  • Compare Us
    • ConnectWise
    • Datto Autotask
  • Solutions
    • I Need To…
      • Run My Business More Effectively

        Find out which customers and services are profitable and gain the confidence to act on this data.

      • Improve My Customer Experience

        Make all interactions as smooth as possible with a fully thought out end to end experience for your customers.

      • Streamline My Sales Process

        Remove unnecessary processes from your sales and account management and let them focus on their customer relationships.

      • Gain Control Of My Projects

        Visualise your workload and forecast your required budgets to ensure you can deliver on your projects.

    • We Are A…
      • Managed Service Provider
      • Telecommunications Provider
      • Cloud Solution Provider
      • Software Company
      • Consultancy Firm
    • Case Studies
      • nGeneration
      • Centrality
      • Commercial Managed IT
  • Start trial
  • Book demo

HaloPSA Guides

Documentation to assist with the setup and configuration of the HaloPSA platform

Guides > AI Azure Translator

AI Azure Translator


In this guide we will cover:

- Enabling Azure AI Translator

- Configuring Azure AI Translator

- Using Translations on a Ticket

- Language Pack AI Translations (v2.184.1+)



The Azure Translator integration allows you to instantly translate notes from users or other agents into the language that you are currently viewing Halo in.


Enabling Azure AI Translator

To use this integration, you must enable the Azure Translator module from within Configuration > Integrations by clicking the '+' icon:

Fig 1. Enabling the module.


Configuring Azure AI Translator

To configure, set up a Translator within Azure > Cognitive Services, and obtain an API Key from "Keys and Endpoints", and paste your API key in Config > Integrations > Azure Translator - Translator API key.


You will need to enter the correct region for your translator model, this can be found in Microsoft's documentation. For example if you were in canadacentral, it should appear the following way:

Fig 2. Adding the API key and region.


Alternatively your region may need to be set to Global, which is the Halo default.


There are options to choose between translating only plain text (to reduce usage costs), or HTML (to include images and preserve the formatting in the translation). A monthly character limit can also be added here.


Using Translations on a Ticket

When active, a translate button will show for each action note. Press it to translate the note. This will auto-detect the language of the note and translate it into your current language using Azure translator.


Fig 3. Untranslated ticket.


The note will then be replaced with the translated version and pressing the button again will revert to the original.


Fig 4. Translated ticket.


Any notes which are translated are stored in the database and the translation is automatically loaded the next time you view the ticket.


Fig 5. Automatically loading the translation.


The first time the translation is made, it may take a few seconds to process, the next time you need to click the translate button it will automatically update via Halo's database:


Fig 6. The same email.


Language Pack AI Translations (v2.184.1+)

The integration can also be used to auto-translate missing strings in a language pack.



In Configuration > Language > Customise Language, select a language to translate. Click the "AI Translate Untranslated" button.


Fig 7. AI Translate Untranslated button.


A loading popup will then show. This will take a while as there is a large amount of data to translate, though only non-translated strings will be translated when using this method to reduce cost of use.


Fig 8. Creating the translations.


Upon completion, a CSV file will be created with the translations. Here, you can review them to make sure they are what you expect.


Fig 9. Translated file.


After confirmation, the file with the translations can then be imported for use.


Fig 10. Import From CSV button.


Popular Guides

  • Asset Import - CSV/XLS/Spreadsheet Method
  • Call Management
  • Creating a New Application for API Connections
  • Creating Agents and Editing Agent Details
  • Departments and Teams
  • Halo Integrator
  • Importing Data
  • Multiple New Portals with different branding for one customer [Hosted]
  • NHServer Deprecation User Guide
  • Organisation Basics
  • Organising Teams of Agents
  • Step-by-Step Configuration Walk Through

Footer

Products

Company

  • Contact us
  • Events
  • Channel Partners
  • Technology Partners
  • Distributors
  • Referral Program

HaloPSA

  • Features
  • Integrations
  • Mobile Apps
  • Blog
  • Pricing

Key Features

  • Service Desk
  • Sales CRM
  • Billable Time Tracking
  • Reporting
  • Contracts
  • Billing
  • Stock Management
  • Projects

Compare PSA

  • ConnectWise
  • Datto Autotask
  • Accelo
  • Harmony PSA
  • Naverisk
  • Top Desk
  • Kaseya BMS
  • Atera
  • Freshservice

Social

  • Terms and Conditions
  • Privacy Policy
  • Security
  • GDPR
  • Modern Slavery Statement
We've moved!

Please visit our new website at USEHALO.COM/HALOPSA