🐛 Describe the Bug
Chinese phone numbers (used as proxy numbers by our custom messaging provider) are treated inconsistently across the platform.
- These numbers are accepted as valid in Contacts
- They work correctly when sending normal messages
- However, the same numbers are marked as invalid in Workflows, causing:
- Workflow actions such as Send Internal Notification or Send SMS to skip these contacts
- Messages to silently fail for workflow-based sends
- This suggests that Workflows use a different phone-number validation logic than Contacts and normal messaging flows, even though the numbers are already saved and actively used elsewhere in the system.
📍 API Endpoint
/workflows
✅ Expected Behavior
There should be consistent phone-number validation across the entire platform.
One of the following should happen:
- Option A (Preferred):
Use the same validation logic in Workflows that is used while saving Contacts and sending normal messages.
- Option B (Acceptable Alternative):
When a custom messaging provider is configured (instead of LC), skip phone-number validation in Workflows and allow the provider to handle validation internally.
In either case:
- A number that is considered valid in Contacts must not become invalid in Workflows
- Existing saved numbers should continue to work without being blocked by workflow-specific validation
💻 Screenshots or Code Samples
Product Area
workflows
📋 Use Case
We are a custom messaging provider and use these phone numbers for internal messaging.
These numbers:
- Are already validated on our side
- Work correctly for direct messaging
- We already have internal logic and safeguards to determine whether a number is valid or invalid
- Workflow-level validation prevents us from sending messages that are otherwise valid and intentional
- Because many of these numbers (probably thousand) are already saved across multiple locations and contacts, this issue affects existing customers not just new setups.
🚨 Why Should This Be Prioritized?
- This issue is actively blocking messages from being sent via Workflows using our custom provider
- It has caused a significant spike in customer support tickets
- Customers are unable to send messages despite:
- Contacts being saved successfully
- Numbers working in other parts of the system
- The inconsistent validation creates confusion and breaks trust, as the same data behaves differently in different modules
This is a critical blocker for customers using custom messaging providers and directly impacts message delivery and customer experience.
🧠 Additional Context
No response
🐛 Describe the Bug
Chinese phone numbers (used as proxy numbers by our custom messaging provider) are treated inconsistently across the platform.
📍 API Endpoint
/workflows
✅ Expected Behavior
There should be consistent phone-number validation across the entire platform.
One of the following should happen:
Use the same validation logic in Workflows that is used while saving Contacts and sending normal messages.
When a custom messaging provider is configured (instead of LC), skip phone-number validation in Workflows and allow the provider to handle validation internally.
In either case:
💻 Screenshots or Code Samples
Product Area
workflows
📋 Use Case
We are a custom messaging provider and use these phone numbers for internal messaging.
These numbers:
🚨 Why Should This Be Prioritized?
This is a critical blocker for customers using custom messaging providers and directly impacts message delivery and customer experience.
🧠 Additional Context
No response