Can ChatGPT host a form?
Yes. ChatGPT Sites can host a form and save submissions. Add Sails and your AI assistant also answers each one from your address, and the replies come back to your inbox.
ChatGPT Sites can host the form and save submissions. Nobody answers the person who filled it.
Sites inside ChatGPT can build a form, publish it on a URL, and keep each submit in a database. That part works. What it leaves undone is the job after the submit. The person who asked for a quote is still waiting for an email, the team hears about the lead only when someone opens the list, and Sites does not run the background services that would follow up the next morning.
The form also lives inside the Sites product. A new chat does not open sites/northside/contact.html by path, and Mail and Routines cannot share that disk. Copying each row into Gmail or Slack by hand is still you finishing the form.
Sails is Sites, Mail, and Routines for that chat. Your AI assistant publishes the form as a file in the workspace and saves each submit as a row. It emails the person back from your address, and when they answer, the reply lands in your Sails inbox where the next chat can read it. A Routine can check the list every weekday morning for anyone still waiting.
Ask in ChatGPT. The form gets answered.
You say what the form should ask and what should happen when someone submits. Your AI assistant publishes the page, saves each submission, and sends the reply. When the person writes back, you ask about it in the same chat or the next one.
Host a quote form on my site. Name, email, phone, and what they need. Email each person back that we will call within a day.
Wrote sites/northside/contact.html
Created table contact_submissions
Published sites/northside
Live at https://northside.sails.app/contact. Each submit is a row, and the person gets a reply from agent@inbox.sails.app.
Sent mail from agent@inbox.sails.app
Received mail in agent@inbox.sails.app
Did anyone write back?
Queried table contact_submissions
Nora replied. She wants a kitchen quote and mornings work best. Her answer is in the inbox thread with the form row.
Every weekday at 8, send me anyone who submitted and never got a call.
Created routine open-leads (weekdays 8:00)
Set. The list comes from contact_submissions each weekday morning.
Saved submissions vs answered submissions
A form that saves rows is half the job. The other half is the reply, the heads up to the team, and the follow-up for whoever slipped through. ChatGPT Sites gives you the URL and the table. You still read the list and write back yourself.
With Sails, the form, the table, the inbox, and the Routine sit on the same workspace disk. Your AI assistant edits the form file and autosave publishes it. The reply goes out from an address, and the answer comes back to a thread the next chat can open. You do not wire a form tool to a mail tool to a scheduler.
Your AI assistant sets all of it up from the chat. Other people open a real URL and submit. The form and the replies stay after the tab closes.
What you get
A reply for every submit
Each person hears back from your address. When they answer, the reply lands in your inbox, not in a list you have to remember to check.
A form on a workspace path
The next chat opens sites/northside/contact.html by name. Ask for a new field and the file, the table, and the live form follow.
Follow-up that runs without you
A Routine reads the same table on a schedule and sends you whoever is still waiting. It runs whether or not a chat is open.
Put your AI assistant to work.
Add Sails to ChatGPT. Your AI assistant hosts the form, answers each submit from your address, and keeps the replies in your inbox.