▣Front Desk Open the partner account
paid
Affiliate 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 / Questions
Turn 14 - the questions

The questions, in full

Ten questions about the support desk, each answered in the same order a reader would meet it: what the desk is, what it can see, what it can give away, what a sentence is worth and where the record lives.

Open the partner accountStart with the ceiling
Desk stub
Questions
ten, answered directly
Where they come from
the mechanism on the other fourteen pages
What is not here
advice about a live dispute
Schema
FAQPage rendered from the same list
Boundary
routes, data rights and the contract are other desks
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 answerThese ten questions cover the whole of this desk in short form: what the support layer is, the screen an agent works from and the ceiling each level holds, what a sentence in a chat is worth, how the queue is staffed, how long the record lasts and how a reader should frame a message so that it produces a decision.
Subject the support desk in ten answersUnit the question - answered in 40 to 60 words eachSchema FAQPage built from this same array, so the markup cannot claim an answer the page does not showBoundary cycle 15 owns the routes, cycle 35 the data, cycle 49 the contractSample the same invented desk used across the site

Ten questions

Where to go next. The mechanism is developed across sixteen pages and the answers above are the short form of it. The overview defines the sample desk every figure on this site is derived from, and the ceiling page owns the four levels of authority referred to throughout.
Start at the overview

The sample desk and the month behind it.

The ceiling at each level

Four levels of authority, each priced.

The queue as arithmetic

Arrivals, seats and idle hours.

The record and its pile

What survives a contact and for how long.

The questions, in full

q01

What is an operator’s first desk?

It is the service layer a player can actually reach: live chat, email, phone and social, staffed from queues, answered from one screen and recorded. It answers questions and applies small credits; it does not decide disputes and it cannot move money out of an account.

q02

Can a support agent see everything the operator knows about me?

No. The screen holds identity state, the balance, the last three movements, bonus state, notes, flags and the contact history. The payment file, the instrument behind a deposit, the market grading rules and other linked accounts are on other systems, which is exactly what limits what the agent may decide.

q03

What is the most a support agent can give me without asking anyone?

On this desk’s sample that is 15.00, because the account screen is enough evidence for a decision of that size. A second line with one more document may give away 150.00 and a case owner 750.00; above that nothing is authorised, and the request becomes a written case.

q04

Is a promise made in a chat binding?

Standard-form terms say no member of staff may vary the agreement, so a reply cannot rewrite a condition. A credit that has actually been applied is money, and a decision with an amount, a date and a reference is something a later reader can check - those two are what a chat can really produce.

q05

Why can’t support just release my withdrawal?

Because the permission to read an account and the permission to move money out of it are deliberately separated. Support reads and records; a payment queue releases on a batch with a cut-off; a finance queue raises the instruction. That separation also protects the account from any single member of staff.

q06

Why does my question keep being escalated?

Each level can see one more document than the level below, and its ceiling rises with what it can see. A question that depends on the payment file or on how a market was graded cannot be decided at the first line, and on this sample 29% of contacts move up for exactly that reason.

q07

How long does an operator keep a chat transcript?

In this desk’s sample, 24 months for a chat transcript and 6 months for a call recording, with email held with the case. The record belongs to the operator even when the agent was employed by an outsourced supplier, so the request is made to the operator by reference and date.

q08

Do response-time standards mean anything?

It depends which kind of number it is. A target, such as 80% of chats answered within 60 seconds, is a staffing decision and leaves a tail that on this sample is 1,776 contacts a month. An average hides that tail. Only the complaints route has a period attached that somebody must meet.

q09

What makes a support message get a decision?

Four parts, in order: the reference on the first line, one ask as one action, the arithmetic in the account’s own figures, and a date the answer is needed by. Anything else - the story of the relationship, or a second question - adds handling time and does not add a decision.

q10

What should I keep from a support contact?

The reference, the times, and the answer. The times matter because a response standard is measured from arrival to pickup, and the reference matters because it is the only thing that makes one conversation findable inside a month of them.