Khabar
4notify Pakistan · the Gazette
GUIDE · Public offices · service centres · citizen notices
Khabar No
KHB-PK-004
Date
2026-05-28
Status
In force
Category
Public services

Appointment and document-ready notices

Anyone who has queued at a service centre in Lahore or Karachi knows the cost of an unannounced wait. An office that runs its own appointment or case system can call the 4notify REST API to send a reminder, a document-ready alert or a change of time. 4notify has no link to NADRA, to identity cards or to any government database, and it does not verify who anyone is.

PushSMSEmail
Preamble

Notice. This Khabar is a guide for offices, service centres and their software suppliers. The office keeps its records and decides what to send. 4notify carries the message and reports delivery status. Please keep national identity card numbers out of message text.

Statutory framework
Electronic Transactions Ordinance, 2002

Background only: general legal recognition of electronic communication in Pakistan.

Prevention of Electronic Crimes Act, 2016

Background only: covers misuse of personal information. Send only what the recipient needs to see.

Right of Access to Information Act, 2017

Background only: concerns public bodies and information access. It sets no messaging duty that 4notify fulfils.

Implementation
01

REST API call from the office system

The office's own appointment or case system calls the 4notify REST API with a JWT token when something changes: booked, ready, rescheduled.

02

Keep identity data out of the message

Use a reference number the citizen already has, not an identity card number. Anyone who picks up the phone should learn nothing sensitive from the lock screen.

03

Pick the channel

SMS reaches every handset. Email suits longer instructions. Push works only inside the office's own mobile app, so use it for citizens who installed it.

04

Delivery status per message

Each notice shows its delivery status in the dashboard and API, so staff can tell whether a citizen was told before they come in.

Delivery envelope
json
POST /api/v1/sms
Authorization: Bearer <JWT>

{
  "to": "+923331234567",
  "text": "Service centre Lahore Township: your document, ref 4471-22, is ready. Collect by Friday 18:00."
}
Sample message
SMS

Service centre Lahore Township: your document, ref 4471-22, is ready. Collect by Friday 18:00. Bring this reference with you.

Compliance checklist
  • Office system calls the 4notify REST API
  • Messages carry a reference number, never an identity card number
  • Channel chosen per notice type: SMS, email or in-app push
  • Delivery status of every notice visible in the dashboard and API
The 4notify difference

One REST API for SMS, email and in-app push citizen notices, with delivery status per message.

Frequently asked questions
Does 4notify connect to NADRA or check identity cards?

No. 4notify has no connection to NADRA and does not verify identity. It sends the messages your own system asks it to send.

Can citizens reply to a notice?

SMS replies are read and sorted by fixed rules and are visible in the dashboard and API. STOP unsubscribes a person from marketing only. What your office does with other replies is up to your system.

Issued
4notify Operations Department
2026-05-28 · KHB-PK-004

Start free

14 days, no card. English-language support across the working week. Mughal arches and truck-art floral panels — but a strictly modern SLA.

Other entries in this issue