Prevent Domain Connection Conflicts in CRM

Your CRM platform now includes a safeguard to prevent a domain from being connected to multiple conflicting product types, which could otherwise disrupt an existing setup. Before a domain is connected to a new product, the system automatically checks if the domain is already in use by another supported product. If a conflict is found, the connection will be blocked, and a detailed error message will explain the issue. This helps you avoid accidentally breaking live Funnels, Websites, WordPress sites, Client Portals, and other connected services.

How Domain Conflict Detection Works

When you attempt to connect a domain to a product, the platform performs a conflict check before validating your DNS records. If the domain is already connected to another supported product type, the system will:

• Block the new connection attempt.
• Identify which product is currently using the domain.
• Display guidance to help you troubleshoot.
• Provide a direct navigation link to the relevant settings when applicable.

For example, if a domain is already connected to a Funnel, trying to connect it to a Client Portal may be blocked to prevent the existing setup from breaking.

Supported Product Types

The conflict detection feature currently applies to the following product types:

• Funnel
• Website
• Store
• Blog
• Webinar
• WordPress
• Client Portal
• Branded Domain

Email-related products are excluded from these conflict checks.

Resolving Domain Conflicts

If you encounter a conflict, carefully review the error message before taking any action.

Same Location Conflicts

If the conflicting product exists within the same location, the error message may include a direct link to the existing domain connection. Use this link to:

• Review the current setup.
• Disconnect the existing product if appropriate.
• Choose a different domain if needed.

Cross-Location Conflicts

If the conflict exists in another location within the same agency:

• The connection will still be blocked.
• A direct link will not be provided.
• The error message will identify the issue so you can investigate further.

Important Notes

• Conflict checks occur before DNS validation checks.
• Domain conflicts are detected across all locations within an agency.
• Existing domain connections are not modified automatically.
• Email products do not trigger product-type conflict checks.

Frequently Asked Questions

Q: What happens if I try to connect a domain that is already in use?

A: The system will block the connection and display an error message explaining the conflict.

Q: Can I override the conflict warning?

A: No. You must resolve the existing conflict before proceeding.

Q: Does this affect existing domain connections?

A: No. Existing connections remain unchanged unless you update them manually.

Q: Why do some errors include a direct link?

A: A link appears when the conflicting product is in the same location, allowing you to navigate directly to the relevant settings.

Q: Why is there no link for some conflicts?

A: If the conflict is in another location within the agency, the system does not display a direct navigation link.

Q: Are email products included in conflict detection?

A: No. Email-related products are excluded from these checks.