Session guidelines

The rules for running a session on Revquix - what to do before it starts, what must not happen during it, and the two things that will cost you your account.

View as .md

If somebody has asked you to take the work off-platform, to pay you directly, or for a five-star review, the answer to all three is no - and this page says why. These are the guidelines shown from your bookings list. They are short because there are only a few rules, and two of them are not negotiable.

Before the session#

Test your camera, microphone and connection before the joining window opens - not inside it.

The window opens 10 minutes before the start, and a mentor spending those 10 minutes discovering their microphone is broken has spent the buyer's session on setup. See running a session for the timings.

Everything stays on Revquix#

Off-platform work has no attendance record, no dispute process, no payment protection and no evidence if the two of you later disagree about what happened. Every protection you have as a mentor comes from the session being on the platform - including the one that pays you when a buyer does not turn up.

If somebody asks to move the conversation elsewhere, the answer is to book another session.

Do not solicit ratings#

Do not ask for a favourable rating, and never offer anything in exchange for one.

A rating that was requested is not information, and a rating that was paid for is fraud. Both are detectable and both are treated seriously.

Doing excellent work and saying nothing is the whole strategy. See ratings and reviews.

Mock interviews owe a report#

A mock interview is not finished when the call ends. The structured feedback report is part of what was sold, it has a deadline, and missing it holds your payout and marks your record.

Session feedback covers what it should contain and exactly what a late one costs.

If something goes wrong#

Report it in the 24 hours after the session rather than letting it close silently. That window is the only way to raise a problem without opening a formal dispute, and it is where a genuine technical failure gets recorded as one.

When someone does not turn up covers no-shows on both sides.

The binding version#

This page is the practical summary. The mentor code of conduct is what you agreed to when you were approved, and it is the document a dispute is judged against.

Was this page helpful?

Last checked against the product on . Behaviour changes are listed in the changelog.