Dealer Casebook: Unverified Host or Manager Instruction

A person approaches the table during a dispute and says:

“I’m the host for this player. Pay it and I’ll sort it out with management.”

Or someone wearing business clothes says:

“I’m a manager. Open the table, change the limit, release the chips, and don’t call anyone else.”

You do not recognise them. They may be legitimate. They may be from another department. They may be senior. They may not be authorised for this decision at all.

The professional question is: how do you respect legitimate authority without following a procedural instruction you cannot verify?

Confidence is not verification

People who belong in a casino often speak with confidence.

So do people who do not have authority over a particular game decision.

Do not use tone, clothing, a name badge, familiarity with the player, or claims of seniority as the only proof that an instruction controls your table.

Keep the game in a safe holding state

If the instruction would move chips, settle a disputed wager, change a limit, alter a procedure, release cash, reopen action, or otherwise change the table state, pause before acting if you cannot confirm authority.

The goal is not to challenge the person publicly.

It is to avoid creating an irreversible action from an unverified command.

Use the property’s normal authority-confirmation path

A dealer should know how to call the floor or designated supervisor.

Use that channel.

A neutral phrase is:

“I need my floor to confirm the instruction before I change the table state.”

That is not insubordination. It is controlled escalation.

Do not demand secret credentials or expose access controls

This case is not a lesson in authentication technology.

Do not ask someone to reveal passwords, access codes, internal phone trees, security questions, hidden identifiers, or restricted credentials at the table.

Use the property’s approved process without explaining how that process could be bypassed.

A host relationship is not automatically game authority

Hosts can be essential to customer service and player relationships.

But a host’s commercial responsibility may not include authority to settle every technical game dispute, custody question, credit control, or procedural exception.

Do not turn “the host said so” into the final game ruling unless the property has clearly authorised that role for the specific decision.

Dealer Casebook: VIP Demands a Procedure Exception covers how commercial pressure should stay separate from required game controls.

A real manager can still be outside the decision chain

The person may genuinely be a manager in another department.

That does not necessarily mean they control table-game procedure.

Similarly, a senior executive may expect the appropriate gaming manager to execute the decision through the correct chain rather than bypassing it informally.

Do not guess authority from job-title prestige.

Do not embarrass a legitimate senior employee

Verification can be discreet.

Avoid saying:

“I don’t believe you’re a manager.”

Say:

“I need to confirm the table instruction through my floor before I act.”

The difference matters. One statement attacks identity; the other protects process.

If the person pressures you to bypass the floor, that increases the need to verify

An instruction such as:

“Don’t call the floor. I’m telling you directly.”

should not make you less cautious.

If the normal process requires a floor confirmation, the attempt to bypass that process is itself a reason to keep the state controlled.

Do not argue. Call through the authorised channel.

Do not create a secret side agreement

A person may say:

“Just do it now and I’ll take responsibility later.”

Responsibility after the fact does not repair an unauthorised action.

If a documented override or exception exists, it should come through the approved process, not a private promise at the table.

Keep the player out of the internal authority debate

The player may try to decide who outranks whom:

“He is the casino manager. You have to listen to him.”

Do not ask the player to authenticate staff authority.

Tell the player you are waiting for the authorised confirmation needed to continue.

If two employees give different instructions, resolve the conflict before acting

Sometimes the unverified person is genuine and another supervisor gives a different direction.

Do not choose the instruction you personally prefer.

Preserve the state and obtain one controlling authorised instruction.

Dealer Casebook: Conflicting Supervisor Instructions covers that conflict in detail.

Document the instruction accurately if required

If the event requires an incident note or handover, record:

• who approached or how they identified themselves;
• the instruction given;
• why you could not confirm authority immediately;
• which authorised role you contacted;
• whether the table state changed before confirmation;
• the final confirmed direction.

Avoid writing “impostor” unless that fact was actually established.

Do not disclose internal authority weaknesses afterward

If the person turns out not to be authorised, do not turn the incident into staff gossip about which doors, badges, phone lines, names, or weaknesses allowed them to sound convincing.

Report through the designated channel. Keep access-control details need-to-know.

Relief must inherit any unresolved command

If you are relieved before authority is confirmed, tell the incoming dealer that the instruction is still unverified.

Do not let the next dealer assume that a confident person standing nearby has already been cleared.

Professional confidence includes verifying authority

A strong dealer is not impressed into action and is not disrespectful toward legitimate leadership.

They know the boundary: authority that changes a controlled table state must be confirmed through the property process when it is not already clear.

That protects both the employee giving the instruction and the dealer expected to execute it.

Verify the instruction, not the person’s social importance

The practical issue is not whether the person is impressive, well known, or genuinely employed by the casino. The issue is whether the instruction they gave is authorised for this table and this decision. Keeping that distinction in mind helps the dealer stay respectful. You do not need to prove someone is an impostor. You need the normal gaming chain to confirm whether the instruction controls the live state before you execute it.

Avoid creating a loyalty test between departments

A host, cage employee, Security supervisor, hotel manager, or executive may be frustrated if the dealer pauses. Do not frame the situation as “my department versus yours.” State the operational requirement: the table needs confirmation from the authorised gaming role before the state changes. That phrasing protects working relationships and reduces the chance that a routine verification becomes a personal contest about status.

If the instruction is later confirmed, execute the confirmed version

Once the authorised chain confirms the direction, listen to the final instruction rather than relying on the first version you heard. The confirmed instruction may contain conditions, timing, documentation, or a narrower scope. Repeat it back if necessary. Verification is not useful if the dealer then acts on the original informal command instead of the controlling confirmed one.

Keep the table explanation short while verification happens

Other players do not need the internal authority discussion. A simple statement such as “We are confirming an instruction before continuing” is usually enough. Avoid naming departments, speculating about the person’s status, or inviting the table to vote on whether they look legitimate. The less social theatre you create, the easier it is for the authorised chain to resolve the issue cleanly.

Verify the instruction before executing it

When someone claiming to be a host or manager gives a procedural instruction you cannot verify, keep the table in a controlled state and confirm the instruction through the authorised property chain. Do not follow the command merely because the person sounds senior, and do not expose access-control methods while verifying them.