From Agile manifesto:
Individuals and interactions over processes and tools
Your objective is NOT to avoid communication. You want to promote it. People in a project must communicate in the most effective way they see fit. I believe you should shift the focus of your energy, changing the question you're looking for answers to questions such as
- How can we as a team effectively make sure information is available about any conversation?
- Where such information could be available?
- Why do I need to write down the outcomes of team conversations?
These questions might help you fine tune the specific needs for your context. There's no canonical answer as it heavily depends on your environment.
Environment #1: Junior team, low confidence between parts, time zone differences. You still want to keep conversations flowing, but you want to have it written somewhere for future reference. Each conversation might be related to a specific ticket, so the outcomes of this conversation could be summarised as a jira comment. Special attention to outcomes and summarised. You definitely do not want transcripts of conversations (as I saw someone doing some years ago).
Environment #2: Seasoned team, high confidence between members. On these cases, there's no better "communication" than working software. Nothing else needs to be written.
Remember: Everything that's not directly contributing to delivery, is a waste. Oftentimes, wastes are needed, but a team doesn't need to stick to them for the sake of the methodology. A methodology is just a mean, a tool for a purpose, not an objective in itself. Your focus should always be on the consistent delivery, not on consistent methodology usage.