How do you communicate agentic conversation UX to engineers?

How do I… research, UI design, etc?

While I’ve dabbled a little bit in the past on chat interfaces and some conversation UX, I’m now on my first end-to-end Agentic AI product and needing to map out nuanced conversation UX workflows (with approval flows, edge-cases, dead-end scenarios, etc etc).

I’ve been using Figma Make (with full access to our coded components) to be a godsend in prototyping specific flows, but I’m finding it quite a challenge in capturing broader workflows and efficiently communicating the conversation flow to our engineers. They always have valid “what if” questions about how the conversation can branch out and what to do display when such and such scenario happens that I’m finding it really time consuming to try to do it all. Especially because of the probabilistic nature of conversations.

Curious here from other designers of agentic/chats UI and conversation UX how you communicate to your engineers? What do your deliverables and artifacts look like and how do you hand them over?

Posted Apr 7, 2026, 11:16 AM UTC

02
Loading comments…