Build a Tally contact form: questions, publishing and checking submissions

Define what happens after submission

This form accepts brochure requests and general questions. It does not automatically confirm a booking, a quotation or a contract. Decide who reviews incoming messages, the response target and the information needed for a reply before adding questions. The completion screen confirms submission, while the team's later handling is a separate stage that needs its own responsibility.

Collect only fields needed for the reply

Create fields for enquiry type, subject, reply email and message. Decide whether name or company is necessary instead of automatically requiring addresses and telephone numbers. Choose appropriate input blocks and distinguish a short label from a long message. Avoid a questionnaire so extensive that a simple request becomes difficult to submit on a phone.

Configure required fields and useful instructions

Require only the fields without which the team cannot act. Help text should explain a format or purpose the submitter needs to know. Email-format validation does not prove that the address can receive a reply. Plan how staff will recognize a corrected resubmission rather than treating every repeated message as a new unrelated case.

Write a realistic completion message

Confirm receipt and explain the expected reply time. Include an urgent contact route only if one is actually supported. Avoid wording that implies a purchase or appointment was confirmed. If adding automatic replies or operator notifications, check their plan availability and destinations separately. The published response promise must match what the team can deliver, including weekends and absences.

Check both preview and the published form

Review question order and required-field behavior in preview, then publish and test the actual URL. At a narrow screen width, inspect long labels, message entry and visible validation errors. After later edits, check the public form again rather than assuming the editor state is already what respondents see. Use fictional practice content and a controlled reply address.

Reconcile submissions with notifications

Test a valid response, a missing required field and a long message. Confirm the accepted response exists in Tally's submissions and, if notifications are enabled, corresponds to the notification received. Missing email alone is not proof that the answer disappeared; inspect the submissions list first. Decide how the team identifies and clears practice responses before routine use.

Add destinations when the process needs them

For a small workload, regular review in Tally may be sufficient. A spreadsheet requirement can use its native Google Sheets integration, while branching across several services may justify Make. Finish the intake and ownership process before expanding integrations. This guide proposes a setup and acceptance checklist; it does not claim an executed account test or require a separate automation product to publish a basic form.

• Set up Tally conditional logic: visibility, required answers and changing choices
• Send Tally responses to Google Sheets: native integration and reconciliation
• Tally pricing: when Free, Pro or Business fits