Complete your Databricks User Groups profile!

Fill out a few details about yourself so the community can get to know you.

Where Governed AI Creates Value in Asia FSI: Customer Support, Regional Marketing, and Cost Control | From Artillery Fire Control to Governed Back-Office AI: An Asia FSI Transformation Blueprint| Re:Cap Hong Kong Databricks FSI Community Day

Hong Kong Databricks FSI group

Nov 28, 12:00 – 1:30 PM (HKT)

0 RSVPs

Data ArchitectureData Engineering

Login to RSVP

About this event

Re:Cap Hong Kong Databricks FSI Community Day

https://vertexmacro.com/events/databricks_community_day_2026/recap/21_databricks_agent_bricks_genie_ontology_cross_border_liquidity.html

https://vertexmacro.com/events/databricks_community_day_2026/recap/22_databricks_agent_bricks_genie_ontology_cross_border_liquidity.html

Topic 11:

Where Governed AI Creates Value in Asia FSI: Customer Support, Regional Marketing, and Cost Control

Focus:

Business and FSI-Focused

Speaker Background:

From military artillery to institutional-grade trading, the speaker delivers market-liquidity depth analysis to international trading desks. The speaker combines precision, decentralized execution, risk discipline, and practical market experience to distinguish where centralized AI governance creates measurable value and where it can obstruct front-office performance.

Description:

Many AI programs begin with a platform-first ambition: centralize all enterprise knowledge, connect every model, and place every employee under one governance framework. In Asia FSI, that strategy can fail when it ignores business culture. Trading desks protect Alpha, move quickly, and develop distinct methods. Their lightweight private Markdown files often encode assumptions, terminology, and tactics that should not be shared across desks. Forcing these materials into a global platform can reduce trust, slow experimentation, and create new confidentiality risks.

This session proposes a more credible business strategy: preserve decentralized front-office knowledge while concentrating enterprise AI investment in customer service and marketing, where shared controls, reusable content, consistent policies, and measurable volume create stronger returns. Unity Gateway becomes the runtime control plane for approved models, agents, and tools. Unity Catalog supplies permissions and policy enforcement for the data behind each interaction. The result is not governance for its own sake, but a portfolio operating model that applies centralization only where it improves economics and risk control.

The first use case is multinational and outsourced customer support. A financial institution may serve Hong Kong, Singapore, Taiwan, Japan, South Korea, and ASEAN markets through internal teams and third-party call centers. Agents require customer context and historical product information, but contractors should not receive raw payment-card data, national identifiers, or unrestricted account history. Unity Catalog ABAC can apply policies according to sensitivity, country, legal entity, and user attributes. Row filters restrict which customers a team can access. Column masks redact protected fields at query time, reducing the chance that PII enters prompts or model responses.

The session demonstrates a historical-policy dispute. A customer contacts support in November and claims that a product purchased in May carried an unconditional-refund right. The current FAQ has changed, creating a risk that an AI assistant answers with today's terms. A Time Travel query retrieves the policy snapshot effective on the transaction date. In-database vector comparison locates the most relevant clauses, and the agent prepares a version-aware response with evidence for the service representative. This can reduce manual archive searches, inconsistent answers, complaint handling time, and avoidable remediation.

The second use case is regional marketing. Taiwan and Japan teams share common infrastructure but compete for budgets and operate under different consent, localization, and data-use requirements. ABAC and row filters isolate market-level sales and customer records without maintaining separate copies of the global database. Column masks suppress identifiers. SQL cosine similarity and L2 distance can compare approved customer-feature vectors inside the governed SQL environment to produce candidate lookalike audiences. Campaign copy remains subject to consent rules, suitability checks, brand review, and human approval.

Audience Takeaways:

Attendees gain an Asia FSI value case, customer-support and regional-marketing use patterns, departmental AI budgeting model, measurable KPI framework, phased rollout plan, and a pragmatic governance principle: centralize shared customer-facing controls while preserving justified front-office autonomy.

Topic 12:

From Artillery Fire Control to Governed Back-Office AI: An Asia FSI Transformation Blueprint

Focus:

Transformation Story and Technical Blueprint

Speaker Background:

From military artillery to institutional-grade trading, the speaker provides market-liquidity depth analysis to international trading desks. The speaker translates fire-control principles, including authorization, verified inputs, controlled range, ammunition accounting, coordination, and after-action evidence, into a practical blueprint for governed AI across Asia FSI operations.

Description:

Artillery operations depend on disciplined control. A mission requires authorized targets, verified coordinates, defined range, ammunition accounting, communication procedures, safety boundaries, and evidence of execution. Enterprise AI has a similar problem at digital scale. Hundreds of agents can send thousands of model requests, consume unbounded tokens, retrieve sensitive records, invoke tools, and generate customer-facing decisions. Without clear control, speed becomes operational, privacy, conduct, and financial risk.

This session tells the transformation story of moving from broad AI ambition to a selective Asia FSI operating model. The first lesson comes from institutional trading: decentralization is not always a defect. Trading desks deliberately maintain separate Markdown knowledge bases because strategies, time horizons, vocabulary, and Alpha differ. A global platform that forces those files into one shared repository can undermine confidentiality and adoption. The transformation therefore begins by classifying knowledge into desk-private, restricted shared, regulated customer, and enterprise-public domains.

Desk-private research remains owned by each trading desk. No cross-desk indexing occurs by default. Access is explicit, and private Markdown content is not used to train, evaluate, or enrich another desk's agent. The enterprise platform focuses first on customer support and marketing, where duplicated models, shared policies, outsourcing, regional data boundaries, and recurring content create a clearer need for common governance.

The target blueprint has six layers. The service layer contains approved customer-support and marketing applications. The agent layer contains bounded agents with named owners, allowed tools, maximum autonomy, and human-escalation rules. Unity Gateway routes model and tool traffic, enforces access and service policies, applies rate limits and budgets, and records usage. Unity Catalog governs tables, functions, models, and other securable assets. The data layer stores customer records, consent, FAQs, manuals, campaigns, policy versions, and embeddings. The evidence layer preserves prompts, retrieved context, model and policy versions, approvals, costs, and outcomes subject to retention and privacy rules.

A multinational customer-support scenario demonstrates the blueprint. An outsourced Southeast Asian call center receives a case from a Taiwan customer. Identity and entitlement are checked before retrieval. ABAC evaluates governed tags and user attributes. Row filters expose only the permitted region and service scope. Column masks hide card, identity, and account fields that are unnecessary for the task. The agent retrieves FAQ and manual passages using SQL vector_cosine_similarity for semantic closeness or vector_l2_distance for Euclidean distance, keeping the comparison inside governed SQL for appropriately sized datasets.

The case then becomes a historical-policy dispute. The purchase date identifies the correct policy-effective period. Time Travel reconstructs the applicable FAQ and terms. Retrieval runs against the corresponding historical content and vector data. The generated response cites the historical version and explains any difference from current policy. A human approves material remedies or compensation. The full chain is reproducible for complaint review, internal audit, legal inquiry, or regulator engagement.

A regional-marketing scenario follows. Taiwan and Japan teams query one global sales environment but receive different rows through policy enforcement. Direct identifiers remain masked. Approved customer features are converted to vectors, and in-database distance functions identify potential lookalike segments without exporting the underlying customer table to a separate Python workflow. The campaign-generation agent receives only permitted aggregates or pseudonymized attributes. Consent, suppression lists, suitability, localization, and brand checks run before activation.

Audience Takeaways:

Participants receive a transformation narrative, six-layer architecture, knowledge-classification model, historical-policy retrieval pattern, in-database vector design, regional isolation controls, token-accounting framework, phased Asia rollout, and production-readiness checklist that balances trading-desk autonomy with governed customer-facing AI.

Hong Kong Databricks FSI Community Day Event Page:

https://vertexmacro.com/events/databricks_community_day_2026/index.html

Presentation(s)

Facilitators

  • Kenny Chan

    Frontier Capital

    Macro Trader

  • Y.C Law

    Investor Group

    Financial Officer ASZEN

  • D Martin

    Financial Group

    Tech Lead

  • Andy Zhang

    AWS

    User Group Leader, Guangzhou

  • Alana Lam

    Frontier Capital

    Senior Asset Manager

Hosts

  • Kenny Chan

    Frontier Capital

    Macro Trader

  • Andy Zhang

    AWS

    User Group Leader, Guangzhou

  • Y.C Law

    Investor Group

    Financial Officer ASZEN

  • Alana Lam

    Frontier Capital

    Senior Asset Manager

  • D Martin

    Financial Group

    Tech Lead

Partners

AWS community builder logo

AWS community builder

AWS FSI Customer Acceleration Group logo

AWS FSI Customer Acceleration Group

DataBricks logo

DataBricks

Databricks for Financial Services logo

Databricks for Financial Services

DataBricks User Groups logo

DataBricks User Groups

Frontier Capital logo

Frontier Capital

MongoDB logo

MongoDB

MongoDB Creators Program logo

MongoDB Creators Program

MongoDB for Financial Services logo

MongoDB for Financial Services

Organizers

  • Dan C

    Tech for Trading

    Dev

  • Kenny Chan

    Frontier Capital

    Macro Trader

Contact Us