Back to course

Progress

No items found.

Learn and master Clay with Clay university

Featured in Clay University

All courses
/
/
Get Your Team Running with Clay in their AI tools
Lesson
3
/
About this lesson
00:00

Get Your Team Running with Clay in their AI tools

This lesson covers the full rollout: admin setup, access permissions, credit limits, and monitoring. You'll have a playbook for getting your team connected with the right guardrails in place, so no one can burn through all your credits.

🗺️ The Three-Phase Rollout

Phase 1: Configuration

RevOps sets permissions, credit limits, and builds the functions reps will access. If you haven't checked out the functions course yet, do that now—we'll link it in the written material.

Phase 2: Activation

Enablement: rollout plan, rep education, change management, hackathons—whatever gets people comfortable using the tools.

Phase 3: Adoption

Reps use it daily in their workflows to get more pipeline and close deals faster.

⚙️ Initial Setup & Configuration

The setup is roughly the same whether you're connecting ChatGPT, Claude, Glean, or any other tool. Platform-specific nuances are included in the written guide below.

Click MCP in the side nav to access the Clay MCP settings page where you'll find two main controls:

  • Access permissions
  • Credit limits

You'll also see a Salesforce sync option that maps Clay user IDs to Salesforce, allowing you to identify account ownership for visibility.

Note: Credit controls and usage monitoring are available on all modern paid plans (Launch, Growth, Enterprise) and Legacy Enterprise. Audiences controls are available to Enterprise customers enrolled in the Audiences Open Beta.

Recommended Setup Sequence

  1. Connect your Clay workspace to ChatGPT or Claude
  2. Set a global credit limit as the default for all reps
  3. Override that limit for specific reps as needed
  4. Monitor usage and adjust based on patterns

Enterprise AEs running heavy enrichment get more. New SDRs ramping up get less.

💳 Setting Credit Limits

Start conservative, then loosen up as you see usage patterns. Teams that set no limits on day one burn through a quarter's worth of credits in a week.

Baseline Recommendations

General baseline: 500 credits per rep per month for light prospecting use.

Heavy SDR users: 2,000 to 5,000 credits per month.

Monitor the first two weeks, then lock in permanent limits.

📊 Monitoring Usage

Once your team is live, the MCP settings page shows:

  • Credits used per rep
  • Which platform each rep is using
  • Access status for all users

🔧 Troubleshooting Common Issues

Rep doesn't see Clay in ChatGPT:

  • Check that access is enabled in the MCP settings
  • Confirm they're logged into the right account (ChatGPT or Claude)
  • Note: Want reps to have access to MCP but not Clay web? Use the sales rep permission role

Credits running out mid-session:

  • Per-rep credit limit is too low
  • Increase the individual limit in the MCP users section

Can't tell who's using what credits:

  • Credit cost breakdown lives in the function view, not the calling table
  • Navigate into each function from the function library to see per-action cost breakdown

Team burning through credits faster than expected:

  • Set global limit and tighten per-rep overrides
  • Check usage patterns to see where spend is going

🔜 What's Next

In the next lesson, we'll cover how to package your best workflows as custom functions so reps can call them directly from ChatGPT or Claude.

Next up

View next lesson