Works with Help Scout via Make, Zapier, n8n or your own endpoint

AI Chatbot for Help Scout: answer the easy half, file the rest properly

A three-person support team does not have a volume problem. It has a sameness problem — half the mailbox is opening hours, order status and password resets. Put Asyntai on the website and those never become tickets at all. The ones that should become tickets arrive in Help Scout as a real conversation, with the customer's email, their actual question, and the chat that led up to it.

Get Started Free See the setup

See what the chatbot would answer

Enter your website and watch the AI answer questions using your own content — these are the messages that stop reaching your mailbox.

Why small Help Scout teams put a chatbot in front of the mailbox

Help Scout is deliberately quiet software. There is no ticket number shouted at the customer, no portal, no status page — a conversation looks like an email because it basically is one. That is why small teams love it, and it is also why the mailbox fills up with things that were never really support work.

Go through last month. A large share of what landed in Help Scout was already answered somewhere on your site: the returns window, the delivery estimate, whether you ship to Ireland, what the plan includes. Every one of those cost a human a context switch and a two-line reply.

Answered on the website

  • Opening hours and delivery times
  • Returns, refunds and warranty rules
  • What a plan or product includes
  • Where to find a setting or a document

Filed as a Help Scout conversation

  • "My order arrived damaged"
  • "I want to cancel and get a refund"
  • "This is the third time I have asked"
  • Anything where the visitor asks for a person

The split is the point. A chatbot that answers everything badly is worse than no chatbot. A chatbot that answers the repetitive half from your own published content, and escalates the rest into a properly formed Help Scout conversation, gives a small team back most of its afternoon.

The measure of success is not how many chats the bot handled. It is how much thinner the Help Scout queue got.

The four chat events that can open a Help Scout conversation

Asyntai fires webhooks on four events. Each webhook you register listens to whichever ones you tick, so a single connector can watch one event or all four.

escalation.requested
The visitor asked for a human. This is the one that should become a Help Scout conversation. Carries the session id and the message that triggered it.
conversation.started
A visitor opened a new chat. Carries the session id, the page they were on and the device type. Useful for reporting, noisy as a ticket source.
message.received
A visitor sent a message and the bot answered. Carries the question, the answer, the session id and the page URL.
takeover.started
One of your own agents took the chat over. Carries the session id and the agent name.

Start with escalation.requested only. It is the event with a one-to-one relationship to real support work, and it will not flood the mailbox you were trying to empty.

How to connect the chatbot to Help Scout

Be clear about the shape of this before you start, because it changes the order of the steps.

Asyntai already ships direct integrations for several helpdesks — Zendesk, Intercom, Front, Gorgias, Freshchat and HubSpot. Help Scout is not one of them. The Help Scout route goes through a connector, and that is a deliberate design choice rather than a missing feature: the Asyntai webhook sends a signed JSON POST and nothing else. It cannot attach an OAuth token or an API key, so it cannot call the Help Scout API by itself. A connector can, because it already holds an authorised Help Scout connection.

Any of these will do the middle bit: Make (Custom webhook, plus the native Asyntai AI Chatbot app), Zapier (Catch Hook, plus the native Asyntai app), Pabbly, n8n, or a small endpoint of your own.

1. Connector
Custom webhook or Catch Hook gives you a URL
2. Asyntai
Paste the URL, tick escalation.requested, set a secret
3. Sample
One real chat teaches the connector the fields
4. Help Scout
Create Conversation in the right mailbox

The four steps in full

Get a listening URL. In Make, start a scenario with Webhooks → Custom webhook. In Zapier, start a Zap with Webhooks by Zapier → Catch Hook. Either way you get a unique generated URL. Copy it.
Register it in Asyntai. Open Settings → API, add a webhook, paste the URL, tick escalation.requested and set a signing secret. Webhooks are on the paid plans.
Send one real chat. Open your own widget and ask for a human. The connector reads that sample and every field becomes mappable. In Make, use Re-determine data structure if you change the event list later.
Add the Help Scout step. In Zapier the action is Create Conversation; in Make the module is Create a Conversation, described as creating a conversation in a mailbox with at least one thread. Pick the mailbox, set the customer email, put the visitor's question in the first thread, and turn it on.
What Asyntai POSTs to the connector
// Headers: Content-Type: application/json // X-Webhook-Event: escalation.requested // X-Webhook-Signature: <HMAC-SHA256 of the body, using your secret> { "event": "escalation.requested", "payload": { "session_id": "s_8f31c0a4", "message": "My order arrived damaged, I need to talk to someone" } }

Once a sample has arrived, mapping into the Help Scout module is drag and drop. In Make's expression syntax, where 1 is the webhook module's number, the fields look like this:

Mapping into Create a Conversation
Mailbox: Support Subject: Chat escalation {{1.payload.session_id}} Thread: {{1.payload.message}} Tag: from-chatbot

Add a tag such as from-chatbot on every conversation the bot files. After a month you can filter on it and see precisely what the bot could not handle — which is the shortest possible list of things to add to your content.

Two Help Scout chatbot workflows worth building first

Both are one webhook plus two or three connector steps. Neither needs code.

The handover becomes a conversation, not a lost transcript

Build this one on day one. The moment a visitor asks for a person, a Help Scout conversation opens in your Support mailbox with their email as the customer and their real question as the first thread. If they gave an email address in chat, run a Find or Create Customer step first so the conversation attaches to the record you already have instead of creating a duplicate.

What changes in practice: an agent opening the queue reads "My order arrived damaged" instead of "chat escalation, session 8f31c0a4", and can reply without asking the customer to repeat themselves.

escalation.requested→Catch Hook→Find or Create Customer→Create Conversation

The bot writes the first draft, your agent edits and sends it

This is the interesting one, and it uses the connection in both directions. After the conversation is created, add an HTTP step that asks Asyntai the same question the visitor asked, then attach the answer with Add Note — a note, so nothing is ever sent to a customer without a human reading it.

Your agent opens the conversation and finds a suggested answer already sitting there, drawn from your own documentation. They keep it, cut it in half, or throw it away. Even at a fifty per cent keep rate that is a meaningful change to a small team's day.

escalation.requested→Create Conversation→POST /api/v1/chat/→Add Note
The draft-a-reply call
// POST https://asyntai.com/api/v1/chat/ // Header: X-API-Key: YOUR_API_KEY { "message": "My order arrived damaged, I need to talk to someone", "session_id": "s_8f31c0a4", "website_id": "YOUR_WEBSITE_ID" } // Response { "success": true, "response": "I am sorry about that. Damaged items are replaced free...", "session_id": "s_8f31c0a4" }

Pass the same session_id the webhook gave you and the answer is written with the earlier chat in mind. The endpoint accepts the key as an X-API-Key header, an Authorization: Bearer header, or an api_key query parameter — useful when your connector cannot set headers. Full reference is in the API documentation.

What the Help Scout chatbot setup gives a small team

Fewer conversations, better ones

Repetitive questions never reach the mailbox. What does reach it is work that genuinely needed a person, which is the only queue worth measuring.

Answers from your own content

The bot answers using your own pages, uploaded documents and FAQ entries — not generic AI knowledge and not invented policy.

Signed deliveries

Every POST carries an HMAC-SHA256 signature of the body in X-Webhook-Signature, so your connector can confirm the delivery really came from your account.

30+ languages into one mailbox

Visitors get replies in their own language automatically. What arrives in Help Scout has the same shape whatever language the chat happened in.

Filters before the mailbox

The connector can route by page, hour or wording — pricing questions to one mailbox, weekend escalations to another — without any logic living in the bot.

A tag that tells you what to write

Tag every filed conversation and you get a running list of the gaps in your own content, ranked by how often customers hit them.

What this actually costs

Three bills, and it is fair to say so up front.

  • Asyntai. Webhooks and the REST API need a paid plan — Starter, Standard or Pro. The free plan gives you 100 messages a month to try the bot itself, with no API or webhook access. See pricing.
  • Help Scout. Billed by Help Scout, unchanged by any of this. Note that Zapier lists tags and custom fields on Create Conversation as needing Help Scout's Plus plan, so check your tier before you rely on tagging.
  • The connector. Make, Zapier and Pabbly all have their own subscriptions and free tiers. A self-hosted n8n or a twenty-line endpoint of your own costs nothing beyond what you already run.

Help Scout chatbot questions

Does Asyntai have a direct Help Scout integration?

Not a direct one. Direct integrations exist for Zendesk, Intercom, Front, Gorgias, Freshchat and HubSpot. Help Scout is reached through a connector — Make, Zapier, Pabbly, n8n or your own endpoint — which holds the Help Scout credentials and calls the Help Scout side for you.

How do I get chat escalations into Help Scout as conversations?

Build the connector side first. Add a Custom webhook in Make or a Catch Hook in Zapier and copy the URL. Paste it into Asyntai under Settings → API, tick escalation.requested, set a secret. Send one real chat so the fields appear, then add Create Conversation and map the question into the first thread.

Can the webhook send a Help Scout API key?

No. Asyntai sends only Content-Type, X-Webhook-Event and X-Webhook-Signature. There is no custom auth header, so the webhook cannot call the Help Scout API directly. The connector supplies the authorised Help Scout connection, which is why it is in the middle.

Can the chatbot draft the first reply inside a Help Scout conversation?

Yes, as a note rather than a sent reply. POST the visitor's question to https://asyntai.com/api/v1/chat/ with your key, take the response field, and map it into Add Note. An agent always reads it before anything goes out.

What does a Help Scout chatbot setup cost?

Asyntai webhooks and the API are on the paid plans (Starter, Standard, Pro); the free plan's 100 monthly messages do not include them. Help Scout bills separately, and so does whichever connector you choose — unless you self-host n8n or write the endpoint yourself.

Other ways to wire the chatbot in

The same four events and the same REST API work through anything that can receive a JSON POST.

Make Zapier n8n Twilio API docs All platforms

Empty half the mailbox before it fills

Answer the repetitive questions on the website, and let Help Scout keep the ones that actually needed you.

Get Started Free