This is the piece of work Utility Gardenhub is built around. It is for product leads, CRM editors, and operations managers who already send push notifications and already collect counts — and who no longer trust the single percentage that appears on a monthly slide.

Who it is for

You have at least one live app, a history of sends (promotional, transactional, or both), and some record of delivery, opens, dismissals, or permission changes. You may send in English, Bahasa Malaysia, Chinese, or a mix. You may already suspect a festive campaign, a payday reminder, or a quiet-hours experiment. You do not need a new counting system from us; you need someone to read the one you have.

The result

You receive a written findings note, a short copy sample with margin comments, and a sitting (in person in Kuala Lumpur or on a call) in which we walk the numbers in the order they actually happened. The note names what the counts can support and what they cannot. It does not invent a score out of 100.

Scope

Included:

  • A sample of send logs covering an agreed window, usually four to eight weeks, with festive or sale periods kept visible rather than averaged away
  • A reading of iOS and Android columns as separate stories when the exports allow it
  • A pass over notification copy for the same window: subject of the alert, time of send, interruption or channel
  • Opt-out or permission-withdrawal clusters, mapped to the days that produced them
  • One findings sitting of up to ninety minutes
  • A revision of the written note if a fact in the log was misread

Excluded:

  • Writing a new notification programme from a blank page (that is a separate commission, and we will say so)
  • Building or configuring any counting software
  • Access to your production systems; we work from exports you control
  • Legal advice on permission language under the PDPA

Provider

Nur Aisyah Hassan leads the audit. Daniel Tan prepares the count tables. Both sit at the Kuala Lumpur desk. If a language in the copy sample is outside our reading (for example Tamil body copy we cannot fairly judge), we say so in the intake and leave that strand out rather than guess.

How the work proceeds

Intake call. Export checklist. Log and copy sample. A conversation with whoever actually presses send — often not the person who booked us. Draft note. Findings sitting. Final note.

The same sequence is described at length on How a review runs.

Duration and place

Three to four weeks is typical once a usable export arrives. Messy Android channel files add time; we flag that in week one rather than surprise you at the end. Work can be entirely remote. If your senders are in the Klang Valley, the findings sitting can be at Office 12, 31 Example Road, Kuala Lumpur 00000.

What you prepare

A date-stamped export of sends, the matching copy (screenshots are acceptable when the admin panel will not print), and a plain explanation of which events you currently treat as “engagement.” If quiet hours or frequency caps exist, send those rules too. We do not need passwords.

Constraints

We will not compress four messy weeks into a single headline number. If two operating systems disagree about what “opened” means, the note keeps the disagreement. If the sample is too thin — a brand-new app with nine sends — we will recommend waiting or shrinking the brief to a cadence review.

Fee

Quoted from RM 4,800 for a single app with two send channels and a modest window. Extra apps, extra languages that need a fair reading, and archives older than three months are priced in the quote. A thirty percent booking amount holds the start week. See Fees.

Questions we hear before a booking

Do you need a seat in our send panel? No. Exports and screenshots. If a vendor insists that “the only way” is a shared login, that is a vendor problem, not a requirement of this audit.

Will you tell us what to send next Thursday? Only insofar as the sample already shows a stacking or timing problem. A new calendar from a blank page is outside this flagship brief.

Can finance sit in? Yes. They often ask the only useful question in the room: which column are we actually quoting.

Next step

Write to the desk with the app name, a sense of weekly send volume, and a week you could start. We reply within two working days with a yes, a no, or a request for a sample row from the log.