Skip to main content
Skip table of contents

Customize the layout using querystring parameters

Description

Querystring parameters can be used to customize the layout, change navigation or just to disable specific features of the application.

Agent footer

Use the following querystring parameters in the url to cutomize the footer for agents. Querystring parameters can be used when directly accessing a meeting using the meeting URL, as well as by simply opening the WeSeeDo application at any other page.

Querystring parameter

Description

1

disable_statusbar

Hide the entire statusbar

2

disable_footer

Hide the entire footer

3

disable_statusbar_text

Hide the text in the statusbar

4

disable_logo

Hide the logo in the footer

5

disable_timer

Hide the timer in the statusbar and footer - only visible when the meeting is running

6

disable_status_slider

Hide the status slider to turn online and offline in the footer

7

disable_name

Hide the name in the footer

8

disable_menu

Hide the menu in the footer

9

disable_menuitem_meeting

Hide menuitem meeting

10

disable_menuitem_appointment

Hide menuitem appointment

11

disable_menuitem_waiting_room

Hide menuitem waiting room

12

disable_logout

Hide the logout button in the footer

For example, use the following meeting url with query string parameters disable the entire footer:
https://sandbox.weseedo.nl/meeting/wCPjvYM7yf7KBwGVU0OsFG6DVBAGqZ5s_6PFMcsoR0GBeKIF8AhkngSqUy9UXBubA?disable_footer=true

Or simply send the user to any part of the application with the query string parameters:

https://sandbox.weseedo.nl/login?disable_footer=true

Participant footer

Use the following queries in the url to cutomize the footer for participants.

Querystring parameter

Description

1

disable_footer

Hide the entire footer

2

disable_statusbar_text

Hide the text in the footer

3

disable_logo

Hide the logo in the footer

4

disable_timer

Hide the timer in the footer

For example, use the following meeting url with query string parameters disable the entire footer:
https://sandbox.weseedo.nl/meeting/wCPjvYM7yf7KBwGVU0OsFG6DVBAGqZ5s_6PFMcsoR0GBeKIF8AhkngSqUy9UXBubA?disable_footer=true

Call notification popup

The call notification popup is visible when an agent is signed in with a meeting-token and the participant join, or when a participant starts a conversation via the website button. It is possible to entirely skip this call notification popup and automatically accept the incoming call.

Disabling the call notification popup applies only to agents and assistant_video roles.

Query

Description

1

auto_accept

Does not display the call notification popup and automatically accepts incoming calls

For example, use the following meeting url with query string parameters disable the entire footer, and also disable the call notification popup:
https://sandbox.weseedo.nl/meeting/wCPjvYM7yf7KBwGVU0OsFG6DVBAGqZ5s_6PFMcsoR0GBeKIF8AhkngSqUy9UXBubA?disable_footer=true&auto_accept=true

Or simply send the user to any part of the application with the query string parameters:

https://sandbox.weseedo.nl/login?disable_footer=true&auto_accept=true

Redirect after login

Use the following query in the url to forward to other pages after the autologin succeeded. Available options for redirects are:

  • ?redirect_after_login=appointment

  • ?redirect_after_login=waiting_room

The default page for roles agent and assistant_video is /meeting and for role assistant default /waiting_room.

Note: it is not possible to send role assistant to /meeting, as this page is not available for this role.

Query

Description

1

redirect_after_login

Redirect to a specific page after a successful login

For example, use the following autologin URL to send users to /appointment after logging in:

https://sandbox.weseedo.nl/login/TOKEN?redirect_after_login=appointment

Disable ringtones

Use the following queries to disable the ringtone(s). Available ringtones are:

  • When a visitor is online, a doorbell plays in the waiting room

  • When the call notification popup opens, a ringtone plays

  • When the meeting starts, a doorbell plays (for agents and assistant_video this only plays when ?auto_accept=true)

All ringtones are enabled by default.

Note: the ringtone for incoming calls is always disabled when ?auto_accept=true.

Query

Description

1

disable_ringtone_waiting_room

Disable doorbell in waiting room when the visitors is online

2

disable_ringtone_incoming_call

Disable ringtone for incoming calls

3

disable_ringtone_start_meeting

Disable doorbell when the meeting starts (for visitors and agents)

For example, use the following meeting url with query string parameter to disable the doorbell when the meeting starts:
https://sandbox.weseedo.nl/meeting/wCPjvYM7yf7KBwGVU0OsFG6DVBAGqZ5s_6PFMcsoR0GBeKIF8AhkngSqUy9UXBubA?disable_ringtone_start_meeting=true

Or simply send the user to any part of the application with the query string parameters:

https://sandbox.weseedo.nl/login?disable_footer=true&auto_accept=true&disable_ringtone_start_meeting=true

Device settings screen

The device settings screen allows to configure video and audio input devices and the audio output device that will be used for the meeting. After allowing permissions, all devices that are detected by the operating system will passed along to this settings screen. Note that some features may not be available in all browsers, WeSeeDo will perform an automatic feature detection to show/hide options that are not available for the given browser. The dialog is depicted below.

When the device settings screen is disabled, and the WeSeeDo camera is detected on your system but is not the default camera, a dialog will appear that allows you to choose to use the WeSeeDo camera instead of your default camera. This dialog is depicted below.

Query

Description

1

show_device_settings

Allows to override default behaviour of showing the device settings screen prior to the meeting.
Note: if the feature device_configuration_screen is not present, then this toggle will have no effect.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.