Improved A2P Campaign Rejection Feedback
We've made it easier to understand why an A2P campaign was rejected and what the user needs to do to fix it.
What's new :
When a campaign submission is rejected, users will now see a "View required fixes →" link next to each rejection reason.

Clicking it opens a detailed modal that breaks down the issue into four clear fields:
- Error code – the specific code returned by the carriers.
- Rejection category – a human-readable label for the type of violation (e.g., Invalid website URL).
- What it means – a concise explanation of why the submission failed.
- Correction needed – the exact action required before resubmitting.

Previously, rejection reasons were displayed as short descriptions with no additional context, leaving users confused about the precise cause of rejection and the required next steps.
Why it matters :
This change shares precise feedback with the user so they can fix issues faster with lesser assistance required from customer support and consequently resubmit with confidence.
Opportunities now available as a dedicated tab on the contact page right panel
Overview
Based on valuable customer feedback on the new Contact Page design, we are introducing an improved way to access opportunities. This update focuses on better visibility, faster access, and a more intuitive layout while we continue building deeper customization capabilities for the contact page.
What’s New
- Opportunities moved to the right panel as a dedicated standalone tab
- Positioned below Associations for improved discoverability
- Decoupled from Associations (view-only change) — no impact on data structure or functionality
- Opportunities are temporarily accessible in two places: Under actions & on the right panel
How It Works
- Navigate to a contact record -> On the right-hand panel, you’ll now see a dedicated opportunities tab below associations.
- This tab provides a clear, focused view of all opportunities linked to the contact
- For the transition period, you can still access opportunities via the actions menu, ensuring no disruption to the current flow

What’s Next
- By Apr 08, 2026, opportunities will be removed from the actions tab and will live exclusively on the right panel
- We are actively working on contact page customization, which will allow you the admins to reposition the opportunities tab and customize contact layout based on their preferences
Fixed: Website Field Now Available in the Contact Changed Trigger
Overview
In the Contact Changed trigger, the Website contact field was not available as a selectable field. This prevented users from starting automations when a contact’s website was updated and forced workarounds outside the trigger.
What’s new
The Website field is now supported in the Contact Changed trigger.
What’s changed
You can now use the Website contact field with the operators has changed and has changed to to trigger workflows when that value is updated.
Additional Notes
- This fix applies to the Contact Changed trigger only.
- The team is also actively working on improving support for other missing fields and operators.
Fixed: Website Field Now Available in the Contact Changed Trigger
Overview
In the Contact Changed trigger, the Website contact field was not available as a selectable field. This prevented users from starting automations when a contact’s website was updated and forced workarounds outside the trigger.
What’s new
The Website field is now supported in the Contact Changed trigger.
What’s changed
You can now use the Website contact field with the operators has changed and has changed to to trigger workflows when that value is updated.
Additional Notes
- This fix applies to the Contact Changed trigger only.
- The team is also actively working on improving support for other missing fields and operators.
Fixed: Website Field Now Available in the Contact Changed Trigger
Overview
In the Contact Changed trigger, the Website contact field was not available as a selectable field. This prevented users from starting automations when a contact’s website was updated and forced workarounds outside the trigger.
What’s new
The Website field is now supported in the Contact Changed trigger.
What’s changed
You can now use the Website contact field with the operators has changed and has changed to to trigger workflows when that value is updated.
Additional Notes
- This fix applies to the Contact Changed trigger only.
- The team is also actively working on improving support for other missing fields and operators.
