paidAffiliate disclosure. The partner link in the masthead and in the bands beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. That matters on this desk in particular: the subject is what an operator’s own staff may and may not do, and this site’s own revenue depends on a reader opening an account. No operator is named, rated or recommended anywhere on this site.
Front Desk / The screen
Turn 03 - the screen
The screen behind the answer
The most common misunderstanding about support is that an agent is looking at everything the operator knows. They are looking at one screen with a fixed set of fields, and the ceiling on what they may decide comes directly from what is on it.
Desk stub
- On the screen
- identity state, balance, three movements, bonus, notes, flags
- Not on the screen
- the payment file, the card, the bank, the grading rules
- Where notes live
- free text, attached to the account
- Who can read them
- any agent, the second line, the quality team
- What limits the ceiling
- the fields, not the goodwill
the turnOne numbered serving of a contact, with its clock and what it cost the desk
the ceilingWhat a level may give away without asking, set by the evidence it can see
the transcriptThe only record that a contact happened, kept 24 months on this sample
Direct answerAn agent works from one screen: the identity checks completed, the balance, the last three movements, the state of any bonus, notes other agents left, any flag on the account and the contact history. The payment instruments, the market grading rules and other customers’ accounts are on other systems, which is why a question that depends on them has to move up a level.
Subject the fields an agent works fromUnit the field - one line of the screen and where it comes fromMoves shown the last three, in this sampleRead access only the agent may read the account and may not change its stateBoundary the operator’s own file about a reader is cycle 35’s question, not this page’s
What is on the screen
field 01Identity state, not identity documents
The screen says whether a check is complete, pending or failed, and when it was last run. The
document itself sits in the verification system, which is a different system with different access
rules; an agent can tell a reader that a document is waiting on a review and cannot tell them what
the reviewer saw.
That is the shape of the whole screen: states are visible, the reasons behind them often are not.
field 02Balance, and the last three movements
The balance is current, and the movement list is short in this sample - three lines - because the
screen is built for answering a question about now rather than for auditing a month. A contact that
needs a longer history is a request for a statement, which is a different process and a different
queue.
The arithmetic matters here: three movements is one field; thirty is a document, and a document
takes an agent far longer than a screen.
field 03Bonus state, notes and flags
Bonus state says whether credit is still subject to conditions and how far through them the account
is. Notes are free text left by other agents, and a flag is a label - both are short, human, and
exactly as reliable as the person who wrote them. Neither is a decision, and neither can move
money.
Everything a note says is also part of the record, which is worth
remembering when a note is added in a hurry.
What is elsewhere
The payment file
Which instrument funded a deposit, whether an authorisation was captured, and what the acquirer returned. Visible from the second line, never from the first.
The market and the rules
How a bet was graded, which rule applied and what the result source said. Not a support system at all, which is why “the chat agreed my bet should have won” cannot be decided on this screen.
Other accounts
Whether a person holds more than one account, or an account linked to another. Visible only as a flag, and only when the linking has already been done by someone else.
- Read the state: what the screen says is true right now, including the identity state and the balance.
- Read the short movement list: three lines on this sample, which answers a now question and not a month question.
- Read the notes and the flags as claims by other people, not as findings.
- Identify the field the answer actually depends on, and if it is not on the screen, that is the reason to move the case rather than to guess.
Read access is the design. The first line can see a balance and cannot move it, cannot adjust a bonus and cannot release a payment. Every one of those is a different permission held somewhere else, which is why a chat can produce a decision about a small credit and not about anything that changes the account’s state.
seven fields the movement list agent minutes per field anything one field further read access only