An agency workflow for client accounts on iPhones

Start with permission

An agency only runs accounts its clients have asked it to run. Before a client's phone or account goes into iFarm:

• Get the client's permission in writing for what you'll do on their accounts: drafts, posts, routine sessions.
• Prefer phones and accounts the client owns. The client logs in to their own apps; iFarm never types passwords.
• Follow each platform's rules and the client's own rules. iFarm is never for fake accounts, fake engagement, spam or mass messaging, and it doesn't hide automation from apps.

iFarm installs a small helper app (WebDriverAgent, open source) on each phone, signed with your Apple developer team, and it appears on the phone as an app called "iFarm". Tell the client. To remove it later, delete the app from the phone (press and hold → Remove App).

Set up: one group per client

1. Prepare each phone: plug it in by USB with a data cable, tap Trust, turn on Developer Mode, and set Auto-Lock to Never. Phones need iOS 16 or later.
2. Give each phone a clear name on the iPhone (Settings → General → About → Name), such as "Client A 1", so its tile and drop folder are obvious.
3. In All phones, check a client's phones and choose Selection → make a group. Groups appear in the sidebar; right-click to rename.
4. If a client has several TikTok accounts on one phone, log in to each once in TikTok, then press Find accounts on this phone under Farm → Accounts.

The Apple Developer Program ($99/year) is recommended for a farm: the helper lasts a year and your team can register up to 100 iPhones a year. A free Personal Team works too, but the helper is re-signed every 7 days (iFarm renews it automatically).

Workflow: editors deliver, the account manager approves

The drop folder lets editors hand off content without touching the Mac.

1. In iFarm, open Waiting for you → Drop folder → Choose… and pick a folder inside Google Drive, Dropbox or iCloud Drive on the Mac. Share that folder with your editors through the storage service, as you normally would.
2. Press Create phone folders: one sub-folder per phone and per group, plus All.
3. An editor puts clip.mp4 and clip.txt (the caption) into the client's phone folder, or a TikTok account's @handle folder. A file in the group's folder goes to each phone in that group.
4. iFarm prepares it on the phone like a drag-and-drop and lists it in Waiting for you, with a Mac notification.
5. The account manager reviews it and chooses Save draft / Post / Discard. With no answer in 30 minutes, it's saved as a TikTok draft, not posted.
6. The files move into _drafted, _posted, _discarded or _failed (with a .reason.txt), so the editor can see the outcome from their own computer.

Need a post held for a time the client agreed? Add clip.json with {"draft_at": "2026-11-02T18:30:00Z"} next to the file and it waits until then.

Approvals stay on by default

By default iFarm asks before posting, sending or following, for drag-and-drop, the drop folder, automations and AI runs alike. A person approves each post. If you use an AI brain to post to several apps, before a tap that sends or posts you get Allow / Don't allow on the phone's tile and in Waiting for you, with the text shown; no answer in 3 minutes means no. iFarm never buys anything.

You can turn approvals off in Setup → Preferences. For client work, we'd suggest leaving them on: it keeps a person accountable for every post.

Routine work per client

1. Record a routine once on one of the client's phones (open the app, check the Inbox, open drafts) and save it.
2. In Plan → Schedules, schedule it for that client's group, once or N times a day at random times inside a window, on chosen weekdays.
3. Chain steps with Flows if one task depends on another (on success, on failure, always).

Planned runs wait while a phone is in use, so a team member picking up a phone isn't interrupted.

History as a record

History (Plan → History) lists every run: the phone, what started it, the result, and a screenshot when it failed. With accounts, it has an Account column and filter, and each account has its own history. That gives you a record to check when a client asks what happened on their account and when.

Keeping clients separate

• Each client's phones sit in their own group, and each phone has its own drop folder.
• Passcodes, Wi-Fi secrets and API keys are stored only in the Mac's Keychain.
• iFarm has no servers and no accounts. Nothing leaves your Mac except the WebDriverAgent download, the community template list when opened, and screenshots sent to the AI provider you choose (none with a local model).
• To keep Wi-Fi out of it, turn off Allow control over Wi-Fi in Setup → Preferences: phones are then reachable over USB only.

Frequently asked questions

Can an agency use iFarm for client accounts?

Yes, with the client's permission and within each platform's rules. Keep posts on "you approve each post" and use phones and accounts the client owns.

How many client phones can one Mac run?

A Mac with 8 GB of memory runs 5–10 phones comfortably, 16 GB runs 10–20, and 32 GB or more runs 20–30, limited by USB hubs. A powered USB hub carries about 10–15 phones.

Does iFarm cost anything per client or per phone?

No. iFarm is free, every feature, with no account, no subscription and no trial. Your costs are the Mac, the phones, USB hubs and, if you choose, the Apple Developer Program and an AI provider.

Can a client see what was posted?

Everything posted goes through the client's own accounts. In iFarm, History records every run, and the drop folder moves each file into _posted, _drafted, _discarded or _failed, which you can share with the client.

Related