Customer support

You answer buyers for eight or ten client accounts, in shifts, from two or three machines. This page is about the parts that decide whose session opens where: one profile in one window, the second step beside the sign-in it belongs to, folders per client, and a log that answers the next morning.

3 min, renewed while open: Lock on an open profile
4 plus the owner: Roles you hand out
3: Log lists in the dashboard
Pages opened: What the daily counter measures
6 digits, 30 second step: One-time code in the profile

What a shift really shares

A support shift is many accounts and few people. Ten seller panels, three operators, and whoever is free answers first.

Put two of those panels in one browser and the platforms see one device answering for two sellers. That link is made by you, not by them.

How a shift is held today	Closes	Leaves open
One browser and ten tabs	Nothing	One device and one address behind every client
A second browser profile	The cookie jar	The machine underneath: fonts, GPU, local address
The password passed in chat	Nothing	A secret in a message and no way to tell who acted
A virtual machine per client	Almost everything	Gigabytes and a separate update cycle per client
A profile per account	Sessions, device, exit address and who may open it	Whether the platform allows you to answer at all

One profile opens in one place

The server holds a lock on the profile. A second machine asking for the same profile is told the holder's machine name, since when, and whether it is your own other computer.

The lock runs for three minutes and is renewed while the window is open. A laptop that dies mid-shift therefore frees the profile by itself.

1
Close the window to hand over
Closing releases the lock at once, and the next operator opens the profile a second later.
2
Take it over on purpose
A takeover is a separate decision, and two takeovers racing each other cannot both win.
3
The previous holder is told
Their next renewal fails, their windows close and a notification names what happened.

The second step sits beside the sign-in

A profile can hold the one-time key of the account it signs into. The six digits then appear in the same window at the moment the form asks for them.

The key stays on this computer and the digits are worked out here, so there is no phone in the middle and nothing to match by name among ten accounts that look alike.

No second device
The code appears where the profile lives, with the connection unplugged.
No hunting for the right entry
The key belongs to the profile, so the code on screen belongs to the account you are answering for.
A mark on the card
You see at a glance which client accounts no longer send anyone to a phone.

Who may open which client

Five roles exist and four of them are handed out. An operator works with the profiles given to them and changes nothing shared; a manager also keeps the proxy pool and the folders; an admin gets billing, the team, the log and other people's profiles.

Folder access narrows what one person sees. The rule is read when profiles are listed and again when one is opened by its identifier, so knowing the number is not a way in.

A person joins by an invite sent to an address that already has an account. The code is good for seven days and can be withdrawn while it is still unused.

Role	Profiles given to them	Shared pool and folders	Billing, team and log
Operator or member	Có	–	–
Manager	Có	Có	–
Admin	Có	Có	Có
Owner	Có	Có	Có

The log answers the next morning

Three lists live in the dashboard: everything the workspace did, browser starts and stops, and sign-ins with the address and country behind them.

A row carries the email of the person who acted and the name of the profile. A deliberate takeover is written down with the machine it was taken from.

Only the owner and admins read it. For an operator the request is refused rather than merely hidden from the screen.

Action list: Every event in the workspace, newest first
Open list: Browser starts and stops, with the profile named
Sign-in list: The address, the country and the machine
Every row carries: The email of the person who acted
A takeover adds: The machine the profile was taken from
One page: 20 rows, with no filter by person or date

The three lists the dashboard opens for the owner and for admins.

What the counter on the card counts

Every profile card carries a daily counter. It counts the pages opened in that profile today and sets them against a safe daily pace for its use case.

Beside it the scenario prints its own ceilings for the day, buyer replies among them. Those are numbers to aim at, and the app neither sees a reply nor tallies one.

Measured
Pages opened in the profile today, per profile, cleared when the date changes.
Not measured
Buyer replies, listing edits, review requests and account switches.
At the top of the day
The bar turns amber and then red. Nothing closes and nothing is refused.
Where the numbers come from
The scenario record, ramped over the first seven days by profile age.

What this does not do

It does not decide who may answer for a seller. The freelance platforms allow one active seller account per person and say who may act on it, and we will not sell a way around a written rule.
It does not put two people in one account at once. One profile opens on one machine, so a handover is closing the window rather than sharing a live session.
It does not tally replies to buyers. The one thing measured is pages opened in the profile today, and the reply number beside it is guidance on a card.
It does not move your response time. The platform scores that from the moment you actually answered.

How to check

Every claim above has a file behind it and a stand that fails when it stops being true.

The second machine is told who holds the profile: apps/server/src/profiles/profiles.service.ts · apps/server/test/profile-lock.js
Folders decide what a member sees and what they may open: apps/server/src/profiles/profiles.service.ts · apps/server/test/group-access.js
The log names the person and the profile, and only admins read it: apps/server/src/logs/logs.service.ts · apps/server/test/audit-filters.js
The daily counter counts pages and stops nobody: apps/desktop/src/lib/pace.js · apps/web/test/потолок-это-ориентир.js
The one-time code matches the published vectors: apps/desktop/src/lib/totp.js · apps/desktop/test/totp.js

Questions

Can two operators sit in one account at once?: No. The second machine is told who holds the profile and since when, instead of quietly opening a second session.
What if a machine dies mid-shift?: The lock expires by itself three minutes after the last renewal, and the next operator opens the profile with nobody unlocking it.
Does the one-time key travel to a colleague?: Not through us. It stays on the machine where it was pasted, and carrying it across is an export that asks first.
Will our own support chat open inside a profile?: Not if it is served from a host on the general tracker list, and one customer-messaging host is on it. Every profile loads that list.
Who reads the workspace log?: The owner and admins. An operator is refused by the server, so the answer is the same whichever way they ask.

Three seats on Business

Business comes with three seats and five machines, and an extra seat is three dollars a month. Start free with two profiles and see how the lock fits your shift.

See plans Download ARMANOS