Skip to content
Function in detail

A SIMPLE GUEST ENTRANCE

Let customers join the conversation from a meeting link

Open the consultation entrance in the browser, enter the requested name and control microphone and camera without creating a Tsumira workspace account.

Illustrative function excerpt

Join the consultation through the browser entrance

The customer chooses a name and device permissions without creating a company workspace account.

MeetingInitial consultation
Participant nameAlex
MicrophoneChosen device
CameraChosen device

The participant confirms

Device access and available capture controls depend on the supported browser.Prepared example; no real customer, live participant or completed action is shown.

Reduce the preparation needed on the customer’s side

An online consultation should begin with the subject of the meeting, not an account setup exercise. The public video entrance lets the intended guest use a meeting link in their browser. The page presents the meeting context and the controls needed to enter. It is a guest route for this conversation; it does not give the participant access to the company’s CRM, internal project records or workspace navigation.

Prepare before entering

The entrance shows the meeting title and scheduled time where available and asks for the participant name. Microphone and camera controls let the person choose how to begin. The browser still needs permission to use the selected devices, and the connection needs a working media service. Installation-free access reduces one kind of friction; it does not remove device or network requirements.

  • Meeting title and timing context
  • Requested display name
  • Microphone and camera controls

Use the conversation controls

Once connected, participants can control their audio and camera, share their screen where the browser supports it and use the meeting’s conversation controls. Leaving is an explicit action. These controls belong to the call experience and should not be confused with persistent project communication or automatically published meeting notes. Choose the appropriate project or customer record for the lasting follow-up.

  • Microphone and camera during the call
  • Screen sharing where supported
  • Leave the call deliberately
Illustrative function excerpt

Joining still needs a working connection

A failed entrance has feedback and retry; it is not shown as a successful call.

MicrophoneChosen device
CameraChosen device
Browser permissionThe participant confirms

Check the actual join outcome

Device access and available capture controls depend on the supported browser.Prepared example; no real customer, live participant or completed action is shown.

Show a useful state when entry is unavailable

Invalid or unavailable entrances do not become a blank customer page, and an ended room can be identified as ended. A failed media connection provides a retry path rather than pretending the person has joined. The room lifecycle is checked independently of the page’s appearance, so an old link is not a promise that the consultation remains open forever.

  • Unavailable and ended-room states
  • Connection feedback and retry
  • Guest access limited to the room lifecycle
A concrete workflow
  1. Open the intended link

    Use the entrance shared for this consultation rather than a general company workspace URL.

  2. Check the context

    Confirm the meeting, enter the requested name and allow the devices needed for the conversation.

  3. Join and participate

    Control microphone and camera, and share a relevant screen only when necessary.

  4. Leave and follow up

    End your participation and record agreed follow-up through the appropriate business workflow.

An illustrative working example

Example: a parent consultation

A school shares a consultation link with a parent. The parent opens it in the browser, checks the meeting context and enters a name. They can begin with the camera off while confirming that the microphone works. The conversation focuses on the learner’s next steps. The school records those agreed actions in its relevant customer or project context rather than assuming the browser call created a permanent written account.

Questions about this topic

Does a guest need a Tsumira workspace account?

The public consultation entrance does not require the customer to create a company workspace account. The intended meeting link provides the guest route.

Does browser access mean every device will always work?

No. Device permissions, browser capabilities, the network and configured video infrastructure still determine whether a connection is possible.

Can the guest see the company’s internal records?

Joining the room does not grant access to CRM, project or company workspace records. Those resources retain their own permissions.

Does leaving automatically end the room for everyone?

Leaving participation and ending a meeting room are different operations. Room management follows the authorized meeting workflow.

Explore connections around this workflow.

Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.

Explore all integrations

Bring your business's work together.

Start with a specific workflow and your team.

Start for free