# Reach support leaders at companies hiring support agents

200 accounts and 400 people, about 252 verified work emails and 756 emails sent from inboxes on your own domain.

Family: [Hiring signals](https://www.routergrowth.com/workflows/hiring-signals.md) · HTML page: https://www.routergrowth.com/workflows/hiring-customer-support

## Give this to your agent

```text
Using RouterGrowth, run this workflow: Find companies hiring customer support agents and email their head of support. 200 accounts, 2 contacts each.
Show me the price before every call, and stop after each stage with a sample of the results so I can adjust.

1. Source on the hiring signal: company.jobs x 200 jobs. Open roles matching the title and location; each job is a company already spending on the problem.
2. Qualify on firmographics: company.enrich x 200 companies. Headcount, industry and location to keep the accounts that fit.
3. Find the people: people.search x 400 profiles. 2 contacts per account by title and seniority, with current role.
4. Get the contact: contact.find x 280 (400 tried, 70% found), contact.verify x 280 verdicts. Charged on a match only: a miss is free, so the estimate is a ceiling.
5. Context for the first line: web.scrape x 200 pages, social.posts x 1,200 posts. One page per account and a few recent posts per person, so the opener is about them.
6. Run the outreach: email.send x 756 (252 contacts x 3 steps). Sequence from inboxes on a domain you own, one call per email.
7. Read the replies: email.messages x 76 inbox reads. Poll the inboxes, classify replies, hand the warm ones to a human.

Before sending: email.domain x 1, email.inbox x 2, on a domain I own.

Budget for one run: about $14.38 plus $6.98 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
```

## Why this works

Support headcount grows when ticket volume outruns the team. The head of support would rather deflect tickets than keep hiring for them.

The first line, as your agent would write it:

> I noticed four support agent roles on your careers page. Is that volume growth, or are response times under pressure?

## The workflow, stage by stage

Source on the hiring signal → Qualify on firmographics → Find the people → Get the contact → Context for the first line → Run the outreach → Read the replies

| # | Stage | Calls | Cost |
|---|---|---|---:|
| 1 | Source on the hiring signal | `company.jobs` x 200 | $0.70 |
| 2 | Qualify on firmographics | `company.enrich` x 200 | $1.42 |
| 3 | Find the people | `people.search` x 400 | $0.15 |
| 4 | Get the contact | `contact.find` x 280, `contact.verify` x 280 | $5.79 |
| 5 | Context for the first line | `web.scrape` x 200, `social.posts` x 1,200 | $3.52 |
| 6 | Run the outreach | `email.send` x 756 | $2.65 |
| 7 | Read the replies | `email.messages` x 76 | $0.15 |
| + | One-time setup | `email.domain` x 1, `email.inbox` x 2 | $6.98 once |

One run: $14.38 for 3,592 calls. Assumptions: 2 contacts per account unless the brief says otherwise, 70% email find rate, 90% verification pass, 3 emails per contact, 30% LinkedIn accept rate. Prices are the catalog's at the time this page was built; `routergrowth inspect` returns the exact quote before a call.

### Source on the hiring signal

Open roles matching the title and location; each job is a company already spending on the problem.

### Qualify on firmographics

Headcount, industry and location to keep the accounts that fit.

### Find the people

2 contacts per account by title and seniority, with current role.

### Get the contact

Charged on a match only: a miss is free, so the estimate is a ceiling.

### Context for the first line

One page per account and a few recent posts per person, so the opener is about them.

### Run the outreach

Sequence from inboxes on a domain you own, one call per email.

### Read the replies

Poll the inboxes, classify replies, hand the warm ones to a human.

## Run it from the command line

```bash
# RouterGrowth workflow: Find companies hiring customer support agents and email their head of support. 200 account
npm install -g routergrowth && routergrowth setup

# one-time setup
routergrowth run -c email.domain -i '{"domain":"<domain>"}'
routergrowth run -c email.inbox -i '{}'

# 01 Source on the hiring signal  (company.jobs x 200)
routergrowth run -c company.jobs -i '{}'

# 02 Qualify on firmographics  (company.enrich x 200)
routergrowth run -c company.enrich -i '{"domain":"<domain>"}'

# 03 Find the people  (people.search x 400)
routergrowth run -c people.search -i '{}'

# 04 Get the contact  (contact.find x 280, contact.verify x 280)
routergrowth run -c contact.find -i '{"first_name":"<first_name>","last_name":"<last_name>","company_domain":"<company_domain>"}'
routergrowth run -c contact.verify -i '{"email":"<email>"}'

# 05 Context for the first line  (web.scrape x 200, social.posts x 1200)
routergrowth run -c web.scrape -i '{"url":"<url>"}'
routergrowth run -c social.posts -i '{"platform":"<platform>","handle":"<handle>"}'

# 06 Run the outreach  (email.send x 756)
routergrowth run -c email.send -i '{"inbox_id":"<inbox_id>","to":"<to>"}'

# 07 Read the replies  (email.messages x 76)
routergrowth run -c email.messages -i '{"inbox_id":"<inbox_id>"}'
```

## Questions

### How do I find companies that are hiring for a specific role?

company.jobs returns live job postings for a title and a location, with the company behind each one. Your agent runs it once per segment, removes duplicates and keeps the companies that fit your size and industry before any contact is looked up.

### Why is an open role a buying signal?

A posted role is a budgeted problem. The company has decided to spend on it, written the requirements down in the job description and named a team that owns it. The leader of that team is the buyer, and the description gives you the first line.

### Who should I contact at a company that is hiring?

The person the new hire will report to, plus one level up. people.search finds them by title and seniority at the company, and contact.find returns a work email that is charged only when one is found.

### How fresh is the hiring data?

Each run reads postings that are live when it runs. A workflow you schedule weekly only needs the new roles, so the second run costs a fraction of the first.

### What does this workflow cost to run?

About $14.38 for one run of 3,592 calls, plus $6.98 once for the sending inboxes. Each call is quoted before it runs and a lookup that finds nothing is not charged, so the figure is a ceiling. There is no subscription: the run is paid from a prepaid balance.

## Related

- [Reach HR leaders at companies hiring in-house recruiters](https://www.routergrowth.com/workflows/hiring-recruiters.md)
- [Reach CMOs at companies hiring performance marketers](https://www.routergrowth.com/workflows/hiring-marketing.md)
- [Reach data leaders at companies hiring analytics engineers](https://www.routergrowth.com/workflows/hiring-data-teams.md)
- [Reach engineering leaders at companies hiring DevOps and SRE](https://www.routergrowth.com/workflows/hiring-devops.md)
- Guide: [How to find high-intent leads from hiring signals](https://www.routergrowth.com/use-cases/find-high-intent-leads.md)
- Guide: [Buying signals: score accounts on hiring, funding and tech changes](https://www.routergrowth.com/use-cases/company-buying-signals.md)
- Skill: [Cold email pipeline](https://www.routergrowth.com/skills/cold-email-pipeline.md)
- Skill: [Hiring-signal outbound](https://www.routergrowth.com/skills/hiring-signal-outbound.md)

Adjust the volumes and assumptions: https://www.routergrowth.com/free-gtm-tools/workflow-generator#q=Find%20companies%20hiring%20customer%20support%20agents%20and%20email%20their%20head%20of%20support.%20200%20accounts%2C%202%20contacts%20each.