Skip to main content
The Chatbase Help Scout integration lets your AI agent open a Help Scout conversation in the mailbox you choose when a customer needs a person, with an AI-written summary of the chat and a link back to the full conversation in Chatbase. It’s for teams that answer customers from a Help Scout mailbox and want the AI agent to handle routine questions first. Tickets can be created from any channel where the Escalations Action runs, such as the Chat Bubble, Help Page, WhatsApp, Messenger, Instagram, and email.

What you can do:

Let the AI resolve routine questions on its own, and hand off to Help Scout the moment a case needs a person, with the full context already attached.

Before you start

  • A Chatbase account on the Basic plan or higher.
  • A Chatbase AI agent. The connection is per AI agent, and each AI agent can connect one Help Scout account.
  • A Help Scout account you can sign in to, with at least one mailbox.

How to connect Help Scout

1

Open your Chatbase AI agent

Log in to your Chatbase dashboard and select the AI agent you want to connect.
2

Connect Help Scout

Choose Integrations, then click Connect under Help Scout. Help Scout opens its authorization page: sign in and approve access for Chatbase. There are no API keys or IDs to enter.
3

Create the Escalations Action

Go to Build > Actions > Create Action, select Create ticket under Escalations, and choose Help Scout as the Ticket Platform. Then pick a Help Scout mailbox (required): tickets created by this Action are sent to this mailbox. The list shows every mailbox in your Help Scout account. Follow the Escalations Action guide for the rest of the setup.
Test the integration by asking your AI agent to speak to a human, and confirm a ticket appears in Help Scout with the conversation summary attached.
To route different requests to different mailboxes, create one Create ticket Action per mailbox, each with its own name and When to use instructions.

What the ticket contains

Each escalation becomes an active email conversation in the chosen mailbox, with:
  • Subject: written by the AI agent from the customer’s issue. The customer is never asked for it.
  • Customer: the customer’s email. The AI agent doesn’t ask for a name on Help Scout, and no name is sent.
  • First thread: an AI-written summary of the conversation, in the customer’s language, added as a customer thread. In Help Scout it reads as if the customer wrote it.
  • Note: a note with a link to the full conversation in Chatbase, added right after the conversation is created.
Chatbase sets no tags or custom fields, and doesn’t attach files the customer sent in the chat.
Chatbase creates the conversation with auto-reply on, so if your mailbox has an auto-reply set up, Help Scout may email it to the customer.

Example

The following exchange is illustrative. A customer on the Chat Bubble writes “I was billed after canceling my subscription, I need someone to look at this.” The AI agent asks for an email, the customer replies “jane@example.com”, and the Support mailbox in Help Scout receives:
  • Subject: Charged after subscription cancellation
  • Customer: jane@example.com
  • First thread: The customer canceled their subscription but was still billed, and asks for the charge to be reviewed.
  • A note with the link to the conversation in Chatbase

What the customer sees

The AI agent asks for the customer’s email if it doesn’t already have it, creates the ticket, and tells the customer the Help Scout ticket number. On the Chat Bubble, Help Page, and Center Stage, a Ticket Created card also shows the number. If creation fails, the card reads Failed to create ticket. Your team replies from Help Scout, and the replies reach the customer by email. Nothing syncs back to the Chatbase conversation, and the AI agent keeps answering in the chat. Creating a ticket uses no extra message credits beyond the AI agent’s normal reply.

Disconnecting Help Scout

Go to Integrations, find Help Scout, and click Disconnect. Disconnecting doesn’t remove the Help Scout Create ticket Actions, and they fail if the AI agent calls them. After disconnecting, delete or update any Create ticket Actions that used Help Scout.

Troubleshooting

Errors appear as a message starting with Help Scout integration failed. Sign in to Help Scout with an account that has access to your mailboxes, approve access, and try again.
The list shows the mailboxes in the connected Help Scout account. Check that the account has at least one mailbox, or reconnect with an account that does.
The card shows Connected as long as a saved connection exists, even if Help Scout no longer accepts it (for example, after access was revoked in Help Scout). Tickets then fail, the customer sees Failed to create ticket, and nobody is notified. Open the conversation in Activity and check the Create ticket Action’s Result for the error, then disconnect and connect again.
That’s your mailbox’s auto-reply. Chatbase creates conversations with auto-reply on, so Help Scout may send it. If you don’t want it sent, adjust the mailbox’s auto-reply in Help Scout.

Frequently asked questions

None to copy. Help Scout connects through its own sign-in page, where you approve access for Chatbase.
The one set in the Action’s Help Scout mailbox field. Create one Action per mailbox to route requests to different mailboxes.
An email conversation. The summary is the customer’s first message, and your team’s replies go to the customer by email.
The Help Scout Action collects and sends only the customer’s email.
They stay, and they fail when the AI agent calls them. After disconnecting, delete or update any Create ticket Actions that used Help Scout.

Next steps

Escalations Action

Configure when your AI agent escalates, which details it collects first, and which channels it can escalate from.