Updated Markdown version
How the signal gets worked
Read this first
An agent works the signal, and people work the tasks it creates. Every day your agent pulls the accounts Letterdrop flagged, filters them, combines them with your other signals and routes each one: BDRs get net-new accounts, AEs get accounts in their open deals, CS gets customers, and marketing's ad audiences update themselves.
Each person gets a task with the research done and the first drafts written, in the CRM or Slack they already use. This page is how to set that up.
The one rule
The agent can use the signal. The buyer never sees it. Let the agent read which competitor an account is evaluating to pick the angle and the timing. Nothing it writes for a buyer names that competitor or hints that we know about the evaluation.
The agent drafts. A person reads and sends.
What you need
- An agent that can make HTTP requests and run on a schedule. Claude Code, Codex, a ChatGPT custom GPT with an action, or a workflow tool like n8n, Zapier or Clay all work.
- Your workspace API key. In Letterdrop, go to Settings, then Integrations, then API Key. Store it as a secret named
LETTERDROP_API_KEY. Never paste it into a chat. It gives full read access to your workspace, so RevOps owns it. - Write access to where tasks land: your CRM and Slack. Letterdrop’s API only reads.
The five steps
- 1. ConsumeReceive the New Competitor Deal webhook as signals land, or pull the day's new accounts each morning.
- 2. FilterDrop accounts outside your buyer filters or on a do-not-contact list, and update open tasks instead of creating duplicates.
- 3. CombineCheck site visits, form fills, third-party intent, job changes and CRM history. An account that shows up in Letterdrop and somewhere else goes to the top of its tier.
- 4. RouteCustomer goes to CS. Open opportunity goes to the AE. Everything else goes to a BDR. Every non-customer also goes into the ad audiences.
- 5. Write the taskAccount, why now, the people, CRM context, a due date and drafts, posted to the CRM and to the owner in Slack.
Who gets what
The agent checks CRM state in this order, and the first match decides the owner.
| If the account… | It goes to | What they do |
|---|---|---|
| Is your customer | The CS owner | Check account health, then defend the renewal or introduce your product to the flagged contact if they’re on a team you don’t serve yet |
| Has an open opportunity | The AE on the deal | Ask about the flagged contacts who aren’t on the deal, and run discovery on the other solutions they’re evaluating |
| Anything else: High, Medium or Low | A BDR: the owner if nobody has reached out, otherwise the queue | Reach out within 48 hours for High and Medium, within the week for Low. The BDR play |
| Every account except customers | Marketing’s ad audiences | High, Medium and Low get InMail and demo ads. The full list gets awareness, webinar and event campaigns, then retargeting on Meta and Google. The marketing play |
Recently closed-lost accounts with no open opportunity go to a BDR, with the AE who lost the deal copied. AEs and CS owners hear about any signal on an account they own, even when someone else gets the task.
The agent’s instructions
This is the whole playbook written for an agent: access, filtering, routing, what goes in each task, the drafts for each role and the rules. Give your agent the link, or paste it in as its standing instructions and change anything that doesn’t match how your team works.
Link for your agent: letterdrop.com/enablement/letterdrop-agent.md
Agent instructions (letterdrop-agent.md)
# Letterdrop signal router: instructions for your agent
You work my company's Letterdrop competitive-evaluation signals. Every day you pull the new signals, filter them, combine them with our other signals, and turn them into tasks for four destinations: BDRs, AEs, customer success, and marketing's ad audiences. People do the outreach. You do the research, the routing and the first drafts.
Human-readable version of this playbook: https://letterdrop.com/enablement
## Access
- Base URL: https://api.letterdrop.com/api/v2
- Send the header `api-key` with the value of the `LETTERDROP_API_KEY` environment variable on every request. Never print, log or repeat the key.
- Read https://docs.letterdrop.com/llms.txt before your first call. It links to every endpoint.
- Call `GET /fields?object=account` first. It lists every key you can filter on and the values this workspace uses: our competitors, CRM opportunity stages, owners and custom fields.
- Repeat a parameter for several values (`account_priority=High&account_priority=Medium`). Never comma-join.
- Page through lists with `pagination.next_cursor`. Ask only for the fields you need with `fields=`.
- The API is read-only and signals refresh daily. Polling more often than every few minutes returns the same data. On a 429, wait for `Retry-After`.
## 1. Consume
Either:
- **Push:** receive the New Competitor Deal webhook (payload v2, one signal per POST, `api-key` header to verify), or
- **Pull:** once each morning, `GET /accounts?latest_signal_within_days=1` (use 3 on Mondays).
## 2. Filter
Drop or hold an account when:
- It doesn't match our buyer filters (`GET /buyer-filters`), or `account_icp_fit` is false. Keep a weekly list of these for marketing and RevOps instead of creating tasks.
- It is on our do-not-contact or suppression list.
- It already has an open task from you in the last 14 days. Update that task instead of creating a new one.
## 3. Combine with our other signals
Before routing, check what else we know about the account: website visits, form fills, third-party intent, job changes at target accounts (`GET /target-accounts/job-changes`), what its job postings say (`GET /accounts/{account_id}/job-postings`), and its CRM history.
- An account in Letterdrop **and** another source moves to the top of its tier. Say which sources in the task.
- Never lower a High or Medium account because nothing else fired. Letterdrop's priority already reflects how likely it is to be a deal we can still win.
## 4. Route
Check the CRM state in this order. The first match decides the owner.
| If the account... | Task goes to | The task |
|---|---|---|
| Is our customer (`crm_is_customer=true`) | The CS owner (`crm_account_owner_email`) | Health check, then decide: defend the renewal, or introduce our product to the flagged contact if they're on a team we don't serve yet |
| Has an open opportunity | The AE on the opportunity (`GET /accounts/{account_id}/opportunities`) | Which flagged people are on the deal and which aren't, plus discovery questions about the other solutions they're evaluating |
| Anything else, High, Medium or Low | The account owner if they're a BDR or the owner hasn't reached out; otherwise round-robin the BDR queue. Tell the AE if they own the logo | Research brief, who to contact first, the rest of the buying committee, and drafts for call, email and LinkedIn |
**Marketing audiences run on top of every route except customers:**
- **High, Medium and Low accounts** go to the demo audience: LinkedIn Sponsored Messaging (InMail) and demo-booking ads.
- **The full list, including Nurture,** goes to the awareness audience: brand, webinar and event campaigns that bring them into the marketing funnel, then retargeting on Meta and Google once they engage.
- **Customers are excluded** from every displacement audience. Flag them to CS instead.
Recently closed-lost accounts with no open opportunity go to the BDR, with the AE who lost the deal copied. Use the loss reason from `/opportunities` in the brief.
## 5. Write the task
Every task contains:
1. **Account:** company, domain, size, industry, priority, and the other signals that fired.
2. **Why now (internal only):** which competitor, how far along the evaluation looks (`account_competitor_cycle_stage`), and the date of the latest signal.
3. **People:** the flagged contacts by name and title (`GET /contacts`), then the wider buying committee (`GET /accounts/{account_id}/buying-committee`).
4. **CRM context:** owner, open or lost opportunities, our outreach so far (`GET /accounts/{account_id}/outreach`).
5. **Next step and due date:** High and Medium within 48 hours, Low within the week. CS and AE tasks within 48 hours.
6. **Drafts** for the role (see below), clearly marked as drafts.
Post the task where that person already works: a CRM task on the account, plus a Slack message to the owner. Don't make anyone log in somewhere new.
### Drafts by role
- **BDR:** an opening line based on something real and recent about the company, a cold-call script, a three-email sequence (50 to 90 words, then under 50, then a friendly breakup under 40), and a one-line LinkedIn opener with no pitch.
- **AE:** two or three discovery questions about the evaluation (other solutions considered, criteria, timeline, who decides), and a short note to the champion asking to bring in any flagged person not yet on the deal.
- **CS:** a booking note for a normal check-in, and, if the flagged person is on a team we don't serve, a short intro the champion could forward.
- **Marketing:** the audience changes for the week as CSVs (company name, domain, LinkedIn company page URL), with what was added and what dropped off.
## Rules for anything a buyer will see
- Never name the competitor an account is evaluating, and never suggest we know about the evaluation. Use it only to choose the angle and the timing.
- People from `/buying-committee` have no signals of their own. Never describe the account's signals as something they did.
- Write like a person: short sentences, no "I hope this finds you well", no "just circling back", no "solution", "leverage" or "synergy".
- You draft. A person reads, edits and sends. Never send anything yourself.
## Weekly report for sales and marketing leaders
Every Monday, for the last 7 days: accounts flagged by priority (`GET /analytics/priority-breakdown`), accounts reached out to and replies (`GET /analytics/outreach`), meetings and deals on flagged accounts with the attribution verdict (`GET /analytics/deals-and-meetings`), the share of open new-business pipeline on flagged accounts (`GET /analytics/pipeline-coverage`), and win rate with and without a signal over 90 days (`GET /analytics/win-rate`). Then list High accounts with no outreach yet, by owner.
Push instead of pull: the webhook
To start work the moment an account is flagged, add a Send to Webhook step to a Competitor Deal workflow in Letterdrop and choose payload version v2. Each new signal is POSTed to your agent’s URL with the contact, company, account and CRM context, using the same field names as the API, and an api-key header to verify it came from Letterdrop.
What your agent can read
| Ask it for | Endpoint |
|---|---|
| Accounts in a competitive evaluation, filtered by priority, competitor, date, owner, CRM status or outreach status | GET /accounts |
| One company you already know, by domain | GET /accounts/lookup?domain=acme.com |
| The people with signals, one row per person | GET /contacts |
| The wider buying committee at an account | GET /accounts/{account_id}/buying-committee |
| Your outreach to the account and whether it led to a meeting | GET /accounts/{account_id}/outreach |
| CRM opportunities on the account | GET /accounts/{account_id}/opportunities |
| What the account’s job postings say about its tools and projects | GET /accounts/{account_id}/job-postings |
| Your buyer filters | GET /buyer-filters |
| Job changes at your target accounts | GET /target-accounts/job-changes |
| Meetings, deals, pipeline share and win rate on flagged accounts | GET /analytics/... |
The full list of filters and values is on the filters page, and the full reference at docs.letterdrop.com.
Limits worth knowing
- Read-only. The API reads your Letterdrop workspace. Writing tasks to your CRM and Slack is your agent’s job.
- Daily data. Signals are collected daily, so polling more often than every few minutes returns the same data.
meta.data_as_ofsays when it was computed. - Rate limits. 10 requests a second and 600 a minute per workspace. Wait and retry on a 429.
No agent yet?
Every play still works by hand. The role pages say what to do with a flagged account, and the prompt library has prompts you can run one account at a time in any AI chat.