FYI: * You will need data from the HelpScout's account admin or owner. As you set up PlayVox’s software, you’ll be named an admin user.

*Similarly, if you’d like to set up a new integration, then you’ll be required to be a PlayVox admin user as well.

This is the data you’ll be asked for during the integration:

(This first 2  steps will happen only if you are not signed into HelpScout).

Name: it is the connector’s name - you may have multiple connections and it is important for you to be able to properly identify them (i.e. HelpScout's chat 1, India’s emails, Technical support chat, etc.).

After typing the connector’s name, you should click on the Accept button - once you do so you’ll be shown an emerging window where you’ll need to connect the accounts (as shown below). As soon as you click on Authorize the integration will be set up.

PlayVox's API Consumption for HelpScout's Integration

FYI - HelpScout offers 400 requests per minute by default.

PlayVox consumes API like so:

  • non filter view consumes 5 requests
  • when selecting a filter, additional 5 requests are used
  • the creation of filters consumes 3 requests
  • and every time you select a different conversation, additional 4 requests will be used.


About the credentials you need:

Supported Operation Mode for HelpScout's Integration

This integration only supports On-demand mode, helping you save on API requests. It is also important to clarify, we do not store any data, as it's name states, our platform simply fetches it when you ask for it. With this option you can filter tickets by: 

  • subject
  • email
  • body
  • status
  • attachments
  • tags
  • mailbox


Now that you have all the data you’ll need, you can continue with the integration process. 

About the data we process, it is transmitted using encrypted TLSv1.2 over HTTPS and data at rest is kept encrypted using industry standard AES-256 on EBS Volumes in Amazon Web Services (AWS) facilities in the USA.

If you’d like to read more, we have articles on:

You can also check out our privacy policy.


Last Edited: 08.13.19

Did this answer your question?