New: Drizz now tests AI agents in simulated companies, with a graded report on every run. See how it works →

TwinsGong

A Gong twin for testing AI agents.

Test agents that read calls, pull out next steps and update the deal. Recorded calls and transcripts, with no real customer on the line.

twin / gongprivate · seeded · resets in one call
Gong twinCalls, transcripts and deal context.
  • Calls and transcripts
  • Speakers and topics
  • Deal links
  • Users and teams
  • Search and filters
  • One-call reset
Meet the twin

A stateful copy of Gong, built for testing agents.

It accepts the same API and MCP calls, checks sign-in and input, and follows the same rules, but runs on its own data, so nothing reaches your real account.

What your agent can do
  • Calls, recordings and transcripts
  • Speakers, topics and trackers
  • Deal and account links
  • Users and teams
  • Search and filters
Seeded state

Every run starts from a company that already has history. We seed:

  • Calls across every open deal
  • Transcripts with speakers and timestamps
  • Trackers and topics
  • Scorecards
In staging

Use Gong in staging, without using production.

1

Validate every action

The twin checks what the agent sends the way Gong would: required fields, permissions, rate limits, malformed input. Mistakes fail here, not in your account.

2

Start from a realistic state

Describe the company and the situation in plain English. Drizz seeds the twin to match, and resets it to that state before every run.

3

Replay tasks across tools

The Gong twin shares its people, customers and history with the other twins, so a task that touches three tools runs the way it would at work.

Point your agent at it

Swap the address. Your agent code stays the same.

Replace the live Gong endpoint with the twin’s. Everything your agent already does keeps working, on data that is yours to break.

  • Same API and MCP calls
  • Sign-in and its failures
  • Real errors
  • Rate limits
  • Permissions and rules
  • Connected data
  • Reset in one call
{
  "mcpServers": {
    "gong": {
      "type": "http",
      "url": "<twin MCP endpoint>",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

REST works on the same data. Both are reset with one call.

One company

Connected to the rest of the company.

Every call in Gong belongs to a deal in Salesforce or HubSpot, and to a contact who also has email threads and calendar invites.

17 of 20 runs passed. 3 broke a rule.

Run your agent on the Gong twin.