How to Find a Customer Success Manager's Email Address (2026)

The fastest way to find a Customer Success Manager's email is to look it up in a contact database, not to guess it. Search by company domain and title, enrich the person, then read the email status before you send. This guide does that against LeadOcean with curl and spends 2 records.

Examples use placeholders (Acme, acme.com, Jane Doe). Swap in your own domain.

TL;DR

• Customer Success Manager (CSM) emails come from three places: a database lookup, a pattern guess at the company domain, or the person's own public posts. Only the first gives you a deliverability status.
• Search by domain and title, enrich with reveal_email, and send only to verified or catch_all_valid addresses.
• Takes about 10 minutes and spends 2 of the 1,000 free records. Sizing the audience first costs nothing.

Prerequisites

• A LeadOcean account. The free plan gives 1,000 records one-off, no card: register here.
• An API key from the app, exported as $LEADOCEAN_API_KEY.
• curl and jq.

export LEADOCEAN_API_KEY="paste-your-key-here"

Every request goes to https://api.leadocean.io with the header x-api-key. A free key has both scopes, search and enrich.

Step 1: Size the CSM list before you pull it

Send count=true as a query parameter with limit 1 and the call returns a total without spending a record. Filters go in a flat JSON body, and every filter is an array of strings.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": ["Customer Success Manager"],
    "jobLevel": ["Manager"],
    "salesRegion": ["EMEA"],
    "limit": 1
  }' | jq '.meta | {total, totalIsExact, distinctCompanies}'

meta.total is capped at 100,000. Enum values are exact strings: Manager works, manager-level returns nothing. The regions are NORAM, LATAM, EMEA and APAC. Title values are keywords, so a title that contains those words also matches.

Step 2: Search for the CSM at one company

Add the company's domain to find the CSM at that account. Each person returned costs one record, so keep limit small.

curl -s -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": ["acme.com"],
    "title": ["Customer Success Manager"],
    "limit": 1
  }' > csm.json

jq '.data | length' csm.json

Wrap a title in square brackets, such as ["[Customer Success Manager]"], for an exact match. Search rows are thin: they carry has_email and has_phone flags, not the address itself.

If the company has no CSM titled that way, try jobFunction set to Customer/Client Service and read a sample. Titles vary: Customer Success Specialist, Account Manager and Client Success Manager all do similar work.

Step 3: Enrich the person to get the email

Each search row carries an id at meta.source_ids.person_id. Send it back to enrich that exact person. Enrich takes exactly one of linkedin_url, email, phone or person_id.

PID=$(jq -r '.data[0].meta.source_ids.person_id' csm.json)

curl -s -X POST "https://api.leadocean.io/v1/people/enrich" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"person_id\": \"$PID\", \"reveal_email\": true}" > person.json

This costs one record. reveal_email costs nothing extra and returns every email we hold for that person. If we hold nothing, you get a 404 and no charge. There is no lookup by name plus domain: search first, then enrich by person_id.

Step 4: Verify before you send

Read email_status and send only to addresses worth sending to. A verified or catch_all_valid status is safe. A catch_all status means the domain accepts everything, so the mailbox may not exist.

jq -r '.data.contact_data.contact_emails[]
  | select(.status == "verified" or .status == "catch_all_valid")
  | .email' person.json

Bounced emails are not refunded, so treat every other status as a no-send. The full list of statuses is verified, catch_all_valid, catch_all, risky, unknown, untested, invalid, role, disposable, spam_trap, abuse, derived and none.

Step 5: Use a pattern only when the lookup finds nothing

When a CSM is not in the data, guess at the company domain, then verify the guess before you send. These are the common patterns:

first.last@acme.com    jane.doe@acme.com
flast@acme.com         jdoe@acme.com
first@acme.com         jane@acme.com
firstl@acme.com        janed@acme.com

Find the pattern from any other address you already hold at that domain, then apply it to the CSM's name. Never send to a guessed address that has not been verified. A guess at a catch-all domain always looks valid and tells you nothing.

Two traps are specific to this role. A shared inbox such as success@ or support@ carries the role status and reaches a queue, not a person. And people change jobs, so check the record's fetched_at date and its still-at-company status before you rely on a job title.

What you get

The Step 1 count is free. The free MCP tool leadocean_count_leads ran these filters on 2026-10-21: title keyword Customer Success Manager, jobLevel Manager, split by salesRegion. It counts people with a verified, catch_all_valid or catch_all email by default, so these are mailable counts.

The four regions sum to less than the worldwide figure because some people carry no region. Each call returned totalIsExact: true and credits: 0. The worldwide count spans 766 distinct companies. These numbers cover people whose title contains the phrase and whose level is Manager, so a Senior CSM or a Head of Customer Success sits in another bucket. Read a sample before you build a campaign on the total.

A record-level response has the shape below (response shape from the API reference, placeholder values):

{
  "success": true,
  "data": {
    "profile_data": { "profile_full_name": "Jane Doe", "profile_headline": "Customer Success Manager at Acme" },
    "contact_data": {
      "has_email": true,
      "contact_current_experiences": [
        { "company_name": "Acme", "company_domain": "acme.com", "job_title": "Customer Success Manager" }
      ],
      "email_status": "verified",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ]
    }
  },
  "meta": { "source": "leadocean" }
}

Each record carries its own fetched_at date, and the dataset refreshes monthly. Check the date on anything you plan to act on.

Troubleshooting

FAQ