How live performer chat works, and what is open now

First: explore the directory

The performer directory is a profile-first alternative to random matching. Cards lead to full profiles so you can read more before deciding whom you are interested in. Public results are drawn from published, verified performer records, not from the entire membership database or unreviewed applications.

An application does not appear immediately in the public list. The verification and content-review process comes first. The directory had no approved performers when this guide was published, and it should not imply that live people are available just because the page has launched. Empty results are honest feedback, not a reason to show fictional profiles.

Second: use filters as discovery tools

The existing directory offers search and filters for self-declared profile information, including gender, orientation, interests and languages, with displayed age and rate filters where information is available. Sorting changes the order of results; it does not change the underlying approval requirements.

Keep gender separate from orientation. Someone’s self-described gender does not tell you their audience preferences, and interest tags are not automatic permission for activities. A language filter is about communication, not a claim about a performer’s country. If a combination leaves no results, remove a restrictive choice rather than assume it describes a hidden available performer.

Third: read availability without inventing it

A profile can display status information, but a label is not an accepted interaction. The current approval flow publishes profiles offline and keeps going-live functionality disabled. Do not treat the presence of status filters, queue labels or a last-online field as proof that a request can be sent.

In a fully enabled service, being available, handling another session and being offline would be different states. Those states would still change, and none would guarantee acceptance. For now, the release notice is the clearest answer: browsing can work while private paid interactions remain unavailable.

Fourth: understand the displayed rate

Performers choose a base credit rate from the allowed options for their current tier. Administrators control those options through platform settings. The public rate is therefore a profile attribute and a comparison point, not an unrestricted promise that any amount can be selected.

The intended interaction price is credits per minute at the applicable performer rate. A displayed affordability estimate divides a balance or entered budget by a proposed rate; it is not actual session accounting. It does not tell you rounding, refunds, reconnect treatment or when a billable clock starts. Current package prices belong on the credit information screen, not hardcoded into an evergreen guide.

Requests, queues and higher offers are not live yet

The proposed private interaction requires a performer’s approval or decline. Queuing is intended to represent waiting for an opportunity to request, not an automatic session. Higher offers are intended to affect eligible ordering under platform rules, not to override someone’s boundaries or force acceptance.

The current service does not implement the operational request queue, eligible bid ordering or reservations. Configuration fields for timeouts and a maximum bid are not the same as a working queue. We are not publishing exact ordering, expiry or cancellation instructions until the actual service is connected. Do not attempt to buy priority by sending money or contact details outside the app.

Waiting and active billing need separate rules

A visitor browsing cards has not started a billable performer session. A person waiting in an eventual queue would still need a clear distinction between waiting, acceptance, connecting and an active interaction. Those transitions must be tied to transactional accounting before the service can take paid requests.

The current release has no performer-session billing start, end or rounding implementation to confirm. We therefore do not claim that charging begins on approval, on connection or at another event; we do not describe whole-minute rounding or per-second billing; and we do not promise automatic credits back after disconnection. Read the actual confirmation and billing terms when a live paid flow becomes available.

Do not infer a cancellation policy from a random-chat membership subscription. Membership renewal, credit purchases and a future per-minute performer session are separate transactions. A budget you write down is useful planning, but it should not be confused with an enforced automatic cap.

Use the right next step for the experience you want

For profile discovery, go to the performer browser. For performer onboarding, use the separate application route and read its requirements first. For spontaneous adult conversations, use the random-chat experience with the access-level filters currently shown to you.

If you have a question about an existing purchase or a disabled feature, contact account support without sharing unnecessary personal details. A guide can explain a confirmed flow, but it cannot create an active performer, waive approval or settle an account balance. Clear expectations now are more useful than precise-sounding instructions for a service that is not yet enabled.