Welcome email for a new team member
An announcement the team can act on: role, start date, one human detail, who they'll pair with, and a concrete way to say hi.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your email
SubjectWelcome Isabelle to the team!
How to use it well
- →Include one human detail (a hobby, where they moved from, what they're excited about) — the role and start date alone don't help anyone start a hallway conversation.
- →Name who they'll actually work with; an all-team, no-team welcome leaves the new hire to figure out reporting lines from the org chart.
- →Give a concrete way to say hi (drop by, a Slack channel, a coffee chat) rather than leaving it as an implicit expectation.
Part by part
- joining us as {{role}} starting {{start_date}}
- Role and date together, which is the information the team needs to know how to interact with them and from when.
- {{human_detail}}
- One non-work fact, which is what gives people something to open a conversation with. A purely professional introduction produces polite silence.
- will be working closely with {{team_members}}
- Names the immediate collaborators, so the new person has a starting map and the named people know to expect them.
- Feel free to say hi {{how_to_say_hi}}
- A specific channel and mechanism. Say hi with no route means most people intend to and never do.
Common mistakes
Please join me in welcoming our new team member!No role, no start date, no context. Nobody knows what they will be doing or how it relates to them, so the reaction is a wave emoji and nothing further.
Writing the human detail without asking them.A personal fact shared without permission is an intrusion on someone's first day, when they have least standing to object. Ask what they are comfortable being introduced with.
Listing their entire CV.An impressive background summary sets the new person up as someone to be measured against rather than met. One line of relevant experience is enough.
Questions
Why include a personal detail at all?
Because it gives people a way in. A role and a start date tell the team what someone does; a shared interest is what produces an actual first conversation rather than an intention to have one.
Should I check the wording with them first?
Yes, always. It costs one message and it avoids introducing someone in terms they would not have chosen — which is a bad first impression they then have to correct themselves.
When should it go out?
On their first morning, or the day before. Sending it a week early means the introduction is forgotten by the time they arrive, which is the moment it was meant to help with.
How large an audience?
The people they will actually work with, plus adjacent teams. A whole-company welcome at scale produces no useful connections and a notification everyone dismisses.