Inbox

Form kinds

A support request is not a job application, and neither is a wedding RSVP. Tell ShipMyForm what a form is and the inbox reshapes itself: a board with the right columns, a card that leads with the right fields, a headcount or a rating histogram where a list is the wrong answer.

All plans: Kinds, boards and summaries are on every plan, Free included. Nothing about your form, its endpoint or its submissions changes when you set one — only how the dashboard reads them.

What each kind gives you

One inbox, one engine, nine presets. A form with no kind is the plain list you already know.

KindViewA row leads withExtra actions
contact / genericListSender and message, as beforeReply, Mark done
multi-stepListProject type and budgetReply, Mark done
supportBoard: New → Open → Waiting on customer → ResolvedSubject, priority, account or order idReply, Resolve, change priority
job-applicationBoard: Applied → Screening → Interview → Offer → RejectedName, role, whether a CV cameDownload CV, Reply, Reject
rsvpList with a headcountAnswer and guest countReply, change the answer
waitlistList with positionsEmail, name, companyReply
newsletterList with a subscriber count and growth lineEmailExport
feedbackList with a rating histogramRating as stars, commentsReply

Board kinds open as a board until you pick otherwise; the board guide covers moving, keyboard and bulk actions.

A job-application form shown as a board: Applied, Screening, Interview, Offer and Rejected columns, each card naming the applicant, the role and whether a CV came.

Set the kind

Three places, same field.

  1. The form generator. Pick a template in the generator and “Host this form” — the hosted form arrives already typed.
  2. Settings → General.“What kind of form is it?” on any form, with Not set as the first option. The columns the choice implies are listed under the selector.
  3. The MCP server. create_form and update_form accept kind; get_form reports it and the stage keys it implies.
mcp
update_form { formId: "frm_…", kind: "job-application" }
// get_form → { kind: "job-application", stages: ["applied","screening","interview","offer","rejected"] }

How fields are matched

A kind cannot assume your field names, because people name fields anything. Each slot is matched in three passes and stops at the first hit: the names the generator uses, then a short synonym list, then — for attachments, links and numbers — the shape of the value. A slot that matches nothing is not shown; an empty “Priority” label would be worse than no label.

SlotMatched field names
CV / attachmentcv, resume, attachment, file, upload, document — or any field holding an uploaded file
Prioritypriority, severity, urgency, impact
Account / orderaccount, account_id, order, order_id, order_number, customer_id, invoice, ticket, reference
Subjectsubject, title, topic, issue, summary
Rolerole, position, job, job_title, vacancy, applying_for, opening
Linklinkedin, portfolio, website, url, link, github, site — or any field holding an http(s) URL
Attendingattending, rsvp, attendance, coming, response
Guestsguests, guest_count, number_of_guests, party_size, plus_ones — or any numeric field
Dietarydietary, diet, dietary_needs, dietary_requirements, allergies, food
Ratingrating, score, stars, nps — a number 1–5, or the generator's "4: Good"
Messagemessage, cover_letter, comments, comment, body, details, description, notes, question, feedback

Matching is case-insensitive and ignores spaces and dashes, so Full Name, full-name and full_name are the same field.

Changing a kind later

Nothing migrates. Submissions keep their stored stage; one that is not a column on the new board shows in the first column rather than disappearing. The counts fold the same way, so the board and the list always agree. Clear the kind and the form is the plain list again.

Related

FAQ

Does setting a kind change my form or its submissions?
No. A kind only changes how the dashboard reads what is already there. Nothing is migrated, renamed or re-sent; your form's endpoint, fields, connectors and existing submissions are exactly as they were. Set it, look, and set it back if you prefer the plain list.
Which plan do form kinds need?
All of them, including Free. The board, the per-kind cards and detail, the headcount, waitlist and rating summaries work on every plan. Replying from the inbox is Starter and up, and assigning to a teammate needs a second seat, which Starter and Business include.
My field is not called "priority". Will it still be picked up?
Probably. Each slot matches the names the form generator uses first, then a short list of synonyms (severity, urgency, impact for priority), and for attachments, links and numbers it falls back to the shape of the value. If nothing matches, the slot is simply not shown and the field stays in the full list below — you never get an empty "Priority" label.
What happens if I change a form from support to job application?
The columns change; the cards stay where they are. A submission whose stored stage (say, "waiting on customer") is not a column on the new board shows in the first column, and any field the new kind promotes is picked up from the existing data. Change it back and everything returns.
Can an AI agent set the kind?
Yes. create_form and update_form on the MCP server take a kind, and get_form reports it along with the stage vocabulary it implies. An agent building a careers page knows it is building one; this is how it tells the inbox.