Skeepers domain migration to room.cxr.skeepers.io — what changes for you

Skeepers is upgrading its domain names to strengthen the stability, security, and performance of its services.
The login URLs for our platform applications are migrating to a single domain: room.cxr.skeepers.io.

Background

The login URLs for our platform applications are migrating to a single domain: room.cxr.skeepers.io. The previous URLs (room.myfeelback.com) will be automatically redirected to this new domain.

This migration was already announced in a first communication in November 2025. This article serves as a reminder ahead of the redirection going live.

Am I affected?

For the vast majority of customers, the redirection is seamless: current URLs will keep working and no action is required in your Skeepers account.

However, action on your part may be required before September 30, 2026 in two cases:

• your organization applies network security rules (firewall, proxy, domain filtering / whitelisting);
• you use OAuth integrations, connectors (Salesforce, Zendesk), or custom webhooks.

Whitelisting: check your network rules

This step applies to all customers whose organization enforces a firewall, a proxy, or a whitelisting policy to control access to external domains.

What to do?

1. Check with your IT / security team whether your organization applies network filtering or domain whitelisting.
2. If so, ask them to add the domain room.cxr.skeepers.io to the list of allowed domains, and to make sure the corporate firewall, VPN, and URL filtering also allow it.
3. Complete this step before September 30, 2026, to get ahead of the redirection going live.

Signs of a whitelisting issue:

• You can't log in to Skeepers from your corporate network.
• Access works over VPN but not off VPN (or vice versa).
• You get 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 everywhere the URL appears in your configuration. The rest of the path stays the same.

For Salesforce or Zendesk connectors

Step 1: update the URL in Skeepers

1. Go to Settings → Connected Apps.
2. Select your application (e.g. "Salesforce" or "Zendesk").
3. Go to Authentication → Managed Authentications.
4. Update the Callback URL field with the new URL.
5. Click Save.

Step 2: update the URL in the third-party console

You also need to update the configuration in the third-party application itself.

For Salesforce:

1. Log in to your Salesforce instance.
2. Go to Setup → Apps → App Manager, then search for "Skeepers".
3. Click Edit.
4. In the Redirect URI field, replace the existing URL with the new one.
5. Click Save.

For Zendesk:

1. Go to Admin Center → Apps and integrations → OAuth Clients.
2. Find the Skeepers integration.
3. Update the Redirect URL field.
4. Click Save.

For other applications: check the application's official documentation. The field is usually called "Redirect URI", "Callback URL", or "Authorization Callback URL".

Step 3: test your connection

1. In Skeepers, go to Settings → Connected Apps.
2. Click Reconnect or Reauthorize for your application.
3. Follow the authentication flow as usual.
4. Once authorized, check that the integration works correctly (Salesforce: check that a sync runs; Zendesk: check that a ticket can be created from Skeepers).

For custom webhooks

Step 1: identify your webhooks

1. In Skeepers, go to Settings → Webhooks (or Integrations depending on your version).
2. For each configured webhook, note its target URL.

Step 2: update the URLs

1. For each webhook containing room.myfeelback.com, click Edit.
2. Replace room.myfeelback.com with room.cxr.skeepers.io.
3. 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

1. In Skeepers, trigger a real action (e.g. create a new feedback, reply to a message).
2. Check that the webhook fires correctly.
3. Check that the data arrives correctly in your system.

If the webhook doesn't fire, check that the URL has been updated, that the new URL is reachable from your system, and review your system's logs for any connection errors.

Key dates

• Before September 30, 2026 — Whitelisting of the domain room.cxr.skeepers.io (if applicable) and updating OAuth integrations, connectors, and webhooks (if applicable) (customer action).

FAQ

If you have any questions, feel free to contact our Customer Care team.