Support
An AI agent for your Help Scout mailboxes.
Connect Help Scout and an OpenHelm agent can keep shared mailboxes under control: recurring triage, a daily list of conversations going stale, drafted replies for the routine questions, and a weekly read on what customers are actually asking.
What agents do with Help Scout. Recurring jobs, checked every run.
Mailbox triage sweep
Classify new conversations by topic and urgency on a schedule, tagging and assigning so the right person sees the right thread first.
Going-stale chaser
Each morning, list conversations without a reply inside your target window and nudge the assigned owner.
Weekly support insights
A short report on question themes, resolution times and recurring friction, built into a data table you can track over months.
Connect Help Scout. A few minutes, once.
Connect Help Scout
Add Help Scout under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Help Scout", "type": "token", "secret": "<your Help Scout API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
How is this different from Help Scout workflows?
Workflows apply fixed rules. The OpenHelm agent reads each conversation and reasons about it, so triage handles phrasing it has never seen, and everything it does is explained in the run log.
How does OpenHelm connect to Help Scout?
With a scoped API key: create one in Help Scout, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Help Scout data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.