What’s Fixed
A pond is shared by design — several agents work the same pool of unclaimed leads and need to see what has already been done on each one. That stopped being true: a member-level agent opening an unclaimed pond lead saw only their own activity. Calls placed by a colleague were missing from the Calls tab, texts were hidden, and the Emails tab reported “No emails yet” even when emails existed. Email subjects still appeared in the activity timeline but opening one returned a load error, so the lead looked half-empty rather than restricted.
The practical cost was duplicated work: agents called leads a colleague had already reached that morning, with no way to tell from the record.
This was never a deliberate decision. An earlier fix correctly scoped voicemails to the agent whose inbox number received them, and that per-agent scoping was subsequently extended to calls, texts and emails on pond leads by pattern rather than by request.
Bug Fixes
- On a lead assigned to a pond and not yet claimed, every agent with access to that pond now sees all calls (including recordings and transcripts), texts and emails on the lead, whoever logged them.
- The Emails tab and the activity timeline now agree with each other on those leads — no more visible subject lines that fail to open.
What has not changed
- Claimed or directly assigned leads stay private to the assignee and their collaborators. Claiming a lead removes it from the pond, and that is what draws the line.
- Your mailbox sharing preference is still yours. If you have chosen not to share your emails with the team, they stay private everywhere, pond leads included. This fix does not override that setting.
- Voicemails are unchanged. A voicemail left on one agent’s inbox number is addressed to that agent, not to the lead, and stays scoped to them.
- Aggregate views are unchanged. My Inbox and the Voicemails list remain scoped to you.
- Partner API integrations are unchanged. A user-scoped API token continues to return only that user’s own activity on unclaimed pond leads, exactly as before — this widening applies to people working in the app, not to external integrations reading through the API.