An open letter to Hon. Dita Angara-Mathay, Secretary, Department of Tourism, Philippines
What DICT's eGov AI Launch Means for the National Tourism Data Layer — and What DOT Must Do Now
The Philippines' DICT launched AI assistant "Kuya A" inside the eGovPH Superapp for 40-60M users, already answering tourism queries with no connection to DOT's data or accreditation registry.
The Assistant Is Already Live
Photo by Pertlink Limited
TL;DR
-
On Monday, 21 September, DICT launched eGov AI inside the eGovPH Superapp — a presidentially-endorsed assistant, “Kuya A,” already live for roughly 40–60 million downloaded users, with “tourism information” explicitly listed among its features.
-
Unlike Klook or Newport World Resorts, this isn't a private partner DOT can bind by contract — it's a fellow government agency's own citizen-facing AI, already serving tourism queries to the country's largest single digital audience, with DOT named nowhere in the launch.
-
The scale changes the stakes. This is the single biggest live distribution channel for Philippine tourism information that exists today — larger than any OTA, larger than DOT's own reach — and it may be running on whatever DICT could assemble on its own.
-
DICT is already one of the five agencies named in this proposal's “From DOT” ask. This is the concrete, dated reason to open that conversation now, not wait for a working group to convene.
-
The President's own remarks at the launch — AI must be “anchored on accountability... and public service,” must “complement, not replace... judgment” — hand DOT a presidential mandate for exactly the standards role this proposal asks it to take.
Bottom line: Kuya A is already answering tourism questions for a plurality of the country. The only open question is whether it's answering them from DOT's truth, or from whatever DICT could find on its own.
What Actually Happened
On Monday, 21 September, the Department of Information and Communications Technology launched eGov AI at a ceremonial event at The Manila Hotel, with a message from President Marcos delivered by Cabinet Secretary Benhur Abalos. The centerpiece is “Kuya A,” a built-in AI assistant inside the eGovPH Superapp offering real-time guidance to help users navigate government services — document extraction, image identification, translation, form understanding, speech generation, electronic Know-Your-Customer identity verification, and, listed explicitly among its features, access to tourism information for local destinations.
The distribution base is not small. eGovPH had already passed 40 million downloads by March — meeting its full-year target months early — and DICT is targeting 60 million users by 2028, on a platform that already integrates over 1,000 government services and the national digital ID system. Kuya A is free for every verified user of that app, immediately.
DICT Secretary Henry Aguda framed the launch as treating AI “not simply as a technological innovation, but as a tool to make public services more responsive, accessible, and efficient.” President Marcos, in his message, cited a 2024 finding that only 14.9 percent of Philippine firms use AI tools at all, and called for the government to make emerging technology work for ordinary Filipinos — while insisting that any such technology be “anchored on accountability, security, and public service,” and that it “complement, not replace” human judgment.
Why This Beats Every Prior Signal in This Series
Every earlier update in this series has warned about the same pattern: AI without a governed data layer beneath it is a more articulate way of accessing fragmented information. Until now, that warning was aimed at private platforms DOT already has a commercial relationship with, or at planning processes still being
| Klook / Newport (Sept 1) | eGov AI / Kuya A (Sept 21) | |
| Who built it | Private platforms, via MOU with DOT | A fellow government agency, DICT — no MOU with DOT exists |
| Reach | Platform-specific user bases | 40–60 million eGovPH downloads — roughly 4 in 10 Filipinos |
| Endorsement | A DOT partnership announcement | The President's own message, delivered at a ceremonial launch |
| DOT's leverage | A contractual clause in a renewed MOU | None yet — no MOU, no mention, no named role |
| Fix | Add a schema clause to the next MOU cycle | Requires DOT to initiate the conversation itself, now |
This is the government's own flagship citizen-facing AI product, launched with the President's name on it, already answering tourism questions for a plurality of the country.
That is a materially harder thing to quietly fix later than a private app's content feed. A wrong answer from Kuya A about a fraudulent operator, a closed ferry crossing, or a fake DOT accreditation does not land on DICT's reputation in the public's mind — it lands on tourism's, and on the President's own AI initiative, in the same week it launched.
What's Missing
Nothing in the public launch material names DOT, references DOT's accreditation registry, or indicates that Kuya A's tourism answers draw from any single authoritative, current source rather than whatever DICT could compile or the model could retrieve on its own. There is no sign of a connection to the eleven-field schema — Where, What, When, Price, Availability, Travel Time, Accessibility, Payment, Booking, Safety, Disruption — that this proposal has argued should sit beneath every tourism-facing interface in the country, public or private.
That is precisely the gap this series has flagged in Klook, in Newport World Resorts, and in DOT's own statistical dashboard: a well-built, well-intentioned system answering tourism questions from whatever source was easiest to reach, not from a governed one. The difference here is scale and authorship. This is not a private partner DOT can bind through a contract clause at MOU renewal. It is a fellow government agency's own product, already live, with no existing agreement to amend.
What DOT Can and Must Do
-
Open direct technical talks with DICT now — DICT is already named in this proposal's five-agency mandate. That relationship, not a new introduction, is the fastest path to a conversation — and the eGov AI launch is the concrete, dated reason to have it this month, not once a working group convenes.
-
Offer the eleven-field schema as Kuya A's tourism source — rather than compete with eGovPH's reach, DOT should propose that Kuya A's tourism-information feature query DOT's governed schema directly — turning an existing 40–60-million-user distribution channel into the single largest interface the Data Layer could have on day one.
-
Use the Rizal–Corregidor–Mt. Samat circuit as the proof case — rather than proposing a national integration all at once, offer DICT a bounded, low-risk pilot: connect Kuya A to the same TIEZA-funded circuit data already planned as this proposal's first build, and expand from there.
-
Turn this into leverage for the PAIIM ask — a government agency's own AI assistant now answering tourism questions, unconnected to DOT, is a concrete illustration of exactly the governance gap DOT's Steering Committee seat is meant to close — worth citing directly in that request.
Benefits to the Country and Tourism
Connecting Kuya A to a DOT-governed source is not a defensive move. Done well, it is the single highest-leverage interface this proposal could secure — at effectively no distribution cost, since the audience and the app already exist.
| Beneficiary | The benefit, specifically |
| The country | Turns an already-committed ₱2.7 billion eGovPH investment into a tourism growth channel too, at zero incremental distribution cost to DOT |
| Tourism | Puts DOT-governed destination content in front of roughly 40–60 million citizens — far beyond what any single OTA, MOU partner, or DOT app could reach on its own |
| Domestic travel | Strengthens "Discover More to Love" by embedding accurate destination information inside an app millions already have open, rather than a separate download |
| Fraud prevention | Extends eGovPH's existing eKYC and identity-verification infrastructure to cover the same establishment-fraud problem DOT warned about on 3 September |
| The traveler | One trusted, government-verified source that already handles translation, documents and identity — tourism information arrives inside a workflow citizens already trust |
A Roadmap for Connecting Kuya A
This is deliberately narrower and faster than the Data Layer's own national roadmap — a bounded integration DOT can begin immediately, using the relationship and the pilot circuit that already exist.
| Phase | Timeline | What happens |
| 0 — Outreach | Weeks 1–2 | DOT initiates contact with DICT through the existing five-agency relationship; scopes a pilot connection for Kuya A's tourism-information feature |
| 1 — Schema Mapping | Weeks 3–6 | DOT's eleven-field schema mapped to Kuya A's existing intent categories — tourism information, translation, document verification |
| 2 — Pilot Connection | Weeks 7–14 | Kuya A's tourism responses for the Rizal Park–Corregidor–Mt. Samat circuit routed through DOT's schema via API, run alongside the circuit's own TIEZA-funded build |
| 3 — Validation | Weeks 15–18 | Accuracy, safety-flag correctness and disruption-alert timeliness measured against live conditions before wider release |
| 4 — National Expansion | Month 5 onward | Kuya A's tourism feature extended to full schema coverage nationwide, in step with the Data Layer's own Phase 4 rollout |
Two Worked Examples
What changes for an actual citizen asking Kuya A a tourism question, once it draws from DOT's schema rather than whatever it can find on its own?
The Verified Operator
| Today — Unconnected | With DOT's schema connected |
| A citizen in Cavite asks Kuya A whether a homestay listing in Corregidor is legitimate. Kuya A has no access to DOT's accreditation registry, so it either declines to answer or returns a generic web result — the same gap behind DOT's own 3 September fraud warning. | Kuya A cross-references the operator against DOT's Safety field in real time and confirms verified status — using the same eKYC infrastructure it already applies to government transactions, now extended to tourism fraud prevention. |
The Storm Warning
| Today — Unconnected | With DOT's schema connected |
| A traveler in Manila asks Kuya A if tomorrow's Corregidor ferry is running, with a weather advisory in effect. Kuya A has no live link to ferry schedules or disruption data for DOT destinations, so it gives an outdated or generic answer — or none at all. | Kuya A pulls the same real-time Disruption field any other connected interface would, and proactively warns the traveler before they leave home — the exact scenario this series has used to illustrate the schema's value since Part One. |
The Pertlink Bottom Line
Kuya A doesn't need DOT's permission to exist. It needs DOT's data to be right.
The President has already made the case DOT needs to make to every other agency: that AI in government must be accountable, secure, and anchored in public service, and must sharpen judgment rather than replace it. DOT does not need to win that argument — it has already been won, publicly, this week. What remains is the smaller, more practical step: making sure the tourism answers a plurality of the country is about to start asking a government AI assistant are the answers DOT actually stands behind.
Made with the help of various AI tools — but always with a HITL
Comments
Comments for this content
0 comments available