Skeepers is updating its domain names to strengthen the stability, security, and performance of its services.
The platform login URLs for our applications are migrating to a single domain: room.cxr.skeepers.io.
Background
The platform login URLs for our applications are migrating to a single domain: room.cxr.skeepers.io. The old URLs (room.myfeelback.com) will be automatically redirected to this new domain.
This migration was first announced in November 2025. This article is a reminder as the redirect is about to be implemented.
Does this affect me?
In the vast majority of cases, no: the redirect is seamless, your current URLs will continue to work, and no action is required in your Skeepers account.
When you first log in to the new domain, however, there are a few practical points to be aware of (saved credentials, forgotten passwords): see the Important points to know after the migration section.
However, two situations require your attention. Check whether either applies to you:
Case 1: Your organization filters domains (firewall, proxy, whitelisting)
What you need to do: add room.cxr.skeepers.io to your list of allowed domains before September 30, 2026. Otherwise, your users may no longer be able to access the service after the switch.
Case 2: You use connectors or webhooks
What happens automatically: starting September 30, 2026, callback URLs will switch to room.cxr.skeepers.io. There will be no service interruption—the old domain room.myfeelback.com will remain active in parallel.
- What we recommend, with no urgency: update your external configurations (Salesforce, Zendesk, third-party applications) starting September 30 to ensure long-term compatibility. The service will continue to work even if you do not do this.
- If you log in through Single Sign-On (Okta, Azure AD, Google Workspace…)
Your SSO login will continue to work normally; the switch is managed automatically on our side. No action is required.
Important points to know after migrating to room.cxr.skeepers.io
Credentials saved in your browser
If your browser had saved your credentials for the old domain (myfeelback.com), they will not be automatically transferred to the new domain room.cxr.skeepers.io. Therefore, when you log in for the first time, your credentials may no longer be prefilled.
Resetting your password
If you need to reset your password using the “Forgot password” option, be sure to enter your username rather than your email address, unless your email address also corresponds to your username on the platform.
Finding your saved credentials
If you are unsure which credentials to use, you can view the passwords saved by your browser:
- Open your browser's settings.
- Go to the Saved passwords or Password manager section.
- Search for entries containing
myfeelbackorroom.myfeelback. - You can then retrieve the username and password previously saved to log in again.
If you find your old saved credentials, we recommend saving them again the first time you log in to the new domain to make future logins easier.
Whitelisting: check your network rules
This step applies to all customers whose organization uses a firewall, proxy, or whitelisting policy to control access to external domains.
If you do not know whether your organization applies network filtering, contact your IT or security department to check.
What should you do?
- Check with your IT/security department whether your organization applies network filtering or domain whitelisting.
- If so, ask them to add the domain room.cxr.skeepers.io to the list of allowed domains, and to verify that the corporate firewall, VPN, and URL filtering also allow it.
- Complete this process before September 30, 2026 to prepare for the redirect.
- Domain to allow: room.cxr.skeepers.io
- Without this prior authorization, your users may experience difficulty accessing the platform or saved links once the redirect is active.
Symptoms of a whitelisting issue:
- You cannot log in to Skeepers from your corporate network.
- Access works over VPN but not outside the VPN (or vice versa).
- You receive a network connection error message.
Connectors & Webhooks: updating URLs
This section applies to customers with Salesforce or Zendesk connections, configured custom webhooks, or other OAuth integrations.
Replace room.myfeelback.com with room.cxr.skeepers.io wherever the URL appears in your configuration. The rest of the path does not change.
| Item | Before (before September 30, 2026) | Starting September 30, 2026 | Recommended action |
|---|---|---|---|
| OAuth callback URL | https://room.myfeelback.com/backend/callbackOAuth/ |
https://room.cxr.skeepers.io/backend/callbackOAuth/(automatic) Old domain still works |
Update in the third-party app starting September 30, 2026 |
| Webhooks | https://example.com/webhook?source=https://room.myfeelback.com/api/... |
https://example.com/webhook?source=https://room.cxr.skeepers.io/api/...(automatic) Old domain still works |
Update in the third-party app starting September 30, 2026 |
For Salesforce or Zendesk connectors
Step 1: Update the URL in Skeepers
- Go to Settings → Connected apps.
- Select your application (e.g., “Salesforce” or “Zendesk”).
- Go to Authentication → Managed authentications.
- Update the Callback URL field with the new URL.
- Click Save.
Step 2: Update the URL in the third-party console
You must also update the configuration in the third-party application itself.
For Salesforce:
- Log in to your Salesforce instance.
- Go to Setup → Apps → App Manager, then search for “Skeepers.”
- Click Edit.
- In the Redirect URI field, replace the existing URL with the new one.
- Click Save.
For Zendesk:
- Go to Admin Center → Apps and integrations → OAuth Clients.
- Find the Skeepers integration.
- Update the Redirect URL field.
- Click Save.
For other applications: refer to the application's official documentation. The field is generally called “Redirect URI,” “Callback URL,” or “Authorization Callback URL.”
Step 3: Test your connection
- In Skeepers, go to Settings → Connected apps.
- Click Reconnect or Reauthorize for your application.
- Follow the authentication flow as usual.
- Once authorized, verify that the integration is working correctly (Salesforce: verify that a synchronization works; Zendesk: verify that a ticket can be created from Skeepers).
For custom webhooks
Step 1: Identify your webhooks
- In Skeepers, go to Settings → Webhooks (or Integrations, depending on your version).
- For each configured webhook, note its target URL.
Step 2: Update the URLs
- For each webhook containing
room.myfeelback.com, click Edit. - Replace
room.myfeelback.comwithroom.cxr.skeepers.io. - Click Save.
Example:
- Before:
https://yourcompany.com/webhook?source=https://room.myfeelback.com/api/feedback - After:
https://yourcompany.com/webhook?source=https://room.cxr.skeepers.io/api/feedback
Step 3: Test your webhook
- In Skeepers, trigger a real action (e.g., create new feedback, reply to a message).
- Verify that the webhook is triggered correctly.
- Verify that the data reaches your system successfully.
If the webhook is not triggered, check that the URL has been updated correctly, that the new URL is accessible from your system, and review your system logs for any connection errors.
Key dates
-
Before September 30, 2026 — Whitelist the
room.cxr.skeepers.iodomain (if applicable) and update OAuth integrations, connectors, and webhooks (if applicable) (customer action).
This deadline gives you several months to complete the necessary updates without urgency.
FAQ
No, this is recommended but not mandatory. The old domain will continue to work. We recommend updating starting September 30, 2026, to ensure long-term compatibility.
Go to Settings → Connected apps. If the page is empty or grayed out, you do not have one.
Your third-party application will no longer be able to authenticate users with Skeepers and will display an error message. This is easy to correct once the issue has been identified.
Yes. Credentials saved by your browser on the old domain are not transferred to room.cxr.skeepers.io. You can find them in your browser's password manager (see Finding your saved credentials).
No, your Skeepers password will not change. However, if you need to reset it using “Forgot password,” enter your username (not your email address, unless it is your username).
No, your data will remain intact. Only the domain is changing.