v2026.3.3

Release date: March 20, 2026

---

✨ New Features

👥 Team Selection When Starting a Conversation

You can now choose which team will be responsible for a service at the moment it is created — whether in individual conversations, bulk message campaigns, or API integrations.

What is it for?

• Distribution control – Assign the right team from the very first contact, without manual transfers later
• Individual conversations – When starting a conversation with a customer, a team selector appears before choosing the channel
• Bulk campaigns – The "Team for new chats" field in the campaign ensures all newly created services go to the right team
• Via API – External integrations can send the teamId field to automatically define the team

How to use?

1. Individual conversation: Open a customer profile → click Start conversation → choose the team in the selector → select the channel
2. Bulk campaign: Create or edit a campaign → find the "Team for new chats" field → select the desired team
3. API: Send the teamId field in the request body when creating a service

Automatic assignment

If no team is selected, the system follows an automatic order: channel default → user's team → organization default team.

---

🐛 Bug Fixes

Invalid number no longer creates a service

For WhatsApp channels with active number validation, when the contact does not have WhatsApp, the service was not being blocked correctly and no clear error was shown. Now the system blocks the creation and displays the exact error message, making it easier to identify the problem.

---

🎯 Benefits

• ✅ Immediate distribution – Services go straight to the right team, without manual transfer steps
• ✅ Campaign consistency – All chats generated by a campaign already come with the team defined
• ✅ Easier integrations – APIs and automations can control the destination team programmatically
• ✅ Clearer errors – Creating a service for an invalid number now fails with a clear, informative message