In a chat-first market, the funnel opens inside the messaging app, not the inbox
Vietnam is a useful stand-in for the wider pattern: Zalo alone reaches 98% penetration and carries an enormous volume of daily chat traffic. Facebook reaches 96.5% of the population aged 13 and up, and Messenger reaches as much as 78.1% of adults, ranking second globally in internet-user penetration. WhatsApp — the channel most Western DTC playbooks default to — sits at just 7% usage in Vietnam, well behind even Instagram's 12%.
That ordering matters for anyone importing an owned-audience strategy built for a different market. The tool most DTC teams reach for first is the smallest channel in the room here, while the channel with the widest reach by far is one most Western playbooks don't mention at all. A brand that builds its owned-audience plan around the wrong default channel isn't just less efficient — it's building around a channel most of the actual audience never opens.
'Owned' means the record is yours, not the conversation window
Every chat platform gives a business a temporary, conditional way to reach a contact, not a permanent one. Zalo's OA messaging window runs 48 hours, with eight free messages inside it before per-message charges apply. Messenger's free window runs 24 hours and resets with every new customer message. Neither of those is an asset — it's a permission that closes on its own, and a business that treats the open window as its 'list' loses reach the moment the customer goes quiet.
An owned record is what survives the window closing: the contact's identity, which channel reaches them, and their consent to be contacted again — stored somewhere the business controls, independent of whether any single conversation happens to be open right now.
This is where most DTC platform features stop short. A messaging window, a follower count, a broadcast list scoped to recently active contacts — these are all views into an audience the platform still holds the terms on, not a record the brand can query, segment or export on its own.
How the record gets built without anyone exporting a spreadsheet
The record has to form itself at the moment of the conversation, across whichever channel the customer actually used — not get assembled later from a batch export. A system built for this captures the contact and their consent the moment a Zalo, Messenger, WhatsApp or Instagram conversation turns into an order or a saved lead, then keeps attaching to that same record on every return visit, regardless of which channel they come back through.
That's also why a single customer-service inbox across channels matters here, not just as a convenience — six channels landing in one place means the record-building step happens once per customer, not once per platform the business happens to be active on.
- Capture identity and consent at the moment a conversation converts, not in a later export
- Attach every return conversation to the same record regardless of which channel it comes through
- Keep the record independent of any single platform's messaging window or app permission
Without the record, every win-back message is renting attention it doesn't own
Zalo's OA broadcast tool caps outreach at four messages a month and one a day, and it only reaches contacts who were active in the last 30 days — a hard, platform-set limit, not a design choice a business can adjust. A contact who's gone quiet for longer simply falls outside that reach, and a business with no independent record of that contact has no way back to them at all.
A business with an owned record still has a way in: the contact's identity and consent exist outside the platform's 30-day window, so a win-back attempt can route through whichever channel is still live, instead of depending on a broadcast tool that already stopped counting that contact as reachable.
This is the practical cost of skipping the record: it isn't a missed marketing opportunity, it's a customer the business paid to acquire once and now has no channel left to reach at all, because the only 'list' it ever had was the platform's own definition of who still counted as active.

