Chronological order for agent arrays in the Data Export API
The Conversations endpoint in the Data Export API (v2) now returns agent_id and agent_name in the order each Agent joined the conversation. Position [0] is the first Agent assigned; the last position is the most recent.
The two arrays remain paired — agent_name[i] corresponds to agent_id[i] — and the order is stable across repeated calls.
For more details, see the conversation object reference.
Edit team member roles inline
Team member roles can now be changed directly from the Team page. The Role column shows a dropdown for each member you have permission to edit, and selecting a new role saves immediately.
Previously, changing a role required removing the team member and re-inviting them with the new permission level.
Who it affects
Owners and Admins managing dashboard access:
- Owners can change the role of any other member.
- Admins can change the role of any member except Owners.
- You cannot change your own role. When you cannot edit a member’s role, it appears as text instead of a dropdown.
The team member whose role changes receives an email confirming the update, including who made the change and their previous and new roles.
Get started
- My team for steps to change a role and the full permissions reference.
Your AI Agent now handles media messages on social channels
On social channels, media and other non-text messages now go to your AI Agent instead of triggering a fixed reply — so the Agent responds in context and explains what it can help with.
What’s changed
- Previously, when a customer sent an image, video, audio, or other file your AI Agent couldn’t read on a social channel (such as WhatsApp), the Agent returned a fixed “Unsupported Messages” response (for example, “Oops! I can only read text”).
- Now, those messages are passed to your AI Agent, which replies directly rather than sending the static response.
- The Handling media messages section, including the editable Unsupported Messages response, has been removed from Config > Channels > Social.
Who this affects
Social channel Agents that relied on the fixed “Unsupported Messages” response. No configuration is required — the change applies automatically.