← Files Job Outreach CopilotARCHIVED FILE

skills/job-outreach-copilot/references/outreach_channel_message_patterns.md

3.55 KB · Oct 5, 2026 · 18:37 UTC

↓ Download file

# Outreach Channel and Message Patterns

## Purpose

Choose the least-friction channel supported by the source and draft a message that feels native to that channel.

## General rules

- Reply where the conversation already exists unless there is a clear reason to move channels.
- Respect explicit contact instructions in the job/recruiter source.
- Use only contact details supplied by the user/source.
- Do not guess an email pattern or personal address.
- Do not claim an existing relationship that is not established.
- Verify current platform limits from official sources when exact limits matter.

## LinkedIn connection note

Use when the person is not already connected and a short note is appropriate.

Structure:
1. role/context;
2. one credible fit point;
3. simple reason to connect.

Keep it short. Do not cram a full cover letter into a connection note.

Avoid:
- "I would be honored";
- long skill inventories;
- compensation/visa details unless directly relevant;
- multiple questions.

## LinkedIn DM

Best for an existing connection or an ongoing LinkedIn thread.

Structure:
- direct context;
- relevance;
- one clear ask.

If replying to a recruiter, answer their question first and preserve the thread's established details.

## Public LinkedIn post with recruiting email

Default: use the provided email as the primary route unless the post says otherwise.

Opening can naturally say:
- "I saw your LinkedIn post about the [Role] opening..."

Do not falsely imply the recruiter messaged the candidate directly.

A short LinkedIn interaction can still be useful if the user wants it, but avoid duplicating the same long pitch across channels.

## InMail

Use only when requested or clearly available/appropriate.

Treat it like a concise cold email:
- context;
- fit;
- ask.

Do not assume paid features or current InMail limits.

## Cold email

Suggested subject patterns:
- `[Role] — [Candidate Name]`
- `Interest in [Role] at [Company]`
- `Regarding your [Role] opening`

Body:
1. source/context;
2. why candidate is relevant;
3. one or two evidence points;
4. next step / resume mention;
5. concise close.

Do not write a full cover letter unless asked.

## Recruiter email reply

Stay in the existing thread.

Prioritize:
1. answer the exact question;
2. add only necessary clarification;
3. confirm next step.

Do not repeat previously settled compensation, sponsorship, location, or availability just to make the reply longer.

## Referral request

Use when there is a real connection or reasonable relationship context.

Pattern:
- mention the role;
- one-line fit;
- ask whether they would feel comfortable referring;
- make it easy to decline;
- offer resume/JD link if relevant.

Do not pressure weak ties or imply an obligation.

## After applying

A post-application outreach should add signal, not merely say "I applied."

Useful content:
- role applied for;
- one relevant qualification;
- interest in speaking;
- application reference only when known.

Never state the application was submitted unless confirmed.

## Follow-up

Shorter than the first message.

Pattern:
- brief reminder of context;
- one-line continued interest or relevant update;
- simple call to action.

Avoid guilt, urgency pressure, or repeated full pitches.

## Thank-you after interview

Keep it brief and specific:
- thank them;
- reference one meaningful topic;
- reinforce interest;
- close naturally.

Do not invent discussion topics that the user did not supply.

## Tone controls

Default:
- professional;
- concise;
- natural;
- confident without entitlement.

Adjust to the user's requested style when supplied.

SHA-256: 99b4dd78530abd9cd0db9bba0838960bec63321daf3336ffe1ccb8f0a501ae01