We publish this sequence so nobody books an engagement audit expecting a same-week miracle or a software walkthrough. The dates flex when an export is late. The order does not.
Week 0 — the question we ask back
You write with the app name and a sense of volume. We ask for one sample row from the send log and one screenshot of an alert as a user would have seen it. If those two artefacts cannot be produced, we pause. Most delays in this work are not conceptual; they are files that never leave the vendor panel.
Week 1 — intake and the export checklist
A forty-minute call. Who presses send. Which languages. Whether quiet hours exist on paper or only in someone’s memory. We send a checklist: date, title or first line, audience or list name, iOS and Android counts if held separately, opt-out or permission events. You remain the controller of the customer list. We want rows, not access.
Week 2 — the log in send order
Daniel Tan lays the window in the order a lock screen would have received it. Festive days stay visible. We do not average Hari Raya into “the month.” If Android channels are a heap of screenshots, this week grows. You will hear about that before week 3, not in the final sitting.
Week 3 — copy beside the counts
Aisyah reads the same window as language: promise in the first line, time of day, stacking, English and Bahasa in the same afternoon. Margin notes go on a sample, not on every transactional receipt. If a language sits outside a fair reading, it is marked out of scope here.
Week 4 — the sender conversation
Often the most useful hour. The person who booked us is sometimes not the person who duplicated a Deepavali send at 15:00. We ask what they thought the count meant on the day. We do not run a workshop. We try to catch the moment a column was renamed as a feeling.
Findings sitting and the note
Up to ninety minutes, in Kuala Lumpur or on a call. Then the written note, with a chance to correct a misread fact. After that the work is closed. A later window is a new brief.
What you will not see
A shared login. A ranking against unnamed “peers.” A single percentage to paste into a board pack. If you need a number for a pack, we will help you quote a column honestly — delivered, opened, or permission lost — and we will refuse to blend them.
Frequently asked along this path
Can we start from Google sheets? Yes, if the columns are dated and the copy can be joined. A sheet that says “campaign 12 — 4.2%” with no send time is not a start.
Do you need the customer list? No. Identifiers can be hashed or omitted. We need event times and which alert they belong to.
What if the painful week is next Thursday? Book a cadence review for that week, not a full audit. An audit wants a window that has already happened.
When you are ready to hold a start week, write to the desk.