Meetings & calls
An AI agent that studies your Gong calls between reviews.
Connect Gong and an OpenHelm agent can work through call recordings and transcripts on a recurring schedule: summarising key calls, tracking objection patterns across the team, and flagging deals whose conversations have turned risky.
What agents do with Gong. Recurring jobs, checked every run.
Daily call summaries
Each evening, summarise the day’s customer calls with outcome, sentiment and next step, delivered as one digest email.
Objection pattern tracking
Log recurring objections and competitor mentions into a data table, so enablement sees what the market is actually saying, week by week.
Deal-risk flags
Watch for risk signals in conversations, such as budget doubt or a new stakeholder, and alert the deal owner with the exact quote and timestamp.
Coaching digest
A weekly note for managers highlighting calls worth reviewing and why, grounded in specific transcript moments.
Connect Gong. A few minutes, once.
Connect Gong
Add Gong 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": "Gong", "type": "token", "secret": "<your Gong API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Can it quantify trends over time?
Yes. Because findings land in OpenHelm data tables rather than one-off summaries, the same job builds a running dataset you can compare month over month.
How does OpenHelm connect to Gong?
With a scoped API key: create one in Gong, 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 Gong 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.