> ## Documentation Index > Fetch the complete documentation index at: https://docs.clarky.ai/llms.txt > Use this file to discover all available pages before exploring further. # Form Submissions > View, manage, and export form responses ## The Submissions Table Every form has its own submissions page where you can review every response that's come in. Open it from the form editor or from **CRM > Forms**, then click the **Submissions** link on the form you want to review. The submissions table shows all responses with sortable columns, an internal/test badge, quick links to the contact record, and an export menu. ## What's in the Table ### Standard Columns Every submissions table includes these columns by default: * **Submitted** — date and time of the submission * **Contact name** — name of the contact created or updated * **Email** — email captured from the submission * **Phone** — phone number captured from the submission ### Response Columns The remaining columns depend on the form's style: A column for each custom field on the form. Standard contact fields populate the existing name/email/phone columns. A column for each question. Form fields questions are automatically expanded — each standard or custom field inside a form fields question becomes its own column, so you can see all the data at a glance instead of a single nested blob. ### Internal Submission Badge Submissions made through the **preview** in the form editor are tagged with an **Internal** badge in the table. This makes it easy to identify test data and keep it separate from real responses. Filter or visually scan for the Internal badge when you're reviewing real lead activity. Test submissions never trigger external automations like notifications. ## Actions on Each Submission For each row in the submissions table you can: Jump straight to the contact's record in the CRM to see their full history Remove a submission you no longer want to keep Deleting a submission removes the response record but doesn't remove the contact it created. Use the CRM if you also want to delete the contact. ## Exporting Submissions The submissions page has an **Export** dropdown with two formats: Downloads all submissions as a JSON array, formatted for readability. Use this when you want a structured, machine-readable snapshot of all responses. Downloads all submissions as a CSV file that opens cleanly in Excel, Numbers, or Google Sheets. Use this for spreadsheet analysis or sharing with non-technical teammates. Both formats include: * Submitted date and time * Contact name, email, and phone * The internal/test flag * Every response column, including form fields expanded into individual fields ## Contact Creation Behavior Every submission either creates a new contact or updates an existing one: Clarky checks the submission's email and phone against existing contacts. If a match is found, the existing contact is updated with any new info from the submission. If not, a brand-new contact is created. For new contacts, the form's default tags are added. If the form has a default pipeline stage, a pipeline card is created (with the default deal value, if set). Updates only add or refresh information — they don't overwrite tags or pipeline stages on contacts that already exist. This protects long-term contacts from being reset every time they fill out a form. ## Email Notifications When notifications are enabled for a form, your team gets an email every time someone submits. The email includes: * The form name and submitter's contact info * All submitted answers with proper formatting * Each question and answer pair on its own line for easy scanning * Form fields questions broken out field-by-field (no nested blobs) Make sure each form's notifications are routed to the right team. A "Contact Sales" form should notify your sales team; a "Customer Feedback" form might notify support. ## Pipeline Cards from Submissions If you set a **default pipeline stage** on the form, every new contact created from a submission will automatically appear as a card on that stage in your sales pipeline. The card includes: * Contact name * Default deal value (if configured) * Default tags (if configured) * A link back to the contact and the original submission This is the fastest path from "lead form on website" to "card in your pipeline" — no manual data entry required. ## Next Steps See how form submissions land on your pipeline Work with the contacts your forms create Get more responses by embedding on your site Back to the Forms overview