A submission lands as a record in the sheet behind the form. What happens next is up to how you set it up — and "nothing" is the default if you skip this.
Add an automation on record created: notify the person or team who handles intake, or post it into a chat channel they already watch.
A form nobody is notified about becomes a sheet of missed requests, and you find out from an annoyed customer.
Give the sheet a Status starting at New, then a board view grouped by it. Now the queue is visible: what is new, what is being handled, what is done.
Add an owner field and assign as you triage, so each submission belongs to a person rather than to "the team".
Keep the reply attached to the record — a comment, or an email sent from the record. Six months later, the request and the answer are in the same place.
If a form matters to your business, chart it: submissions per week, and how many are still New after a day. Two numbers on a dashboard, and you know whether the process works. See Dashboards and charts.
A public form will eventually collect junk. Keep required fields meaningful, and triage rather than delete on sight — an odd-looking submission is occasionally a real customer having a bad day.
Related: Build a form and collect responses · Share and embed a form · Automate the repetitive parts