Skip to main content

​
Messenger

The Messenger tab in the Thread Admin Panel is where you control the settings of your customer Messenger applications. It has five sub-tabs: Settings, Design, Hours, Installation, and Teams Apps.

​
The Settings Tab

Messenger Settings tab
On this page you configure the properties of your Messenger, including the Support type and the Show all tickets in Chat toggle (formerly “Proactive Messages”) — learn more about the latter in Show all tickets in Chat and excluded boards.

​
Support type: “Standard Chat” vs “Chat with SLAs”

The Support type is a single choice you make in the Settings tab. It controls the new-request button customers see in Messenger and whether they are shown a response-time expectation. Chat with SLAs is the default. Chat with SLAs: Customers start a new thread with the Chat button, and Messenger tells them when to expect a response to new threads. The default expected response time is 5 minutes, which matches the Swarm Mode response timer in Inbox; you can also change it to No estimate (no time is shown to the customer) or a Custom time. Selecting Chat with SLAs also enables Swarm Mode for your Inbox users. Standard Chat: Customers start a new thread with the Request button. No response-time expectation is set, so these threads can be treated more like an email thread in terms of timed response.
Outside your configured support Hours (“After Hours”), Chat with SLAs falls back to the Standard Chat / Request experience so customers aren’t shown a response time your team can’t meet while offline.
In this section, you are also shown a version of your own branded Messenger which you can use for testing purposes.

​
OTP sign-in emails

When a contact signs in to Messenger, Thread emails them a one-time verification code (OTP). These emails carry your branding automatically: the email shows your workspace name and logo instead of Thread’s, and the sender line reads as your workspace name “via Thread”. There is nothing to enable. You can also customize the support address shown inside the email. The OTP email tells the contact who to reach if something seems off. By default it directs them to help@getthread.com. To use your own support address instead:
  1. Go to Admin Panel → Messenger → Settings.
  2. Scroll to Customize Contact Email, near the bottom of the tab.
  3. Enter your support email address and click Save.
Customize Contact Email field on the Messenger Settings tab, where you enter the support address shown in OTP emails
OTP emails are still sent from Thread’s address (no-reply@getthread.com); the sending address itself can’t be changed. This customization applies to Messenger OTP sign-in emails only. Approval emails are unchanged.

​
The Design Tab

The Design tab is where you brand Messenger. Changes save in real time and roll out to the Web, Desktop, and Microsoft Teams versions of Messenger almost instantly. You control four things:
  • Primary color — the accent color used for the launcher button, the composer, and other branded elements.
  • Web icon — the icon shown inside the round launcher button on your website and in the Desktop app.
  • In-app logo — the logo shown in the Messenger header, on the sign-in screen, and in OTP sign-in emails.
  • Chatbot messages — the bot name, whether to append “(bot)” to bot replies, and optional custom prompt text.
Both fields accept the same file types and size limit, but they render at different sizes, so the source images shouldn’t be the same asset: Accepted formats: PNG, JPG, JPEG, BMP, WebP, SVG. Maximum file size: 10 MB. Uploads open a crop tool so you can frame the image before saving. Transparent PNG or SVG works best for the Web icon so it sits cleanly on the colored launcher button.
If you’re overriding Messenger design for a single client, the Design tab on that client’s Settings page has the same fields and the same specs. See Override settings for a single client.

​
What a customer experiences

Worth knowing when you’re configuring the above, because it’s what your settings produce. A customer clicking Chat is asked to describe their issue. The request has two parts:
  • Description — becomes the issue description your technician sees. Encourage detail; it’s what makes the request actionable straight away.
  • Device: if the contact has configurations associated in your PSA, they’re listed and the customer picks the affected one. Choosing None of the above creates the ticket with no configuration attached.
Either way the ticket lands on the board your Messenger settings route to, and dispatch or Triage Agent takes it from there. Once a technician is assigned, the customer sees that technician’s name at the top of the chat window and is notified. You work the resulting ticket wherever you receive it — Inbox, or the Teams or Slack Companion App: replying, adding internal notes, and taking the usual actions.

​
The Hours Tab

This section allows you to set a working hours schedule if you wish. Hours outside of these are referred to as “After Hours”, and you can display a custom message that lets your customers know the support team is currently offline.

​
The Installation Tab

This section includes your Messenger’s unique App ID as well as a custom snippet you can use to embed Messenger in your website. For more info on embedding Messenger in websites, see this help doc. You can also send contacts a direct link to the hosted web Messenger instead of embedding it. See Link directly to web Messenger.

​
Teams Apps

This section shows you the custom Teams apps you have created, and allows you to edit and duplicate existing Teams apps. For more info on these apps, please see this help doc.