Messaging your booker

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:

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.

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.

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.