Running Accounts Day to Day

At six on a Friday evening a client asks who signed in to its account last Tuesday, and from where. A team with a register answers in two minutes. A team without one starts scrolling through chat history.

A naming and record-keeping system

Good operations start with a boring name. A pattern such as client, platform, region and number is enough: acme-ig-us-01. The same name goes on the browser profile, the proxy label and the password manager entry. Anyone on the team can then trace one account across all three.

The register is a single shared sheet with one row per account. It answers three questions at a glance: which profile, which proxy, which client. A fuller record looks like this.

- profile: acme-ig-us-01
  client: Acme Outdoor
  platform: Instagram
  permission: services agreement, signed 2026-03-02
  home: browser profile
  proxy_label: acme-ig-us-01-isp
  proxy_type: static ISP
  proxy_exit: 203.0.113.45, Dallas, United States
  timezone: America/Chicago
  language: en-US
  owner: Priya
  backup: Tom
  two_factor: authenticator app, client holds backup codes
  created: 2026-03-04
  last_review: 2026-11-06
  incidents: none

Two fields deserve a comment. The permission line points to the document in which the client authorized the work. The record holds no password. Passwords live in the password manager and nowhere else.

A register only works if it is edited at the moment of change. A proxy swapped on Wednesday and recorded on Friday leaves two days in which the sheet is wrong. The rule that holds up in practice is short: no change to a profile, proxy or owner without a matching edit to its row.

Starting new accounts gradually

A retailer opens a new account for its German market. On day one, the sensible work is setup: genuine business details, a verified email and phone number, a profile photo and a short description. Launching ads and fifty posts in the first hour is not how a real regional team behaves.

Platforms tend to watch new accounts more closely than established ones. Ordinary, gradual activity is the honest answer to that, because a new account run by a real team starts slowly anyway.

Genuine details matter more than pace. The email, phone number and business information should belong to the client or brand that owns the account. An account built on borrowed or invented details is fragile from the first day, whatever the setup around it.

The ramp applies to single accounts opened for a real purpose. Creating accounts in bulk, or opening spares in case one is lost, is a different activity. Most platforms forbid it, and this handbook does not cover it.

Team workflow, roles and handover

Most account trouble inside agencies is caused by people, not fingerprints. Two operators open the same profile. A contractor keeps access for months after a project ends. Roles in the antidetect tool prevent both.

Handover needs a routine as well. The outgoing operator closes the profile, writes one line in the register and names the next person. The incoming operator reads that line before opening anything. One person works in a profile at a time, as chapter 2 explained.

When someone leaves, the admin removes the seat the same day. The same goes for clients. When a contract ends, the agency hands back access, deletes the profile and releases the proxy.

Security

An agency's antidetect workspace is a set of signed-in sessions for every client it serves. It deserves the care given to a bank login.

• Turn on two-factor authentication for every platform account, with an authenticator app where offered.
• Leave backup codes with the client, who owns the account.
• Turn on two-factor authentication for the antidetect tool and the proxy dashboard as well.
• Keep passwords in a password manager, in one vault per client.
• Never send a password or a code through chat or email.
• Review the tool's access log weekly for unexpected openings.
• Give each person the lowest role that lets the work get done.

The access log is the most neglected item on that list. Five minutes a week is enough to spot a profile opened at an odd hour. The same check catches one opened by someone who has moved to another client.

Automation with restraint

Automation is safest where it replaces chores. Scheduling approved posts through a platform's own tools is a chore. So is pulling weekly reports, or checking that a landing page loads in six countries. The ad verification page covers proxies for that last case.

Automated engagement is another matter. Scripted follows, likes, comments, messages and reviews are restricted or banned on most platforms. They also produce exactly the timing patterns described in chapter 1. This handbook treats them as out of bounds.

Window synchronizers and RPA deserve the same care. Repeating one click across ten client profiles in the same second creates ten identical timestamps. Used for QA across regions, that is harmless. Used for posting, it ties the ten accounts together.

When an account is restricted

Restrictions happen to careful teams too. What matters is a calm, documented response through the platform's own channels.

1. Stop activity. Pause scheduled posts and any automation on the affected account.
2. Read the notice. Save a screenshot and note the stated reason, the date and any deadline.
3. Tell the client. Report the same day, with the notice attached.
4. Appeal through the platform. Use the official appeal or review form, with accurate information. The account owner should submit it.
5. Leave the setup alone. Do not open a replacement account or switch proxies to get around the restriction.
6. Record the outcome. Add the incident to the register and review what led to it.

Step five is where teams make things worse. A replacement account opened during a restriction can turn a temporary limit into a permanent one. It can also draw in the client's other accounts. If the appeal fails, the decision stands. The next conversation is with the client, not with a new profile.

Policies change, so a yearly reading of each platform's terms belongs on the team calendar. The ProxyLook pages for social media and e-commerce proxies cover the network side. Tool details are in the antidetect browser directory.