Recruiting and cold outreach

A recruiter, a sourcer or a salesperson on cold outreach opens dozens of other people's profiles a day and writes first messages from one account under a real name.

That account is not one of fifty. Losing it costs the connections, the message history and the thing the money arrives through.

At home the same computer and the same exit address often carry somebody else's account on the same platform. Two accounts sharing a device and an address are two accounts a platform can join.

A second browser profile does not help there. Underneath it sit the same fonts, the same graphics card and the same address, and those are what the joining is done by.

This network is built around one account per person under a real name, and it acts separately on automated collection of data from it.

Read that in its own terms rather than here. The rules change, and a paraphrase on our page falls behind them.

So a second identity here is a no, and it is the first line of the box further down rather than a footnote at the end.

What a profile does instead is keep the account you do have in a sealed session: its own cookie jar, its own device answers, its own way out.

Four of the counts the app keeps are the ones this work spends. Profile views and invitations are the two the network watches closest, because a person on the other side sees both.

The numbers are ours. No platform published them for us, and they sit under what the network itself permits on purpose.

A profile starts at a fifth of each on its first day and reaches the full number on the seventh.

Searching is the cheapest way to spend a day without noticing. A search that returns a page of people is one search, and the profile you open after it is already a view.

Nothing turns amber on the invitation count for you. The card colours the page count, and the four numbers sit beside it as guidance you keep.

When you create a profile the list holds no separate work scenario for this network. Pick Social media: all four counts above live in it, and this network's own request rules load with it.

The band on the profile card there is 200 pages a day, four times what a careful day on this network looks like. For this work that band is not the number to read, the four counts are.

Nothing arrives tuned to this one network out of the box, and saying otherwise would be the easiest sentence to write on this page.

Sixteen of its tracking parameters come off the address before a request leaves, and its advertising click id comes off with them.

A list of domains cannot reach a site's own requests, so ten path rules do that, and they fire on this network's hosts and nowhere else.

Read receipts and typing notices travel over a WebSocket, where no request filter reaches. Those frames are dropped inside the page.

• Its own link and session tags

  trk, trkInfo, lipi, lici, src, trackingId, refId, eBP, recommendedFlavor, midToken, midSig, trkEmail, connectionOf, orig, anchorTopic, contextUrn

  16

• Its advertising click id

  li_fat_id

  1

Each person keeps their own account in their own profile, with its own device answers and its own way out, which matters most when several of them work from one office.

A profile opens in one window at a time, because one account live from two places is the pattern that gets accounts flagged.

The workspace log keeps a row for every action worth arguing about: who, what, when, and which workspace it belonged to.

When somebody leaves, their seat and their access to shared profiles go in one step, and the rows they wrote stay in the owner's history.

The app has a flow builder, and it drives a real profile window with real steps. On this network the rules name automated collection as something acted on.

So a flow here is a risk you decide to take, not the feature this page is sold on.

What a finished run leaves is a log of its last lines. No row is written into a system of record, and there is nothing to export into one.