Yeah - I get it. We all want to mitigate the number of gears in the machine and for many reasons. This is not unreasonable and without seeing the entire set of survey requirements, it’s not wise for anyone to second-guess your approach.
However, from experience, as soon as one hack is employed in a solution, you need to be prepared for many additional workarounds to get to a “perfect” solution", so brace yourself.
I’m not really an expert in matters involving surveys but I have recently deployed an SMS-based survey system for an Airtable client. They have a table of brief questions and another table of responses. The SMS process uses Twilio (and the API) to send questions to respondents that have opted-in and they simply answer with y/n or other 1,2,3,… responses.
I guess we live in a texty world now because this has increased their response participation by 75%. Also, this is how most of the NPS score companies are operating now. It’s a little more complex than using forms, but once the framework is in place, there are huge advantages.