Most Singapore service firms running Meta lead ads have the same gap. The form collects a name and mobile number but says nothing clear about consent. Then, weeks later, someone on the team sends a promo to that number by WhatsApp or SMS without checking whether it is on the Do Not Call Registry.
A pdpa meta lead form fixes the first half of that problem. A simple consent record in your CRM and a short set of follow-up rules fix the second half. This post walks you through all three, with steps you can finish this week.
One note before we start: we are a marketing agency, not a law firm. Everything below is how we set up campaigns for clients. Read the PDPC’s own guidance, and ask your lawyer about anything specific to your business.
Where the consent gap usually opens
From what we see when we audit accounts, the problem rarely comes from bad intent. It comes from two habits.
The first habit is launching an Instant Form with only Meta’s defaults: prefilled name, phone and email, plus a link to a privacy policy. Nothing on the form tells the person what you will contact them about or how. Nothing lets them say yes or no to marketing.
The second habit is treating every lead as a permanent contact. Say a homeowner asks for an aircon servicing quote in March, never books, and gets a “festive promo” WhatsApp blast in December. They asked about one job, once. That later message is marketing, and it is the kind of message where Do Not Call Registry marketing rules come into play.
Both habits are easy to fix. The fix is mostly wording, one or two extra fields, and a rule your team actually follows.
What your form has to tell someone before they tap Submit
Facebook lead ads consent in Singapore comes down to the person knowing three things before they hand over their number:
- Who is collecting it. Use your registered business name, not just your Facebook Page name if they differ.
- Why. “To reply to your request for a quote” is a different purpose from “to send you offers and updates.”
- How you will contact them. Phone call, WhatsApp, SMS, email. Name them.
The reply to their own request is the main reason they filled in the form, so say it plainly. Marketing is a separate, optional purpose, so ask for it separately. If marketing consent is a condition of getting a quote, the form is asking for more than the job needs.
Keep the form lean too. Do not ask for NRIC numbers. The PDPC has advisory guidelines that restrict collecting them, and a quote for a cleaning job or a renovation does not need one.
How to build a PDPA Meta lead form in seven steps
This is the core of the work. Each step is something you or your web person can do in an afternoon.
-
Write your purpose sentence. One line, at the top of the form’s intro section: “[Business name] will use your details to contact you about your request for [service].” Keep it to what you will actually do.
-
Add your privacy policy link and check it works. Meta requires a privacy policy link on every Instant Form. Open it on your phone. It should load fast, name your business, explain how you use contact details, and tell people how to withdraw consent or ask for their data. It should also name a contact for your Data Protection Officer, since the PDPA expects organizations to designate one.
-
Turn on a custom disclaimer with separate checkboxes. Instant Forms let you add a custom disclaimer with checkboxes. Use two:
- Checkbox A (required): “I agree to be contacted by phone, WhatsApp or SMS about this request.”
- Checkbox B (optional): “I’d also like to receive offers and updates from [business name] by WhatsApp and SMS. I can opt out anytime.”
Leave both unticked by default. If your form editor will not let you make one optional, use a custom multiple-choice question for marketing consent instead, with “Yes” and “No” answers.
-
Ask one qualifying question that sets expectations. For example: “When would you like us to contact you?” with options like “Today”, “This week” and “Just researching.” It improves lead quality, and it gives you a clear record of what the person asked for.
-
Use the thank-you screen to confirm the channel. Write something like “Thanks. We’ll WhatsApp you from our business number within the working day.” Now the first message they get is one they expected.
-
Test the form end to end. Use Meta’s lead ads testing tool, or submit a test lead yourself, and check that the consent answers come through to wherever your leads go. If your CRM shows the name and phone but drops the checkbox answers, the form is not doing its job.
-
Save a copy of the form wording with a version label. Screenshot the live form or paste the text into a shared document, labeled something like “Aircon form v2, live from 18 Nov.” When someone later asks what a lead agreed to, you can show them the exact wording.
Storing consent with the lead in your CRM
Consent you cannot find later is close to useless. The DNC rules talk about clear and unambiguous consent kept in a form you can refer back to. A checkbox answer that sits in a CSV on someone’s laptop does not meet that bar.
Here is the minimum we set up for every lead that lands in a client’s CRM:
The fields
- Contact consent: yes or no, with the source (for example “Meta Instant Form”).
- Marketing consent: yes, no, or not asked.
- Consent date and time: taken from the lead’s submission time, not the day someone imported it.
- Form version: the label from step 7.
- Campaign and ad: so you know which offer they responded to.
- Opt-out date: blank until they ask to stop.
Getting the data there automatically
Downloading leads by hand from Meta and pasting them into a spreadsheet is where consent answers get lost. Connect the form directly to your CRM, either through Meta’s native CRM integrations or a connector tool, and map every consent question to its own field. Do not leave the answers buried in a notes box.
Once leads flow into the CRM cleanly, you can do more than stay compliant. You can mark which leads became paying jobs and send that back to Meta, so your ads learn to find more people like your real customers. That is what we set up with offline conversion tracking from your CRM back to Meta, and the consent fields ride along with it.
Rules for WhatsApp and SMS follow-up
Most Singapore customers expect a reply on WhatsApp, so that is where the risk sits. PDPA WhatsApp follow-up is not a separate legal category in your team’s day-to-day work. Treat a marketing message on WhatsApp the same way you treat a marketing SMS. The PDPC’s guidance on the DNC provisions covers messages sent to Singapore numbers, so check it rather than assume an app is exempt.
Print these rules and pin them where your sales team works.
Rule 1: Reply to the request, freely
If someone asks for a quote, call or WhatsApp them about that quote. Send the quote, confirm the appointment, chase the missing photo of the job site. This is the conversation they started.
Rule 2: Marketing needs consent and a DNC check
Anything beyond their request counts as marketing. That includes a promo, a new service or a seasonal offer. Send it only if both of these are true:
- the lead’s marketing consent is recorded as “yes” in your CRM and there is no opt-out date, and
- you have checked the number against the DNC Registry and the result is still valid under the PDPC’s rules on how long a check lasts.
You can skip the DNC check only where the person has given clear and unambiguous consent under the DNC rules, kept in a form you can refer back to. Check the PDPC guidance on what qualifies before you rely on it.
A lead who answered “No” to marketing must never get marketing messages, whatever the DNC result says. The same goes for leads marked “not asked.” A clear DNC check only covers the DNC rules. It does not give you permission to use details collected for a quote request for a new marketing purpose.
Rule 3: Every marketing message carries an opt-out
End marketing messages with a simple line such as “Reply STOP to opt out.” When someone replies, fill in the opt-out date in the CRM the same day. One person owns this job, not “whoever sees it.”
Rule 4: No personal phones for marketing
Marketing messages go from a business number only, ideally through WhatsApp Business or a shared inbox tied to the CRM. Personal phones are where opt-outs vanish and old leads get blasted.
Rule 5: Track what follow-up earns
When a follow-up message includes a link to your booking page, tag it with our free UTM link builder. You will see which messages lead to bookings and which only annoy people, and you can cut the second kind.
Frequently asked questions
Does the privacy policy link Meta requires count as consent? No. The link tells people how you handle data, but nobody has agreed to anything just because a link exists. Use the custom disclaimer checkboxes or a clear question so the person actively says yes.
Can I make the marketing checkbox required so every lead opts in? We advise against it. If someone only wants a quote, forcing them to accept promos to get one blurs the line between replying and marketing. It also puts off good leads. Keep contact consent required and marketing consent optional.
A lead ticked “no” to marketing but booked a job. Can I send them offers now? Being a customer can change what is allowed, and the DNC rules have specific provisions for ongoing relationships with customers. Those provisions have conditions, so check the PDPC guidance or ask your lawyer before you rely on them. The simple route is to ask for marketing consent again at the booking or invoice stage and record the answer.
We have old leads from forms with no consent wording. What do we do with them? Keep replying to anyone whose original request is still open. Leave every old lead with no recorded marketing consent out of your marketing campaigns. A clear DNC check does not change that, because it does not give you consent to use details collected for a quote request for marketing. Do not message the whole list at once to “ask for consent”, because that message can itself count as marketing. The safer way is to ask when the person next contacts you or books, for example with a consent question at booking or on the invoice, and record the answer in your CRM. Check your approach with a lawyer before you start.
Do these rules apply if my agency or freelancer sends the messages? Yes. Your business stays responsible for messages sent on its behalf, and the agency or freelancer can be liable too. Make sure whoever sends them works from the same CRM fields and opt-out list, and put this in your agreement with them.
Your next step
This week, open your live Meta lead form and add the two consent checkboxes from step 3, then submit a test lead and confirm both answers land in their own fields in your CRM. If the answers do not come through, or you want leads, consent and booked jobs all flowing back to Meta, Chat with us on WhatsApp and we will help you set it up.