Support
An AI agent behind your Intercom inbox.
Connect Intercom and an OpenHelm agent can keep the support queue honest: triaging new conversations on a schedule, chasing threads that slipped through, drafting suggested replies from your documentation, and mining conversations for the questions your docs never answer.
What agents do with Intercom. Recurring jobs, checked every run.
Queue triage runs
On a recurring schedule, classify open conversations by topic and urgency, and flag the ones that look angry, churny or high-value.
Unanswered-conversation digest
A daily list of conversations past your response target, grouped by assignee, emailed before the morning stand-up.
Suggested reply drafts
For common question types, draft replies grounded in your help centre and past answers, left as notes for the agent handling the thread.
FAQ gap mining
Log recurring questions into a data table with counts, so the docs team writes the article that removes fifty tickets, not the one that removes two.
Connect Intercom. A few minutes, once.
Connect Intercom
Add Intercom 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": "Intercom", "type": "token", "secret": "<your Intercom API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Will customers know it is an agent?
The agent works behind the scenes by default: triaging, drafting and reporting. Whether anything is sent to a customer automatically is your choice, set per job through the autonomy level.
How does OpenHelm connect to Intercom?
With a scoped API key: create one in Intercom, 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 Intercom 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.
More in Support
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.