Give the helper a defined job
The person you would call after losing your phone may be the right recovery contact. But being kind, technically confident or related to you is not enough. You need someone who can recognize a genuine request, reach their own account and help without asking for your password.
Start while you can still sign in. This comparison covers personal Apple Accounts on iPhone and personal Google Accounts in a computer browser. Choose the route for the account you actually need to protect; choosing a different provider is not the task. Workplace and school accounts may require an administrator.
Apple says a recovery contact can supply a code without gaining access to your account. Google documents a separate recovery-contact feature, distinct from a recovery email address. Neither setup below requires handing a friend your password. Keep the enrollment inside the provider’s settings rather than improvising a shared login.

Write down the role before sending an invitation: “Help me through the provider’s recovery process when I request it directly.” That is a narrow responsibility. If you also want someone to pay bills or retrieve documents while you are unavailable, arrange those permissions separately.
Compare people before comparing settings
Ask the candidate whether they are willing, then discuss a realistic failure. “If my phone were missing and I borrowed another phone, how would we establish that it was me?” Their answer matters more than their willingness to click an invitation.
| Candidate | Useful strength | Question to resolve |
|---|---|---|
| Someone in your household | Can recognize you and meet in person | Could one theft or evacuation remove both people’s devices? |
| A close friend elsewhere | May remain reachable during a local disruption | Do you have a contact route outside the account being recovered? |
| A technically skilled acquaintance | May understand account settings | Do they know you well enough to challenge an impersonator? |
These are editorial selection criteria, not provider eligibility rules. Prefer someone who respects boundaries and can calmly refuse an urgent but unverified request. Someone who pressures you to disclose passwords, monitors your communications or uses access as leverage is unsuitable, even if they are family.
In a hypothetical example, Maya considers her partner and her sister. Her partner usually travels with her, with both phones in the same bag. Her sister lives elsewhere and they speak regularly. Maya chooses her sister for this failure scenario, then agrees on a way to make contact without Maya’s email. Geography alone would not establish trust.
Enroll in the right service, then check acceptance
Apple: confirm the person was added
Apple’s setup instructions require compatible Apple devices: iOS 15, iPadOS 15 or macOS Monterey 12 or later, including your associated devices. Both people need iMessage and must meet the regional minimum age. Follow prompts for two-factor authentication.
- On your iPhone, open Settings → [your name] → Sign-In & Security → Recovery Contacts.
- Tap Add Recovery Contact, follow the prompts and choose the intended person.
- Family Sharing members are added automatically; others must accept in Messages. Look for confirmation that the person was added.
An unanswered invitation is unfinished work. If enrollment fails, resolve eligibility or software prompts using the official instructions. Do not remove an actively used device merely to clear a warning without understanding the consequences.
Google: acceptance starts another waiting period
Follow Google’s computer instructions:
- Open your Google Account at myaccount.google.com; check the signed-in address.
- Choose Security & sign-in → How you sign in to Google → Recovery contacts → Add recovery contact.
- Enter the helper’s email and choose Send request. They receive your name, email address and profile photo.
Invitations expire after seven days; accepted contacts require another seven days before use. Availability varies by region, account and device. Enrollment requires working access. If the option is absent, preserve existing methods; do not substitute a friend’s mailbox.
Agree on how a real request will begin
Make a short agreement with your helper. They should expect to hear from you directly, identify you independently and work from their own settings. An unexpected message saying “support needs your code for me” should trigger a pause.
For a remote request, agree to call a previously known number when possible. A missing phone may make that impossible, so identify another practical route beforehand: an in-person meeting or a known mutual contact who can arrange one. A familiar profile picture or urgent writing style is weak evidence on its own.
Apple explicitly says helpers should give a recovery code only directly to the person they are helping, never to someone requesting it on that person’s behalf. Its helper instructions put the owner’s verification first. Once recovery is underway, the helper uses Settings → [their name] → Sign-In & Security → Recovery Contacts → Account Recovery For → your name → Get Recovery Code. The owner enters that six-digit code on their own device.
Do not generalize Apple’s code procedure to Google. During an actual Google recovery, follow the options offered in that account’s recovery process. A helper’s role is to respond to the legitimate process, not to collect your usual sign-in codes, password or an exported password vault.
Rehearse readiness without creating a lockout
Keep working sessions and normal authentication methods intact. Meet or call your helper and perform a preparation check:
- Identify the exact account and provider covered. Separate personal and work identities explicitly.
- Confirm that enrollment completed. For Google, also check that the post-acceptance waiting period has elapsed.
- For Apple, have the helper locate your name under Account Recovery For. Stop before generating a code.
- Find the agreed contact route with your usual phone put aside. Check that the details are available outside the account you might lose.
The success record should describe observations: “Invitation accepted; helper found my Apple entry; alternate telephone number located.” Do not write “recovery tested.” You have checked preparedness, not proved that a future recovery will be accepted.
If the helper cannot find the entry, compare identities and enrollment status while access remains available. If their only contact details are inside your locked mailbox, record an accessible copy. If they cannot operate their own device reliably, choose another willing person and repeat the preparation.
A hypothetical failure illustrates the distinction: Jonah’s friend says, “I saw your message,” but cannot say which account received it. Jonah had treated a conversational acknowledgment as completed enrollment. They inspect the account settings together and resolve the identity mismatch before travel. Keeping the discussion specific prevents reassurance from replacing evidence.
Replace the person when needed, and preserve a fallback
Revisit the arrangement after a changed relationship, lost device or new contact address. Ask whether the person still wants the responsibility. A contact who once agreed should be able to withdraw without being pressured to remain available indefinitely.
Apple documents removal at Settings → [your name] → Sign In & Security → Recovery Contacts → person’s name → Remove Contact. The former helper receives a message. They can also remove themselves. Follow Apple’s removal instructions, then revisit the list to check your intended change.
For Google, open the same Recovery contacts settings, choose the trash control and Confirm. If you still trust the existing helper, establish the replacement before retiring useful coverage. If trust has ended, remove that person promptly and accept that the replacement may not be ready immediately.
If an Apple helper is unavailable, ordinary account recovery may still be necessary. Apple’s waiting-period guidance says recovery can take days or longer and support cannot shorten it. Follow its device-use instructions carefully: using other signed-in devices can cancel a request, with exceptions for the device that started recovery. Do not launch repeated requests hoping to speed things up.
Keep a small private record naming the account, helper, alternate contact route and last review date. Exclude passwords and generated codes. The useful outcome is a person who understands the job, an enrollment that has actually completed, and an honest record of what remains unproven.
Sources, versions & scope
The steps describe the documented controls and expected checks; they are not a claim that every device or software release has been physically tested. Platform and version differences are stated with the procedure.
- Apple Support: Set up a recovery contact for your Apple Account
- Google Account Help: Set up recovery options (Computer)
- Apple Support: Get a recovery code for a friend or family member as their Apple Account recovery contact
- Apple Support: Remove a recovery contact from an Apple Account
- Apple Support: What to expect during account recovery
Knowligent Editors
First published · Updated
Documentation-led digital-life guidance, with AI-assisted research and drafting. Examples are identified, source links are provided, and device-testing limits are stated.
Editorial standards

