Call prep from Slack: message a domain, get the read

The problem this solves

Call prep is a two-minute job that takes twenty, because the facts live in six places and the rep has a browser full of other tabs. The result is that prep happens for the calls that feel important and gets skipped for the rest, and the skipped calls are where the pipeline quietly leaks. If the prep could be requested in the place the rep already is, with the answer arriving before the call connects, it would happen every time.

Slack is that place for most sales teams. A channel named #sales-prep, a message containing a domain, and a reply in the thread within a minute: what the company does, how big it is, what it runs, what it is hiring, whether it has money, who the buyer is with a verified address, and the one question that turns a cold call into a conversation. The thread keeps the context, so a follow-up question - 'who else is on the committee?' - is answered without repeating the domain.

The Company Intelligence Agent sits in the channel as a standing mission. Nothing is scheduled; it responds when addressed, and every reply is short enough to read on a phone in the elevator.

How the mission runs

1. Listen in #sales-prep. The Company Intelligence Agent watches #sales-prep for messages that contain a domain or a company name addressed to it, resolves the company, and starts a thread under the message so the read stays attached to the request.
2. Build the read from live data. Firmographics supply what the company does, headcount and HQ; technographics the stack in the categories that matter to your product; hiring data the open roles by department; funding data the latest round. Each fact is one line, and the sources are kept for follow-ups.
3. Find and verify the likely buyer. People search identifies the person who would own a purchase of your product at a company of that size, and the email finder plus verification produce a deliverable address, shown with its status in the reply.
4. Write the opening question. From the freshest signal - a posting, a round, a technology change - the agent writes one question that invites the prospect to talk about their situation, and closes the read with it.
5. Reply in the thread and keep the context. The read is posted in the thread within a minute. Follow-up messages in the same thread - more contacts, the competitor set, a longer brief in Docs - are answered with the company already in context, and the read is saved on the company in the workspace for the next person who asks.

The prompt

This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.

What comes back

A reply in the Slack thread under any domain posted to #sales-prep: a two-minute read with what the company does, size, HQ, the relevant stack, open roles by department, latest funding, the likely buyer with a verified email, and one opening question, with follow-up questions answered in the same thread. Every read is saved on the company in the workspace.

Make it yours

• Post the read as a DM to the rep who asked instead of in the channel.
• Ask for the full account plan in Google Docs as a follow-up in the thread.
• Run the same standing mission in Telegram or WhatsApp for reps on the road.
• Add the last CRM touch and the owner to the read by connecting HubSpot or Pipedrive.

Frequently asked questions

Go deeper

• Company and person data for AI agents: the complete guide
• AI SDR: what it actually is, and when you need one
• The complete guide to agentic AI for GTM data