Yes, Hubspot has approved the Thena integration. We use O-Auth to connect to Hubspot.
In a private channel, we do not pull the user data to cater to privacy. That is why, you are asked to explicitly add the requestor in order to send it to Zendesk. This is then used to map and show the relevant user in Zendesk.
Each Slack workspace has the ability to choose whether or not to display a member's email address. If the workspace has set this to
No one, then Slack does not provide the email address of your customers through its API (image below)
The email is critical for our Hubspot integration to work. This is because we sync contacts between Slack and Hubspot using the
Thena whitelables the responses with the agent name and profile picture. If your agent's response is being delivered on Slack with the Thena icon and name, one of the following is the root cause:
- Agent user does NOT exists on Slack
- Agent has a different email on Slack vs that on Hubspot (case sensitive)
In this scenario, Thena will automatically create a new user in Hubspot.
In a private channel, we do not pull the user data to cater to privacy. That is why, you are asked to explicitly add the requestor in order to send it to Zendesk. This is then used to map and show the relevant user in Hubspot.
Yes, you can enable what's known as a
default tag to send to Hubspot. This can be something like
thenaSlackRequest. All requests that originate from Slack will have the default tag applied. To request default tagging, please reach out to the Thena team.
No - Internal notes are viewed as collaboration within the Support team. As a result, we do not show the internal notes to the customer. This can, however, be configured to send a one time dump of notes to the customer channel (to be used as a summary).
Updated about 2 months ago