How do I make a customer support request form in Notion?

Make a customer support request form in Notion: build a tickets database, add a form view, require an email, share it to the web and track it on a board.

Nookesh KarriNovember 19, 20267 min read
Light cover card with the title 'How do I make a customer support request form in Notion?' in dark text and a blue accent bar

To make a customer support request form in Notion, create a tickets database, add a Form view, and make the email question required. Then share the form with Anyone on the web with link so customers without Notion can use it. Each request lands as a new page that you track with a Status property on a board.

What a customer support request form in Notion needs

A customer support request form in Notion needs six questions: who is writing, what kind of issue it is, what happened, who is affected, and how soon it matters. Everything else belongs in properties your team fills in.

Notion’s own forms guide suggests support forms carry an Issue Type property (“bug, feature request, account problem”) and a Priority Level. I’d split that second one in two.

Property Type On the form? Why
Name Title Yes, required A person to address
Email Email Yes, required The only way to reply
Issue type Select Yes, required Routes the request
What happened Text, long answer Yes, required The actual problem
Who is affected Select Yes Measures impact
How soon do you need this Select Yes Measures urgency
Priority Select No Your team sets it
Status Status No To-do, In Progress, Complete
Assignee Person No Who owns the reply
Received Created time No Fills in automatically

A government guide to structuring forms has a good test for every row: only add a question if you know you need the information to deliver the service, and why. If nobody on your team would act on “Company size,” cut it.

How to build the form step by step

Building the form is eight short steps once the table above is decided. Forms are available to “all members on all Notion plans,” according to the forms help page, so the Free plan is enough to start.

  1. Create the database. Make a new database called Support requests and add the properties from the table.
  2. Add the form view. Select + next to the existing views, choose Form, then Create questions. Each question is connected to one property.
  3. Remove the internal questions. Delete Priority, Status and Assignee from the form. The properties stay in the database.
  4. Set the required ones. Open each question’s ••• menu and turn on Required for Name, Email, Issue type and What happened.
  5. Turn on Long answer for What happened, and add a Description such as “Tell us what you expected and what you saw instead.”
  6. Edit the submit screen. Under Form settings, then Submit screen, write a Confirmation body that says when to expect a reply.
  7. Share it. Select Share form, then Who can fill out, then Anyone on the web with link.
  8. Send a test request from a private browser window and check the new row.

The form creation walkthrough covers the builder in more detail.

Why the email question has to be required

The email question is the only link between a public request and the person who sent it. Notion states that respondents to forms shared with Anyone on the web with link “will automatically be anonymous,” so nothing else identifies them.

A support request with no way to reply is worse than no request, because the customer thinks you’ve heard them. Mark Email as required, and use the formula check from the required email guide to flag typos.

Why customers shouldn’t set their own priority

Customers shouldn’t pick the priority, because everyone’s own problem feels like the top one. Ask two factual questions instead and set the priority yourself.

A university service desk’s priority matrix guide explains the split. Impact is the effect on the business. Urgency “is not about effect as much as it is about time.” And “priority is where impact and urgency intersect.” The same guide gives the classic failure: a customer files a “high priority” request for a new mouse when the old one works fine.

So the form asks:

  • Who is affected? Just me / My team / All our users
  • How soon do you need this? It’s blocking my work now / This week / No rush

An “All our users” plus “blocking now” request goes to the top. A “Just me” plus “No rush” one waits. My take: this is the one change that makes a small support queue fair. You stop working tickets in the order of who shouted loudest.

How to track and assign incoming requests

Track requests on a board view grouped by Status, so each new ticket starts in the first column and moves right as you work it. Notion’s Status property groups its tags into To-do, In Progress and Complete, which is enough for a small team.

Add a second board grouped by Priority. Notion’s guide describes the same idea, a Kanban board that sorts requests by urgency levels like Low, Medium, High and Critical.

For alerts, the free option is the email copy of each submission under Submit screen. Database automations with a Page added trigger do more. Send notification to alerts up to 20 people in your workspace, and Edit property can set an Assignee by issue type, as the auto-assign guide shows.

Send Slack notification posts to a channel, but Notion’s page contradicts itself: one line says Free plan users can create Slack notification automations, another lists the action under Plus, Business and Enterprise. Test it on your plan. The other actions need a paid plan.

How customers hear back

Customers can’t see their ticket, so every update has to reach them by email. Access to submission, the setting that lets a respondent view their response, only exists when the form is limited to your workspace and anonymous responses are off. A public support form never qualifies.

On a paid plan, the Send mail to automation action fills that gap. It sends from your Gmail account to an external address, and the message can include properties from the ticket. You need a Gmail account, and emails “may take up to two minutes to arrive.” The confirmation email guide walks through an acknowledgement message.

On the Free plan, reply by hand from your own inbox and change the Status when you do.

Where the native form falls short, and where nDBForms fits

The native form has two gaps for support work. Customers can’t see their ticket, as covered above. And follow-up questions by issue type, like asking for an order number only on billing problems, need conditional logic, which is only on Business and Enterprise plans.

nDBForms reads the same Support requests database and generates matching fields, and each submission creates a new page in it. On its Pro plan ($12/month founding price), customers can upload files up to 10 MB each to your Google Drive, and conditional logic works with any Notion plan. You also get an email notification for each new submission. Start from one of the form templates.

The honest limitation: nDBForms is a form, not a help desk. It doesn’t thread replies or show customers a ticket portal, and its Free plan stops at 100 responses a month. If you answer hundreds of requests a week, use real support software. For internal requests, the IT support ticket post is the closer fit.

FAQ

Can customers fill out a Notion form without an account?

Yes. Share the form with Anyone on the web with link, and people who don’t use Notion can fill it out. Their responses are automatically anonymous.

Can customers check the status of their request in Notion?

Not on a public form. Access to submission only exists for workspace-only forms with anonymous responses off, so send status updates by email instead.

Should customers choose their own priority?

I wouldn’t let them. Ask who is affected and how soon they need a fix, then set priority yourself from those two answers.

Do I need a paid Notion plan for a support form?

No. Forms work on all Notion plans. Most database automations need a paid plan, though Free plan users can create Slack notification automations.

How do I get notified about a new support request?

Turn on the email copy of each submission under Form settings, then Submit screen. On paid plans, a Page added automation can also notify teammates.

Sources