Client Login Codes for Social Media Agencies

The cleanest way for an agency to handle client login codes is not to need them: ask the client to give your team its own access through the platform’s business tools, such as partner access in Meta Business Suite. Where an account still sends its login code by text to one phone, put that number on a company iPhone with the client’s agreement, and let Fwrd post each code to a private Slack or Microsoft Teams channel for that client.

What you need: the client’s written agreement; the iPhone that gets the codes, on iOS 26 or later, either a company phone the client agreed to put on the account or the client’s own iPhone if they choose to set it up; a private Slack or Teams channel for that client; and Fwrd.

How do agencies get client login codes without the client’s phone?

Start with the platform’s own access for agencies, and forward codes only for what’s left. Partner and role access give each person on your team their own sign-in, so nobody waits on the client for a code.

Meta’s help centre says a business can share assets such as Pages and ad accounts with a partner, such as an agency, from Meta Business Suite, with full control or partial access for tasks like creating content, managing ads and responding to messages (Meta, read October 25, 2026). Instagram accounts are assigned in Business Suite too (Meta, read October 25, 2026). Look for the same kind of access on each other platform you run before you forward anything.

Which approach fits each client account?

It depends on what the platform offers and what the client is comfortable with. Use this as a quick guide.

How to post client login codes to a private channel

Set this up on the iPhone that gets the codes, with the client knowing what is forwarded and where.

1. Make one private channel per client. In Slack, create an incoming webhook for the channel at api.slack.com/apps (Create New App, From scratch, Incoming Webhooks). In Teams, choose More options (•••) in the channel, then Workflows, then “Send webhook alerts to a channel”, and copy the URL.

2. Add the channel in Fwrd. Open Fwrd, tap +, choose Slack or Microsoft Teams, and paste the URL into the Configuration field. Tap Send Test Message, then save with the tick.

3. Keep only that platform’s codes. In the same destination, choose Only Some Texts under Which Texts and add a word the platform’s code texts use to Contains Any Of, such as its name, if the text includes it. On a client’s own phone, this keeps their other texts off your channel.

4. Create a Message automation. On iOS 27, open Shortcuts, tap Library, then Automation, then +. If you see Describe a shortcut, tap Edit. Tap Automation, then Message, change Sender to Message, and type code. On iOS 26, open the Automation tab, tap +, choose Message, and type code under Message Contains.

5. Let it run without asking. On iOS 27, tap the arrow beside the trigger and check Confirm Before Run is off, then under ⓘ, then Privacy, check Allow Running When Locked is on. On iOS 26, choose Run Immediately, then tap Next and Create New Shortcut.

6. Add Fwrd’s action. Search for Forward, add Forward Message to All Destinations, and set its Message field to Shortcut Input (on iOS 26, Shortcut Input, then Message). Tap back to save (Done on iOS 26).

7. That’s it. New code texts for that client now post to its channel on their own, with the iPhone unlocked or locked.

Running several clients from one company iPhone? Add a destination per client channel, each with its own word filter, so each code lands only where it belongs. The Slack guide and Teams guide show each screen; the automation guide covers Shortcuts.

Agree it with the client first

• Only with the client’s knowledge and agreement. Put it in writing: which accounts, which phone, which channel, and who is in it.
• Business accounts only. Don’t forward codes for a client’s personal accounts, and on their own phone keep the filter narrow so only the platform’s codes leave it.
• Read each platform’s terms. Partner and role access are the route the platforms themselves offer; prefer them wherever they exist.
• Keep the channel small. Anyone in it can use a code. Remove people the day they leave, and remove the destination when the client leaves.

Fwrd keeps the webhook URL in the iPhone’s Keychain, not inside a shortcut anyone holding the phone can open, and codes go straight from the iPhone to Slack or Teams. A busy agency passes 15 free forwards a month quickly; as of October 2026, Fwrd Pro removes the limit for $4.99 a month or $29.99 a year, bought once on the iPhone that gets the codes.

What forwarding can’t do

• It can’t reach codes sent to an app or by email. Forwarding moves texts only. Codes from an authenticator app, or inside a platform’s own app, stay where they are.
• It can’t work while the phone is off or offline. After a restart, forwarding waits until someone unlocks it once, and an iPhone that isn’t unlocked for three days restarts itself.
• It doesn’t replace the client’s say. The client can change the number or turn the automation off at any time, and that’s their right.
• It only goes one way. Nobody can reply from the channel, and only new texts are posted.