The chat shell becomes honest about what the platform can do for this customer, right now. Tools, knowledge bases, native capabilities, plugin-provided extensions — surfaced inline rather than hiding behind menus. License gates and tenant-enabled features drive the same UI signal. Customers stop asking for things the platform already supports because they couldn't find them.
Next patch
Today, a customer asks “can Eldric do X?” in chat. Sometimes the answer is yes, the feature is enabled on their tenant, but it's reached through a settings page they haven't found. Sometimes the answer is yes, but only with a license tier they haven't activated. Sometimes the answer is no, but with a clear path to enabling it.
Today the customer's UI doesn't tell them which. The chat shell talks; the settings live elsewhere; the connection between the two is something the customer has to assemble themselves.
This page updates as each piece lands. The release notes are the formal cut.
For the retention side of the same UI work, see retention UX. For the chat shell story today, see first run. For the full 5.0.x roadmap, see what's next in 5.0.x.