◆ LinkedIn

Send a connection request

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI want to reach out to Marco, head of product at WaveShift, to ask about potential openings.…+
I want to reach out to Marco, head of product at WaveShift, to ask about potential openings. Send a connection request on Monday that mentions I saw his talk at ProductConf, says I’m exploring senior PM roles in fintech, and asks if he has five minutes for coffee; keep it under 40 words and make the ask easy to decline.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I send Marco a connection request, make it easy for him to say yes: pull the talk title…+
Before I send Marco a connection request, make it easy for him to say yes: pull the talk title he gave at ProductConf, surface a shared interest in fintech payments, and suggest a brief, low-effort next step (15-minute virtual coffee). Keep the language respectful and specific to his role at WaveShift.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI’m about to request a connection with Marco, who spoke on payments at ProductConf. I don’t…+
Drafting a cold connection to a senior product leader; unsure what hook will land.
I’m about to request a connection with Marco, who spoke on payments at ProductConf. I don’t know whether to lead with praise or a concrete ask. Which opener gets higher accept rates for senior product leaders, and give me a 30–35 word connection message that references his talk and proposes a short informational chat without sounding transactional.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver months I send cold connection requests to product leaders and most accepts never convert…+
Cold connection requests rarely get responses beyond an accept.
Over months I send cold connection requests to product leaders and most accepts never convert to conversations. What one change in my opener or follow-up habit will double conversion to a reply? Recommend the habit, a short script for the follow-up and when to send it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from LinkedIn's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.