◆ LinkedIn

Accept 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 taskPriya from DataWave sent a connection request with the note ‘Love your work on onboarding…+
Priya from DataWave sent a connection request with the note ‘Love your work on onboarding metrics.’ Accept her on Friday and include a one-line note saying thanks and mentioning I’d like to swap notes on onboarding experiments next month; check her profile for mutual connections first.
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 accepting Priya’s request from DataWave, make the connection easier to turn into a…+
Before accepting Priya’s request from DataWave, make the connection easier to turn into a conversation: show the mutual connections and three profile points I can use to open a thread, suggest a one-line thank-you plus a topical invite that sounds natural for her role in growth engineering.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentPriya from DataWave requested to connect saying she loves my onboarding work but didn’t say why…+
A recruiter-style connection request arrives with a vague compliment.
Priya from DataWave requested to connect saying she loves my onboarding work but didn’t say why she wants to connect. I’m wary of adding recruiters I don’t know. What’s the likeliest reason she’s reaching out, and what brief acceptance message keeps the door open without sounding like I’m fishing for referrals?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep accepting connection requests without a plan and then my feed fills with irrelevant…+
I accept many connection requests and later regret unknown contacts cluttering my feed.
I keep accepting connection requests without a plan and then my feed fills with irrelevant posts. How should I decide, fast, which requests to accept and what one-line policy will stop me from accepting generic recruiter outreach? Recommend the decision rule and the exact note to send on accept.
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.