back_office_ops · finance · workflow

GCash uses Glean to save employees 2-3 hours a week and reach 90%+ adoption

Without a centralized intranet, GCash employees had to manually search across disconnected applications to find information, constantly interrupting their own and colleagues' workflows and harming organizational productivity.

How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Employee needs information
A worker needs information but previously had to interrupt colleagues or toggle across applications to find it.
Tools used
GleanGlean Agent Builder
Outcome

Glean saves GCash employees 2-3 hours per week, has achieved over 90% adoption in some departments, and enabled citizen developers to build personalized AI agents through Glean Agent Builder.

Results
Time saved2-3 hours a week
Volumeover 90%
Source

https://www.glean.com/resources/customer-stories/gcash

How we source this →

Grounding & classification
Source type: vendor customer story
20 fields verified against source quotes.
ai agententerprise searchknowledge searchknowledge basemetric backednamed customerproduction runtime claimedtools describedworkflow describedfinancial servicesemployee productivitytime savedvendor customer storyback office opscompliance monitoringagentic task executionrag answering