In WB, the "save" button and "save and close" are two different functions. Regarding the "save" function, which should not close things out when selected, it unfortunately will reposition things so that it goes back to the top. Our team members using the "save" function experience some user frustration or delays, due to the repositioning that takes place when "save" is pressed.
There is no "auto-saving" function currently, and the advice was that it would have to be globally implemented for all users instead of an implementation for a specific custom client. We understand a global change may not be possible. So what we would like to present as constructive feedback is that the save button is needed, but when used during real-time, it is time-hampering as each time we save, it refreshes and repositions to the top of the record; and we need this fixed so that at least the "save" button doesn't do that repositioning every time. It seems some other competitors have resolved this issue (e.g. SAP, Filevine) possibly, and some still struggle with the functionality issue (the problem of repeat repositioning). Also, another CRM program has it set up in 3 horizontal pages so that people aren't scrolling down or up, and they go through pages, so the reposition doesn't happen. We think addressing this issue in development for multiple users could help WB become a leader and help with user acceptance and training as well as efficiency for all. Thank you for considering this specific feedback! There may be more than one user-friendly solution and we look forward to seeing progress in development.