Contact the studio and manage push notifications

Use Contact Us to send the studio an email from the Online Client, and use Push Notifications to manage notifications for the current browser.

#Before you begin

Sign in to the correct studio account. Although studio settings can offer Contact Us in guest navigation, the current DSM Next Contact routes require a client session. This draft therefore documents signed-in use only until guest behavior is fixed or verified.
The studio controls whether the contact form appears and must configure a recipient and working email delivery.
Contact security can use a five-character security code or Google reCAPTCHA. The form can ask for an additional security check after an automated check cannot confirm the request.
Push Notifications manages the current browser and device only. Repeat the setup separately on every browser or device where notifications are wanted.
JavaScript is required for push notifications. The Contact page has a basic non-JavaScript form, but its normal interactive presentation and some security-check behavior use JavaScript.

Important: Contact Us and Messages are different. Contact sends an email to the studio; it does not create a reply thread in the Online Client message list.

#Send a contact message

Sign in and select Contact Us if the studio provides it.
If studio contact information appears, confirm that you are contacting the intended location.
Review Your Name, Your Email, and Your Phone. Signed-in account details can be filled in automatically.
Enter the request under Message.
Complete the displayed security check:
- enter the five-character Security Code and select its refresh control if the code is unreadable; or
- complete the reCAPTCHA prompt when it appears.
Review the recipient studio, your reply email, and the message.
Select Send once.

Warning: Selecting Send attempts to deliver an email and records contact-form activity. Do not include card or bank details, passwords, health information, legal documents, or other sensitive data unless the studio has specifically approved that channel.

#What happens after Send

The studio receives an email at its configured contact address when delivery succeeds.
The submitted email becomes the reply-to address, so make sure it is correct.
The page should display Thanks for your message. We will contact you shortly. when the configured email service is available.
A delivery warning or error means the page has not confirmed delivery. Use the studio's displayed phone number or another approved contact method.

Important: Do not send the same message repeatedly while the result is unknown. Record the exact message on the page and check the studio's alternate contact information.

#Enable push notifications for this browser

Open the account menu and select Push Notifications.
Wait while the page checks the browser's current subscription.
Confirm that the page says Push notifications are currently disabled.
Select Enable Push Notifications.
When the browser asks whether the site may send notifications, choose Allow only on a trusted personal device.
Wait for Push notifications are enabled for this browser.

Enabling creates a browser subscription for the signed-in member and saves the current device's subscription details for the studio's notification service.

Warning: Notifications can appear on the lock screen or desktop and may reveal that you have a studio message. Do not enable them on a public, shared, or unmanaged device.

#Disable push notifications for this browser

Open the account menu and select Push Notifications on the device to change.
Confirm the page says notifications are enabled for this browser.
Select Disable Push Notifications.
Wait for Push notifications are currently disabled.

This removes the current browser subscription. It does not disable subscriptions already enabled in another browser or on another device.

#Confirm it worked

For Contact, rely on the page result:

Thanks for your message. We will contact you shortly. confirms the application's successful path.
Your message was not delivered, Failed to send your message, or another error means to use an alternate contact method.

For push notifications, return to Push Notifications in the same browser. The status should match the action just completed. A full end-to-end test also requires a safe test notification from the studio; receiving ordinary studio email or seeing an Online Client message does not by itself prove browser push delivery.

#Troubleshooting

#Contact Us is missing while signed in

The studio may have disabled the form or not configured its contact email. Use its published phone or email address. Do not guess a Contact URL from another studio's Online Client.

Current menu logic can offer Contact Us to a guest while the route remains behind the signed-in session gate. Sign in before using the form. This mismatch requires product verification before the manual promises guest contact access.

#The contact form is disabled

Use the studio information displayed on the page, if available. The form cannot send until the studio enables and configures it.

#The security code is rejected

Enter the current five-character code exactly as displayed. Refresh the code and try once more if it changed or is unreadable. For reCAPTCHA, complete the additional prompt if the page requests one.

#The page reports an email or delivery error

Copy the exact error without including the private message text, then contact the studio through its published phone number or another approved method. Do not assume the email arrived, and do not keep selecting Send.

#Push Notifications says the browser is incompatible

Use a current browser that supports service workers, browser push, and visible notifications. If notification permission was previously blocked, update the site's notification permission in the browser settings and refresh the page.

#Selecting Enable returns to disabled

Check whether the browser blocked the permission prompt, whether private-browsing restrictions are active, and whether the studio's site is allowed to register notifications. Then refresh and check the status before trying again.

#Notifications work on one device but not another

This is expected when only one browser is subscribed. Sign in on the other trusted device and enable notifications there separately.

#Disabling one device did not stop another

Open Push Notifications on each subscribed browser and select Disable Push Notifications. Browser subscriptions are separate.

#Which events create a push notification?

The current page supports subscriptions and includes a new-message notification response, but the complete outbound event list was not verified in a test studio. The studio should state which events it sends; do not assume that every message, announcement, class change, or financial event creates a browser notification.