Forms, friction and personal data

You will be able to build a form that asks only for what you need and handles personal data correctly under the PDPA.

Mei Ling sells cakes, and in this invented example her order form once had twelve fields: name, email, phone, address, postal code, date of birth, how you heard about us, cake size, flavour, design notes, delivery date, and a newsletter tick box. She was trying to get to know her customers, while they only wanted to order a cake. Plenty of them opened it on their phone, saw the length of it, and messaged her on WhatsApp instead or never contacted her at all.

Whatever your page is asking someone to do, the form is the final step before they do it. It is also the point where you take in personal data, which comes with obligations under the law.

Deciding which fields to keep

Each field asks the visitor for effort: one more question to read and one more answer to type, usually with a thumb on a small screen. With every added field, a few more people drop out. You never see those people. All you notice is a lower number of finished forms than you might have had.

Keep only the fields you need for the next step. The test is what you must have in order to do what the visitor asked for. Things that could come in handy someday, or that would be nice for your records, do not pass. Begin by writing down the single thing the visitor wants from you, then list the fields that thing requires and no others. Anything left over can wait until the confirmation, wait until the customer has committed, or become optional.

Mei Ling's new form has name, phone number, delivery date, cake size, and a single box for design notes. The delivery address comes later, when she confirms the order, since she only needs it if she can take the booking. The question about how the customer heard about her now sits in the confirmation message, and answering it is optional.

Priya, another invented example, runs a tuition centre with free Saturday trial lessons for P5 and P6 children. Booking a trial takes four pieces of information: the parent's name, a phone number so she can confirm the slot, the child's level, and which Saturday they prefer. The child's school, the parent's email address and how they heard about the centre are not needed for a trial. If the family comes in and decides to stay, she can ask for those then.

What the PDPA asks of your form

How organisations in Singapore collect, use and disclose personal data is governed by the Personal Data Protection Act (PDPA). Two parts of it matter most for a form: consent and purpose. As a general rule, you need someone's consent before collecting their personal data. You have to explain why you want it and how it will be used and disclosed, and you should then use it only for those stated purposes.

On the form itself, this means a brief consent line in plain words beside the submit button, saying what the details are for. Make the words "privacy notice" in that line a link to a page that sets out the details and explains how people can contact you about their data.

Sending marketing, for example news about classes coming up, is a different purpose from providing the service someone requested. Get consent for it on its own, through a box the person ticks themselves. The box starts unticked, and it is never folded into agreeing to the booking.

Guides written for small businesses are on the website of the Personal Data Protection Commission (PDPC). Treat what you read here as a summary only. The details matter, so read the PDPC's current guidance as well.

Phone numbers and Do Not Call

Marketing calls and text messages to Singapore phone numbers fall under the PDPA's Do Not Call provisions. Broadly, people can add their number to a national register to opt out of marketing messages. Before a business sends such messages, it has duties to check that register or to hold the right kind of consent. There are specific conditions and exceptions, so read the PDPC's Do Not Call guidance before you send marketing to any number collected through your form. If you plan to use a messaging app for marketing, check the PDPC's current guidance on that first too.

Contacting a parent about the trial they booked is one kind of message, and sending them promotions afterwards is another. Keep the two apart on the form and in everything you send later.

Priya's form, once finished, has four fields: parent's name, mobile number, child's level (P5 or P6) and preferred Saturday slot. Its button reads "Book my free trial". Beneath the button is this line: "No payment needed. We'll use your details to confirm your trial and contact you about it. Privacy notice." A separate box, left unticked, says: "Send me news of upcoming classes by WhatsApp."

Telling people what happens after they submit

The moment a form goes through, the screen should tell the visitor what happens next and by when. If they see a blank page or just the word "Submitted", they cannot tell whether it worked, and some send the form a second time while others give up and leave.

Priya's thank-you screen says: "Thanks. We'll confirm your Saturday slot by WhatsApp within one working day. If you need to change it, just reply to that message." One working day is an example figure; promise a time you can actually meet.

After that, follow up with a confirmation sent through whichever channel you said you would use, so the visitor has something to keep. It should restate what they requested, explain the next step, and tell them how to change or cancel. A message to a parent could open with: "Thanks, Mrs Lim. We've got your request for a trial on Saturday. We'll confirm by WhatsApp within one working day." Finish it with a line telling her how to change or cancel the trial.

The easiest mistake while you build yours is holding on to a field because it might be useful later, like Mei Ling's date of birth question or Priya's question about the child's school. If you cannot name the step that needs a field, leave it for the confirmation or for after the customer has committed.

Build the form for your landing page with as few fields as you can. Add a consent line and write the confirmation message people will get.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).