The short version

Keep the context in the thread, make the next action small and stop when someone declines. No response does not justify an endless sequence.

Choose timing from the situation

If someone gave you a date, use it. If you met yesterday, a short thank-you while the details are fresh is sensible. If a cold message went unanswered, allow more time and consider whether a reminder adds anything.

Editorial starting points, not proven response-rate rules
SituationSuggested action
A useful meetingThank them within a day or two; include anything you promised.
An unanswered first messageConsider one brief follow-up after about a week, then stop unless there is genuinely new context.
They said 'contact me next month'Follow that instruction rather than your own sequence.
They offered an introductionSend a forwardable note promptly; give them room to decide whether to use it.
They declined or asked you to stopEnd the outreach. Do not try another channel.

There is no reliable universal best day or hour for a networking email. These intervals are practical defaults, not findings from an experiment. Account for holidays and the person's stated availability.

1. After no response

Subject: Re: Question about junior data roles

Hi Salma, one follow-up on my note below. I'm trying to understand whether your team's junior analysts spend more time on reporting or data quality. A sentence by email would be helpful if a call is inconvenient. I'll leave it here if now isn't a good time.

Fictional example. Replace the details with your own experience.

Keep the original thread so they do not have to reconstruct the request. Do not ask whether they 'saw your last email' or imply they owe an explanation. If the original request was too broad, narrow it rather than repeating it.

2. After a networking event

Subject: Your point about supplier onboarding

Hi Elena, we spoke after the procurement panel yesterday. Your example of testing a supplier handoff before changing the whole process helped me rethink a project. Here is the checklist I mentioned: [public link]. Good meeting you, and thanks for the conversation.

Fictional example. Replace the details with your own experience.

Not every follow-up needs an ask. A useful exchange can end with thanks. Do not attach a resume simply because you now have an email address.

3. After you used someone's advice

Subject: An update on the portfolio you reviewed

Hi Ben, you suggested that I show the decisions behind my design, not only the final screens. I added a short accessibility test and explained what changed after it. The case study is clearer now. Thank you for pointing me in that direction.

Fictional example. Replace the details with your own experience.

Report the actual change. Avoid turning every update into a new request, and do not send weekly progress reports unless the person asked to stay that closely involved.

4. After an offer to introduce you

Subject: Short introduction for your colleague

Thanks for offering to connect us, Noor. Here is a short note you can forward if you are still comfortable: Alex is a financial analyst exploring planning roles in manufacturing. They have worked on inventory reporting and would value a brief conversation about how your team uses forecasts. No problem if the timing no longer works.

Fictional example. Replace the details with your own experience.

Make it easy to forward without implying endorsement. If your contact has not confirmed the other person's interest, do not add that person to the thread yourself.

5. When there is a real deadline

Subject: Analyst opening closes Friday

Hi Chris, a quick update: the analyst role we discussed closes Friday. I'll apply through the careers site before then. If you still have time to share the team context you mentioned, I'd appreciate it, but please don't rearrange your week on my account.

Fictional example. Replace the details with your own experience.

State the real deadline once. Do not manufacture urgency, and do not miss an application deadline while waiting for a possible introduction. A hiring-process follow-up should go to the recruiter or contact who actually owns that process.

Know when to leave it alone

LinkedIn's professional community policies prohibit spam and unwanted repetitive contact. A professional email address is not permission to continue indefinitely either. A refusal ends the sequence; silence usually means directing your effort elsewhere.

If a follow-up is being sent automatically, check for a reply first. A new conversation, a refusal or a completed introduction should cancel any reminder that no longer makes sense. 'Just following up' sent after a thoughtful answer makes the recipient feel unheard.

Sources & further reading

Sources checked October 21, 2026. Study dates and limitations are noted in the article; organizer pages can change.