Set boundaries / expectations ahead of time. Tell them you will acknowledge an issue within 24 hours and provide a solution within 7 days _if_ it's important.
Whatever works for you.
You should reserve the right to outright reject feature requests without providing a convincing reason beyond "it's not within our scope".
2. Recognise that you have an opportunity to practice the courage of telling people things that they do not want to hear.
3. Recognise that when you have employees and investors, they'll be relying on you to tell them things they don't want to hear.
4. Recognise that your future self will find it far harder to practice courage if his past self abandoned him to the risk of homelessness.
Pick something also that doesn't need constant human hands/duck tape. E.g. if you are web scraping, and someone changes their site HTML structure on 3pm on a Wednesday, then you have to be hands on to fix it.
If you are running an app that is self sufficient - you put the hours in at the weekend to make it robust, it doesn't bother you during the week, most of the time.
In other words, build stuff that ... scales :-)
At the $1bn company I would get vendor responses quickly, because we paid for enterprise support. At the scrappy startup I just got used to responses coming a day or so later (especially since I was working with USA vendors while I was based in Taiwan).
If a customer wants a 1-2 hour response time they'll pay much more for it.
Low key, in most cases those people would be better off selling fake healing crystals on Etsy.
What then?