How WhoCam works, from guest entry to the next decision.

1. Enter as a guest or use your account

Choose the chat entry button to see video, audio or text options. A new visitor can receive a guest session without completing a full registration form. If you later choose a sensitive or account-specific action, the product can ask you to sign in; that later prompt does not make guest entry a false promise. Opening the page alone does not begin a conversation. The video chat without registration guide explains that boundary in detail without duplicating this step-by-step product route.

Hardware permission appears only where the selected mode needs it. If permission is already available, the product can proceed; if it is denied or unavailable, the screen provides the relevant next step. Guest access does not override the browser’s camera and microphone controls.

If this is your first visit and you would rather prepare before entering, the first random video chat guide walks through a small, low-pressure first session. It complements the product steps here with practical conversation preparation.

2. Read the matching state

After the real match-start request succeeds, the product listens for its normal server and realtime events. The matching screen—not the marketing page—shows the current product state and owns the transition into a call.

Waiting, connecting, permission denied and call ended require different actions. WhoCam keeps those states distinct and does not add another match-start, match-next or match-end request around them.

3. Continue, stop or resolve an account state

During a call, use the current controls to continue or leave. The other person may also end the conversation. Read any interruption, balance notice or offer before choosing another action; a call ending and an account needing attention are different situations.

Pricing and recharge screens read current products and account balance. A successful screen follows confirmed payment state; pending, cancelled, failed and ended-call returns stay distinct.

4. Know which screen is authoritative

Public pages explain the route and the reasons behind a control. They cannot know the current account balance, regional offer, browser permission or whether a live session still exists. The screen holding that live state wins when wording differs.

This boundary also keeps support useful. A report should name the exact product screen and observed state, rather than treating a general guide as proof that every account must behave identically. The WhoCam FAQ answers the shorter recurring questions without replacing live account evidence.

The homepage is an entry, not a waiting room

Choose “See who’s live” to open the chat options. You are not reserving a person shown in a homepage photo, and browsing the public page does not start a hidden match. The photos and coloured streams introduce the site; the matching screen is where your session begins.

You can look at the available modes before deciding to start. If you are using mobile data, sharing a room or still setting up headphones, finish those checks first. There is no need to race a homepage timer or keep the page open to hold a place.

Account state comes from the product

A returning visitor may already have an active session. A new visitor may see guest access or be asked to sign in when using an account feature. Follow the options on your screen; another person’s screenshot may show a different balance, allowance or account state.

If you use Google, choose the account you intend to keep using and check which service is requesting access. Signing in helps you return to your account. It does not verify the identity or intentions of the person you may meet in a later conversation.

Mode choice and media permission are different decisions

Choosing video, audio or text describes how the user wants to communicate when those modes are available. Browser permission answers whether the site may use a specific camera or microphone. Selecting video should not be described as permission already granted.

If access is denied, check the permission message before trying again. Your browser may require you to change its site setting, and the operating system may separately block the browser app. The camera guide walks through these checks, including a camera already being used by another app.

Start belongs inside the real matching flow

Once the necessary account and mode conditions are known, the product presents its actual start action. The landing CTA and this product Start are not duplicate buttons: the first enters the application; the second confirms a product state after choices or permissions that the public page cannot make on the user’s behalf.

Read the selected mode before pressing Start, especially after returning from another screen. Video uses camera and microphone; audio needs the microphone; text does not need either. If the mode is not what you intended, change it before starting rather than granting access automatically.

Matching status explains what the system knows now

Looking means the current request is searching under the product’s available conditions. Connecting means a candidate connection is being established. Connected means the live call state is active. Ended means the previous call should not be presented as recoverable unless the product explicitly offers that path.

There is no fixed duration for finding or connecting. Give a transition a moment, but do not keep tapping Start or Next to force it along. If an error appears, read it before retrying. If you simply no longer want to wait, use Exit to return to the options.

Next, Stop, report and block have separate jobs

Next leaves the current conversation and asks for another match. Stop ends the session. Report is for conduct that needs review; block is for limiting further contact where offered. On a phone, locate the exit before settling into the call so you can reach it without searching through menus.

An ordinary mismatch does not need a report. You can leave a quiet or awkward call politely and move on. If someone threatens, pressures or harasses you, end the exposure first and then use report or block. Reporting does not guarantee a particular enforcement outcome or response time.

Check your balance before deciding to continue

Your account shows any available free allowance and remaining balance. During a call you may see a reminder that time or credit is running low. Decide whether you want to continue before choosing a package. Ending the session is a valid choice; you do not owe the other participant a purchase.

When checkout opens, package, currency and total on that screen are authoritative. Success, pending, failed and cancelled remain different states. A return from payment does not guarantee restoration of the previous call; the product’s current ended or available state controls the next action.

A clean finish closes media and clarifies the next route

After Stop or an ended call, verify that camera and microphone indicators turn off. The page may offer a new match, account action or recharge depending on the actual state. It should not leave an old participant image on screen as if the connection remains active.

On a shared device, sign out and remove saved checkout details as appropriate. For a technical issue, record the browser, device and state. For a payment issue, keep the order reference. For harmful conduct, use the report path. Matching each problem to its owner prevents one generic support message from obscuring the next action.

If you return later, check the account and mode again instead of assuming the previous session has resumed. A fresh match may connect you with someone else. Save a payment reference if you are checking a recharge, but never send a password or one-time sign-in code as proof of purchase.

For answers that are not covered here, the WhoCam FAQ separates account, camera, cost and safety questions so you can find the relevant next step.