Metlivi Blog

How to Write the Friend Request and First Message to an Old Friend

Keep the friend request and the first chat message as two different jobs. The request note is an identity label: your name, the shared context, and a calm reason for adding them. If the request is accepted, the first message becomes a short bridge: greet them, name what brought them to mind, offer one small update, and leave one optional question. Do not squeeze an apology, a reunion plan, and the history of the silence into the verification field. Acceptance only opens a channel; it does not confirm that the other person wants a long conversation or a renewed friendship.

August 26, 202612 min readRelationships & Life StagesBy Metlivi Editorial Team
Section 1

Use the request note as a compact identity card

A useful verification note answers “Who is this?” before it asks for attention. Write the name the friend knew, then one stable shared reference: the school year, team, workplace, neighborhood, or mutual activity you genuinely shared. Finish with the present reason, such as “I came across our old project photo and wanted to say hello.” A workable line is: “Hi Mei, this is Lin from the 2016 community orchestra. I found your profile while sorting old concert photos and wanted to say hello.” Avoid a bare “It’s me,” an inside joke that only makes sense after recognition, or several personal facts that resemble a quiz. The recipient should be able to recognize you without revealing anything new.

Section 2

Match detail to the risk of a mistaken account

Names, profile photos, and mutual contacts can be outdated or copied. Before sending, compare two or three ordinary public signals that should fit together, such as school and approximate period, a known activity, or a mutual contact already visible to both sides. Do not investigate private addresses, relatives, phone numbers, or workplace schedules. If uncertainty remains, use a known channel you already possess or ask a mutual friend to pass your own contact details, not to disclose theirs. A privacy regulator specifically recommends checking an online identity through a separate real-world route when possible. The aim is to prevent a mistaken request, not to assemble a dossier or test the person with secret questions.

Section 3

Let the first message continue, not restart, the introduction

After acceptance, do not send another mysterious greeting. Repeat the shared context in one clause because people accept requests quickly and may not remember the note. Then add the real trigger and one present detail: “Thanks for accepting—Lin from the orchestra here. I heard the spring program last week and remembered our percussion rehearsal. I have started playing again on weekends. How have you been spending your time lately, if you feel like sharing?” One question is enough. Research suggests that hesitation about old friends is common and that unexpected reach-outs may be appreciated more than senders expect on average, but neither finding promises a reply. Write for clarity, not for a predicted outcome.

Section 4

Choose a version that fits the history you actually share

For a neutral drift, use identification plus a current trigger. If the last exchange ended with an unfinished practical matter, acknowledge that fact briefly and avoid pretending nothing happened: “I realized I never returned the book list we discussed; I’m sorry for leaving that unfinished.” If there was a clear request for no contact, a block, repeated unanswered attempts, or a serious conflict, do not use a new account or friend request to bypass it. Where you simply do not know what happened, do not invent an explanation or ask the recipient to reassure you. The first contact can be warm while remaining small. A friend request is not the place to settle blame, demand forgiveness, or announce what the relationship must become.

Section 5

Read acceptance, silence, and replies as separate signals

An accepted request means only that the account connection was allowed. A brief reply may support a brief exchange; an enthusiastic update may support one relevant follow-up; a decline closes the invitation. No response does not reveal the reason and does not justify sending the same note through several platforms. Do not monitor public posts as evidence that the person owes you a reply. If you later discover that you contacted the wrong person, apologize once, remove the connection if appropriate, and stop. Keep financial requests, verification codes, identity documents, and urgent links out of this exchange. If a supposedly familiar account asks for money or sensitive data, verify through a separate known route before doing anything.

Section 6

Use a final send check that protects both sides

Before tapping send, check six items: the account is reasonably matched; your name is recognizable; the shared context is accurate; the note contains no private fact; the first message has no hidden deadline; and you are prepared for yes, no, a short answer, or silence. Read both fields together. The request note should not promise an explanation that the first message never gives, and the first message should not assume acceptance settled the friendship. Save a draft, remove repeated cushioning, and send once. The useful outcome is not a particular reply. It is a contact attempt that can be understood quickly, answered freely, and left alone without extra work.

Related questions

Common questions

Should I apologize for the years of silence in the friend request?

Only include a brief, specific apology when you know there is something concrete to acknowledge. A long apology belongs outside the request field and must not require reassurance.

Can I send another request from a different account?

Do not use another account to bypass a declined, removed, blocked, or unanswered request. If the first account was genuinely mistaken or compromised, resolve that fact through a known route before contacting again.

What if I am not certain the profile is theirs?

Pause. Compare limited public context or use a separate channel you already know. Do not request private documents or collect personal data merely to confirm a casual reconnection.

Related reading

Keep exploring this topic