We’ve identified a recurring issue where users may accidentally configure their forwarding or business number to the same LC (LeadConnector) number that is receiving incoming calls. This creates a call loop, causing multiple simultaneous call events and triggering repeated missed-call text responses.

Currently, the platform does not detect or prevent this configuration, which can lead to confusion, unintended automation triggers, and a poor user experience.

Requested Enhancement:

Introduce a system-level safeguard that:

Detects when a forwarding number matches the assigned LC number

Flags potential call loop configurations in real time

Displays a clear warning or error message during setup

Optionally prevents saving the configuration until corrected

Expected Impact:

Prevents accidental call loops

Reduces support tickets related to repeated triggers

Improves reliability of missed-call text automation

Enhances overall user experience with proactive guidance

This feature would help users avoid a common but disruptive setup issue and ensure the system behaves as expected without requiring manual troubleshooting.