# Messaging your booker

> A thread on every confirmed booking - when it opens, when it turns read-only, and why there is no way to message someone before they buy.

Source: https://www.revquix.com/docs/mentors/messaging-your-booker
Last verified: 2026-09-03

---

**If you need to ask the person who booked you for their resume, a job description or any other
document before the call, this is how.** Every confirmed booking has a message thread on its detail
page, shared with the person who booked
it. Both of you can write, and both can attach files.

## What it is for

The gap it fills is specific: **asking for something before the call.** A resume to review, the job
description you are interviewing against, the repository you are supposed to look at. Meet has no
file transfer, and the intake form closes at checkout, so before this existed the only options were
to go off-platform or to open a formal dispute - neither of which is reasonable for "please send me
your CV".

## When it opens

The thread exists once you and the buyer have a **confirmed booking** together. That is the whole
rule, and it has a consequence people ask about:

> **Note** - There is no pre-purchase messaging, deliberately
>
> Somebody browsing your profile cannot message you. If you could be messaged before a purchase, the
> answer to most questions would be free advice given in a chat box, and the mentor who replies fastest
> rather than best would win. Questions belong in the service description; conversation begins at a
> booking.

Because it is keyed to the pair rather than to a single booking, a returning buyer continues the same
conversation rather than starting a fresh one each time.

## When it goes read-only

The thread stays open for **14 days** after your last live booking, package or dispute with that
person. After that the composer disappears and the transcript remains.

> **Note** - 14 days, not 7, and the reason is specific
>
> The mock interview feedback deadline and the dispute SLA both sit inside that period. Closing the
> channel earlier would mean a buyer with a follow-up question about feedback they just received has
> to open a dispute simply to get somewhere to ask it.

The transcript is never deleted - the attachments in it may be the buyer's own documents, and
history is what a dispute is decided on. The reason shown is decided by the server, from state your
browser does not have: every booking between you, the package entitlement, whether a dispute is
open. That is why the card sometimes differs from what you would guess from one booking's status.

## What you can send

|                              |                                               |
| ---------------------------- | --------------------------------------------- |
| Message length               | **5,000 characters**                          |
| Attachments per message      | **5**                                         |
| Size per file                | **10 MB**                                     |
| Total attachments per thread | **200 MB**                                    |
| File types                   | PDF, Word, PowerPoint, Excel, PNG, JPEG, WebP |

That list is the whole allowlist. A `.zip`, a `.txt` or a code file is refused - the types permitted
are the ones a resume, a portfolio or a slide deck actually arrives as.

> **Note** - You have 15 minutes to delete a message
>
> After that it stands. Attachment links you are given expire after 15 minutes too and are re-issued
> when you open the thread again - so a link copied out of the page will not work for somebody else
> later.

## Notifications

A ten-message burst is not ten emails. Notifications are debounced over a 15-minute window, and one
is suppressed entirely if the other person reads the thread within a minute of you writing.

So a reply that arrives quickly is a person, not an alert loop.

## Messages are checked

Content is screened automatically. Repeatedly flagged behaviour is escalated for review - the
threshold is a handful of flags over a month, so a single false positive is not a problem.

## What not to put in it

- **Payment arrangements.** Taking a session off-platform is against the terms, and it removes the
  attendance record that protects you in a dispute.
- **Anything you would not want read back.** A dispute reads the thread.

- [Disputes](https://www.revquix.com/docs/mentors/disputes) - What evidence is looked at, and how.

- [Running a session](https://www.revquix.com/docs/mentors/running-a-session) - The call itself.