Changelog Update

Select a Custom Default Agent in Pods

🎯 What is it?

You can now choose a default agent for an entire Pod. Once set by a Pod editor, every new conversation started in that Pod will automatically begin with the selected agent, instead of the standard default. This setting lives directly in your Pod settings.

💡 Why is it useful?

Teams often rely on a specific agent that already has the right context, skills, and connected data for their work. Until now, members had to manually pick that agent each time they started a conversation, an easy step to forget and a source of inconsistency across a team. Setting a default agent at the Pod level removes that friction and ensures everyone starts from the same, well-prepared assistant.

⚙️ How does it work?

An editor of the Pod opens the Pod settings and selects the agent they want as the default. From that point on, all new conversations created in the Pod open with this agent already selected.

✨ Concrete Use Cases

Here's how you could use it:

• Support team Pod: Set a customer-support agent as the default so every new conversation is handled by an agent that already knows your product documentation and support tone.

• Sales team Pod: Default to an agent connected to your CRM and sales playbooks, so account managers immediately get relevant, context-aware answers without any setup.

📈 Benefits for you

• Consistency across your team: everyone talks to the same specialized agent by default.

• Time saved: no need to manually select the right agent for each new conversation.

• Better answers from the start: conversations begin with the context, skills, and data your team actually needs.

🚀 How to access it?

This is available to all users. If you're an editor of a Pod, open your Pod settings and select the agent you'd like to set as the default for new conversations. Existing conversations are unaffected.