When self-service is the better answer

I wouldn't want a customer paying me just because I'm the only one with the login.

If they need their shop's hours changed on the website, I'd want to know whether they're choosing my help or just stuck waiting for me.

There could be a good reason for me to handle it. Maybe the hours also affect bookings, and updating the page leaves people able to make appointments while the shop is closed. The owner might be paying me to catch that.

But I'd still want to see whether I could make those changes happen together, so they wouldn't have to remember how the two systems connect. It might take some work to give them a reliable way to do it. That seems worth considering before I assume they need me for every update.

They might not want to touch any of it. Sending me the hours and getting on with running the shop could suit them better. I wouldn't try to talk them out of that.

It also doesn't have to be all or nothing. They could pay me to handle most updates and still want to change the hours themselves when something comes up. I'd want to know that before making their access depend on whether I'm around.

If you're building a service, pick a routine request you expect customers to keep making. Find out what they'd want to do themselves if they had a reliable way to do it. There may be work they'd happily pay you to handle, even when they have the option. I'd want to build around that, and leave them able to get on with the rest.