Ask for an intro in Venom People
Ask one of your own contacts for an intro. Venom drafts the ask and a note to forward, tracks it to introduced, reminds you to nudge, and links it to a Funnel deal. It sends only when you press Send through Venom, one message per press.
Reach tells you when the way to someone is through one of your contacts: "Ask Priya (worked together at Stripe 2019–21)". An intro ask is the next step. Venom drafts the message to Priya and a short note about you that she can forward to the target as is. It then keeps track of whether the introduction happened and tells you when to nudge.
There are two ways to send the ask or a nudge, and both need you to act each time:
- A channel button opens your own WhatsApp, Telegram or email with the text in it. Venom sends nothing; the tap is what it records.
- Send through Venom hands one message to Venom Comms, from you, to the connector. See Send through Venom.
Nothing sends an intro on a timer or by itself. A due nudge is drafted and shown to you; it goes only when you send it.
Who can introduce you
On one of your own people, Who can introduce me? lists:
- your own contacts first: people you know who share a company (now or before, with the years) or a school with them, or whom you recorded as knowing them. Contacts you have been in touch with come first, strongest link first. One you have never exchanged a message, call or meeting with is marked you have not spoken and comes last;
- colleagues after: teammates who shared someone with the same name and company. Asking one of them goes through the colleague request, which they accept or decline.
Being in your contacts is not a connection. If nothing links a contact to the target, they are not listed, and an agent
asking through them is told there is no connector. If you know how two people know each other and People does not, say
it in your own words (agents: fact); it goes into the ask as you wrote it.
The section is hidden when nobody links to the person.
Start an ask
- Reach: a row whose route is Intro has an Ask for intro button, with the connector, the target and the shared fact filled in.
- A person's page: Ask next to a contact under Who can introduce me?
- Reach, many at once: select people, then Ask for intros (under More). Each target gets its best connector of your own. The rest are held and listed with the reason: no connector, the connector already has two open asks, or an ask is already open. Up to 50 at a time: with more selected, the dialog says only the first 50 are drafted. Link to a deal (optional) puts every draft on one Funnel deal.
- A deal's page in Funnel: Ask for intro next to People. Pick someone on the deal or type a name (and company), then who of your people can introduce you, then your goal. The draft is on that deal. See Asks on a deal.
A connector has at most two open asks from you at a time, whichever way you ask (a button, the person page, bulk or an agent). A third is held: "Priya already has 2 open asks".
You add one line on what you want from the intro. Venom drafts the ask straight away from what People holds, with no model call, and opens it under My asks.
The ask and the note to forward
The ask goes to the connector: the shared fact ("I see you and Sam overlapped at Stripe (2019–21)"), who you want to meet and their role, your reason, and an easy way to say no.
The note to forward is written as you, to the target, in about 60 to 90 words: your one line about what you do, why you want to talk, why them (their role, when People knows one; a company alone is not a reason), that you asked the connector to pass it on, and a small ask (20 minutes). It says the connector knows you both only when People holds it (you recorded that they know each other, or they are or were at the same company at the same time). It has no flattery and is meant to be forwarded without edits.
Your one line and the name you sign with come from What I do (for intro blurbs) in People settings. The
name is the one you set there, else the display name of your calendar booking page or your organisation's directory, never
your email address. Until both are known, the drafts keep a visible gap, [what you do, in one line] or [your name]. A
missing reason leaves [why Sam would want to talk] the same way. The send buttons stay off while a gap is left. Venom never
invents any of them. Setting them fills them into drafts that still show the gap.
Both texts are editable while the ask is a draft; once sent they stay as the connector got them. Rewrite in my voice makes one model call through your organisation's gear, under the daily People AI limit. The rewrite reads a few of your earlier messages for your tone, keeps every fact and adds none, and has to pass the same checks as any draft: no placeholders, no links nobody gave it, no sales language. If the limit is spent or the rewrite fails the checks, the template draft stays. A draft with a gap is not rewritten.
My asks
Network → My asks lists your asks in four groups:
| Group | States | What you do there |
|---|---|---|
| To send | draft | edit, rewrite, send with a channel button or through Venom |
| Waiting | asked | nudge when due; They agreed, Introduced, Declined, Drop |
| Agreed | agreed | Introduced when it happens |
| Done | introduced, declined, no reply, dropped | read what happened |
Each row shows connector → target, the state, its age, the date of the next nudge and the deal it is on (or Link to deal). Colleague requests you sent are listed in the same groups, marked via the colleague.
Taps are idempotent. Tapping a channel button twice records one message.
- Send (a channel button): the ask is asked, and the ask and note are logged as your message to the connector.
- Nudge: five days after asking with no change, a one-line nudge is drafted ("Hi Priya, any luck with the intro to Sam?") and the ask shows in Today. Sending it logs it, and the next nudge is due five days later. After two nudges with no answer the ask becomes no reply.
- They agreed: the connector said yes. An agreed ask is not nudged and never expires. Ten days after the yes, My asks and Today ask you once: "Priya agreed 10 days ago. Has it happened?", with Introduced and Not yet.
- Introduced: the target is added to People if they were only a name, with how you met set to "Introduced by Priya" and the introduced-by relationship. If one of your people already has that name, Venom asks "Is this Sam?" first, so you pick them or add a new person. A touch is logged on them, and a thank-you for Priya joins Today's list (due the next day). If one of these steps fails, tapping Introduced again finishes the rest. Add to pipeline opens Funnel with the person.
- Declined, Drop: closed, with an optional note.
If the target writes to you or meets you while an ask is open, the ask shows Looks like this intro happened? with an Introduced button. Venom suggests this and never closes the ask on its own.
There is one open ask per you, connector and target. Asking again opens the existing one.
Send through Venom
On a draft, and on a nudge that is due, Send through Venom sends that one message to the connector through your organisation's Venom Comms, as you: the ask and the note to forward together, or the nudge. Pick the channel when there is more than one: email, WhatsApp, SMS or Telegram (your own Telegram, connected in Comms). Only channels your organisation's Comms carries and the connector has an address for in People are offered. With none, there is no button; send it from your own app.
Each press is one message. A double click, a second tab or a retry sends nothing new and says what happened to the first. Unsaved edits to a draft are saved first, so what goes is what you see. Nothing sends on a timer: a due nudge waits for you.
It goes through the same path as a bot's outreach, so the same rules hold:
- the connector has not opted out in Comms and is not tagged do-not-contact;
- WhatsApp's 24-hour window: outside it WhatsApp needs an approved template, and the message is refused with that reason;
- Comms' quiet hours by the connector's time zone: the message is scheduled, not dropped;
- a member whose role does not manage Comms: the message waits in Comms for an owner or admin to approve;
- from a bot's chat or routine: that bot's channels, daily caps, re-contact window, scope, pace and quiet hours. A bot that asks first holds the message in its approval card. A bot set to leave drafts does not send intros at all.
When Comms has the message, the ask moves exactly as the manual Send does: a draft becomes asked (the nudge count goes up for a nudge) and the message is logged once on the connector. Refused, failed or held, the ask keeps its state, and the card says why ("Not sent: Priya opted out of SMS", "Held in Comms for an owner or admin to approve", "Waiting for approval in the bot's outreach queue"). A held message moves the ask once it is approved and goes.
Asks on a deal
An ask can belong to one Funnel deal: set it when you ask from the deal's page or in bulk, or later with Link to deal on My asks (any state). The deal chip on the card opens the deal; × unlinks it. A deleted deal leaves the ask unlinked.
When an ask on a deal becomes introduced, the target joins the deal's people (once, however often you tap) and the deal's timeline gets one row, "Intro made: …". The row names the target only when their profile is shared with the whole organisation, and never names the connector. The stage does not move; that is still your call.
Only deals you can see can be linked.
Today and Reach
Today has an Intros section when there is something to do: drafts to send, nudges that are due, and intros that look done. It is hidden otherwise.
In Reach, someone with an ask you sent (asked or agreed) is ranked as Waiting with the reason "Intro asked (Priya, 3d)", rather than as a fresh pick. Waiting rows are left out by default, the same as people you just wrote to. A draft nobody has seen keeps its route and shows a small "Intro ask drafted (Priya)" label.
Colleague requests
A colleague request can carry a note to forward too: Draft from my pitch fills it from your one line and your reason. The colleague sees the note and your message, and nothing else of yours. Once the colleague accepts, either side can close the request as Introduced. The first close keeps its time and note.
Privacy
Asks are yours alone. Nobody else in the organisation, owners and admins included, can list, read or change them, also when they can see the deal an ask is on: a deal's Intros section, its board label and its "has open intro ask" filter only ever show your own asks. The connector is always one of your own people. A target with a profile is also one of yours. A colleague's contact is reached through the colleague request, never through an ask of yours, and a colleague's target stays hidden until the existing sharing rules show it.
Agents
| Tool | What it does |
|---|---|
people_intro_path |
the colleagues who know someone and, for one of your own people, your own contacts who could introduce you (connectors, never-spoken ones last) |
people_introask_create |
draft an ask: connector and target (or target_name, target_company), goal, and fact in your words when People holds no link. targets (up to 50) drafts in bulk, at most 2 open per connector, and lists the held ones. deal: a Funnel deal id to put the ask (or every bulk draft) on |
people_introask_list |
your asks with state, age, texts, a due nudge, the "did it happen?" hint, the deal, the channels Venom can send on and what the last send through Venom did; your colleague requests after; your pitch. group: send, waiting, agreed, done. deal: only the asks on that deal |
people_introask_update |
edit a draft's text, blurb, goal; rewrite: true; action sent, nudged, agreed, introduced, declined, no_reply, dropped, with channel and note; deal links it to a deal ("" unlinks). introduced on a name one of your people has answers with the candidates first: call again with match (their id, or new) |
people_introask_send |
send the draft (or the due nudge) to the connector through Venom Comms: ask, optional channel (email, whatsapp, telegram, sms). One message per call; the answer says sent, scheduled, held for approval, refused or failed, and why. Call it only when your user asked to send that message. With no channel Comms can reach the connector on, it says so |
people_introsetting_set |
your one line, pitch, and the name to sign with, sign_name |
people_intro_request |
a colleague request, now with an optional blurb |
people_intro_respond |
action: introduced closes an accepted colleague request |
Over REST: GET and POST /api/v1/people/intro-asks, PATCH /api/v1/people/intro-asks/{ask},
POST /api/v1/people/intro-asks/{ask}/send,
PUT /api/v1/people/intro-asks/settings. See People for agents.