# Account Allocation
Source: https://docs.getwhitewhale.com/account-allocation
Assign accounts to team members — one at a time or in bulk.
## Reassign one account
Find the account in your list, click the **Owner** name, and select a different team member from the dropdown. The change takes effect immediately.
## Reassign in bulk
Select multiple accounts using the checkboxes, then click **Assign Owner** at the bottom. Choose the new owner and all selected accounts are reassigned at once.
If your CRM is connected, ownership changes in WhiteWhale will sync to your CRM automatically.
## Assigning accounts from Suggestions
If you want to assign new accounts to team members as they come in from Account Suggestions — including round-robin distribution — that's handled separately in the Suggestions flow.
Set up round-robin assignment or direct allocation when accepting accounts from Suggestions.
## Related
Add accounts to your team's book of business.
Let WhiteWhale surface and assign net-new accounts automatically.
Understand what each team role can see and do.
# Account Scoring Explained
Source: https://docs.getwhitewhale.com/account-scoring-explained
Understand how WhiteWhale scores accounts based on signal recency, volume, and priority. Learn what a good score looks like and how to use it to prioritize.
Every account in WhiteWhale gets a score from 0 to 100. The score tells you how recent and how relevant the signal activity is on that account — and by extension, how worth your time it is right now.
## What the score actually means
The score is a proxy for signal density and recency. A higher score means more of your signals have fired recently, and that those signals are higher priority.
A perfect score of 100 would mean every single one of your signals fired on that account in the last 30 days simultaneously. In practice, that's nearly impossible — it would require a company to have a new CRO, be hiring for five different roles, shift their go-to-market motion, and hit every other signal you track all at the same time.
Most accounts will never score above 60. That's completely normal and expected.
## What good looks like
| Score range | What it means |
| ----------- | ---------------------------------------------------------------------------------------------------------- |
| **0–10** | Few or no signals. Not worth prioritizing right now. |
| **10–30** | The typical range for a solid account with real signal activity. Most of your workable accounts live here. |
| **30–50** | VERY Strong signal activity — multiple recent, high-ranked signals. Worth prioritizing. |
| **50–100** | Exceptional. Rare. Multiple high-priority signals firing simultaneously in a short window. |
Don't anchor to a fixed number. Spend a week clicking through your accounts and you'll quickly develop a feel for what a "good score" means for your specific signal set. Every team's baseline is a little different.
## What drives the score up
Two things push a score higher:
* **Recency** — signals that fired in the last 30 days count more than older ones
* **Signal rank** — High-ranked signals contribute more to the score than Low-ranked ones
An account with one High-ranked signal that fired yesterday will outscore an account with five Low-ranked signals that fired six months ago.
## What the score is not
The score is not a lead score, a revenue predictor, or a guarantee of fit. It's purely a signal-activity indicator. An account can score low and still be a great prospect — it just means nothing notable has happened recently that WhiteWhale detected. Conversely, a high score means the timing looks good, not that the deal is certain.
Use it as a prioritization tool, not a qualification filter.
## Related
Understand what WhiteWhale monitors and how signals are detected.
Find your accounts with the freshest signal activity.
Better signals lead to more meaningful scores.
Save filtered views by score range to work your highest-priority accounts first.
# Adding Accounts
Source: https://docs.getwhitewhale.com/adding-accounts
Upload accounts to WhiteWhale, assign them to your team, and optionally clean the list using signals before they go live.
## How to add accounts
From the Accounts page, click **New Search** in the top nav.
Give the list a name — something that describes what these accounts are. For example: *Jack's Territory*, *Closed Lost Q1*, *Enterprise Targets*.
Paste in company domains in any format — line by line, comma separated, straight from a CSV. WhiteWhale cleans them up automatically.
Select who these accounts should be assigned to. You can assign them to yourself or to anyone else on the team — useful if you're uploading lists for other reps.
Tag the batch to keep things organized. Examples: *Enterprise*, *Working*, *Closed Lost*, *Reached Out*. Tags make it easy to filter and build segments later.
WhiteWhale starts scanning immediately. Accounts that already exist in the system will appear right away. The rest will populate as they finish scraping — signals, details, and the Why Now will show up as they're ready.
## If you have a big list, find the best accounts
If you have more accounts than credits — say 5,000 domains but only 300 credits — WhiteWhale won't let you upload the full list directly. You need to tell it how many to add.
From the Accounts page, click **New Search** in the top nav.
Give the list a name — something that describes what these accounts are. For example: *Jack's Territory*, *Closed Lost Q1*, *Enterprise Targets*.
Add all the domains you have — even thousands.
Click **Advanced Settings** below the domain input box.
Enter the number of accounts that fits your credit limit. WhiteWhale will scan the full list and activate the best-scoring accounts based on your signals. The rest will appear as suggestions so you can review them later or activate them when you have more credits.
If you want to filter the list further before WhiteWhale picks the best ones, toggle on **Clean the List**. This lets you add signal requirements (accounts must have at least one of your selected signals) and firmographic filters (employee count, geography, industry) so only accounts that pass your criteria are even considered.
WhiteWhale scans the full list, applies your filters if set, and activates the top accounts up to your limit.
**Advanced Settings** sets *how many* accounts to add. **Clean the List** controls *which* accounts qualify. Use Advanced Settings alone when you trust WhiteWhale to pick the best ones by signal score. Add Clean the List on top when you want to enforce specific criteria first.
## A third way: Account Suggestions
WhiteWhale can also recommend net-new accounts you haven't thought of yet based on your signals and ICP. See [How Account Suggestions Work](/how-account-suggestions-work) to set that up.
## Related
Free up account slots without permanently removing accounts.
Permanently delete accounts from your list.
Assign accounts across your team.
# Adding Users
Source: https://docs.getwhitewhale.com/adding-users
Invite unlimited team members to WhiteWhale at no extra cost. Configure roles, permissions, and account visibility so every rep sees the right signals.
## How to add a user
Click **Team** in the left nav.
Enter the new user's name and email address.
Choose between **Super Admin** or **Member**. See the role guide below.
WhiteWhale will automatically send the user a login email with everything they need to get set up.
## Roles
Super Admins can see all accounts across the entire platform, regardless of who they're assigned to. They can also edit signals and manage Account Suggestions.
**Best for:** Sales leadership, RevOps, go-to-market engineers, or anyone who needs a full view of the team's book of business.
Members only see accounts assigned to them. They work their own list without visibility into other reps' accounts by default.
**Best for:** Individual AEs and SDRs working their own territory.
Members can be further configured with two optional permissions:
* **Admin access** — grants the member elevated permissions within the platform
* **Viewer access** — lets the member view another specific user's accounts without being assigned to them. Useful for SDR/AE pairs where the SDR needs visibility into the AE's accounts, or for SDRs working multiple AEs at once.
## Who gets which role
| Role | Super Admin | Member |
| -------------------------------- | ----------- | -------------------------- |
| Sees all team accounts | ✓ | ✗ |
| Sees only assigned accounts | — | ✓ |
| Can edit signals | ✓ | ✗ |
| Can manage Account Suggestions | ✓ | ✗ |
| Can view another user's accounts | ✓ | ✓ (with viewer permission) |
## Related
Remove a team member from WhiteWhale.
Full breakdown of what each role can access and do.
Assign accounts to team members after they've been added.
# Fixing/Improving Searches
Source: https://docs.getwhitewhale.com/adjusting-your-suggestions
Tune your account searches to surface better-fit accounts and fix common issues.
Account Suggestions will never be perfect — but with a few adjustments, 80–95% of what surfaces should be accounts you'd actually want to work. This page covers how to tune your searches when results are too broad, too narrow, or just slightly off.
## Providing feedback on individual accounts
When a suggestion isn't a fit, click the **X** next to the account to reject it. WhiteWhale will ask you why — too big, too small, wrong industry, wrong signals.
Based on your feedback, the system will prompt you to edit the search directly. For example, if you reject an account because it's the wrong industry, WhiteWhale will open the industry filter so you can remove the one that doesn't fit.
Over time, this feedback loop tightens your results without you having to think about the filters separately.
## Editing your search
You can update any live search at any time. Click into the search and adjust your signal selections, time range, company size, industry, or location. The search will re-run automatically with the new parameters.
WhiteWhale will also throw warnings in the search builder if your parameters are too narrow or too broad — and tell you what to fix.
## Common problems and how to fix them
Usually caused by one of these: **Too many Must Have signals.** If you require five signals, an account needs all five to appear. Four out of five won't show up. Switch to **Any Match** (the light purple default) unless you have one specific signal that's a hard requirement.
**Signals that don't logically co-exist.** If you require both VC funding and PE investment as Must Haves, that's a rare combination that doesn't make practical sense. Make sure your Must Have signals would logically appear together on a real account.
**Too few companies in the search pool.** If you're searching for software companies in Bermuda, there are only two. WhiteWhale can't find 200 suggestions from a pool of two. Widen your location or industry filters to increase the pool. The sweet spot is somewhere between a few hundred and 20,000 companies.
Your search pool is probably too large. If WhiteWhale is scanning 800,000 or a million companies, it takes time to work through all of them. Results will trickle in rather than flood in. Narrow your filters — tighten industry, location, or company size — to bring the search pool down to the 20,000 or under range. You'll see faster, higher-quality results.
Your firmographic filters need refinement.
* **Wrong industry** — click reject on a bad account, tell WhiteWhale it's the wrong industry, and it will prompt you to edit the industry filter directly
* **Wrong size** — tighten the employee count range
* **Wrong geography** — check your location filter for regions you don't actually serve
The search finds accounts that match your signals — if the signals aren't specific enough, the matches won't feel relevant. Tighten up the signal descriptions or add context. See [Improving Signals](/improving-signals) for a guide on making signals more precise.
## Experiment freely
There's no limit on how many searches you can create. Run different variations — test different signal combinations, industries, and company sizes — and see what comes back. Keep the ones that produce good results. Delete the ones that don't.
The best search setup is usually 2–3 signals set to Any Match, in the industries you win in most, with a company pool between a few hundred and 20,000. Start there and adjust based on what you see.
## Related
Reject suggestions to help WhiteWhale improve your search results.
Create a new search from scratch.
Better signals lead to better search results.
# API Reference
Source: https://docs.getwhitewhale.com/api
Access WhiteWhale data programmatically via REST API. Pull accounts, signals, scores, and Why Now summaries into any workflow. Full endpoint reference included.
## Overview
The WhiteWhale API gives you full programmatic access to your account data, signals, users, and Account Suggestions. Common use cases:
* Pipe WhiteWhale data into tools not covered by native integrations
* Build your own CRM integration
* Automate account uploads and status changes
* Embed WhiteWhale signal data into your own platform or internal tooling
**Base URL:** `https://app.getwhitewhale.com/v1`
**API Docs:** [https://app.getwhitewhale.com/api\_docs](https://app.getwhitewhale.com/api_docs)
***
## Authentication
Every request requires two headers:
| Header | Description |
| --------- | ------------------------------------------------ |
| `api-key` | Your WhiteWhale API key |
| `user` | The email address of the user making the request |
```bash theme={null}
curl -H "api-key: YOUR_API_KEY" \
-H "user: you@company.com" \
https://app.getwhitewhale.com/v1/get_user_data
```
### Getting your API key
The API key is **shared across your whole team** — one key per WhiteWhale instance.
Click **Settings** in the left nav.
Find the **API & Webhooks** section — it manages both programmatic access and event delivery.
Your active API key will appear. Copy it and store it securely for the team.
![Generating Api Key]()
Keep your API key secure and do not share it publicly or commit it to version control. Anyone with this key has full API access to your WhiteWhale instance.
***
## Rate limits & global errors
**Rate limit:** 600 requests per minute, global across all routes.
| Status code | Meaning |
| ----------- | --------------------------------------------------------------------- |
| `401` | Authentication failed — API key missing, incorrect, or user not found |
| `404` | User or resource not found |
| `429` | Rate limit exceeded |
***
## Endpoints
### Accounts
Returns WhiteWhale data for your accounts. Filter by specific domains, status, or ICP. Includes signal data and account details.
**Key parameters:**
| Parameter | Type | Default | Description |
| ---------------- | ------- | ------- | ------------------------------------------------------------ |
| `account_filter` | array | `[]` | Filter to specific account domains |
| `status` | string | `all` | Filter by status: `active`, `archived`, `farsight`, or `all` |
| `signal_data` | boolean | `true` | Include signal data in response |
| `lite` | boolean | `false` | Return lightweight response without full account data |
| `limit` | integer | `100` | Max accounts to return |
| `offset` | integer | `0` | Pagination offset |
| `icp_id` | string | — | Filter to a specific ICP |
**Response:** Array of `Account` objects including name, score, status, signal answers, and account details (LinkedIn URL, industry, employee count, etc.)
Upload one or more accounts by domain. By default, accounts are first sent to Account Suggestions for pre-scoring before being activated.
**Body:**
| Field | Type | Required | Description |
| ---------- | ---------------- | -------- | ---------------------------------------------------------------------------------------------- |
| `accounts` | array of strings | ✅ | List of account domains to upload |
| `farsight` | boolean | — | Default `true` — sends to Account Suggestions first. Set to `false` to add directly as active. |
| `icp` | string | — | ICP to upload accounts to. Default: `Master` |
If `farsight: true` (default), uploaded accounts land in Account Suggestions and must be activated. If you have a webhook configured, you'll receive a pre-score payload when they're ready. If `farsight: false`, accounts are immediately active and will consume credits.
Change the status of one or more accounts. Activating accounts consumes credits.
**Body:**
| Field | Type | Required | Description |
| ------------ | ---------------- | -------- | ------------------------------------------ |
| `accounts` | array of strings | ✅ | Account domains to update |
| `new_status` | string | ✅ | `active`, `archive`, or `delete` |
| `icp` | string | — | ICP to apply changes to. Default: `Master` |
Pass in a list of raw URLs and get back the normalized domains as WhiteWhale will store them. Useful for validating your input before uploading.
**Body:**
| Field | Type | Required | Description |
| ---------- | ---------------- | -------- | ----------------------------- |
| `accounts` | array of strings | ✅ | Raw account URLs to normalize |
***
### Signals
Returns the list of signal question formats the platform supports. Use these to validate signal text before adding via the API.
**Response:** Array of `Template` objects with the question format, a title, whether the template is complete, and examples for templates with placeholders.
```json theme={null}
{
"templates": [
{
"title": "M&A",
"question": "Did {account} recently acquire or merge with another company?",
"complete": true
},
{
"title": "Hiring",
"question": "Is {account} hiring for <>?",
"complete": false,
"examples": [
"Is {account} hiring for engineers?",
"Is {account} hiring for any sales positions?"
]
}
]
}
```
Add one or more signals programmatically. Signals must match a template format from `/v1/get_signal_templates`, unless `ignore_templates: true` is set.
**Body:**
| Field | Type | Required | Description |
| ------------------ | ------- | -------- | --------------------------------------------------------------------------------- |
| `signals` | array | ✅ | Array of signal objects (see below) |
| `ignore_templates` | boolean | — | Default `false`. Set to `true` to add custom signals outside the template format. |
**Each signal object:**
| Field | Type | Required | Description |
| -------- | ------ | -------- | -------------------------------------------------------------------- |
| `signal` | string | ✅ | The signal question text |
| `name` | string | ✅ | A unique name for the signal within the ICP |
| `icp` | string | ✅ | Name of the ICP to add the signal to |
| `q_rank` | number | — | Signal rank: `0` (disqualify), `0.1` (low), `1` (normal), `6` (high) |
**Signal rank behavior:**
* `0` — any account matching this signal is set to an arbitrary negative score. Use to disqualify accounts.
* `6` — Account Suggestions uses High-ranked signals to find new accounts. At least one signal of rank `6` is required for Account Suggestions to work.
Delete a signal from an ICP by signal ID. Retrieve signal IDs from `/v1/get_user_data`.
**Body:**
| Field | Type | Required | Description |
| ----------- | ------ | -------- | ---------------------------- |
| `signal_id` | string | ✅ | UUID of the signal to delete |
***
### Users
Returns signals, ICPs, remaining credits, and active account count for the authenticated user.
**Response:** `UserOverview` object with:
* `icps` — list of ICP names
* `icp_id_dict` — map of ICP name → ICP ID
* `signals` — all signals across the user's ICPs
* `credits_remaining` — remaining account credits
* `active_accounts` — current active account count
Returns an array of `UserOverview` objects for every user in your WhiteWhale instance. Requires admin authentication.
Programmatically invite a new user to your WhiteWhale instance.
**Body:**
| Field | Type | Required | Description |
| -------------- | ------- | -------- | -------------------------------------------------------------------- |
| `email` | string | ✅ | Email address for the new user. Stored entirely lowercase. |
| `email_alerts` | boolean | — | Default `false`. Set to `true` to enable email alerts for this user. |
**Errors:** `403` if out of user seats. `409` if a user with that email already exists.
Remove a user from your instance. Requires the authenticating user to be an admin.
**Body:**
| Field | Type | Required | Description |
| ------- | ------ | -------- | --------------------------- |
| `email` | string | ✅ | Email of the user to delete |
**Errors:** `403` if the user is not in your organization.
***
### Account Suggestions (ICP)
Returns details for one or all ICPs in your instance, including signals, Account Suggestions mode, and constraints.
**Parameters:**
| Parameter | Type | Description |
| --------- | ----- | -------------------------------------------------------------------------- |
| `icp_ids` | array | Optional. ICP IDs to fetch. If omitted, returns all ICPs in your instance. |
Creates a new ICP as a child of your Master ICP. The new ICP inherits the Master ICP's signals.
**Body:**
| Field | Type | Required | Description |
| ---------- | ------ | -------- | ------------------------------------- |
| `icp_name` | string | ✅ | Name for the new ICP. Must be unique. |
**Errors:** `400` if an ICP with that name already exists.
Switches one or more accounts to a different ICP.
**Body:**
| Field | Type | Required | Description |
| ------------ | ------ | -------- | ------------------------------- |
| `accounts` | array | ✅ | Account domains to move |
| `target_icp` | string | ✅ | Name of the ICP to move them to |
This operation can take as long as adding a new account. Plan accordingly for large batches.
Deletes an ICP and all its associated accounts and signals. Cannot be used to delete a Master ICP.
**Body:**
| Field | Type | Required | Description |
| -------- | ------ | -------- | ------------------------- |
| `icp_id` | string | ✅ | UUID of the ICP to delete |
**Errors:** `400` if ICP not found for user. `403` if attempting to delete a Master ICP.
Activates or deactivates Account Suggestions for an ICP.
**Body:**
| Field | Type | Description |
| -------- | ------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `icp_id` | string | ICP to update |
| `state` | string | `"false"` (off), `"limited"` (only scans uploaded accounts), or `"unlimited"` (scans the full internet within your constraints) |
At least one signal of rank `6` (High) is required for Account Suggestions to find new accounts. Account Suggestions runs automatically at 3:00 UTC daily. To trigger immediately, use `/v1/icp/run_farsight`.
Triggers an immediate Account Suggestions run for the specified ICP. Can only be called once every 2 hours.
**Body:**
| Field | Type | Required | Description |
| -------- | ------ | -------- | ---------------------------------- |
| `icp_id` | string | ✅ | ICP to run Account Suggestions for |
Update the geography and industry constraints for Account Suggestions. Filters take effect immediately and will reject any queued accounts that fall outside the new parameters.
**Body:**
| Field | Type | Required | Description |
| ------------------------ | ------ | -------- | ------------------------------------------------- |
| `icp_id` | string | ✅ | ICP to update |
| `filter_list` | array | ✅ | List of countries, states, or industries to apply |
| `inclusion_or_exclusion` | string | ✅ | `"inclusion"` or `"exclusion"` |
| `list_type` | string | ✅ | `"country"`, `"state"`, or `"industry"` |
Use ISO 3166-1 alpha-2 codes for countries, two-digit codes for US states. Retrieve valid codes from `/v1/utilities/location_codes` and valid industries from `/v1/utilities/industries`.
Sets minimum and maximum employee count for Account Suggestions. Accounts outside this range are automatically rejected.
**Body:**
| Field | Type | Required | Description |
| -------- | ------- | -------- | ------------------------------------ |
| `icp_id` | string | ✅ | ICP to update |
| `min` | integer | — | Minimum employee count. Default: `0` |
| `max` | integer | — | Maximum employee count. Default: `0` |
***
### Webhook
Sets the webhook endpoint for your account. WhiteWhale will POST signal and account events to this URL automatically.
**Body:**
| Field | Type | Required | Description |
| ------------- | ------ | -------- | ---------------------------------------- |
| `webhook_url` | string | ✅ | The URL WhiteWhale should send events to |
See the [Webhooks](/webhooks) page for full payload documentation.
Sends a test payload to your registered webhook endpoint and returns the payload in the response so you can inspect it.
**Body:**
| Field | Type | Required | Description |
| --------------- | ------- | -------- | --------------------------------------------------------------------------------------------------- |
| `event_type` | string | ✅ | `"account.upload"` or `"account.signal"` |
| `spoof_payload` | boolean | — | Returns a fake payload with the correct data structure. Requires at least one signal on an account. |
| `icp_name` | string | — | If provided, returns a real signal and account name instead of spoofed data. |
The payload returned via this route is unsigned. The actual test payload delivered to your webhook endpoint will be signed.
***
### Utilities
Returns a dictionary of valid country and state codes accepted by the API. Use these when setting Account Suggestions geography constraints.
Returns all valid industry strings accepted by the API. Maps to LinkedIn's industry taxonomy.
***
## Related
Full payload reference and setup guide for WhiteWhale webhook events.
Connect WhiteWhale to Clay via webhook or CSV export.
Native HubSpot integration for CRM sync.
Native Salesforce integration for CRM sync.
# Archiving Accounts
Source: https://docs.getwhitewhale.com/archiving-accounts
Free up account credits by archiving accounts you're no longer actively monitoring.
Archiving pauses an account and returns its credit slot so you can add a new account in its place. All historical signal data is preserved — archiving is not the same as deleting.
## How to archive an account
Locate the account you want to archive.
Click the **Monitoring** status on the account and hit **Archive**. The account is immediately paused and the credit slot is freed up.
## What archiving does
* Stops the account from being monitored — no new signals will fire
* Frees up one credit slot for a new account
* Preserves all historical signal data — you can still view everything that was found before archiving
## Tracking your credits
You can see your current credit usage on the **Searches** page. It shows how many credits you have left, how much space is available, and lets you add more credits if needed.
Credits reset every month, so you can rotate your full account list — archive your current accounts at the end of the month and add a fresh set.
You can only archive each account once per month. You cannot archive and re-add the same account repeatedly within the same billing period unless you use another credit.
## Related
Add a new account after freeing up a slot.
Permanently delete an account and its signal data.
Understand how account credits work and when they reset.
# Assigning Suggestions
Source: https://docs.getwhitewhale.com/assign-suggestions-round-robin-etc
Activate suggested accounts and assign them to your team — individually, in bulk, or via round-robin.
In your search results, you'll see two types of accounts — monitored accounts (already active) and suggestions shown in orange (found by WhiteWhale but not yet tracked). Activating a suggestion turns it into a monitored account with full signal data, Why Now summaries, and live updates.
## How to activate suggestions
Use the checkboxes to select individual suggestions or select all at once. WhiteWhale will show you how many of your selection are suggestions vs. already monitored.
You'll be prompted to choose how to assign them.
* **Assign to one person** — all selected accounts go to a single team member
* **Round-robin** — accounts are evenly split across your team
Once activated, the accounts switch from suggestions to monitored. This means they get live updates, new signals, and full Why Now summaries — all the details that were locked behind the preview unlock.
Try to activate as many suggestions as your plan allows. Monitored accounts get live signal updates every day — suggestions don't. The sooner you activate, the sooner you know when something changes.
## Related
Reassign ownership of accounts already in your active list.
Tune your search filters to improve suggestion quality.
Understand how activating suggestions uses credits.
# Best Outreach We've Seen
Source: https://docs.getwhitewhale.com/best-outreach-we-ve-seen
See how top sales teams turn WhiteWhale buying signals into booked meetings. Includes a proven outreach framework, real email examples, and messaging tips.
The best teams using WhiteWhale get meetings from calls, emails, and LinkedIn notes. Most use a mix of all three. What separates them from everyone else isn't the channel — it's that they know exactly which accounts to go after and exactly why to reach out right now.
## Start with better accounts
Think about it this way. You have two bags of accounts.
**Bag one:** 10 accounts pulled from a traditional sales tool. Filtered by industry, employee count, geography. Solid parameters.
**Bag two:** Those same 10 accounts — same filters — but every account also has a signal. A new leader just came in. They're talking publicly about a problem you solve. They launched a product in a market where they need what you sell.
Which bag performs better?
The signal bag — every time. And the reason is simple: a signal implies a potential problem. It's not a random account that fits your ICP on paper. It's an account where something is happening right now that creates a real need.
Reading between the lines of multiple signals is where you get the full picture. A new CFO coming in after a merger means someone is probably buried in reconciling books that weren't done well. A company investing in a new market means they're hiring, scrambling, and trying to move fast. A new product launch means they have goals to hit that they haven't hit yet.
Every signal gives you something to read into. Your outreach should reflect that.
## The framework that works
The best messages from WhiteWhale follow this structure every time:
What did you observe? What specific signal did you see?
What does that signal imply about the problem they're likely facing? Read between the lines.
How have you solved that exact problem before?
Give them a reason to respond. A 1-pager, a specific resource, something tangible and low-commitment.
**The formula:** *(I noticed you were doing X) → (I bet that causes Y problem) → (Here's how we help) → (Lead magnet)*
## A real example
Here's this framework in practice — a LinkedIn note from a rep selling a sales coaching platform:
Jeff —
I wouldn't reach out if I hadn't done my homework. Saw you were hiring for 5 inbound SDRs that are doing demos.
I'm not a gambler, but I'd bet you're thinking about how to ramp those reps as fast as possible so they can start taking meetings and generating pipeline. Usually the problem is teaching them all the nuance of the demo calls and the product pitch.
If that's something you're thinking about, I built a live call analysis program that makes sure reps never miss an important question to ask or key point to drill into. I have a 1-pager I specifically made for your company that shows screenshots of the system in action and what your reps would see.
Want me to send it over?
Notice what this message doesn't do: it doesn't pitch features, it doesn't ask for 30 minutes, and it doesn't lead with the company name. It leads with *show me you know me* — evidence that the rep did their homework — and makes a single low-friction ask at the end.
## What to expect when you do this right
Before WhiteWhale, most reps are working a random selection of accounts. No idea if the timing is right. No signal to reference.
When you layer in the framework above — personalized to the specific signal — the conversion rate goes up not just because you're showing the prospect you understood their situation. You're also reaching out to accounts more likely to be in-market. It will never be 100%, but this kind of research goes a long way.
Use the Why Now summary as your research foundation. It connects the dots between all the signals on an account and gives you the "I noticed" and "I bet" in one place. Copy it into Claude or ChatGPT and ask it to help you turn the story into a message.
***
## From signal to booked call — a partner playbook
*The following playbook is from [Advanced Client](https://www.getwhitewhale.com/partner/advanced-client), a WhiteWhale Elite Agency partner that builds AI-native GTM systems for B2B companies.*
A signal is only worth something if someone acts on it. Here are two plays for getting from "a signal fired" to "a rep is having a relevant conversation" — pick the one that matches how your team works.
### Play 1: The manual play
Good if you want to keep things simple and let your reps drive.
A new signal lands in your Slack, email, or the WhiteWhale platform.
Use LinkedIn Sales Navigator to find the decision-makers at that account.
Find their phone numbers and emails.
Add the contacts to your CRM and include the signal data so the rep knows exactly why this account is worth their time.
Simple, fast to start, no extra tooling. The trade-off is it relies on someone manually working each signal as it comes in.
### Play 2: The automated RevOps play
This is Advanced Client's recommended setup. It takes the manual work out of the first few steps so your team only spends time on the conversations that matter.
Use WhiteWhale's webhook to send every new signal straight into a Clay table the moment it fires.
Configure the Clay table to search for your ICP at that account — sales leaders, founders, heads of marketing, whatever titles you target. They get found and added automatically.
Run Clay's waterfall enrichment (10+ providers) to source a valid email and phone number for each contact.
From here you have two options:
**Option A: Rep-led** — Push the enriched contact into your CRM, assign it to the right rep, and pass the signal data across so they can reach out with relevance.
**Option B: Fully automated** — Use a Claygent to write a personalized email from the signal data, then push the contact and the AI-written message into your email and LinkedIn tool to kick off a sequence automatically.
### Stacking signals in your message
The more signals you can reference, the stronger your message. A single signal is good. Two or three stacked together tells a story that's impossible to ignore.
Hey Steve, reaching out because of your recent funding round (congrats). It made sense to get in touch now you've just brought Sarah in as CRO, because we help with \[xyz].
Funding round plus a new exec hire plus hiring for sales roles tells a far stronger story than any one signal on its own. Layer them up wherever you can.
Want help setting up the automated play end to end? Advanced Client builds the Clay tables, enrichment, routing, and sequences so your WhiteWhale signals turn into booked calls without your team having to wire it together.
***
## Related
Get the full signal story on an account before you write a word.
Connect WhiteWhale to Clay via webhook for the automated play.
Find the accounts with the freshest signal activity.
Find the signals most likely to surface buying moments for your ICP.
# Clay
Source: https://docs.getwhitewhale.com/clay
Connect WhiteWhale to Clay via webhook to automatically send buying signals into your enrichment and outreach workflows. Step-by-step setup guide included.
WhiteWhale connects to Clay via webhook. Every morning when a new signal fires, WhiteWhale automatically sends the full signal payload to your Clay table — no manual exports, no copy-pasting.
## What's included in the payload
Each webhook event includes everything you need to build enrichment flows and run outreach from Clay:
* Company URL and LinkedIn URL
* All active signals for the account — not just the new one, but the full history
* The Why Now summary
* Signal sources, quotes, and facts
* Current account owner (if you have multiple users)
## How to connect
In your Clay table, add a new data source and select **Webhook**. Clay will generate a webhook URL for your table.
If you haven't done this before, Clay's webhook setup guide walks through the full process — see the link below.
Copy the URL Clay provides for your table's webhook source.
In WhiteWhale, go to **Settings** and scroll down to **Webhook Settings**. Paste the Clay webhook URL into the field and click **Continue**, then **Save**.
From this point forward, every new signal that fires will automatically send a payload to your Clay table each morning.
The payload includes all signals on the account, not just the one that triggered the webhook. This gives you the full context to build a complete Why Now story inside Clay before running any enrichment or outreach.
## What to build in Clay
Once the data is flowing, you can use the WhiteWhale payload fields to power enrichment flows. A common setup:
* Pull **company name** and **owner** from the WhiteWhale payload
* Use the **company URL** to find contacts and enrich with email, title, and LinkedIn
* Build outreach sequences triggered by specific signals in the payload
## One-off export: get your accounts into Clay now
If you want to get your existing accounts into Clay without waiting for the webhook to run, you can export them directly as a CSV.
Use the checkboxes to select the accounts you want to export. You can select individual accounts or all accounts at once.
WhiteWhale will download a CSV with your selected accounts and their signal data.
In Clay, create a new table and import the CSV file as your data source.
Clay's full guide to importing and working with CSV data sources.
Use the webhook for ongoing automation and the CSV export for one-time imports or backfills.
***
## Clay webhook documentation
Clay's full guide to setting up and working with webhook data sources.
## Related
Full reference for the WhiteWhale webhook payload and how to register endpoints.
Access WhiteWhale data programmatically via the API.
Understand what data WhiteWhale collects before building flows around it.
# Creating Signals
Source: https://docs.getwhitewhale.com/creating-signals
Create custom buying signals in WhiteWhale by typing a plain-English description or browsing the Signal Library for proven templates across dozens of categories.
There are two ways to add a signal: write your own using the description box, or pick one from the Signal Library. Both start from the **Signals** page in the left nav.
## Option 1: Describe it yourself
This is the fastest way to add a signal when you already know what you're looking for.
From the Signals page, click **Add Signal** in the top right.
Type your idea in plain language — no need to format it as a question. Examples:
* *I want to know if they're hiring for marketing roles*
* *I want to know if their CEO just talked about the team needing to use AI*
* *Did they just open 2 new offices in London?*
You can describe multiple ideas at once. WhiteWhale will generate a separate signal for each one.
Click **Generate Signals**. WhiteWhale will translate your description into the question format the platform uses and show you a preview with an explanation of how it was formatted.
For each generated signal, assign a rank: **Low**, **Medium**, or **High**. This controls how prominently matching accounts surface in your queue.
Click **Add Signal**. WhiteWhale will immediately begin scanning your existing accounts and updating your queue. You'll see a loading indicator next to the new signal while the first scan runs.
## Option 2: Browse the Signal Library
If you want inspiration or aren't sure what to look for, the Signal Library generates ideas based on your specific business.
From the Add Signal panel, click **Signal Library**. WhiteWhale will surface signal ideas tailored to your ICP and sales motion.
Browse the suggestions and click into any one you want to add. For example: *Do they use Outreach?* or *Are they hiring an SDR manager?*
Assign a priority rank and click **Add Signal**. It joins your list and starts scanning immediately.
Not sure what signals to create for your ICP? See [How to Get Unique Signal Ideas](/how-to-get-unique-signal-ideas) for a full walkthrough on building a signal list from scratch.
## Related
Understand what signals are and what sources WhiteWhale monitors.
Browse the full library of signal templates.
Fix signals that are too broad, too noisy, or returning wrong results.
Build a signal list tailored to your ICP from scratch.
# Credits & Billing
Source: https://docs.getwhitewhale.com/credits-and-billing
Understand how WhiteWhale account credits work, when they refresh, and how to add more. Credits control how many accounts your team can actively monitor each month.
## What's included
WhiteWhale includes unlimited users, unlimited live searches, and all integrations on every plan. The one thing credits control is **actively monitored accounts** — the accounts WhiteWhale scans every day for new signals.
## How credits work
Your plan comes with a set number of account credits. Each credit represents one actively monitored account for the month.
**You use a credit when you:**
* Upload an account via New Search → Upload a List
* Activate a suggestion from a live search
Once an account is monitored, WhiteWhale scans it daily and gives you the full signal data — sources, quotes, facts, and the Why Now summary. Suggestions (shown in orange) are just a preview until activated.
## Checking your credit usage
Go to **New Search** → **Upload Your List**. The credit bar will appear showing:
* Your total credit limit for the plan
* How many accounts you're currently monitoring
* How many more you can add this month
**Each month your credit balance resets** and you can choose to swap out the accounts you are currently monitoring up to your plan limit. For example, on a 300-account plan you can archive your current accounts and monitor a fresh 300 each month.
## Adding more credits
If you need more account capacity:
* From **Settings** → scroll to **License** → click **Manage License**
## Related
Add accounts and use your available credits.
Free up credits by archiving accounts you're no longer monitoring.
Run a live search to find new accounts with your signals.
# Deleting Signals
Source: https://docs.getwhitewhale.com/deleting-signals
Permanently remove a signal from your WhiteWhale account. Deleting a signal stops future monitoring and removes it from your signal library and scoring model.
## How to delete a signal
From the Signals page, click the **trash icon** next to the signal you want to remove and confirm the deletion.
The signal is immediately removed from your list. Over the next 10–15 minutes, WhiteWhale will re-score all affected accounts and update their rankings to reflect the change.
Deleting a signal is permanent. If you want to stop receiving alerts without losing the signal, [mute it](/muting-signals) instead.
## How many signals should I have?
Aim for **10–15 active signals** at any given time. Enough to get a detailed picture of every account, without so many that the signal queue becomes hard to work through.
Feel free to delete signals that aren't returning useful results and replace them with better ones. Iterating on your signal list over time is normal and expected.
## Related
Pause alerts without removing the signal entirely.
Fix signals before deciding to delete them.
# FAQ
Source: https://docs.getwhitewhale.com/faq
Answers to the most common questions about WhiteWhale — signals, accounts, searches, scoring, integrations, billing, and troubleshooting.
## Signals
Between 15 and 20 active signals. This gives you enough coverage to find activity across your accounts regularly. Mark your top 5–8 as High priority — these drive your account scores and Account Suggestions. If you only have 1–2 signals on a small number of accounts, you won't see enough results to be useful.
See [Creating Signals](/creating-signals) and the [Signal Library](/signal-library).
Yes. You can add, edit, mute, or delete signals as much as you want at any time. There's no limit and no cooldown.
Yes. WhiteWhale supports fully custom signals — describe anything you want to find in plain language and the platform will convert it into the right format. See [Creating Signals](/creating-signals).
Two ways:
1. **Describe it** — click Add Signal and type your idea in plain language. WhiteWhale will interpret it and create one or more signals formatted for the sources it checks.
2. **Signal Library** — click Signal Library for ideas generated based on your business. If the suggestions don't feel relevant, go to **Settings** → **Business Context** and **Signal Context** and update the information about what you sell. The platform uses this to generate better library suggestions and improve signals across the board.
See [Creating Signals](/creating-signals) and [Signal Library](/signal-library).
News articles, press releases, the company's website, job postings directly from the company's ATS (Greenhouse, Lever, Workday), earnings calls, earnings reports, and company social posts (LinkedIn). Sources are checked daily. See [How Signals Work](https://www.getwhitewhale.com/blog/what-is-a-sales-signal).
When you add a new signal, WhiteWhale searches across all your active accounts and suggestions. This typically takes 10–15 minutes, sometimes longer depending on how many accounts you have. A loader icon appears over the signal count while it's running. Go back to the Signals page at any time to check progress.
Two possible causes:
1. **The signal is too narrow.** The information doesn't exist in any of the sources WhiteWhale checks. Try broadening the signal question or removing overly specific qualifiers.
2. **It hasn't found it yet.** Your current accounts may not have this signal, but other companies might. Run a search specifically for this signal to find accounts that match. WhiteWhale will also throw an error after a period of time if it can't find the signal at all.
Mute the signal so it stops sending alerts. Go to the **Signals** page, find the signal, and click the **bell icon** in the mute column. When it turns red, the signal is muted — it still runs in the background but won't notify you.
If you want to keep alerts but tighten the results, add context to the signal instead. See below.
The system can only understand as much as you give it. Add more context so it knows exactly what you're looking for.
Go to the **Signals** page → find the signal → click the **book icon** under options. This opens the Context Window where you can add qualifications in plain language:
* **Geography:** *"Only job postings in the United States"*
* **Time period:** *"In the last 12 months"*
* **Specificity:** *"Only if they mention replacing their current CRM, not just using one"*
You can also edit the signal text directly for small changes. Both methods trigger a re-scan when saved.
See [Improving Signals](/improving-signals).
**Muting** stops the signal from sending alerts (via Slack, Teams, email, API, webhook) but keeps it running in the background. The signal still appears on account cards and profiles — it just won't notify you.
**Deleting** removes the signal entirely and re-scores all your accounts. It cannot be undone.
Use muting for background context signals. Use deleting when you want to remove a signal permanently. See [Muting Signals](/muting-signals) and [Deleting Signals](/deleting-signals).
***
## Accounts & Credits
Check the **Searches** page — it shows your current credit usage, how much space you have, and lets you add more credits if needed. See [Credits & Billing](/credits-and-billing).
Adding an account directly or activating an account from suggestions each use one credit. Accounts in your suggestions that haven't been activated do not use credits — they're previews only.
**Archiving** pauses an account, preserves all its signal history, and frees up a credit slot.
**Deleting** permanently removes the account and all its data. It cannot be undone.
When in doubt, archive. See [Archiving Accounts](/archiving-accounts) and [Removing Accounts](/removing-accounts).
Go to **New Search** → **Upload Your List** and paste all your domains. Toggle on **Clean the List** at the bottom to filter by signals, employee count, geography, and industry before uploading — so only the best accounts use your credits.
See [Adding Accounts](/adding-accounts).
Go to your active accounts and either archive or delete the ones you're done with. Archiving is better because it preserves signal history. Once you've freed up slots, add new accounts from uploads or activate suggestions.
Credits reset every month, so you can rotate your full list monthly — archive the current set and add a fresh batch. See [Archiving Accounts](/archiving-accounts).
Your credit limit resets every month. If you need more accounts before the reset:
1. **Free up space** — archive or delete accounts you're no longer working
2. **Upgrade your plan** — go to **Settings** → **Manage License** to move to a higher tier
See [Credits & Billing](/credits-and-billing).
Connect HubSpot or Salesforce so WhiteWhale can read your deal data. This enables automatic ownership updates and pushes WhiteWhale data into your CRM.
If you only want WhiteWhale to read ownership without writing data back, just don't map the write fields during setup.
See [HubSpot](/hub-spot) or [Salesforce](/salesforce).
***
## Searches & Account Suggestions
When you add accounts manually, you already know which companies to monitor. Account Suggestions searches across millions of companies to find ones you haven't thought of yet — companies that match your ICP filters and already have signal activity.
Check these in order:
**1. Did the search finish?** Searches typically take a couple of hours. The page shows if it's running, how many hours are left, and what percentage is complete. Check the **Jobs** button at the top for active searches in the queue.
**2. Is it a live search?** If the search isn't set to live, it won't run automatically. Make it live to start a run that continues every day.
**3. Are your parameters too restrictive?** Click **Edit Search** and check the bottom — it shows how many companies match your filters. Under 100 is too few. Over a million will take a long time. The sweet spot is a few hundred to 20,000.
**4. Are your signals too rare?** If your signals are extremely specific, even a large pool won't return results. Broaden the signal or check if it fires on any existing accounts first.
If you require multiple signals as Must Have, every account needs all of them simultaneously. Four out of five won't show up. Also make sure your Must Have signals logically co-exist — requiring both VC funding and PE investment doesn't make practical sense.
Stick to **Any Match** (light purple) unless you have one specific characteristic that's a hard requirement.
See [Adjusting Your Suggestions](/adjusting-your-suggestions).
Click the **X** on bad suggestions to reject them and provide feedback (too big, too small, wrong industry). WhiteWhale will prompt you to edit the search filters directly.
If you're rejecting a lot, check your firmographic filters first — geography, industry, and employee count are the most common culprits. Then consider adding a characteristic signal as a **Must Have** to define a hard ICP requirement.
See [Adjusting Your Suggestions](/adjusting-your-suggestions).
Results often start appearing within minutes. The count grows daily as WhiteWhale works through all the matching companies. A search that returns 59 results on day one may return hundreds by the end of the week.
The best results come from 3–5 searches running at any given time. Many users exceed that and run ten or more. Each search can target a different signal combination, industry, or company size.
Yes. Select accounts using the checkboxes and click **Activate**. You can assign them to one person or round-robin across your team. See [Assigning Suggestions](/assign-suggestions-round-robin-etc).
***
## Scoring
The score (0–100) reflects how much recent, high-ranked signal activity an account has. It's a prioritization tool — use it to decide which accounts to work first. See [Account Scoring Explained](/account-scoring-explained).
Most workable accounts score between 15 and 50. Scores above 50 are strong. Scores above 70 are rare — they'd require multiple high-ranked signals firing simultaneously. Don't anchor to a fixed number; spend a week clicking through your accounts and you'll develop a feel for what "good" looks like for your signal set.
Scores update daily as new signals fire and older signals age out. A score drop doesn't mean the account is less interesting — it just means nothing new happened recently.
***
## Alerts & Notifications
Check three things:
1. **Do you have active accounts?** Monitored accounts show a green indicator on the Accounts page. If nothing is monitored, there's nothing to alert on.
2. **Are your notifications turned on?** Go to **Settings** → **User Notifications** and make sure **Daily Signals** is enabled.
3. **Do your signals have results?** If you only have a few signals on a small number of accounts, alerts will be infrequent. Add more accounts (up to your plan limit) and aim for 15–20 signals.
Go to **Settings** and enter your **Slack Member ID**. To find it: in Slack, click your profile → three-dot menu (⋯) → **Copy Member ID**. Paste it into WhiteWhale and save.
Go to **Settings** and change the default AI option to whichever tool you prefer.
***
## Integrations
Go to **Settings** → **Integrations** → find your CRM and click **Set Up**. Use the one-click setup for a standard configuration. You'll need to create a handful of custom fields first — the setup screen shows you exactly which ones. See [HubSpot](/hub-spot) or [Salesforce](/salesforce).
WhiteWhale runs a full sync daily between 5–9 AM ET. It also updates your CRM immediately when a new account is added or activated. See [HubSpot](/hub-spot) for full sync details.
Go to **Settings** → **Integrations** → connect Slack. Then go to **Settings** → **User Notifications** and turn on **Daily Signals** and **Assigned Accounts**. To get personally tagged, copy your Slack Member ID and add it to your WhiteWhale profile. See [Slack](/slack).
Yes, on Enterprise plans. Contact [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) to get set up. See [Microsoft Teams](/microsoft-teams).
The fastest way: go to Claude → **Settings** → **Connectors** → **Custom Connectors** → add `https://app.getwhitewhale.com/mcp`. Then start a new chat and give Claude your API key and email. See [Claude MCP](/mcp-claude-chat-gpt-etc) for the full setup guide.
Go to **Settings** → **API & Webhooks** → click **Generate API Key**. The key is shared across your whole team. See [API Reference](/api).
***
## Team & Permissions
**Super Admins** can see all accounts across the platform, edit signals, manage Account Suggestions, and administer the team.
**Members** can only see accounts assigned to them. They can optionally be given viewer access to see another user's accounts, or admin access for elevated permissions.
See [Roles & Permissions](/roles-and-permissions).
Yes. Give the SDR **Viewer** access to the AE. They'll have read-only visibility — signals and account data, but can't reassign or edit. See [Adding Users](/adding-users).
They're most likely a **Member** without viewer access. Members only see accounts assigned to them by default. Either make them a viewer of the relevant user's accounts, or make them a Super Admin if they need full visibility. See [Roles & Permissions](/roles-and-permissions).
Removing a user deletes their profile and settings. Their accounts remain in the system but lose their assignment. Reassign accounts to another rep before removing the user. See [Removing Users](/removing-users).
Email [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) with the email you'd like to switch to and we'll update it for you.
***
## Billing & Plans
Go to **Settings** → **Manage License**. If you are the account owner (the person who signed up with their email in Stripe or Lemon Squeezy), you'll have direct access to change, upgrade, or cancel.
If you're not the owner, either ask the owner to make the change or check your email for a link to view the Stripe subscription. The manage license section also shows the support email at the bottom.
We don't do traditional trials, but you can preview your signals before purchasing. Go to the website, click **See Your Signals**, and enter your website. WhiteWhale will generate and validate signals for you. If they look useful, select a plan.
If you have questions after previewing, [book a meeting](https://www.getwhitewhale.com) with the team.
***
## Still have questions?
Email [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) or [book a call](https://www.getwhitewhale.com) with the team.
# Glossary
Source: https://docs.getwhitewhale.com/glossary
Definitions for every term in WhiteWhale, including signals, Why Now summaries, account scoring, searches, ICP parameters, and credit allocation.
## Account
A company you are monitoring in WhiteWhale. Each active account uses one credit and is scanned daily for new signal activity.
***
## Account Score
A number from 0 to 100 that reflects how much recent, high-ranked signal activity an account has. Higher scores mean more signals have fired recently. Most workable accounts score between 15 and 50. Scores above 70 are rare. See [Account Scoring Explained](/account-scoring-explained).
***
## Active Account (Monitored)
An account that is being monitored daily and consuming a credit slot. Monitored accounts show a green indicator and have full signal data available — sources, quotes, facts, and the Why Now summary.
***
## Archived Account
An account that has been paused. Archiving stops new signals from firing and frees up the credit slot. Historical signal data is preserved. See [Archiving Accounts](/archiving-accounts).
***
## Clean the List
An option when uploading accounts via New Search → Upload a List. Lets you filter a large list by signals, employee count, geography, and industry before uploading — so only accounts that pass your criteria use credits. See [Adding Accounts](/adding-accounts).
***
## Context Window
The additional instruction field on each signal (shown as a book icon). Use it to add constraints like geography, time range, or specificity that the signal question alone can't capture. For example: *"Job listings from the United States only"* or *"In the last 90 days."* See [Improving Signals](/improving-signals).
***
## Credit
One credit = one actively monitored account for the month. Uploading an account or activating a suggestion each use one credit. Credits reset monthly. Your plan determines your total monthly credit limit. See [Credits & Billing](/credits-and-billing).
***
## ICP (Ideal Customer Profile)
The definition of your target customer. In WhiteWhale, your ICP determines which signals you track, which accounts you monitor, and what your searches look for.
***
## Live Search
A search that is set to actively run. Live searches scan automatically every day, looking for new accounts that match your filters and have your signals. Your plan determines how many searches can be live at the same time — most plans allow one. Click on a search to check if it says **Live** at the top. See [Setting Up Searches](/setting-up-account-suggestions).
***
## MCP (Model Context Protocol)
A protocol that lets Claude connect to external tools and data sources. The WhiteWhale MCP gives Claude direct access to your account data, signals, and scores so you can ask questions about your book of business in plain English. See [Claude MCP](/mcp-claude-chat-gpt-etc).
***
## Member
A user role in WhiteWhale. Members can only see accounts assigned to them. They can optionally be given viewer access to see another user's accounts, or admin access for elevated permissions. See [Roles & Permissions](/roles-and-permissions).
***
## Pre-Meeting Research Brief
An email WhiteWhale sends 24 hours before any calendar meeting with a tracked account. Includes what the company does, the Why Now summary, meeting time, location, and company size. Requires Google Calendar connected. See [Pre-Meeting Research Brief](/pre-meeting-research-brief).
***
## Search
The core way to get accounts into WhiteWhale. Go to **New Search** on the Accounts page and choose one of two types:
* **Upload a List** — paste company domains you already have. Use Advanced Settings to set a credit cap on large lists, and Clean the List to filter by signals and firmographics.
* **Find New Accounts** — WhiteWhale searches across millions of companies to find ones that match your ICP and have signal activity. Make the search **Live** so it runs every day automatically.
You can create as many searches as you want. Each one appears in your search list with its own results. See [Adding Accounts](/adding-accounts) and [Setting Up Searches](/setting-up-account-suggestions).
***
## Segment
A saved set of account filters. Instead of rebuilding the same filter combination every time, you save it once and return to it with one click. Segments are live — they always reflect the accounts that match your filters right now. See [How Segments Work](/how-segments-work).
***
## Signal
A question WhiteWhale asks about every account every day. For example: *Did they hire a new CRO? Are they hiring SDRs? Did they announce new funding?* When the answer is yes, the account surfaces with the source, quotes, and a Why Now summary. See [How Signals Work](https://www.getwhitewhale.com/blog/what-is-a-sales-signal).
***
## Signal Priority
A rank assigned to each signal that determines how much it influences an account's score.
| Rank | Weight | Use for |
| -------------- | ------ | ------------------------------------------------------------------------------- |
| **High** | 6.0 | Your strongest buying signals. Required for live searches to find new accounts. |
| **Normal** | 1.0 | Standard signals — the default for most. |
| **Low** | 0.1 | Background context. Consider muting so they don't generate alerts. |
| **Disqualify** | 0.0 | Negative signals. Accounts matching these are scored down. |
***
## Suggestion
An account found by a search that hasn't been activated yet. Suggestions appear in orange with a preview of their signal data. Activate a suggestion to unlock full signal details and the Why Now summary — this uses one credit. See [Assigning Suggestions](/assign-suggestions-round-robin-etc).
***
## Super Admin
A user role in WhiteWhale. Super Admins can see all accounts across the platform regardless of assignment, edit signals, manage searches, and administer the team. See [Roles & Permissions](/roles-and-permissions).
***
## Webhook
An automated way to send WhiteWhale data to another tool whenever a signal fires or an account is uploaded. Used to connect WhiteWhale to Clay, custom CRMs, internal tools, and other platforms. See [Webhooks](/webhooks).
***
## Why Now
A 2–3 sentence summary WhiteWhale generates for each account that connects the dots between all its active signals. It tells you what's changing at the company, what that implies, and why right now is the right time to reach out. The foundation of signal-based outreach. See [Using the Why Now Summary](/using-the-why-now-summary).
# Google Calendar
Source: https://docs.getwhitewhale.com/google-calendar
Connect Google Calendar to WhiteWhale and get automatic pre-meeting research briefs with buying signals and Why Now summaries 24 hours before every call.
WhiteWhale connects to your Google Calendar and automatically prepares a research brief before any meeting with a tracked account. No manual prep needed — the brief lands in your inbox 24 hours before the call with everything you need to walk in prepared.
## How to connect
Click **Settings** in the left nav and scroll to **Integrations**.
Follow the prompts to authorize WhiteWhale to access your calendar.
Select how WhiteWhale should handle your upcoming meetings:
| Mode | What it does |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **On** | Sends a research brief 24 hours before each meeting with a tracked account. Nothing is added to your account list automatically. |
| **On — Auto Upload** | Sends research briefs and automatically adds any account you have a meeting with to your WhiteWhale list. Uses account credits. |
| **Off** | Pauses the integration. No briefs are generated. Your connection is preserved. |
Not sure which mode to pick? Start with **On**. You get pre-meeting briefs without touching your account list or credits. Switch to Auto Upload later if you want your calendar to drive your book of business automatically.
## What's in the brief
WhiteWhale sends the brief by email 24 hours before the meeting. Each brief includes:
* Meeting time, company HQ location, and employee count
* **What they do** — a plain-English summary of the company
* **Why Now** — the signal story: what's changed recently and why now is the right time to be talking to them
## Disconnecting
To disconnect, go to **Settings** → **Integrations** → **Google Calendar** → click **Disconnect**. You can reconnect at any time.
## Related
See what the brief looks like and learn how to use it.
Understand the signal story in your brief before the call.
Manually add accounts to your list.
# How to Get Unique Signal Ideas
Source: https://docs.getwhitewhale.com/how-to-get-unique-signal-ideas
Move beyond generic signals like funding rounds and leadership changes. Find the non-obvious buying signals that actually surface real purchasing moments for your ICP.
## Use Claude to build your signal list
The fastest way to build a great signal list is to use the WhiteWhale Signal Creator — a Claude skill trained specifically on how WhiteWhale signals work, what makes them fire reliably, and how to write the non-obvious signals that actually move deals.
Tell it what you sell, who you sell to, and what triggers a purchase. It will generate a prioritized signal set with explanations for each one.
A Claude skill that builds a custom signal list for your ICP. Works in Claude.ai and Claude Desktop.
**How to use it:**
1. Download the `.skill` file above
2. Open [Claude.ai](https://claude.ai) and upload the file, or install it in Claude Desktop
3. Tell Claude what you sell, who buys it, and what your best customers looked like before they bought
4. Claude will generate a prioritized, ready-to-paste signal set tailored to your business
The skill is trained to find the non-obvious signals — the ones in job postings, website language, and company behavior that reveal pain without ever mentioning your product category. These are the signals that drive the most pipeline.
***
## Think in layers, not lists
Most people start with the obvious signals — funding rounds, leadership changes, hiring spikes. Those are fine, but every competitor is watching the same things. The accounts that convert fastest come from signals that surface pain before the prospect has started evaluating solutions.
Build your signal set across these layers:
New leaders re-evaluate their entire tool stack within the first 90 days. This is almost always the highest-converting signal for any product.
The key is specificity — identify the exact titles that buy, champion, and budget for your product, then create a signal for each.
* **Buyer** (approves the purchase) → usually C-suite: CRO, CMO, CFO, CTO
* **Champion** (uses it daily and pushes for it) → usually VP or Director level
* **Budget holder** (controls the budget line) → sometimes the same as the buyer, sometimes not
*Example for a sales tool:* New CRO or VP of Sales (buyer) + New Head of RevOps (champion)
Growth creates operational strain. Companies expanding faster than their systems can handle are the most receptive buyers — they feel the pain acutely and have budget to solve it.
* Did raise a funding round recently?
* Is expanding into a new geographic market?
* Did open a new office or facility recently?
* Did acquire another company recently?
* Is hiring rapidly across multiple functions?
Tailor to your industry. A restaurant chain opening new locations is different from a SaaS company raising a Series B — but both signal growth strain.
These are the signals most people never think to write. Instead of asking "does this company need my product," ask: *what would a company be doing or saying publicly if they had the problem my product solves?*
Then write a signal that detects that behavior.
**Real examples of this thinking:**
| What you sell | Observable proxy signal |
| ------------------------ | -------------------------------------------------------------------------------------------------------------- |
| Corporate cards | Do they post jobs with heavy travel requirements? (high travel = high expense volume) |
| LMS / training software | Do their store manager job postings mention training as a responsibility? (means no training system exists) |
| Competitive intelligence | Do their job postings mention building competitive battlecards? (means they're losing deals to competitors) |
| Legal AI | Do they post for roles involving document review or due diligence? (high-volume manual work = automation pain) |
**Job postings are the best source for these signals.** Companies reveal their pain in plain text when writing job descriptions — they mention broken processes, tools they wish they had, and responsibilities that only exist because no system handles them yet.
Every industry has 2-3 moments that create outsized urgency. These are the signals you can only write if you know your vertical deeply.
| Industry | High-urgency events |
| -------------------------- | --------------------------------------------------------------------------- |
| SaaS | Competitor launches, platform migrations, new product categories |
| Healthcare | New compliance requirements, facility expansions, system consolidations |
| Legal | Firm mergers, new litigation, regulatory changes |
| Restaurants / Retail | Seasonal hiring spikes, location expansion, health code violations |
| Multi-location / Franchise | Acquisition of new locations, new regional leadership, franchise agreements |
Ask yourself: *what happened at my best customers 60–90 days before they bought?* That's your industry-specific signal.
These tell you the prospect is already aware of the product category. Useful for personalizing outreach, but shouldn't drive account scoring since they don't indicate timing.
* Does mention using \[competitor]?
* Does mention using \[legacy tool]?
* Do their job postings mention \[manual process]?
Set these to **Low** priority and consider muting them so they add context without flooding your queue.
These tell you *who* fits your ICP but not *when* to reach out. Add them for account context, but mute them so they don't generate daily alerts.
* Does have more than 2 office locations?
* Does offer \[type of service or product]?
* Does operate in \[industry or vertical]?
***
## Mine your own sales history
Your best signal ideas aren't in a template — they're in your own closed-won deals. Before writing new signals, ask:
* What was happening at your best customers 60–90 days before they bought?
* What did they say in the first call that made it clear the timing was right?
* Was there a specific event — a hire, a product launch, a reorg — that created the urgency?
* What do your customers have in common that your prospects don't?
If you have sales call transcripts or CRM notes, feed them to the Claude skill above. It will extract the buying triggers and turn them into signals automatically.
On [certain plans](https://www.getwhitewhale.com/pricing), **Closed-Won** backtesting is available. This analyzes your recent deals and finds which signals showed up before you closed them and not in the ones you lost. Giving you a clear picture of where you win deals.
***
## Write signals that will actually fire
A signal that never fires is worse than no signal at all — it dilutes your scoring and trains you to ignore the queue. Before adding any signal, ask: *would this information ever appear in a news article, press release, job posting, earnings call, or company website?*
* Leadership hires and departures (press releases, LinkedIn)
* Funding announcements (press releases, news)
* Job postings and hiring patterns (company ATS, job boards)
* Product launches and new features (press releases, company website)
* Expansion into new markets or geographies (press releases, news)
* Earnings call language and executive quotes (earnings reports)
* Company social posts about initiatives or wins
These feel logical but depend on information companies almost never share publicly. Rewrite them as observable proxies instead.
| Won't fire | Rewrite as |
| ---------------------------------------- | -------------------------------------------------------- |
| Did increase their L\&D budget? | Is hiring for instructional designers or L\&D roles? |
| Does need better data hygiene? | Do job postings mention data cleanup or CRM management? |
| Did decide to evaluate new vendors? | as posted an RFP or hired a procurement lead? |
| Is unhappy with their current provider? | Does mention replacing or migrating from \[category]? |
| Won't fire | Rewrite as |
| ---------- | ---------- |
| | |
| | |
| | |
| | |
***
## Related
Copy-paste signal templates organized by category and use case.
Add signals to WhiteWhale using the description box or in-platform library.
Fix signals that are noisy, too broad, or firing from the wrong geography.
Understand what sources WhiteWhale monitors and how signals become alerts.
# How to See All New Signals
Source: https://docs.getwhitewhale.com/how-to-see-all-new-signals
Find your most recent signal activity and export accounts for outbound campaigns.
## Your accounts are already sorted
When you land on the **All Accounts** page, accounts are sorted by most recent signal date by default. The accounts at the top have the freshest activity — start there.
Click into any account and the first card will show you the most recent signal with its source, details, and Why Now.
## Filter by time range
If you want to narrow the view, go to **Filters** → **Signal Recency** and set a window — for example, last 3 months. This shows you only accounts with signal activity in that period.
## Export for outbound campaigns
Once you've filtered your accounts, click **Export** to pull the data into a CSV. Use this to run campaigns in Clay, your outreach tool, or anywhere else you work your accounts.
## Related
Understand the signal context before reaching out.
Save your filtered views for ongoing use.
Push exported accounts into Clay for enrichment and automated outreach.
Turn signal data into messages that get replies.
# HubSpot
Source: https://docs.getwhitewhale.com/hub-spot
Connect WhiteWhale to HubSpot to sync account scores, buying signals, and Why Now summaries directly to your CRM. Native app with an in-CRM signal card.
Connecting HubSpot gives your reps WhiteWhale data — scores, signals, and Why Now summaries — directly inside the CRM they already work in. No spreadsheets, no manual exports.
## What the integration does
* **Daily sync** — WhiteWhale pulls your company and deal data from HubSpot each day and pushes updated scores, signals, and Why Now summaries back to the mapped fields
* **Real-time updates** — when a new account is added or activated in WhiteWhale, it immediately syncs to HubSpot
* **Deal context** — mapping your deal pipeline lets WhiteWhale surface different signals based on where each prospect is in your sales cycle
***
## How the sync works
* **Daily sync window:** 5–9 AM ET. WhiteWhale pulls your company and deal records and pushes updated WhiteWhale fields back to HubSpot.
* **Real-time updates:** When a new account is added or activated in WhiteWhale, the CRM is updated immediately.
* **First week:** Expect a higher volume of requests during initial calibration as the sync establishes its baseline.
* **Read/write scope:** WhiteWhale only reads from the fields you map and only writes to the WhiteWhale-specific fields you create. It will not modify any other HubSpot data.
***
## Permissions and scopes
WhiteWhale connects via a verified HubSpot public app and requests the minimum permissions needed to function.
**Required scopes:**
* `crm.objects.companies.read`
* `crm.objects.companies.write`
* `crm.schemas.companies.read`
* `oauth`
**Optional scopes (unlocked when deal mapping is enabled):**
* `crm.schemas.deals.read`
* `crm.objects.deals.read`
* `crm.objects.owners.read`
* `crm.schemas.companies.write`
* `sales-email-read`
## How to connect
Click **Settings** in the left nav, then scroll to the HubSpot section.
![Screenshot 2026 06 11 At 6 23 55 PM]()
Click **Settings** in the left nav, then scroll to the HubSpot section.
![Screenshot 2026 06 11 At 6 23 55 PM]()
You'll be prompted to connect your HubSpot account. Follow the authentication steps in the HubSpot portal.\\
![Screenshot 2026 06 11 At 6 24 46 PM]()
You'll be prompted to connect your HubSpot account. Follow the authentication steps in the HubSpot portal.\\
![Screenshot 2026 06 11 At 6 24 46 PM]()
Once authenticated, you'll have two options:
* **One-click setup (recommended)** — WhiteWhale maps the standard fields automatically. Best for most teams.
* **Custom mapping** — manually map company and deal fields if you need non-standard field names or a more complex CRM setup.
For one-click setup, WhiteWhale will show you a list of fields to create in HubSpot with their required field types. Create these fields in HubSpot first, then return and click **I've created these fields and I'm ready to map**.
For custom setups, open the below information card called "Fields to Create".
## Field reference
### Company fields
These are the fields WhiteWhale reads from and writes to on your HubSpot company records.
| Field | Required | Description |
| :-------------------- | :------- | :---------------------------------------------------------------------------------------------------------- |
| `crm_id` | ✅ | HubSpot object ID of the company (`hs_object_id`) |
| `Company_Domain` | ✅ | Company website URL (`domain` or `website`). WhiteWhale can only process companies with a domain on record. |
| `BirdDog_Description` | Optional | WhiteWhale's Why Now summary for the account |
| `BirdDog_Score` | Optional | Account score from 0–100 based on signal strength |
| `BirdDog_Link` | Optional | Direct link to the account's report in WhiteWhale |
| `BirdDog_User` | Optional | Links the account to the appropriate WhiteWhale user for automatic assignment |
| `BirdDog_Originated` | Optional | Records whether WhiteWhale originated the account, for attribution |
| `BirdDog_Add_Date` | Optional | Date the account was first added to WhiteWhale |
| `BirdDog_Signal_List` | Optional | All signals currently matching this account |
### Recommended custom field configurations
Create these fields in HubSpot before running setup. All fields should be grouped under **Company Information**.
* **Field type:** Single-line text
* **Label:** WhiteWhale Description
* **Description:** A summary of the most recent WhiteWhale signals for the company
* **Default value:** Blank
* **Field type:** Number
* **Label:** WhiteWhale Score
* **Description:** A score from 0–100 showing the strength of WhiteWhale signals for this company. Scores above 80 are strong but rare — even a score above 10 likely has valuable information.
* **Default value:** Blank
* **Field type:** URL
* **Label:** WhiteWhale Link
* **Description:** A link to the full account report in the WhiteWhale platform
* **Default value:** Blank
* **Field type:** Rich text
* **Label:** WhiteWhale Signals
* **Description:** The most recent signals WhiteWhale found on the company
* **Default value:** Blank
* **Field type:** Single checkbox
* **Label:** WhiteWhale Originated
* **Description:** Records if WhiteWhale originated the account
* **Default value:** Blank
* **Field type:** Date and time picker
* **Label:** WhiteWhale Add Date
* **Description:** Records the date the account was originally added to WhiteWhale
* **Default value:** Blank
* **Field type:** Multiple checkboxes
* **Label:** WhiteWhale Signal List
* **Description:** List of all WhiteWhale signals that apply to this account
* **Option style:** Tag (recommended)
* **Options:** Enter one placeholder option — WhiteWhale will override with the correct values automatically
### Deal fields
Mapping your deal pipeline is optional but unlocks two additional capabilities: signal recommendations that adapt based on deal stage, and the ability to backtest which signals correlate most strongly with closed-won deals.
## Field reference
### Company fields
These are the fields WhiteWhale reads from and writes to on your HubSpot company records.
| Field | Required | Description |
| :-------------------- | :------- | :---------------------------------------------------------------------------------------------------------- |
| `crm_id` | ✅ | HubSpot object ID of the company (`hs_object_id`) |
| `Company_Domain` | ✅ | Company website URL (`domain` or `website`). WhiteWhale can only process companies with a domain on record. |
| `BirdDog_Description` | Optional | WhiteWhale's Why Now summary for the account |
| `BirdDog_Score` | Optional | Account score from 0–100 based on signal strength |
| `BirdDog_Link` | Optional | Direct link to the account's report in WhiteWhale |
| `BirdDog_User` | Optional | Links the account to the appropriate WhiteWhale user for automatic assignment |
| `BirdDog_Originated` | Optional | Records whether WhiteWhale originated the account, for attribution |
| `BirdDog_Add_Date` | Optional | Date the account was first added to WhiteWhale |
| `BirdDog_Signal_List` | Optional | All signals currently matching this account |
### Recommended custom field configurations
Create these fields in HubSpot before running setup. All fields should be grouped under **Company Information**.
* **Field type:** Single-line text
* **Label:** WhiteWhale Description
* **Description:** A summary of the most recent WhiteWhale signals for the company
* **Default value:** Blank
* **Field type:** Number
* **Label:** WhiteWhale Score
* **Description:** A score from 0–100 showing the strength of WhiteWhale signals for this company. Scores above 80 are strong but rare — even a score above 10 likely has valuable information.
* **Default value:** Blank
* **Field type:** URL
* **Label:** WhiteWhale Link
* **Description:** A link to the full account report in the WhiteWhale platform
* **Default value:** Blank
* **Field type:** Rich text
* **Label:** WhiteWhale Signals
* **Description:** The most recent signals WhiteWhale found on the company
* **Default value:** Blank
* **Field type:** Single checkbox
* **Label:** WhiteWhale Originated
* **Description:** Records if WhiteWhale originated the account
* **Default value:** Blank
* **Field type:** Date and time picker
* **Label:** WhiteWhale Add Date
* **Description:** Records the date the account was originally added to WhiteWhale
* **Default value:** Blank
* **Field type:** Multiple checkboxes
* **Label:** WhiteWhale Signal List
* **Description:** List of all WhiteWhale signals that apply to this account
* **Option style:** Tag (recommended)
* **Options:** Enter one placeholder option — WhiteWhale will override with the correct values automatically
### Deal fields
Mapping your deal pipeline is optional but unlocks two additional capabilities: signal recommendations that adapt based on deal stage, and the ability to backtest which signals correlate most strongly with closed-won deals.
For one-click setup, WhiteWhale will show you a list of fields to create in HubSpot with their required field types. Create these fields in HubSpot first, then return and click **I've created these fields and I'm ready to map**.
For custom setups, you'll need to have fields of the same type for the system to be able to publish data.
* **Field type:** Single-line text
* **Label:** WhiteWhale Description
* **Description:** A summary of the most recent WhiteWhale signals for the company
* **Default value:** Blank
* **Field type:** Number
* **Label:** WhiteWhale Score
* **Description:** A score from 0–100 showing the strength of WhiteWhale signals for this company. Scores above 80 are strong but rare — even a score above 10 likely has valuable information.
* **Default value:** Blank
* **Field type:** URL
* **Label:** WhiteWhale Link
* **Description:** A link to the full account report in the WhiteWhale platform
* **Default value:** Blank
* **Field type:** Rich text
* **Label:** WhiteWhale Signals
* **Description:** The most recent signals WhiteWhale found on the company
* **Default value:** Blank
* **Field type:** Single checkbox
* **Label:** WhiteWhale Originated
* **Description:** Records if WhiteWhale originated the account
* **Default value:** Blank
* **Field type:** Date and time picker
* **Label:** WhiteWhale Add Date
* **Description:** Records the date the account was originally added to WhiteWhale
* **Default value:** Blank
* **Field type:** Multiple checkboxes
* **Label:** WhiteWhale Signal List
* **Description:** List of all WhiteWhale signals that apply to this account
* **Option style:** Tag (recommended)
* **Options:** Enter one placeholder option — WhiteWhale will override with the correct values automatically
Click **Test Connection**. WhiteWhale will run its checks and flag any errors. Fix any issues and test again until the connection is confirmed.
![Screenshot 2026 06 11 At 6 27 04 PM]()
Click **Test Connection**. WhiteWhale will run its checks and flag any errors. Fix any issues and test again until the connection is confirmed.
![Screenshot 2026 06 11 At 6 27 04 PM]()
Use one-click setup unless you have a specific reason to customize. It takes a couple of minutes and works for the vast majority of HubSpot instances.
***
## Setting up the HubSpot App Card
Once your field mapping is complete, you can add the WhiteWhale app card to your HubSpot records so reps can see signal data directly inside HubSpot without leaving the CRM.
Download the WhiteWhale app directly from the HubSpot App Marketplace:
Install the WhiteWhale app to your HubSpot instance.
Once installed, authorize WhiteWhale to connect to your HubSpot account:
Click to complete the OAuth authorization.
In HubSpot, go to the **Card Library** and search for **BirdDog Research**. Add it to the company record layout so it appears on every account page.
Not sure how to add app cards? See [HubSpot's guide to installing and managing app cards](https://knowledge.hubspot.com/integrations/install-and-manage-app-cards).
Once the card is added, reps will see WhiteWhale signal data — scores, signals, and the Why Now summary — directly on the HubSpot company record without needing to open WhiteWhale separately.
***
## Field reference
### Company fields
These are the fields WhiteWhale reads from and writes to on your HubSpot company records.
| Field | Required | Description |
| ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------- |
| `crm_id` | ✅ | HubSpot object ID of the company (`hs_object_id`) |
| `Company_Domain` | ✅ | Company website URL (`domain` or `website`). WhiteWhale can only process companies with a domain on record. |
| `whitewhale_description` | Optional | WhiteWhale's Why Now summary for the account |
| `whitewhale_score` | Optional | Account score from 0–100 based on signal strength |
| `whitewhale_link` | Optional | Direct link to the account's report in WhiteWhale |
| `whitewhale_user` | Optional | Links the account to the appropriate WhiteWhale user for automatic assignment |
| `whitewhale_originated` | Optional | Records whether WhiteWhale originated the account, for attribution |
| `whitewhale_add_date` | Optional | Date the account was first added to WhiteWhale |
| `whitewhale_signal_list` | Optional | All signals currently matching this account |
### Recommended custom field configurations
Create these fields in HubSpot before running setup. All fields should be grouped under **Company Information**.
* **Field type:** Single-line text
* **Label:** WhiteWhale Description
* **Description:** A summary of the most recent WhiteWhale signals for the company
* **Default value:** Blank
* **Field type:** Number
* **Label:** WhiteWhale Score
* **Description:** A score from 0–100 showing the strength of WhiteWhale signals for this company. Scores above 80 are strong but rare — even a score above 10 likely has valuable information.
* **Default value:** Blank
* **Field type:** URL
* **Label:** WhiteWhale Link
* **Description:** A link to the full account report in the WhiteWhale platform
* **Default value:** Blank
* **Field type:** Rich text
* **Label:** WhiteWhale Signals
* **Description:** The most recent signals WhiteWhale found on the company
* **Default value:** Blank
* **Field type:** Single checkbox
* **Label:** WhiteWhale Originated
* **Description:** Records if WhiteWhale originated the account
* **Default value:** Blank
* **Field type:** Date and time picker
* **Label:** WhiteWhale Add Date
* **Description:** Records the date the account was originally added to WhiteWhale
* **Default value:** Blank
* **Field type:** Multiple checkboxes
* **Label:** WhiteWhale Signal List
* **Description:** List of all WhiteWhale signals that apply to this account
* **Option style:** Tag (recommended)
* **Options:** Enter one placeholder option — WhiteWhale will override with the correct values automatically
### Deal fields
Mapping your deal pipeline is optional but unlocks two additional capabilities: signal recommendations that adapt based on deal stage, and the ability to backtest which signals correlate most strongly with closed-won deals.
| Field | Required | Description |
| ---------------- | -------- | ----------------------------------------------------------------------- |
| `crm_id` | ✅ | HubSpot deal ID (`hs_object_id`) |
| `crm_company_id` | ✅ | ID of the primary company on the deal (`hs_primary_associated_company`) |
| `Name` | Optional | Deal name |
| `Stage_name` | Optional | Current deal stage |
| `Amount` | Optional | Deal size |
| `Close_date` | Optional | Expected close date |
| `Prob` | Optional | Close probability |
| `Is_closed` | Optional | Whether the deal is closed |
| `Is_won` | Optional | Whether the deal is won |
| `Created_date` | Optional | Date the deal was created |
***
## Need help?
If you run into errors during setup or need help with custom field mapping, contact the WhiteWhale team.
## Related
Connect WhiteWhale to Salesforce.
Get signal alerts delivered to Slack.
Push WhiteWhale data to your own systems via webhook.
Access WhiteWhale data programmatically.
# Improving Signals
Source: https://docs.getwhitewhale.com/improving-signals
Fix WhiteWhale signals returning wrong-geography results, casting too wide a net, or surfacing stale data. Tips for tightening signal accuracy and relevance.
If a signal isn't returning what you expected, you don't need to delete it and start over. Most signal issues fall into one of three categories — and each has a straightforward fix.
## The three common signal problems
Results are coming from countries or regions you don't serve.
The signal is matching accounts that technically fit the question but aren't what you meant.
The signal is surfacing old matches from months or years ago.
## Fix 1: Wrong geography
Use the **Context Window** to tell the system which countries or regions to restrict results to.
From the Signals page, locate the signal returning results from the wrong location.
Click the **book icon** next to the signal. This opens the Context Window where you can give the system additional instructions.
Type your restriction in plain language. For example:
* *Job listings from the United States only*
* *Headquarters in the US, UK, or Canada*
* *Exclude results outside North America*
Click **Save**. WhiteWhale will re-run the signal with the new constraint applied.
## Fix 2: Signal is too broad
When a signal is casting too wide a net, you have two options depending on how much you need to change.
**For small edits** — use the inline signal editor. Click directly into the signal text and add the missing specificity. For example, changing *"Are they running an account-based marketing program?"* to *"Are they running an email-based ABM program?"* is a quick edit that takes seconds.
**For bigger changes** — use the Context Window. If you need to add multiple conditions or explain nuance the signal text alone can't capture, open the book icon and write out the full context. For example: *Only match if the ABM program is focused on email outreach, not paid ads or direct mail.*
The core principle: just tell the system what you want. The more specific context you give it, the more precisely it will match.
## Fix 3: Results are stale
By default, WhiteWhale searches across all time so you get the full picture on every account. If you only want recent activity, add a time constraint to the signal.
Open the signal editor or Context Window and add language like:
* *In the last 90 days*
* *Recently*
* *In the last 6 months*
Once you save, WhiteWhale will re-run the signal and update both your account scores and your Account Suggestions with the fresh results.
## Two ways to edit a signal
| Method | Best for |
| ------------------------------ | ------------------------------------------------------------------------------------------ |
| **Edit the signal text** | Small, targeted word changes |
| **Context Window (book icon)** | Geography constraints, multiple conditions, time limits, or anything requiring explanation |
Both methods trigger a full re-scan of your accounts when saved.
## Related
Add new signals using the description box or Signal Library.
Temporarily stop a signal from surfacing new matches.
Build a signal list tailored to your ICP from scratch.
Browse proven signal templates by use case.
# MCP (Claude, ChatGPT, etc)
Source: https://docs.getwhitewhale.com/mcp-claude-chat-gpt-etc
Connect WhiteWhale to Claude, ChatGPT, or Gemini via MCP to chat with your signal data in plain English. Ask for top accounts, draft emails, and build one-pagers.
The WhiteWhale MCP connects Claude directly to your WhiteWhale account. Once it's set up, you can ask Claude questions about your accounts and signals in plain English and get real answers from your live data.
**MCP stands for Model Context Protocol.** It's a way to give Claude access to tools and data outside of the conversation. You don't need to understand how it works — just follow the setup steps below and Claude will handle the rest.
## What you can ask Claude
Once connected, ask Claude anything about your WhiteWhale data:
* *"Which accounts should I reach out to today?"*
* *"Add these 20 companies to my list: \[paste domains]"*
* *"What signals am I tracking and are they configured well?"*
* *"How many account credits do I have left?"*
* *"Find me new target accounts that match my ICP"* Claude will pull your live WhiteWhale data and respond in plain English — no dashboards, no exports, no copy-pasting.
***
## Prerequisites
You need a **WhiteWhale account** with an API key.
### Get your API key
In WhiteWhale, go to **Settings** → **API & Webhooks** → click **Generate API Key**. Copy the key — you'll need it in the next step. Your **user** is the email address you use to log into WhiteWhale.
***
## Setup: Claude Connector (Easiest)
This is the fastest way to connect — no downloads, no config files, no terminal.
In Claude, go to **Settings** → **Connectors** → **Custom Connectors**.
Paste this URL: `https://app.getwhitewhale.com/mcp`
Press connect and in Claude you will be prompted to login to your account and authorize to complete the Claude connection.
Open a new chat and tell Claude who you are and what you want. Example prompt:
```text theme={null}
Please pull my best 5 accounts from WhiteWhale for [YOUR COMPANY].
I want to know exactly why they are good for what I sell.
```
Claude will respond with your actual WhiteWhale data. From here, keep asking questions in plain English — "Show me signals on \[company]", "What's my score on \[account]", "Add these domains to my list."
***
## Setup: MCP (Advanced)
If you use the Claude Code or ChatGPT, you can connect via a config file instead.
**Requires:** [Node.js 18 or later](https://nodejs.org)
Open this file in any text editor:
* **Mac:** `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
If the file doesn't exist yet, create it.
Paste the following into the file, replacing the placeholder values with your actual API key and email:
```json theme={null}
{
"mcpServers": {
"whitewhale": {
"command": "npx",
"args": ["-y", "@getbirddog/mcp"],
"env": {
"BIRDDOG_API_KEY": "your-api-key-here",
"BIRDDOG_USER": "you@yourcompany.com"
}
}
}
}
```
Fully quit and reopen Claude Desktop. You should see **whitewhale** appear in the tools list.
***
## Setup: Claude Code
If you use Claude Code (the command line version), run this command in your terminal:
```bash theme={null}
claude mcp add whitewhale \
-e BIRDDOG_API_KEY=your-key \
-e BIRDDOG_USER=you@company.com \
-- npx -y @getbirddog/mcp
```
***
## Built-in workflows
Claude comes with a set of pre-built WhiteWhale workflows you can trigger with a single prompt:
| Ask Claude | What it does |
| ------------------------------- | ---------------------------------------------------------- |
| *"Show me my daily priorities"* | Your highest-scoring accounts ranked by signal activity |
| *"Add accounts"* | Validates and uploads a list of companies |
| *"Review my signals"* | Checks your current signal setup and suggests improvements |
| *"Find new accounts"* | Runs Account Suggestions to discover new target accounts |
| *"Give me an account overview"* | Full summary of your WhiteWhale setup and health |
***
## Troubleshooting
Fully quit and restart Claude Desktop or Claude Code after editing the config file. A partial close won't pick up the changes.
Check that your API key has no extra spaces or line breaks when you pasted it. Make sure `BIRDDOG_USER` is the exact email address you use to log into WhiteWhale.
Make sure `BIRDDOG_API_KEY` and `BIRDDOG_USER` are inside the `"env"` block in your config file, not in the `"args"` section.
Run `node --version` in your terminal. If it shows lower than v18, [download the latest version of Node.js](https://nodejs.org).
Run `npx --yes @getbirddog/mcp@latest` in your terminal.
***
## Optional: faster startup
By default, the MCP downloads fresh each time Claude starts. To make it launch faster, install it globally:
```bash theme={null}
npm install -g @getbirddog/mcp
```
Then change `"command": "npx"` to `"command": "birddog-mcp"` and remove the `"args"` line from your config.
***
Keep your API key secure. Never paste it into a shared document or commit your config file to version control. Add `claude_desktop_config.json` and `.claude/mcp.json` to your `.gitignore`.
**GitHub:** [github.com/BirdDog-Intel/WhiteWhale-MCP](https://github.com/BirdDog-Intel/WhiteWhale-MCP)
## Related
Access WhiteWhale data programmatically without Claude.
Understand the account data Claude is pulling for you.
# Microsoft Teams
Source: https://docs.getwhitewhale.com/microsoft-teams
Get WhiteWhale buying signal alerts delivered directly to your Microsoft Teams channels. Keep your sales team updated on account activity without leaving Teams.
WhiteWhale can send signal alerts, account suggestions, and deal updates directly into your Microsoft Teams channels — so your reps get notified where they already work.
**Teams alerts are available on Enterprise plans.** To get set up, contact the WhiteWhale team at [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) and they'll walk you through the configuration.
## What you'll receive in Teams
Once connected, WhiteWhale delivers the same alerts as Slack — directly into the channel of your choice:
* **Daily Signals** — new signal activity on your accounts, with the source, key details, and a link back to the platform or your CRM
* **Assigned Accounts** — when a new account is assigned to a rep
* **Recommended Accounts** — when Account Suggestions surfaces new matches
## Getting set up
Teams setup is handled by the WhiteWhale team. Reach out and they'll get your workspace connected.
Email [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) to get Teams alerts configured for your account.
## After setup: turn on your notifications
Once your workspace is connected, each rep should go to **Settings** → **User Notifications** and enable the alerts they want to receive in Teams.
At minimum, turn on **Daily Signals** and **Assigned Accounts** to get full value from the integration.
## Related
Set up signal alerts in Slack — available on all plans.
Find signal activity directly in the platform.
# Muting Signals
Source: https://docs.getwhitewhale.com/muting-signals
Mute a WhiteWhale signal to stop alerts without deleting it. Muted signals stay in your library and continue scoring accounts but will not trigger notifications.
## How to mute a signal
From the Signals page, click the **bell icon** next to the signal you want to mute. When the bell turns red, the signal is muted.
Click it again to unmute.
## What muting does
Muting stops the signal from sending alerts through Slack, email, the API, and webhooks. The signal keeps running in the background — matches still appear on company cards and in account profiles, they just won't actively notify you.
## When to mute vs. leave active
A good rule of thumb: keep alerts on for signals that should change how you act on an account right now. Mute signals that are useful for context but not urgent enough to interrupt your workflow.
| Leave active | Mute |
| ----------------------------------------- | ---------------------------- |
| They shifted from self-serve to sales-led | Do they run ABM? |
| They hired a new CRO | What does the company do? |
| They posted about pipeline problems | Are they a Series B company? |
## Related
Permanently remove a signal you no longer need.
Fix signals that are too noisy or returning the wrong results.
# Pre-Meeting Research Brief
Source: https://docs.getwhitewhale.com/pre-meeting-research-brief
Get an automatic research brief with buying signals and Why Now context delivered 24 hours before every meeting. Works with Google Calendar and tracked accounts.
WhiteWhale connects to your Google Calendar and automatically prepares a research brief before any meeting with a tracked account. No manual prep needed — the brief lands in your inbox 24 hours before the call.
## What's in the brief
![Screenshot 2026 06 10 At 2 46 53 PM]()
Every brief includes:
* **Meeting time, HQ location, and company size** at a glance
* **What they do** — a plain-English summary of the company and what they build
* **Why Now** — the signal story: what's changed recently, what they're trying to achieve, and why now is the right time to be in front of them
## How to connect Google Calendar
In the left nav, go to **Settings** → **Integrations**.
Follow the prompts to authorize WhiteWhale to access your calendar.
You'll be asked to select one of three modes:
WhiteWhale analyzes your upcoming meetings and sends a research brief 24 hours before each meeting with a tracked account. Your account list stays as-is — nothing is added automatically.
WhiteWhale sends research briefs **and** automatically adds any account you have a meeting with to your WhiteWhale list. Good for reps who want their calendar to drive their account list. Keep in mind this will use account credits.
Calendar integration is paused. No briefs will be generated and no accounts will be added. Your connection is preserved so you can turn it back on anytime.
Not sure which mode to pick? Start with **On** (research briefs only). You get the full value of pre-meeting prep without touching your account list or credits. Switch to Auto Upload later if you want your calendar to automatically populate your book of business.
## Disconnecting
To disconnect Google Calendar, go to **Settings** → **Integrations** → **Google Calendar** and click **Disconnect**. You can reconnect at any time.
## Related
Understand the Why Now and how to use it to build your outreach angle.
Manually add accounts to your list.
Full setup guide and troubleshooting for the Google Calendar integration.
# Quick Start: Admin
Source: https://docs.getwhitewhale.com/quick-start-admin
Set up WhiteWhale in under an hour. This admin guide walks through creating signals, adding accounts, connecting your CRM, and inviting your sales team.
This guide walks you through everything you need to do as an admin to get WhiteWhale fully configured for your team. Follow these steps in order — each one builds on the last.
***
## Step 1: Invite your team
Add everyone who will be using WhiteWhale before you start assigning accounts.
Click **Team** in the left nav and click **Add User**.
Enter their name, email, and select a role:
* **Super Admin** — sales leadership, RevOps, anyone who needs full visibility
* **Member** — individual AEs and SDRs working their own territory
WhiteWhale emails them their login automatically.
Full guide to roles, permissions, and team configuration.
***
## Step 2: Build your signal list
Signals are the questions WhiteWhale asks about every account. A good signal list is the foundation of everything — account scores, live searches, and the Why Now summaries all depend on it.
**Aim for 10–15 signals.** Mark your top 5–8 as High priority.
Click **Signals** in the left nav, then click **Add Signal**.
Type what you're looking for in plain English. WhiteWhale will convert it into the right format. You don't need to phrase it as a question — just describe it.
Not sure what signals to add? Start here:
* Did they hire a new CRO or VP of Sales?
* Are they hiring multiple AEs or SDRs at once?
* Did they announce new funding?
* Are they expanding into a new market or geography?
* Do they mention a problem your product solves?
* **High** — your strongest buying signals. Use for 5–8 signals.
* **Normal** — standard weight signals.
* **Low** — background context, mute these so they don't flood your queue.
Build up to 10–15 signals before moving on.
Copy-paste templates organized by category — funding, hiring, leadership, technology, and more.
Build a signal list specific to your ICP and sales motion.
***
## Step 3: Add accounts or run a search
You have two options here — use one or **both**.
Use this if you already have a set of accounts you want to monitor — assigned territories, closed-lost deals, a target list from your CRM.
Go to the **Accounts** page → click **New Search** → select **Upload a List**. Name the list, paste your company domains, and assign an owner. WhiteWhale cleans up the formatting automatically.
If your list is larger than your credit limit, toggle on **Clean the List** to filter by signals and firmographics before uploading — so only the best accounts use your credits.
Full guide including the Clean the List feature for large lists.
Use this if you want WhiteWhale to find net-new accounts that match your ICP and already have signal activity.
Go to the **Accounts** page → click **New Search** → select **Find New Accounts**. Name the search, then set your filters:
* **Signals** — leave as Any Match (avoid Must Have for now)
* **Time range** — how recent signals need to be
* **Company size** — employee count range for your ICP
* **Industry** — match to LinkedIn industry categories
* **Location** — countries or US states you serve
Click **Save and Make Live Search**. Results often appear within minutes and grow daily as the search runs.
Full setup guide with filter recommendations.
You can run both at the same time. Many teams upload a known list of accounts and run a live search to find net-new ones in parallel.
***
## Step 4: Connect your integrations
Get WhiteWhale data flowing into the tools your team already uses.
Go to **Settings** → **Integrations** → find HubSpot or Salesforce and click **Set Up**. Use the one-click setup for a standard configuration.
Once connected, WhiteWhale scores, signals, and Why Now summaries sync to your CRM daily.
Setup guide and field reference.
Setup guide and field reference.
Go to **Settings** → **Integrations** → connect Slack or Teams. Once connected, your reps will get notified directly in their channel when a new signal fires on one of their accounts.
Have each rep go to **Settings** → **User Notifications** and turn on at minimum **Daily Signals** and **Assigned Accounts**.
Setup guide and notification options.
Setup guide and notification options.
Go to **Settings** → **Integrations** → **Google Calendar** → click **Connect**. Choose **On** to receive research briefs 24 hours before any meeting with a tracked account.
Setup guide and mode options.
***
## Step 5: Assign accounts to your team
Once accounts are in WhiteWhale — either uploaded directly or found by a live search — assign them to your reps.
**For accounts already in your list:** Click the **Owner** name on any account and select the rep it should go to.
**For accounts from a search:** Select the suggestions (shown in orange) using the checkboxes → click **Activate** → choose to assign to one person or round-robin across the team.
**Pro tip:** Filter by geography, industry, or employee count before assigning to quickly route accounts to the right rep by territory or segment.
Reassign ownership on accounts already in your list.
Bulk assign or round-robin accounts from your search results.
***
## You're set up. What's next?
Send your reps to the **Rep Quick Start** guide so they know how to work their queue from day one.
The rep's guide to working signals, using the Why Now, and booking meetings with WhiteWhale data.
# Quick Start: Rep
Source: https://docs.getwhitewhale.com/quick-start-rep
Start booking meetings with WhiteWhale on day one. Learn how to work your signal queue, read Why Now summaries, and turn buying signals into outreach.
WhiteWhale tells you which accounts to reach out to, why, and when. This guide walks you through how to get value out of it from your first login.
***
## Step 1: Check your accounts
![Screenshot 2026 06 10 At 4 50 17 PM]()
Your admin has already set up signals and assigned accounts to you. When you log in, you'll land on **All** — this shows every account in your WhiteWhale instance. To see just your accounts, filter by your name under the owner filter.
If your admin has run specific searches, you can also click into those to see the accounts and suggestions from that search.
Every account has a score from 0 to 100. Higher scores mean more recent, higher-ranked signals have fired. A score anywhere from 15 to 50 is a solid account worth working. Scores above 50 are strong. You'll rarely see anything above 70.
Understand what the score means and what a good score looks like for your book.
***
## Step 2: Find your freshest signal activity
![Screenshot 2026 06 10 At 4 50 41 PM]()
Don't start with your account list from top to bottom. Start with what's new.
Your accounts are already sorted by most recent signal date. The accounts at the top have the freshest activity — start there. Accounts with signal activity from the last 1–3 days are your highest priority — something just happened and you have a narrow window to act on it.
You can also use **Filters** → **Signal Recency** to narrow to a specific time window, or filter by a specific signal to find accounts where a particular trigger fired recently.
Sort and filter your accounts by signal date to find the best timing.
***
## Step 3: Read the Why Now before you reach out
![Screenshot 2026 06 10 At 4 51 11 PM]()
Click into any account and read the **Why Now summary** first. It connects the dots between everything WhiteWhale found on the account and tells you in 2–3 sentences what's changing, why it matters, and why now is the right time to reach out.
This is the most important thing WhiteWhale gives you. Use it to decide whether an account is worth your time — and if it is, use it as the foundation of your outreach.
**Ask yourself:** How does this Why Now connect to what I sell? What problem does it imply they're facing? How have I solved that before?
How to read the Why Now and use it to build your outreach angle.
***
## Step 4: Use Claude to build your pitch (Optional)
![Screenshot 2026 06 10 At 4 01 22 PM]()
Once you have the Why Now, don't start from a blank page. Copy the summary and paste it into Claude with a simple prompt:
> *"Here's what's happening at this account: \[paste Why Now]. We sell \[product] that helps companies \[outcome]. Help me write a 2–3 sentence opener that connects their situation to our value."*
Claude will turn your signal data into a specific, personalized message in seconds. You can also ask Claude to help you understand the account better, identify the right contact to reach out to, or draft a follow-up sequence.
If your team has the **Claude MCP** set up, you can ask Claude directly about your WhiteWhale accounts without ever leaving the conversation:
* *"Which of my accounts should I prioritize today?"*
* *"What's happening at \[company]?"*
* *"Show me all my accounts with new CRO signals"*
Connect Claude to your WhiteWhale data for hands-free research.
Get the full signal story before you write a word.
***
## Step 5: Send the right message
We don't tell you how to do outreach, and we can't even promise meetings because so much goes into booking one. However, if you are looking for a place to get started after over 700 sellers have used WhiteWhale, the outreach that works from WhiteWhale follows a simple format every time:
1. **I noticed** — reference the specific signal you saw
2. **I bet** — name the problem that signal implies
3. **Here's how we help** — connect it to your product
4. **Lead magnet** — give them a reason to respond
**Example:**
> *Jeff — I wouldn't reach out if I hadn't done my homework. Saw you were hiring for 5 inbound SDRs taking demos. I'd bet you're thinking about how to ramp those reps fast so they can start generating pipeline. Usually the problem is teaching them the nuance of the pitch. If that's something you're thinking about, I have a 1-pager I built specifically for your company — want me to send it over?*
The channel matters less than the message. The best teams use a mix of calls, emails, and LinkedIn notes. What makes them work is leading with the signal — showing the prospect you did your homework before you said a word.
Real examples and the full framework for signal-based outreach.
***
## Step 6: Set up your notifications
Make sure WhiteWhale can reach you when something happens on your accounts.
**Slack or Teams:** Ask your admin to confirm you're connected. Then go to **Settings** → **User Notifications** and turn on at minimum:
* **Daily Signals** — new signal activity on your accounts
* **Assigned Accounts** — when a new account is assigned to you
**Google Calendar:** Connect your calendar and WhiteWhale will send you a research brief 24 hours before any meeting with a tracked account — so you always walk in prepared.
Get signal alerts in Slack.
Automatic research before every meeting with a tracked account.
***
## The data doesn't look right?
WhiteWhale is fully customizable — the signals, filters, and search settings your admin chose are a starting point, not permanent. If you're seeing:
* **Signals firing from the wrong geography** — the signal needs a location constraint added
* **Signals that are too broad or not relevant** — the signal needs more context or a tighter description
* **Accounts that don't fit your ICP** — the search filters need adjusting
* **Scores that seem off** — it may be a signal priority issue
You can't break anything by flagging this. Send your admin the specific example and point them to the relevant docs. The system improves the more it's tuned.
Share with your admin when signals are noisy or off-target.
Share with your admin when search results aren't the right fit.
***
## What good looks like
Before WhiteWhale, you're pulling accounts based on firmographics alone — industry, size, geography. No idea if the timing is right.
With WhiteWhale, every account you reach out to has a reason. Something changed. Something happened. You're not guessing — you're acting on a signal that tells you this account has a problem right now that you can solve.
The reps who get the most out of WhiteWhale check their new signals daily, read the Why Now before they reach out, and lead every message with the specific thing they noticed. That's it. Same accounts, same messaging — just better timing and better context.
See what the best teams are doing with WhiteWhale data.
# Removing Accounts
Source: https://docs.getwhitewhale.com/removing-accounts
Permanently delete accounts from WhiteWhale — one at a time or in bulk.
## Remove one account
Scroll to the far right of the account row and click **Remove**. You'll have the option to provide feedback before the account is pulled out.
## Remove accounts in bulk
Select multiple accounts using the checkboxes, then click **Delete**. All selected accounts are removed at once.
Deleting an account removes it and all its signal data permanently. This cannot be undone. If you want to preserve the signal history and free up a credit, [archive the account](/archiving-accounts) instead.
## Archive vs. delete
| | Archive | Delete |
| ------------------------ | ------- | ------ |
| Frees up a credit slot | ✓ | ✓ |
| Signal history preserved | ✓ | ✗ |
| Can be reversed | ✓ | ✗ |
When in doubt, archive. It keeps your data and achieves the same result.
## Related
Pause an account and preserve its signal history.
Add a new account after freeing up a slot.
# Removing Users
Source: https://docs.getwhitewhale.com/removing-users
Remove a team member from your WhiteWhale workspace. Reassign their accounts to other reps before removing them to keep your book of business fully covered.
## How to remove a user
Click **Team** in the left nav.
Hover over the user's row — a trash icon will appear on the right side.
The user is immediately removed from the platform.
Removing a user cannot be undone. They will lose all account assignments and any settings they had configured. You can re-invite them, but they will start fresh.
Only remove users who have left the team or no longer need access — not as a way to temporarily pause access.
## Related
Invite a new team member or re-add a previous one.
Adjust what a user can see and do without removing them.
# Roles & Permissions
Source: https://docs.getwhitewhale.com/roles-and-permissions
Understand what Super Admins and Members can see and do in WhiteWhale. Control who manages signals, assigns accounts, invites users, and views team-wide data.
WhiteWhale has two roles: **Super Admin** and **Member**. Members can be further customized with optional viewer and admin permissions.
## Role overview
| Permission | Super Admin | Member | Member + Admin | Member + Viewer |
| ------------------------------- | ----------- | ------ | -------------- | --------------- |
| See all team accounts | ✓ | ✗ | ✓ | ✗ |
| See assigned accounts only | ✗ | ✓ | ✓ | ✓ |
| View a specific user's accounts | ✗ | ✗ | ✓ | ✓ |
| Edit signals | ✓ | ✗ | ✓ | ✗ |
| Manage Account Suggestions | ✓ | ✗ | ✓ | ✗ |
| Manage team members | ✓ | ✗ | ✓ | ✗ |
| Assign accounts to other users | ✓ | ✗ | ✓ | ✗ |
## Super Admin
Super Admins have full visibility and control across the platform. They can see every account regardless of who it's assigned to, edit signals, manage Account Suggestions, and administer the team.
**Best for:** Sales leadership, RevOps, go-to-market engineers, and anyone who needs a complete view of the team's book of business.
## Member
Members work their own list. By default they only see accounts assigned to them — they have no visibility into other reps' accounts.
**Best for:** Individual AEs and SDRs working their own territory.
Members can be given two optional permissions when you add or edit them:
**Admin access** — elevates a Member to have the same platform controls as a Super Admin, including signal editing, Suggestions management, and team administration. Use this for a team lead or senior rep who needs management access without a full Super Admin seat.
**Viewer access** — lets a Member see a specific user's accounts without being assigned to them. The viewer cannot edit or reassign those accounts — read-only visibility only.
Viewer access is designed for SDR/AE pairs and team structures where one person needs visibility into another's book without owning it.
Common setups:
* An SDR needs to see their paired AE's accounts to support outreach
* An SDR is working with multiple AEs and needs visibility across all of them
* A manager wants a rep to have read-only access to a specific territory for learning or handoff purposes
## Choosing the right role
| If they are... | Give them... |
| ---------------------------------------- | ---------------------------- |
| A CRO, VP of Sales, or RevOps lead | Super Admin |
| A go-to-market engineer or sales ops | Super Admin |
| An AE working their own territory | Member |
| An SDR working their own outreach | Member |
| An SDR paired with an AE | Member + Viewer (of that AE) |
| A team lead who needs to manage settings | Member + Admin |
## Related
Invite a new team member and assign their role.
Remove a team member from the platform.
Assign accounts to team members after they've been added.
# Salesforce
Source: https://docs.getwhitewhale.com/salesforce
Connect WhiteWhale to Salesforce to sync account scores, buying signals, and Why Now summaries directly into your CRM records. Setup guide and field mapping included.
Connecting Salesforce keeps WhiteWhale data — scores, signals, and Why Now summaries — inside the CRM your reps already work in. No manual uploads, no spreadsheets.
## What the integration does
* **Daily sync** — WhiteWhale pulls your accounts and opportunities from Salesforce each day and pushes updated scores, signals, and Why Now summaries back to the mapped fields
* **Real-time updates** — when a new account is added or activated in WhiteWhale, it immediately syncs to Salesforce
* **Deal context** — mapping your opportunities lets WhiteWhale surface different signals based on where each prospect is in your pipeline
## How to connect
Click **Settings** in the left nav, then navigate to **Integrations**.
Scroll to the Integrations module and click **Salesforce**.
Select **Default** for your production org or **Sandbox** for testing, then click **Submit**.
You'll be redirected to Salesforce. Log in with your Integration User credentials to complete the OAuth flow.
Once connected, map your Salesforce fields to WhiteWhale's fields inside the platform. See the field reference below.
Use a dedicated Integration User with API access and read/write permissions on Accounts, rather than a personal user account. This keeps the connection stable if individual users leave or change roles.
***
## Field reference
### Account fields
| Field | Required | Description |
| ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------- |
| `sf_id` | ✅ | Salesforce Account ID |
| `Account_Domain` | ✅ | Company website URL. WhiteWhale can only process accounts that have a domain on record. |
| `WhiteWhale_Description` | Optional | WhiteWhale's Why Now summary for the account |
| `WhiteWhale_Score` | Optional | Account score from 0–100 based on signal strength |
| `WhiteWhale_Link` | Optional | Direct link to the account's report in WhiteWhale |
| `WhiteWhale_User` | Optional | Links the account to the assigned WhiteWhale user. Most teams map this to the existing Account Owner field. |
| `WhiteWhale_Signals` | Optional | Most recent signals matching this account |
### Recommended custom field configurations
Create these fields on the Account object in Salesforce before mapping. Make sure all fields are visible to relevant users and accessible to API integrations.
* **Type:** Text Area (Long)
* **Label:** WhiteWhale\_Description
* **Length:** 1,000 characters
* **Help text:** Summary of WhiteWhale signals for the account
* **Type:** Number (0–100)
* **Label:** WhiteWhale\_Score
* **Help text:** Auto-populated WhiteWhale signal score
* **Type:** URL
* **Label:** WhiteWhale\_Link
* **Help text:** Link to the full account report in WhiteWhale
* **Type:** Rich Text
* **Label:** WhiteWhale\_Signals
* **Help text:** Latest WhiteWhale signals for the account
### Opportunity fields
Mapping opportunities is optional but lets WhiteWhale tailor signal recommendations based on deal stage and helps backtest which signals correlate with closed-won deals.
| Field | Required | Description |
| --------------- | -------- | -------------------------------- |
| `sf_id` | ✅ | Salesforce Opportunity ID |
| `sf_account_id` | ✅ | ID of the related account |
| `Name` | Optional | Opportunity name |
| `Stage_name` | Optional | Current deal stage |
| `Amount` | Optional | Deal value |
| `Close_date` | Optional | Expected close date |
| `Prob` | Optional | Close probability |
| `Next_step` | Optional | Next planned action |
| `Lead_source` | Optional | Opportunity lead source |
| `Is_closed` | Optional | Whether the deal is closed |
| `Is_won` | Optional | Whether the deal is won |
| `Created_date` | Optional | Date the opportunity was created |
***
## User mapping
WhiteWhale identifies users by their company email address. To link WhiteWhale users to their Salesforce counterparts, send a two-column CSV (email, Salesforce user ID) to [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com). This ensures signals, accounts, and opportunities are correctly attributed by rep.
***
## How the sync works
* **Daily sync window:** WhiteWhale runs at least one pull and push operation per day, keeping your Salesforce fields up to date automatically
* **Real-time updates:** When a new account is added or activated in WhiteWhale, Salesforce is updated immediately
* **First week:** Expect a higher sync frequency while the integration calibrates. Around 100 API calls per day is typical after the initial period.
* **Read/write scope:** WhiteWhale only reads from the fields you map and only writes to the WhiteWhale-specific fields you create. It will not modify any other Salesforce data.
***
## Authentication details
WhiteWhale connects via a Salesforce Connected App hosted within WhiteWhale's org. When your first user authenticates, Salesforce automatically creates a shadow copy of the app in your own org — visible under **Setup → App Manager**. No package installation is required.
**OAuth scopes:**
* Manage user data via APIs (`api`)
* Perform requests at any time (`refresh_token`, `offline_access`)
* Access unique user identifiers (`openid`)
**To revoke access:** Go to **Setup → Security → Connected Apps OAuth Usage** in Salesforce and revoke the token there. You can also contact WhiteWhale and we'll disconnect and delete all authentication data on request.
**Sandbox support:** WhiteWhale supports Salesforce sandbox environments. Select **Sandbox** during setup to connect your test environment using the same flow as production.
***
## Need help?
Contact the WhiteWhale team at [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com) for setup assistance or advanced configuration help.
## Related
Connect WhiteWhale to HubSpot.
Push WhiteWhale data to your own systems.
Access WhiteWhale data programmatically.
Get signal alerts delivered to Slack.
# Setting Up Account Searches
Source: https://docs.getwhitewhale.com/setting-up-account-suggestions
Run a live search to find net-new accounts with your signals across millions of companies.
Account Suggestions is one of the most powerful features in WhiteWhale. It searches through millions of companies and tens of millions of sources — news articles, press releases, job postings, websites — to find accounts that match your signals right now.
## How to run a search
Select **Find New Accounts** (not Upload a List — that's for adding accounts you already have).
Give it a descriptive name — for example, *Building Outbound* or *New CROs in SaaS*.
Choose which signals you want accounts to match. Each signal can be set to **Any Match** (light purple — the default) or **Must Have** (requires every account to have that signal).
Avoid using Must Have on more than one signal. If you require five signals, an account needs all five to show up — which almost never happens. Stick to Any Match unless you're narrowing by a single defining characteristic like "uses usage-based pricing."
Configure the remaining parameters:
* **Time range** — how recent signals need to be (e.g., within the last year)
* **Company size** — employee count range that fits your ICP
* **Industry** — one or more industries you typically sell into
* **Location** — countries or US states
WhiteWhale will show you the total number of companies that fit your filters. This is how many records it will search through for your signals.
A search across 10,000 records will return results quickly. A search across 800,000 records will take significantly longer — consider narrowing your filters if the number is too high.
WhiteWhale starts scanning immediately. You'll often see results within minutes — accounts that already have your signals. More will continue to appear every day as the search runs through the remaining records.
## How live searches work
A live search runs automatically every night, searching through your parameters for new accounts with your signals. Results show up in your search list and keep growing over time.
Your plan includes a set number of live searches — most plans allow one at a time, though higher plans may have more. You can update the filters on a live search at any time, and the search will re-run with the new parameters.
To check if a search is live, click on it — it will say **Live** at the top if it's actively running. If it doesn't say Live, it's paused and won't find new accounts until you make it live again.
## Deleting a search
Hover over the search name and you'll see a dot with a minus icon appear. Click it to remove the search. This frees up a live search slot if you want to run a different one.
Start narrow and expand. A focused search across 10,000 records with 2–3 signals will return high-quality results fast. You can always widen the filters later once you see what's coming in.
## Common mistakes
First, make sure the search is live. Click on the search — it should say **Live** at the top. If it doesn't, make it live. Most plans only allow one live search at a time, so if you have another search set to live, you'll need to switch it.
If it is live, check the Jobs button at the top to see if a scan is currently running. Searches run overnight and can take a few hours to complete.
If your search is scanning 800,000 records, it will take days or weeks to work through them all. Results will trickle in slowly. Narrow your filters — tighten industry, location, or company size — to bring the number down to a more manageable range.
If you set multiple signals to Must Have, an account needs every single one to appear. Four out of five won't cut it. This is the most common reason for zero or near-zero results. Switch to Any Match and results will increase significantly.
Check all of the above first. Then verify your signals are actually firing on your existing accounts — if a signal returns zero results on accounts you already track, it won't return results in a search either. See [Improving Signals](/improving-signals).
## What happens next
Matched accounts appear in your search results. From there you can activate them, assign them to reps, or round-robin them across the team.
Change your filters or signal requirements after the search is live.
Mark suggestions as good or bad fit to improve future results.
Assign accounts to reps individually, in bulk, or via round-robin.
# Signal Library
Source: https://docs.getwhitewhale.com/signal-library
Browse the WhiteWhale Signal Library for curated buying signal templates organized by category. Copy proven signals or use them as inspiration for your own.
## Use Claude to build your signal list
The fastest way to build a great signal list is to use the WhiteWhale Signal Creator — a Claude skill trained specifically on how WhiteWhale signals work, what makes them fire reliably, and how to write the non-obvious signals that actually move deals.
Tell it what you sell, who you sell to, and what triggers a purchase. It will generate a prioritized signal set with explanations for each one.
A Claude skill that builds a custom signal list for your ICP. Works in Claude.ai and Claude Desktop.
**How to use it:**
1. Download the `.skill` file above
2. Open [Claude.ai](https://claude.ai) and upload the file, or install it in Claude Desktop
3. Tell Claude what you sell, who buys it, and what your best customers looked like before they bought
4. Claude will generate a prioritized, ready-to-paste signal set tailored to your business
The skill is trained to find the non-obvious signals — the ones in job postings, website language, and company behavior that reveal pain without ever mentioning your product category. These are the signals that drive the most pipeline.
***
## Using the Signal Library in WhiteWhale
The fastest way to find signal ideas is directly inside the platform. WhiteWhale reads your business and generates suggestions tailored to your ICP — no blank page, no guessing.
From the Signals page, click **Add Signal** in the top right.
Switch to the **Signal Library** tab. WhiteWhale will generate a list of signal ideas based on your business.
Browse the suggestions and click into any one you want to add. For example: *Do they use Outreach?* or *Are they hiring an SDR manager?*
Assign a priority — **Low**, **Medium**, or **High** — and click **Add Signal**. It joins your list and starts scanning immediately.
Not sure where to start? The in-platform library is the best first stop. Come back to the templates below to fill gaps or go deeper on a specific category.
***
## Copy-paste templates
All signals follow the same pattern: **Does** **\[observable behavior or announcement] \[with qualifiers]?** The templates below are ready to paste into WhiteWhale. Adjust the qualifiers to match your ICP.
## Starter Pack: 25 signals to get going
These cover the essentials across funding, hiring, leadership, and strategy. Start here if you're building your signal list from scratch. Mark your top 5–8 as **High** priority.
1. Does have any mergers or acquisitions (M\&A) in progress or recently announced?
2. Has announced new venture capital or private equity funding?
3. Is expanding into a new market or geography?
4. Has appointed new leadership (CEO, CRO, CMO, CIO, CISO, VP Sales, VP Marketing)?
5. Has launched any new products or major features?
6. Is hiring multiple sales roles (AEs/SDRs) at once?
7. Is hiring roles related to digital transformation or modernization?
8. Is hiring data, AI/ML, or analytics roles?
9. Is hiring security or compliance roles?
10. Has opened a new office or facility?
11. Has announced layoffs, restructuring, or a reorg?
12. Is migrating to or standardizing on a specific cloud provider?
13. Does mention vendor consolidation or tool rationalization?
14. Is running pilots or proofs of concept (POCs)?
15. Has issued an RFP or tender in our category?
16. Does mention new partnerships or alliances?
17. Has won government or enterprise contracts recently?
18. Is pursuing certifications or audits (SOC 2, ISO 27001, FedRAMP, HIPAA)?
19. Has announced a strategic initiative or transformation program?
20. Has reported material changes in earnings calls related to our solution area?
21. Is adopting or sunsetting relevant technologies or platforms?
22. Is expanding headcount rapidly in our ICP functions?
23. Does mention intent data, account research, or programmatic outbound?
24. Has entered new vertical segments or customer tiers?
25. Is experiencing incidents or outages that may drive urgency?
If a starter signal is too noisy, add a qualifier in the Context Window. For example: *"Exclude staffing firms, agencies, and holding companies. Focus on B2B companies only."*
***
## Signals by category
* Has announced new funding (seed, A, B, C, PE)?
* Does have any M\&A activity (acquiring or being acquired)?
* Has divested a business unit or asset?
* Has hired a new CRO or Head of Sales?
* Has hired a new CMO or VP Marketing?
* Has hired a new CIO, CTO, or CISO?
* Has restructured or reorganized departments relevant to our solution?
* Has launched a new product, platform, or feature relevant to our solution?
* Is running a pilot or POC in our category?
* Does mention a transformation initiative (digital, data, AI, security)?
* Is hiring multiple sales roles (AEs/SDRs) concurrently?
* Is hiring data, AI, or analytics roles?
* Is hiring security or compliance roles?
* Is hiring RevOps or sales operations roles?
* Is entering a new market or region?
* Has announced a partnership or alliance relevant to our solution?
* Has opened a new office or facility?
* Is migrating to a specific cloud (AWS, Azure, GCP)?
* Is consolidating vendors or rationalizing tools?
* Has adopted or replaced a core platform in our ecosystem?
* Has faced a notable incident or outage with customer impact?
* Is pursuing SOC 2, ISO 27001, HIPAA, or FedRAMP certification?
* Has announced regulatory exposure or deadlines that relate to our solution?
Use these as negative filters to keep your queue clean. Add them to your list and mute them — they'll suppress irrelevant accounts from surfacing.
* Is primarily a recruiting or staffing firm?
* Is a consumer-only (B2C) brand with no B2B motion?
* Is outside of our supported geographies?
* Does exclusively serve SMB if we target enterprise?
* Does lack a sales or marketing function?
**Context to add:** *"Exclude staffing firms, agencies, and holding companies. Focus on B2B."*
***
## Signal writing frameworks
Use these when the starter pack doesn't fit your ICP or you want to build something more specific.
The fastest way to construct a valid signal:
* Does mention ``?
* Is hiring ``?
* Has announced ``?
* Is expanding into ``?
* Is consolidating or replacing ``?
Match a buyer persona to a pain point and a triggering event.
| Persona | Pain | Trigger |
| --------- | --------------- | ------------------- |
| Sales | Pipeline growth | New CRO |
| Marketing | Enablement | Hiring burst |
| IT | Modernization | Platform migration |
| Security | Compliance | Regulation or audit |
**Example:** Does have a new CISO and mention security modernization or compliance gaps?
Build one signal per buying stage to cover the full funnel.
| Stage | What to look for | Example signal |
| ------------- | ------------------------------ | -------------- |
| Awareness | Mentions the problem | |
| Consideration | Hiring, programs, budgets | |
| Decision | RFPs, pilots, platform choices | |
Pair a change event with its intended outcome for higher-precision signals.
**Pattern:** Has `` to achieve ``?
**Example:** Has centralized GTM operations to accelerate revenue growth?
Add these directly in the Context Window to tighten any signal.
| Qualifier type | Example context |
| -------------- | ----------------------------------------------------------------- |
| Region | *US, Canada, UK, and EU only* |
| Recency | *Prioritize results from the last 90 days* |
| Seniority | *Leadership announcements and manager-level roles and above only* |
***
## Related
Add signals from the description box or directly from this library inside the platform.
Build a signal list tailored specifically to your ICP and sales motion.
Fix signals that are too broad, wrong geography, or returning stale results.
Understand what sources WhiteWhale monitors and how signals become alerts.
# Slack
Source: https://docs.getwhitewhale.com/slack
Connect WhiteWhale to Slack to get buying signal alerts, account suggestions, and deal updates delivered to team channels or individual reps automatically.
## What you'll see in Slack
Once connected, WhiteWhale sends alerts directly to your Slack. Each alert includes the signal source, a quote or detail from that source, and a link back to the account in WhiteWhale or your CRM.
You can also receive alerts for account suggestions when new matches are found, and deal revival notifications if you have a CRM connected.
## Step 1: Add the WhiteWhale app to your Slack channel
During onboarding you'll be prompted to add the WhiteWhale app to your Slack workspace. Search for **WhiteWhale** in the Slack App Directory and add it to the channel where you want alerts to appear.
If you missed this during onboarding, you can add the app at any time from the Slack App Directory.
## Step 2: Turn on your notifications
Click **Settings** in the left nav and scroll down to **User Notifications**.
| Notification | Delivered via | What it does |
| ------------------------ | ------------- | -------------------------------------------------------------------- |
| **Daily Signals** | Slack | Alerts for net-new signals found on your accounts. Turn this on. |
| **Deal or Revive** | Slack | Monitors closed-lost deals for new activity. Requires CRM connected. |
| **Assigned Accounts** | Slack + Email | Notifies you when an account is assigned to you. |
| **Recommended Accounts** | Slack | Notifies you when new Account Suggestions are found. |
| **Pipeline Overview** | Email only | Weekly pipeline summary. Not delivered via Slack. |
| **Assignment Overview** | Email only | Assignment summary. Not delivered via Slack. |
At minimum, enable **Daily Signals** and **Assigned Accounts** to get full value from the integration.
## Step 3: Set up personal tagging
To get tagged in Slack alerts so you receive notifications, you need to connect your Slack Member ID to your WhiteWhale profile.
In Slack, click your profile picture or name. In the profile panel that opens, click the **three-dot menu** (⋯) and select **Copy Member ID**.
In WhiteWhale Settings, paste your Member ID into the Slack ID field and click **Save**.
Once saved, WhiteWhale will tag you directly in alerts for your accounts.
## Related
Set up signal alerts in Microsoft Teams.
Find recent signal activity in the platform.
Connect your CRM to unlock deal revival alerts.
# Using the Why Now Summary
Source: https://docs.getwhitewhale.com/using-the-why-now-summary
Learn how to read the WhiteWhale Why Now summary to quickly assess an account and craft outreach with the specific context that gets replies from prospects.
**The Why Now summary is the most important output WhiteWhale produces.** Most signal tools send you one data point. WhiteWhale connects the dots between multiple signals and writes a two to three sentence story explaining why this account matters right now — and why you should reach out today rather than next quarter.
## What the Why Now tells you
Click into any account and you'll see three things: the Why Now summary, the underlying signals that informed it, and the sources those signals came from.
The Why Now pulls from all active signals on the account — the facts, quotes, numbers, and dates — and synthesizes them into a coherent story. A good Why Now tells you what's changing at the company, why that creates urgency, and what outcome they're likely trying to achieve.
**In about two seconds, you should know whether this account is worth your time.**
## How to use it
**Step 1: Read the Why Now first.** Before digging into individual signals, read the summary. If the story doesn't connect to what you sell, move on. If it does, go deeper.
**Step 2: Dig into the signals.** The signals beneath the summary are the raw evidence — the job postings, press releases, earnings quotes, and website changes that built the story. Use these to get specific details you can reference in outreach.
**Step 3: Build your angle with AI.** Once you know the story, use an AI tool to help you turn it into a pitch. Copy the Why Now and relevant signal details into Claude, ChatGPT, or Gemini and ask it to help you connect the account's situation to what you sell.
For example:
> *"Here's what's happening at this account: \[paste Why Now]. We sell \[product] that helps companies \[outcome]. Help me write a two-sentence opener that connects their situation to our value prop."*
This is how the best teams on WhiteWhale are turning signal data into pipeline — not by sending generic outreach, but by leading with the specific story happening at the account right now.
The Why Now is only as strong as your signals. If the summary feels generic or off, it's usually a sign that your signals need to be more specific to your ICP. See [How to Get Unique Signal Ideas](/how-to-get-unique-signal-ideas).
## Related
Find your most recent signal activity across all accounts.
Use WhiteWhale signal data to prep for a call in minutes.
Better signals produce better Why Now summaries.
Connect WhiteWhale directly to Claude to work with signal data without copy-pasting.
# Webhooks
Source: https://docs.getwhitewhale.com/webhooks
Receive WhiteWhale buying signal and account events in real time via webhook. Push data to Clay, Zapier, custom workflows, or any endpoint that accepts JSON.
WhiteWhale can POST events to any URL you specify whenever a signal fires or an account is added from suggestions. Use webhooks to pipe data into Clay, trigger automations, update internal tools, or build custom CRM integrations.
## Setup
There are two ways to register a webhook URL.
**Option 1: In the platform:** Go to **Settings** → **API & Webhooks** → paste your endpoint URL and save.
**Option 2: Via the API:** `POST /v1/set_webhook` with your URL in the request body.
```bash theme={null}
curl -X POST https://app.getwhitewhale.com/v1/set_webhook \
-H "api-key: YOUR_API_KEY" \
-H "user: you@company.com" \
-H "Content-Type: application/json" \
-d '{"webhook_url": "https://your-endpoint.com/whitewhale"}'
```
One webhook URL per account. The same endpoint receives all event types.
***
## Testing your webhook
Before going live, send a test payload to your endpoint using the API.
```bash theme={null}
curl -X POST https://app.getwhitewhale.com/v1/test_webhook \
-H "api-key: YOUR_API_KEY" \
-H "user: you@company.com" \
-H "Content-Type: application/json" \
-d '{
"event_type": "account.signal",
"spoof_payload": true
}'
```
| Parameter | Description |
| --------------- | ----------------------------------------------------------------------------------------------------- |
| `event_type` | `"account.upload"` or `"account.signal"` |
| `spoof_payload` | `true` returns a fake payload with the correct structure. Requires at least one signal on an account. |
| `icp_name` | Optional. If provided, returns a real signal and account name instead of spoofed data. |
The payload returned in the API response is unsigned. The payload delivered to your actual webhook endpoint will be signed.
***
## Event types
WhiteWhale sends two types of events.
Sent every morning when a new signal match is found. This is the most common event type and the primary source of daily signal data.
**Payload structure:**
```json theme={null}
{
"event": "account.signal",
"event_time": "2025-06-10T08:00:00Z",
"data": [
{
"owner_email": "rep@company.com",
"account": "acme.com",
"signal_name": "New CRO Hired",
"source": "https://techcrunch.com/...",
"pub_date": "2025-06-09T14:30:00Z",
"why_now": "Acme just brought in a new CRO from Salesforce who has publicly committed to overhauling their outbound motion over the next 90 days.",
"full_signal_summary": "...",
"crm_account_id": "hs_123456",
"article_summary": {
"headline": "Acme Corp Appoints New Chief Revenue Officer",
"quotes": ["We're rebuilding our GTM from the ground up"],
"relevant_facts": ["New CRO previously led sales at Salesforce", "Acme targeting 3x revenue growth"],
"one_sentence_summary": "Acme hired a new CRO with a mandate to overhaul their sales motion.",
"signal_summary": "...",
"document_type": "news_article"
}
}
]
}
```
**Signal payload fields:**
| Field | Type | Description |
| -------------------------------------- | -------- | --------------------------------------------------------------- |
| `owner_email` | string | WhiteWhale user who owns the account |
| `account` | string | Account domain |
| `signal_name` | string | Name of the signal that fired |
| `source` | string | URL of the source document |
| `pub_date` | datetime | Publication date of the source |
| `why_now` | string | WhiteWhale's Why Now summary for the account |
| `full_signal_summary` | string | Extended summary of the signal |
| `crm_account_id` | string | CRM account ID if CRM is connected |
| `article_summary.headline` | string | Headline of the source document |
| `article_summary.quotes` | array | Key quotes from the source |
| `article_summary.relevant_facts` | array | Key facts extracted from the source |
| `article_summary.one_sentence_summary` | string | One-line summary of the source |
| `article_summary.document_type` | string | Type of source (news article, job posting, earnings call, etc.) |
Sent when a new account is uploaded or when Account Suggestions finishes pre-scoring an account. Returns the full account object including all signal data.
**Payload structure:**
```json theme={null}
{
"event": "account.upload",
"event_time": "2025-06-10T08:00:00Z",
"data": [
{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "Acme Corp",
"icp_name": "Master",
"icp_id": "9f0979ca-5f3a-40c5-afe5-41cfd70cde6a",
"owner_email": "rep@company.com",
"summary": "Acme is expanding into enterprise and just hired a new CRO...",
"scaled_score": 74,
"status": "farsight",
"account_data": {
"full_name": "Acme Corporation, Inc.",
"linkedin_url": "https://linkedin.com/company/acme",
"industry": "Software",
"li_employees": 320,
"location": {}
},
"signals": [...],
"signal_list": ["New CRO Hired", "Hiring SDRs", "Series B Funding"]
}
]
}
```
**Key account fields:**
| Field | Type | Description |
| --------------------------- | ------- | ------------------------------------------------------------------------- |
| `id` | string | WhiteWhale account UUID |
| `scaled_score` | number | Account score 0–100. If status is `farsight`, this is a prediction score. |
| `status` | string | `active`, `archived`, or `farsight` |
| `summary` | string | Why Now summary |
| `signal_list` | array | Names of all signals currently matching this account |
| `signals` | array | Full signal answer objects with sources, quotes, and dates |
| `account_data.li_employees` | integer | Employee count from LinkedIn |
| `account_data.linkedin_url` | string | Company LinkedIn URL |
***
## Timing
| Event | When it fires |
| ---------------- | ------------------------------------------------------------------------------------------------------- |
| `account.signal` | Daily, each morning when new signal matches are found |
| `account.upload` | Immediately when an account is uploaded or activated, and when Account Suggestions finishes pre-scoring |
***
## Related
Full endpoint reference including `/v1/set_webhook` and `/v1/test_webhook`.
Use webhooks to pipe WhiteWhale data directly into Clay.
# Welcome to WhiteWhale
Source: https://docs.getwhitewhale.com/welcome
Learn how WhiteWhale monitors your target accounts daily for custom buying signals and delivers Why Now summaries so your sales team knows exactly who to contact and why.
Most sales teams reach out to accounts based on firmographics — industry, size, geography. They all pull from the same lists, run the same sequences, and wonder why response rates are falling.
WhiteWhale is different. Instead of generic intent data, you get **custom buying signals** — questions you write, specific to your ICP, monitored every day across news, job postings, earnings calls, social, and the web. When something changes at an account that matters to your sales motion, you know about it first.
The result: your reps know exactly which accounts to contact, with a specific reason to reach out, right now.
***
## How it works
Define 10–15 questions that describe what makes a perfect buying moment for your team. *Did they hire a new CRO? Are they hiring SDRs? Did they announce a new market expansion?* These are your signals.
WhiteWhale scans news, press releases, job postings, earnings calls, company websites, and social posts daily — looking for answers to your questions across every account in your book.
When signals fire, WhiteWhale connects the dots and writes a **Why Now summary** — a 2–3 sentence explanation of what's changing at the account and why it's worth reaching out today.
Your reps use the Why Now to personalize outreach with the specific thing they noticed. Not a generic pitch — a message that shows the prospect you did your homework.
***
## Where to start
Set up signals, add accounts, connect integrations, and invite your team.
Learn how to work your signal queue, use the Why Now, and book more meetings.
***
## Key features
Write the exact questions that matter to your sales motion — not a library of generic intent topics.
A multi-signal story that tells you what's happening at an account and why now is the right moment.
Run a search and WhiteWhale finds net-new accounts with your signals across millions of companies — automatically, every day.
Syncs with HubSpot, Salesforce, Slack, Teams, Google Calendar, Clay, and more.
***
## Questions?
Reach out to the WhiteWhale team at [hello@getwhitewhale.com](mailto:hello@getwhitewhale.com).
# Workflow Guides
Source: https://docs.getwhitewhale.com/workflow-guides
Step-by-step automation workflows that turn WhiteWhale signals into pipeline — using Claude, Clay, HubSpot, and your outreach tools.
These workflows show you how to connect WhiteWhale to your existing stack and automate the path from "a signal fired" to "a rep is having a conversation." Pick the ones that match your tools.
***
## Workflow 1: Signal → Contact Enrichment → Multi-Channel Sequence (Claude + Apollo/Zoominfo/Other Contact Tool)
**What it does:** When a signal fires, Claude automatically finds the right contacts at that account, enriches them with verified emails and phone numbers, and drafts a personalized multi-channel sequence — all from a single conversation.
**Tools needed:** WhiteWhale (Claude connector), Apollo (Claude connector) or Other Contact Data tool with Claude Integration
### Setup
Go to Claude → **Settings** → **Connectors** → **Custom Connectors** → add `https://app.getwhitewhale.com/mcp`. When prompted, enter your API key and user email.
In Claude, go to **Settings** → **Connectors** → search for **Apollo.io** → click **Connect** and authorize via OAuth. No API key needed — it uses your Apollo account directly.
After connecting, go to **Connectors** → **Configure** beside Apollo.io and review permissions for each action.
### The workflow
Open a new Claude chat with both WhiteWhale and Apollo connectors enabled, then run through these prompts:
**Step 1 — Pull your hottest accounts**
```text theme={null}
Show me my top 10 WhiteWhale accounts by score that have had
a signal fire in the last 7 days. For each one, show me the
account name, score, and the Why Now summary.
```
**Step 2 — Pick an account and find contacts**
```text theme={null}
For [COMPANY NAME], search Apollo for the following people:
- VP Sales, CRO, or Head of Revenue
- VP Marketing or Head of Demand Gen
- Head of RevOps or Sales Operations
Only include people based in the United States. Grab their emails and phone numbers.
```
**Step 3 — Draft a personalized sequence**
```text theme={null}
Using the WhiteWhale Why Now summary for [COMPANY] and the
contact details you just found, write a 3-step outbound sequence
for [CONTACT NAME], [TITLE]:
Step 1: LinkedIn connection request (under 300 characters)
Step 2: Email (use the I noticed / I bet / here's how we help
/ lead magnet framework)
Step 3: Follow-up email 3 days later (short, reference the
first email)
We sell [YOUR PRODUCT] that helps companies [YOUR VALUE PROP].
Use the specific signals — don't be generic.
```
**Step 4 — Add to Apollo sequence (optional)**
```text theme={null}
Create these contacts in Apollo and add them to the
[SEQUENCE NAME] sequence using my [EMAIL ACCOUNT] sending account.
```
Adding contacts to an Apollo sequence can trigger live outbound depending on your sequence settings. Always confirm the sequence name, sending account, and volume before approving.
You can also use ZoomInfo's MCP connector instead of Apollo for contact enrichment. The workflow is the same — connect ZoomInfo in Claude's Connectors settings, then swap the Apollo search and enrich prompts for ZoomInfo equivalents.
***
## Workflow 2: Strategic One-Pager for a Target Account (Claude)
**What it does:** Claude creates a polished, branded one-pager for a specific account — using WhiteWhale's Why Now and signal data to show the prospect exactly how your product maps to their situation. Send it as a leave-behind, attach it to a cold email, or use it as a pre-meeting document.
**Tools needed:** WhiteWhale (Claude connector), Claude
### The workflow
**Step 1 — Pull the account data**
```text theme={null}
Connect to WhiteWhale and pull the full account details for
[COMPANY DOMAIN]. Show me:
- The Why Now summary
- All active signals with their sources and dates
- The account score
```
**Step 2 — Generate the one-pager**
```text theme={null}
Create a one-page PDF or document for [COMPANY NAME] with the
following sections:
HEADER:
- Our logo [attach or describe your logo/brand colors]
- Title: "How [YOUR COMPANY] Can Help [COMPANY NAME]"
- Date
SECTION 1 — What We Noticed
Summarize the 2-3 most relevant signals in plain English.
Don't list them — tell the story of what's happening at the
company right now.
SECTION 2 — What This Usually Means
Based on those signals, describe the problems they're likely
facing. Be specific. Reference their industry and situation.
SECTION 3 — How We Help
Describe our product and how it specifically addresses the
problems above. Include 1-2 relevant customer proof points
if I provide them.
SECTION 4 — Suggested Next Step
A single, low-friction CTA. Example: "We built this brief
specifically for your team. Happy to walk through it in
15 minutes — here's my calendar link."
FORMATTING:
- Use [BRAND COLOR] as the accent color
- Clean, modern layout
- No more than one page
- Professional tone, not salesy
```
**Step 3 — Iterate**
```text theme={null}
Update the "How We Help" section to emphasize [SPECIFIC FEATURE]
and add this customer proof point: [PASTE CASE STUDY OR STAT]
```
Save your best one-pager as a template prompt. Once you have the format dialed in, you can generate a new one for any account in under 60 seconds — just swap the company name and Claude pulls fresh signal data from WhiteWhale automatically.
***
## Workflow 3: Auto-Create CRM Tasks When Signals Fire (HubSpot)
**What it does:** When a WhiteWhale signal fires, a task is automatically created in HubSpot and assigned to the account owner — with the signal details, Why Now, and source included in the task description. Reps see the task in their HubSpot queue and know exactly what to do.
**Tools needed:** WhiteWhale webhook, HubSpot Workflows (Operations Hub Professional or Enterprise)
### How it works
```text theme={null}
WhiteWhale signal fires
→ Webhook sends payload to HubSpot workflow
→ HubSpot creates a task on the matching company
→ Task assigned to the account owner with signal context
→ Rep sees task in their HubSpot queue
```
### Setup
In HubSpot, go to **Automation → Workflows** and create a new workflow. Add a **Send a webhook** action (under Data ops). Set the method to **POST** and paste your WhiteWhale webhook URL.
For a full walkthrough of setting up webhook-triggered workflows in HubSpot, watch this guide: [HubSpot Webhook Workflows →](https://www.youtube.com/watch?v=gyHk8bVt1pE)
Go to **Settings** → **API & Webhooks** → paste the HubSpot webhook URL and save. WhiteWhale will now POST signal events directly to your HubSpot workflow every morning when signals fire.
In WhiteWhale, go to **Settings** → **Test Webhook** and send a test payload. Confirm it arrives in your HubSpot workflow and triggers correctly.
In your HubSpot workflow, add a **Create Task** action after the webhook trigger. Map the fields from the WhiteWhale payload:
| HubSpot task field | WhiteWhale source |
| ------------------ | -------------------------------------------------------------------- |
| Subject | `Signal: {signal_name} — {account}` |
| Body | `Why Now: {why_now}\n\nSource: {article_summary.headline}\n{source}` |
| Associated company | Match using `crm_account_id` or search by `account` domain |
| Assigned to | Match using `owner_email` |
| Due date | Today + 1 day |
| Priority | High |
| Type | To-do |
### What the rep sees
A task appears in their HubSpot queue:
> **Signal: New CRO Hired — acme.com**
>
> Why Now: Acme just brought in a new CRO from Salesforce who has publicly committed to overhauling their outbound motion over the next 90 days. Combined with their recent Series B, they're scaling the sales team fast.
>
> Source: TechCrunch — Acme Corp Appoints New Chief Revenue Officer [https://techcrunch.com/](https://techcrunch.com/)...
The rep opens the task, reads the Why Now, and reaches out — without ever logging into WhiteWhale.
***
## Workflow 4: Signal → Enriched Contacts → Automated Outreach (Clay)
**What it does:** WhiteWhale signals flow into Clay automatically via webhook. Clay finds the right contacts at each account, enriches them with verified emails and phone numbers, and either pushes them to your CRM for rep-led follow-up or kicks off an automated sequence.
**Tools needed:** WhiteWhale webhook, Clay, your CRM (HubSpot/Salesforce), email/LinkedIn outreach tool (Instantly, Lemlist, HeyReach, etc.)
### Setup
In Clay, create a new table and add **Webhook** as the data source. Clay will generate a webhook URL.
Reference: [Clay Webhook Integration Guide](https://university.clay.com/docs/webhook-integration-guide)
Go to **Settings** → **API & Webhooks** → paste the Clay webhook URL and save.
Every morning when a signal fires, WhiteWhale sends the full payload to your Clay table — including the company URL, LinkedIn URL, all signals, the Why Now, sources, quotes, and the account owner.
Add the following columns to your Clay table:
**Column 1 — Company name** Pull from the WhiteWhale payload `account` field.
**Column 2 — Account owner** Pull from `owner_email` so you know which rep owns the account.
**Column 3 — Find contacts** Use Clay's **Find People at Company** enrichment. Set it to search for your target titles (VP Sales, Head of Marketing, etc.) at the company URL from the WhiteWhale payload.
**Column 4 — Waterfall enrichment** Run Clay's waterfall enrichment on each contact to source verified email addresses and phone numbers from 10+ providers.
**Option A: Rep-led (push to CRM)**
Add a Clay integration to push the enriched contact into HubSpot or Salesforce. Include the signal name and Why Now summary in a custom field so the rep has full context when they see the record.
**Option B: Fully automated (push to outreach tool)**
Add a **Claygent** column that takes the WhiteWhale signals, Why Now, and contact details and writes a personalized first-touch email. Then push the contact and the AI-written email into Instantly, Lemlist, or HeyReach to kick off a sequence automatically.
### One-off export alternative
If you don't want ongoing automation and just need to get your current accounts into Clay:
1. Go to the **Accounts** page in WhiteWhale
2. Select the accounts you want to export using the checkboxes
3. Click **Export** — WhiteWhale downloads a CSV
4. Import the CSV into Clay as a new table
Reference: [Clay CSV Import Guide](https://university.clay.com/docs/csv-import-overview)
The WhiteWhale webhook payload includes all signals on an account — not just the one that triggered the event. This means your Claygent can reference the full signal story when writing outreach, not just a single data point.
***
## Workflow 5: Daily Account Briefing in Slack (WhiteWhale + Claude + Slack)
**What it does:** Every morning, Claude pulls your top-priority accounts from WhiteWhale and posts a summary to a Slack channel — so your team starts the day knowing exactly which accounts to work.
**Tools needed:** WhiteWhale (Claude connector), Slack (Claude connector), Claude Cowork
### The workflow
Set up a recurring Cowork task or run this manually each morning:
```text theme={null}
Connect to WhiteWhale and pull my top 5 accounts by score
that have had a signal fire in the last 3 days.
For each account, format a brief like this:
**[Company Name]** (Score: [X])
Why Now: [1-2 sentence summary]
Signal: [Most recent signal name] — [date]
Then post this to the #sales-signals Slack channel with the
header "🐋 Morning Signal Brief — [Today's Date]"
```
### What the team sees in Slack
> **🐋 Morning Signal Brief — June 25, 2026**
>
> **Acme Corp** (Score: 62) Why Now: Acme just hired a new CRO from Salesforce and raised a \$40M Series B. They're scaling the sales team aggressively. Signal: New CRO Hired — Jun 24
>
> **Globex Industries** (Score: 48) Why Now: Globex is consolidating their sales tech stack after acquiring two companies. Job postings mention replacing their current outbound tools. Signal: Vendor Consolidation — Jun 23
>
> *\[3 more accounts...]*
***
## Which workflow should I start with?
| If you want... | Start with... |
| -------------------------------------------- | -------------------------------------------------------------------------------- |
| The fastest results with no setup | Workflow 1 (Claude + Apollo/Zoominfo/Other Contact Tool) — runs in a single chat |
| Personalized collateral for enterprise deals | Workflow 2 (One-pagers) |
| Tasks auto-created for reps in HubSpot | Workflow 3 (HubSpot webhook) |
| Fully automated signal → outreach pipeline | Workflow 4 (Clay) |
| A daily team briefing | Workflow 5 (Slack) |
## Related
The messaging framework and partner playbooks that make these workflows convert.
Full payload reference for building custom automations.
Access WhiteWhale data programmatically for custom workflows.
Setup guide for connecting WhiteWhale to Clay.