"Make the feature more useful."

Please write a user story. It's hard to determine what you want.

"As Sales Agent I would like the <feature> to be extended so it's more useful to me."

(ノಥ,_｣ಥ)ノ彡┻━┻

I feel your pain. I think BDD with User stories is one of those hipster ways to develop, which does not do any good to the final product. If you have a solid testing strategy there is no need for these damn user stories

Color everything pink and call it done.

When they complain, point out that the story is not specific enough to have omitted that solution and 'allow' them to amend it. Explain to them that there is never anything more expensive than building the wrong thing and that it's their job to prevent that.

.. Or do your own BA work by interviewing the users. Then, have your department charge their department for your time spent on feature analysis work.

@darktheme Frankly, I like user stories if done "right". It's nice if the acceptance criteria is defined. It sets me in the right perspective, it voices a need, without proposing a solution, and it can be challenged in order to find the real issue.

(I have identified a lot of XY-problems this way by when people wrote their user story as a solution to their problem.)

Though yes, it adds overhead and for some projects it's too much. And if people don't invest time and effort in their user story, all hope is lost.