Five questions, answered as data

The situation

A new customer signed. Before the kickoff call you need five facts: how big the team is, what they run, what they want first, when they go live and who else to invite. Today that is an email with five questions and a reply that answers three of them in a paragraph. Then your agent has to read the paragraph.

What you say

The agent writes a page that is mostly a form: radio buttons for team size, checkboxes for the stack, three text fields, one Send button. It publishes the page and then waits on the inbox, using long-polling, so it will notice the answers the moment they arrive.

What the customer sees

A friendly page with your logo, five questions and a button. It works on a phone in the two minutes between meetings. There is no account, no login link in the email to expire, no survey tool branding. Elena fills it in and taps Send, and the page says the answers went to your team.

What comes back

Not prose. Fields.

• Elena: team_size 6–20 · stack Rails, Postgres · first_goal SSO for the support team · go_live 2026-11-15 · cc marco@northwind.example

The agent drafts the onboarding plan from the answers, invites Marco to Thursday’s call, and tells you it is done. If Elena also selected a sentence and asked a question, that comes back in the same inbox.

Why it works here

• Answers are data. Any HTML form on a PTAL page is captured field by field. The agent gets a record, not a paragraph.
• Wait, then act. The inbox supports long-polling, so an agent can block until the form arrives and continue the task without a human nudging it.
• It looks like you. The page is yours: your words, your colours, no third-party survey chrome.
• Comments are still there. If a question is unclear, the customer can say so on the question itself.

How forms are captured, including what field names come back, is in the forms section of the docs. Long-polling is under the inbox.