Sign inStart free trial
Documentation

Getting started

Set up Saetta in about 15 minutes. You'll need admin access to HaloPSA and to your Microsoft 365 tenant.

1. Sign in

Sign in to the Saetta console with your Microsoft 365 work account. Your 14-day trial starts when you connect HaloPSA.

2. Connect HaloPSA

  1. In HaloPSA, go to Configuration → Integrations → HaloPSA API → View Applications → New.
  2. Set Authentication Method to Client ID and Secret (Services) and Login Type to Agent.
  3. For Agent to log in as, choose an agent with full permissions, such as an administrator or a dedicated API agent with an administrator role. A limited agent causes permission errors.
  4. On the Permissions tab, grant all. Save, then copy the Client ID and Client Secret.
  5. In the Saetta console, paste your HaloPSA URL, Client ID and Client Secret. Saetta installs its webhooks and custom fields automatically.

3. Link your technicians

In Console → Users, link each HaloPSA agent to their Microsoft 365 account. Each linked technician is one seat. Linking lets Saetta route tickets to the right person in Teams.

4. Install the Teams app

Saetta is coming to the Microsoft Teams Store and Microsoft AppSource, expected within about 4 weeks. Until then, your Microsoft 365 admin installs Saetta directly for your organization in a few minutes, as described below. Nothing changes for your team once the store listing is live.

Your Microsoft 365 admin adds Saetta to your organization's app catalog once. It then appears under Apps → Built for your org for everyone you allow.

  1. Download the Teams app package: saetta-teams.zip. Don't unzip it.
  2. Open the Teams admin center and go to Teams apps → Manage apps. Select Upload new app → Upload and choose the file.
  3. If uploads are blocked, open Org-wide app settings (in Manage apps → Actions) and turn on Let users interact with custom apps. Make sure your permission policy allows Saetta.
  4. Recommended: in Teams apps → Setup policies, add Saetta under Installed apps (and Pinned apps if you like) for your technicians. Saetta then installs itself for them, so ticket alerts reach everyone without each tech adding it.
  5. Each technician who wasn't auto-installed opens Apps → Built for your org → Saetta → Add. To send a HaloPSA queue to a channel, also add Saetta to that team.

Changes in the Teams admin center can take a few hours to reach every user.

5. Install the Outlook add-in

Saetta is coming to the Microsoft Teams Store and Microsoft AppSource, expected within about 4 weeks. Until then, deploy it from the Microsoft 365 admin center as described below.

  1. Open the Microsoft 365 admin center and go to Settings → Integrated apps → Upload custom apps.
  2. Choose Office Add-in, select Provide link to manifest file and enter https://saetta.io/downloads/saetta-outlook.xml. (Or download the manifest and upload it.)
  3. Assign it to your technicians (or the whole organization), accept the permissions and select Deploy.

The Saetta button appears in Outlook (desktop, web and Mac) for assigned users, usually within a few hours and at most 24.

6. Route tickets and SMS

Saetta follows your HaloPSA assignment rules. A ticket assigned to a technician goes to that technician in Teams. A ticket waiting in a queue goes to the channel you map in Console → Settings → HaloPSA queues. Replying from the card assigns the ticket to you.

7. Messaging (optional add-on)

In Console → SMS, enter your business details and submit your carrier registration (required for all business texting in the US; approval takes 5–7 business days). Then either keep the number your customers already know, including a Teams Phone number, or pick a new local number. Texting starts as soon as the carriers approve your registration.

8. Choose a plan

Before your trial ends, pick a plan in Console → Billing. You can change plans or cancel at any time.

Need help? See Support.