Support integration guide
Help Scout + UbiGrowth workflows
Help Scout is a shared-inbox support platform focused on conversational customer service for smaller teams. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Help Scout part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a support workflow around Help Scout with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Conversation, Customer, Mailbox, Thread, Tag, Workflow, and Saved Reply. Help Scout scopes Conversations to a Mailbox, and the same Customer can hold conversations across several mailboxes. A per-mailbox view is not the customer's history.
Help Scout is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Support integrations are usually justified with deflection metrics, which is the wrong starting point. The expensive part of a ticket is not the reply; it is the time an agent spends assembling context from Help Scout, the CRM, the product, and the issue tracker before they can write anything useful.
The second cost is escalation. A ticket handed to another team without account context, history, and reproduction detail comes back as a question, and the customer waits through a round trip that added nothing.
You're likely here because
- Agents assemble customer context from several systems before replying
- Escalations arrive at other teams missing the detail they need
- Support tooling improvements never clear the engineering backlog
Record model
What a Help Scout integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Help Scout's.
Identity and matching
Help Scout scopes Conversations to a Mailbox, and the same Customer can hold conversations across several mailboxes. A per-mailbox view is not the customer's history.
Start here
Read Conversations awaiting a reply past the team's response target across all mailboxes, so nothing hides in a quiet inbox.
What this will not do
It will not scale as a ticketing system. Help Scout models email conversations; workflows needing structured ticket state should hold it elsewhere.
The constraint to plan around
Threads carry the message type — customer, reply, note — and the API returns them in one list. A workflow that concatenates threads will mix internal notes into what it treats as the conversation.
Build notes
What you actually have to reason about in Help Scout.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| thread type | customer, reply, or note — concatenating threads mixes internal notes into the conversation |
| mailbox id | the scope; a per-mailbox view is not the customer's history |
| status | active, pending, closed, spam |
| assignee | ownership, and the field that makes an unanswered conversation attributable |
| customer email | the identity across mailboxes, since Help Scout has no separate account object |
Authentication
OAuth 2 client credentials or authorization code, with mailbox-level access following the user. Tokens are short-lived and refresh must be handled properly.
Events and delivery
Webhooks per event type with signature verification, covering conversation and customer events. Coverage is good enough that polling is rarely needed.
Workflow
How the Help Scout workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Pick up the ticket with context
The account, purchase, and prior-conversation context for a Help Scout ticket is assembled before the agent starts writing.
Step 02
Triage against real priority
Tickets are grouped by issue type, account context, and age so the queue reflects what matters rather than arrival order.
Step 03
Draft with the human in the loop
A response is drafted from the assembled context and reviewed by the agent, who remains responsible for what the customer receives.
Step 04
Escalate with the history attached
Escalations carry account context, history, and reproduction detail into the receiving system, removing the clarification round trip.
Design decisions
The support decisions this connection forces.
Each of these has to be settled before the Help Scout workflow is allowed to write anything.
Step 01
Define the escalation contract
Decide what an escalation leaving Help Scout must include — account context, history, reproduction detail — so the receiving team does not have to ask.
Step 02
Keep the customer-facing boundary explicit
Context assembly, triage, and drafting can be automated well before automated replies are appropriate. Treat those as separate decisions.
Implementation path
How to implement the Help Scout workflow.
- 01
Pick one high-volume issue type and map exactly which context an agent needs to resolve it.
- 02
Connect Help Scout and the systems holding that context, at scopes limited to support use.
- 03
Build a triage or context surface in Launch and test it against recent real tickets rather than samples.
- 04
Once cross-mailbox response monitoring works, add customer-level history so an agent sees prior conversations regardless of which mailbox held them.
Governance
Controls that matter.
Control 01
Customer-facing replies stay under human review; the workflow assembles and drafts rather than autonomously answering.
Control 02
Access exposes the customer context the workflow needs, not the whole account surface.
Control 03
Billing, refund, and account-change actions require explicit human authorization.
Failure modes
How a Help Scout integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
An internal note is sent to the customer as a reply.
Cause
A reply thread was created where a note was intended.
Fix
Set the thread type explicitly and verify in a test mailbox before enabling.
Symptom 02
A conversation goes unanswered in a quiet mailbox.
Cause
Monitoring was per mailbox and that one had no owner watching.
Fix
Monitor across all mailboxes with a single response-time target.
Symptom 03
Conversation text includes internal discussion.
Cause
Threads were concatenated without filtering by type.
Fix
Filter threads by type before assembling conversation content for any downstream use.
What changes at scale
Rate limits are per app per minute. Webhook coverage is good enough that polling is rarely justified, which is the main scaling decision.
Examples
What a working Help Scout workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Support workflows
With Help Scout connected, the account, purchase, and prior-conversation context relevant to a ticket is assembled before the agent starts, instead of across five open tabs.
Triage surface
A Launch-built queue view groups Help Scout tickets by issue type, account value, and age — the view the team actually needs, without waiting for engineering capacity.
Limitations and considerations
What to validate before you depend on this.
- Threads carry the message type — customer, reply, note — and the API returns them in one list. A workflow that concatenates threads will mix internal notes into what it treats as the conversation.
- Creating a reply thread rather than a note emails the customer. The two are adjacent in the API and this is the mistake that gets made.
- When structured ticket state is required. Help Scout models email conversations, and forcing ticket semantics onto it means holding that state elsewhere anyway.
- This is not an autonomous customer-facing agent. Replies should stay under human review, particularly where the account or issue carries real consequences.
- Context quality depends on the systems behind Help Scout. A stale CRM record produces a confident and wrong summary.
FAQ
Help Scout integration questions.
What records does a Help Scout integration actually work with?
The primary records are Conversation, Customer, Mailbox, Thread, Tag, Workflow, and Saved Reply. Help Scout scopes Conversations to a Mailbox, and the same Customer can hold conversations across several mailboxes. A per-mailbox view is not the customer's history.
What should the first Help Scout workflow be?
Read Conversations awaiting a reply past the team's response target across all mailboxes, so nothing hides in a quiet inbox.
What will a Help Scout integration not do?
It will not scale as a ticketing system. Help Scout models email conversations; workflows needing structured ticket state should hold it elsewhere.
What is the main constraint to plan around?
Threads carry the message type — customer, reply, note — and the API returns them in one list. A workflow that concatenates threads will mix internal notes into what it treats as the conversation.
What changes about a Help Scout integration at scale?
Rate limits are per app per minute. Webhook coverage is good enough that polling is rarely justified, which is the main scaling decision.
How does authentication work for Help Scout?
OAuth 2 client credentials or authorization code, with mailbox-level access following the user. Tokens are short-lived and refresh must be handled properly.
Does Help Scout support webhooks, and can they be trusted?
Webhooks per event type with signature verification, covering conversation and customer events. Coverage is good enough that polling is rarely needed.
What is the risk of writing to Help Scout?
Creating a reply thread rather than a note emails the customer. The two are adjacent in the API and this is the mistake that gets made.
When is connecting Help Scout the wrong call?
When structured ticket state is required. Help Scout models email conversations, and forcing ticket semantics onto it means holding that state elsewhere anyway.
What should a Help Scout integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Help Scout to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Does this replace Help Scout?
No. Help Scout stays the system of record for conversations. The workflow layer sits around it for context assembly, triage, and connected escalation.
Will it reply to customers automatically?
Not by default, and not until the workflow has been proven. Context assembly and drafting are separate decisions from automated sending.
How do escalations improve?
The escalation carries its trigger, account context, and history into the receiving system, which removes the clarification round trip that usually costs the customer another day.
How this access is governed
What ARIA is allowed to do in Help Scout, and who decides.
Connecting Help Scout is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.