discoverability and efficiency in chat-first interfaces

How do you solve for discoverability and efficiency in natural language chat first interfaces?

Today, we're witnessing huge adoption of LLMs in the products we use and many big product builders very bullish on chat first interfaces. I am not.

I still think there is huge value in stitching a user experience that directs the user to get things done seamlessly and effortlessly. Whether chat first or not is a debate for another time. Today I have another question for you to ponder -

Imagine you are using a chat app to book a flight. You might not realise that you can also book rental cars or set reminders to make your future bookings from the same interface. The app has to somehow let you know about these features. Discoverability problem!

What if you are filling a loan application. Think if it will be easier to quickly fill a form or type everything in full sentences on a chat interface. Efficiency problem!

While designing chat interfaces for products, it is important to solve discoverability and efficiency of actions so that the users can easily find out about the cool capabilities of your products and get their things done seamlessly!

I'll think about this today and present my answer in a follow up post. Meanwhile, I am genuinely curious to know if this is a problem you have faced in your products and how do you solve it?