Before sending specified marketing messages to Singapore telephone numbers, teams need a campaign record that shows the DNC account used, the numbers checked, the channel-specific register status, and whether consent evidence was used instead of a DNC clearance.
Connect each campaign approval to the message classification, Singapore telephone-number scope, relevant DNC registers, result date and expiry, consent evidence where relied on, sender identity, suppression record, and accountable sender.
This page is a launch checklist for Singapore PDPA DNC marketing checks. It covers the records a campaign owner should keep before voice, text, or fax telemarketing goes live: DNC Registry account evidence, channel-specific register status, result validity, consent evidence, sender responsibility, and triggers for a new check.
1
Section 1
When a campaign needs a DNC marketing check
Start with the message, not the audience list label. Under PDPC guidance, a commercial marketing message to a is generally a when one purpose is to advertise, promote, or offer goods, services, land, an interest in land, a business opportunity, or an investment opportunity.
For each campaign, record whether the message will be sent by voice call, text channel, fax, or a data application that uses a . If the team is relying on instead of checking the DNC Registry, keep the consent evidence in the same launch record and make the approval say which sender, number, channel, and message category the consent covers. Check the PDPA's Eighth Schedule separately because a message within an exclusion is not a , while a mixed-purpose message remains specified if a non-excluded marketing purpose is also present.
Classify the message as specified, excluded from specified-message treatment, or blocked for legal review because the purpose is unclear.
Identify every sender: the brand, business unit, agency, call centre, or platform that sends, causes, or authorises the message.
Separate voice, text, and fax channels because the DNC Regulations define separate No Voice Call, No Text Message, and No Fax Message Registers.
Do not treat a request for telemarketing consent sent to a as outside DNC controls; PDPC guidance treats offers to send specified messages as specified messages.
Defines the No Voice Call, No Text Message, and No Fax Message Registers used for channel-specific DNC status checks.
No Fax Message Register, No Text Message Register or No Voice Call Register
2
Section 2
Account and sub-account evidence to keep
The DNC Registry business rules distinguish the main account from sub-accounts. A useful campaign file should show which main account was used, which sub-account or user submitted the check, and whether the checker was acting for its own organisation or on behalf of another organisation.
For agency, reseller, group-company, or outsourced call-centre launches, keep the on-behalf evidence with the DNC check output. The campaign owner should be able to show who authorised the marketing, who submitted the DNC check, and which organisation names were declared for on-behalf checking at the time of submission.
Record the main account holder, sub-account user, submission timestamp, campaign owner, and approving privacy or legal reviewer.
For Singapore-registered organisations, keep the Unique Entity Number (UEN) or account registration evidence used for DNC account administration; for overseas organisations, keep the company registration evidence used for the account.
For on-behalf checks, retain the downloaded On Behalf List or equivalent export with the campaign record.
Do not approve a vendor-sent campaign unless the record names both the business authorising the message and the vendor or call centre that will send it.
Supports keeping main-account and sub-account evidence because the DNC Registry account model allows one main account and sub-accounts for multiple users.
Each organisation/individual will only be allowed to apply for one main account.
Supports naming both business and vendor senders because PDPC guidance treats persons who send, cause, or authorise specified messages as responsible senders.
causes the message to be sent or the voice call to be made
3
Section 3
How to use DNC check results
The campaign approval should store the submitted list, rejected-number report, filtered-number output, summary, and any on-behalf export. The business rules say submitted telephone numbers are checked against all three DNC Registers, but the launch decision should still compare the campaign channel with the relevant register status: voice campaign to No Voice Call, SMS or MMS campaign to No Text Message, and fax campaign to No Fax Message.
Treat the 21-day period from receipt of the results as a validity window, not a general review cadence. A result supports telemarketing activity only while it remains valid and while the campaign facts still match the checked list, sender, channel, and message. If the period has lapsed and the organisation intends to continue telemarketing, perform another DNC check.
Accept only Singapore telephone numbers in the DNC submission format supported by the Registry and keep rejected-number reasons out of the approved send list.
For Small Number Lookup, retain the immediate result; for Bulk Filtering, retain the downloaded filtered numbers, summary, on-behalf list, and rejected numbers files.
Block channel sends where the relevant register status says the number is listed and no evidence covering that channel is being relied on.
Re-check only where supported by the operational facts: the 21-day result period has lapsed, the number list changed, rejected numbers were corrected and resubmitted, or the team no longer has the consent evidence it planned to rely on.
Supports channel-status review, the 21-day result-validity window, and re-checking after the window lapses because DNC submissions are checked against all three registers.
Results returned from the DNC Registry are valid for up to 21 days.
Recommended next step
Turn DNC checks into campaign launch evidence
Use Sorena to capture Singapore PDPA DNC account evidence, register results, consent proof, sender ownership, and re-check triggers before marketing campaigns go live.
If a campaign proceeds because the organisation has in evidential form, the campaign owner should retain the specific consent artefact rather than a generic CRM flag. PDPC guidance expects consent evidence to be accessible for later reference and, for electronic consent, to show the individual's choice, date and time, the relevant screen or form, and the clauses consented to.
The launch record should also show withdrawal handling. If consent is withdrawn, the organisation needs a record of the notice, its scope, the affected channel, the sender or agent instructed to stop, and the date when the stop action was completed. Later registration on a DNC Register does not itself withdraw already given to a particular sender.
Keep the consent text, positive action, number, channel, sender, timestamp, capture location, and terms that applied when consent was given.
For third-party sourced numbers, keep evidence that the user or subscriber gave for this sender to send specified messages to that , or perform the DNC check before sending.
For outsourced campaigns, require the vendor to return send logs, suppression results, withdrawal notices, and proof that agents stopped sending when instructed.
Do not rely on inaction, a broad marketing-purpose statement, or consent for the wrong telephone number as a substitute for DNC clearance.
Keep the separate PDPA basis for collecting and using telephone numbers; a DNC result only addresses the DNC sending rule.
For text and fax campaigns, verify that the message identifies the sender, gives working contact information, and explains how to opt out through the same medium. For voice campaigns, verify that calling line identity is not concealed.
Supports retaining reproducible consent evidence, rejecting inaction as consent, checking third-party source evidence, and treating later DNC registration separately from withdrawal given to a sender.
PDPC guidance supporting the duty to check, sender responsibility, specified-message analysis, and consent evidence requirements.
Supports the duty to check the DNC Register before sending specified messages unless clear and unambiguous consent in evidential form is available.
Supports naming both business and vendor senders because PDPC guidance treats persons who send, cause, or authorise specified messages as responsible senders.
Show 1 more
Supports retaining reproducible consent evidence, rejecting inaction as consent, checking third-party source evidence, and treating later DNC registration separately from withdrawal given to a sender.
"unless the person has obtained clear and unambiguous consent in evidential form"
More quoted passages
"causes the message to be sent or the voice call to be made"
Primary operational source for DNC Registry account creation, main and sub-account use, register checks, all-register output, and 21-day result validity.
Supports keeping main-account and sub-account evidence because the DNC Registry account model allows one main account and sub-accounts for multiple users.
Supports channel-status review, the 21-day result-validity window, and re-checking after the window lapses because DNC submissions are checked against all three registers.
"Results returned from the DNC Registry are valid for up to 21 days."
More quoted passages
"Each organisation/individual will only be allowed to apply for one main account."