Module 1 · Day 1 · AnyCompany Support Workshop

Introducing Generative AI — From AI to Foundation Models

The hierarchy, the building blocks, the AWS toolkit, and what GenAI can (and can't) do for GS Support teams across SEA

ARTIFICIAL INTELLIGENCE MACHINE LEARNING DEEP LEARNING GEN AI 🧠 📊 🔮
Generative AI
Create new content
The innermost, most specialised layer. Models like Claude and GrabGPT that generate text, code, and structured outputs. AnyCompany Support uses this for case context summaries, SOP-grounded answers, DSAT write-ups, and post-call notes.
Scope
Narrowest

💡 Click any ring to explore that layer

How The Layers Build On Each Other

Each layer adds a new capability on top of the one below. AnyCompany Support uses every level — pick the right layer for the job.

Generative AI
+ creates new content  2020s boom
Case summaries · SOP-grounded answers · DSAT write-ups · post-call notes
🔮
Deep Learning
+ discovers patterns from raw data  2010s+
Voice-to-text transcription (Project Echo) · sentiment detection · intent classification on chatbot turns
📊
Machine Learning
+ learns from labelled data  1980s+
Fraud / DUI scoring · DSAT prediction · forecast volume by interval (NICE IEX) · churn / re-contact prediction
🧠
Artificial Intelligence
Foundation: rule-based decisions  1950s+
Routing rules in ARC / IVR · SLA timers · escalation thresholds · the "if booking is > X minutes ago, route to IRT" logic
💡 Cohort takeaway: You don't need to choose one layer. The best Cyborg builds combine them — for example, ML scores an incoming case for likely DUI severity in milliseconds, then GenAI writes the case context summary explaining why the score is what it is, with the booking and history pulled in. Specialist-tier builders: this is the hybrid pattern Day 2 builds toward.

⚡ What Can Generative AI Do?

A practical menu of GenAI capabilities — illustrated through work GS Support teams already do today, every shift, across every market.

📝

Text generation

Drafts that read like a teammate wrote them — first-response emails, escalation Slack templates, DSAT root-cause write-ups, post-call notes.

📑

Summarization

40-turn THA chat transcript → 1-page case context. 20-min IRT call → 5-bullet timeline. ARC chatbot handover → structured brief for the agent.

💬

Q&A over your SOPs

"How do I handle a refund for a cancelled GrabFood order with partial delivery in MY?" — answered from the SOP / KB corpus, with citation. Anchored on your SOP Lookup Top Idea.

🏷️

Classification with reasoning

"This is a true Safety case (severity P1) because…" — auto-fill PAC tags + DSAT root cause + Safety severity, with rationale visible for QA.

🔄

Translation & localisation

Read a Vietnamese chat transcript, write the case summary in English. Localise an SOP step for KH/MM agents working in a 2nd language.

🧮

Code & SQL generation

"Write the SQL to pull this week's IRT cases by symptom_l1 from the datalake" — useful for the WFM / Reporting specialists in this room (4 of you).

🖼️

Image & multimodal

Read a screenshot a PAX sent, extract the booking ID, parse a receipt image. Multimodal models handle screenshots, photos, and chat captures the way agents actually receive them.

🎙️

Voice & transcription

Transcribe an outbound IRT call, extract action items, generate the post-call note (Project Steno / Project Echo territory). The agent reviews and approves.

📊 What this means in practice: The eight capabilities above are not separate products — they are modes of the same underlying model. The same Claude or GrabGPT that drafts a case summary will also classify a Safety case, summarise a 40-turn chat, and translate a Vietnamese transcript. One platform, many uses — which is why Module 2 on GS Support use cases (anchored on your cohort's Top 6) ties everything together.

🏗️ Foundation Models — The Building Blocks

Behind every GenAI application is a foundation model — a large pre-trained AI that's been fine-tuned for the task. Knowing the basics helps you choose wisely.

🧠

What is a foundation model?

A massive AI trained on huge volumes of text, code, images, and audio — that can be adapted to many downstream tasks without re-training from scratch.

🌐

Trained on broad data

Books, websites, papers, code repositories, transcripts. The model learns language patterns, world knowledge, and reasoning shortcuts from this corpus.

🎯

One model, many tasks

Same Claude can write a poem, summarize a 10-K, classify a vendor, and explain an audit finding. Generality is the breakthrough.

📊

Scale matters

Bigger models (Opus, Nova Premier) capture more nuance but cost more. Smaller models (Haiku, Nova Micro) are fast and cheap. Match model to task.

The four families you'll meet in this workshop

FamilyMakerStrengthsWhere it shines for finance
Claude (Opus / Sonnet / Haiku)AnthropicReasoning, instruction-following, safety, long contextThe default for Claude Cowork. Case summaries, SOP Q&A, DSAT write-ups, edge-case Safety reasoning.
Amazon Nova (Premier / Pro / Lite / Micro)AmazonCost-efficient at every tier; wide multimodal rangeCost-sensitive bulk workloads. PAC auto-tagging across 400k MIWI cases / month, ticket classification.
Llama (Meta)MetaOpen-weight, customizable, strong general-purposeSelf-hosted scenarios. Specialist-tier note: useful when you need to fine-tune on Grab-specific terminology.
Mistral / SEA-LION / othersVariousSpecialised strengths — multilingual, including SEA languagesSEA-language transcripts (THA / BHS / VNM / FIL) where general models struggle with native phrasing or short forms.
💡 Cohort takeaway: You don't pick the foundation model upfront. The use case picks it. Module 6 (Tokenization & Pricing) walks through the model-selection decision with cost-per-case math at GS volumes. For now: know that several families exist, that Bedrock makes them all available, that GrabGPT and Valet sit on top of these, and that the choice has real cost implications when you're running at 400k cases / month.

☁️ AWS Generative AI Services — The Toolkit

AWS provides a stack of services from the foundational model layer to ready-to-use applications. Here's the part that matters when you're scoping a Cyborg build with GTS / GSTF.

Amazon Bedrock

Amazon Bedrock

The unified API to access foundation models — Claude, Nova, Llama, Mistral, and others — without managing infrastructure. Where your Cyborg AI workloads run when GTS / GSTF productionise them.

Bedrock Guardrails

Bedrock Guardrails

The safety layer — redacts PAX / DAX / MEX PII, blocks prompt injection, filters off-topic responses, enforces grounding. Module 7 has the live demo.

Bedrock Knowledge Bases

Bedrock Knowledge Bases

Managed RAG — point Bedrock at your SOP / KB corpus, and it handles embeddings, vector store, retrieval. Module 9 covers the pattern (your SOP Lookup Top Idea sits here).

Bedrock AgentCore

Bedrock Agents & AgentCore

Build autonomous agents that orchestrate Skills, tools, and data. Day 2 territory — your Cowork agent productionised inside the Grab AWS account.

Amazon SageMaker

Amazon SageMaker

End-to-end ML platform — used by data-science teams building custom models (e.g., the AI Forecasting Module from your Top Ideas list). GTS / Eternals territory.

Amazon Quick

Amazon Quick

The new agentic AI workspace from AWS — connects to enterprise data (docs, dashboards, warehouses), answers questions, and takes action. Successor to Amazon Q Business; analogous to Glean + Valet for the AWS-native side.

Amazon Textract

Specialised AI services

Textract (receipt / screenshot extraction), Transcribe (call audio → text — Project Echo / Steno territory), Translate (SEA languages), Comprehend (NLP). Useful building blocks inside larger agents.

AWS Lambda

The integration layer (GTS / GSTF)

API Gateway, Lambda, Step Functions — what plumbs an agent into D365, the datalake, Slack, NICE IEX. Day 2's Plugins / MCP topic touches this. You don't build it — but you scope it.

What you actually need to know

LayerWho works at this layerWhat you do here
Application layer (Cowork, GrabGPT, Valet, Glean)You — GS Ops, Specialists, TQM, WFMUse the AI directly. Write prompts. Build Skills. This workshop's primary level. Where Cyborg apps live.
Model layer (Bedrock, Bedrock Guardrails)GSTF / GTS / Cyborg Specialist tierChoose models, configure guardrails, monitor cost & quality. The Cyborg builders in this room will dip into this.
Infrastructure layer (SageMaker, Lambda, Step Functions)GTS, Eternals, platform engineeringCustomise, deploy, integrate with D365 and the datalake. Not your job — but knowing it exists helps you scope and hand-off cleanly.
🎯 What's important for this workshop: You'll spend most of Day 1 and Day 2 at the application layer — Claude Cowork as the platform, with concepts that map directly to GrabGPT and Valet inside Grab's stack. Knowing the deeper layers exist (Bedrock, SageMaker) helps you have credible conversations with GTS / GSTF about where the workload runs, what data it touches, and how it integrates with D365 / datalake. You don't need to operate those layers — but you do need to scope and govern them.

⚠️ Three Challenges Every Cyborg Builder Should Know

Generative AI is powerful — and unevenly reliable. These are the three failure modes you'll see most often in GS workflows, and where the rest of the workshop addresses each.

🎭

Hallucination

The model invents plausible-sounding facts — a SOP step that doesn't exist, a refund threshold that's wrong for your market, a confidently invented booking ID. Always verify policy answers, amounts, and named entities against D365 / KB.

→ Module 7 · Governance & Trust covers verification techniques. Your SOP Lookup agent uses citation-required steering as the fix.
🔐

Privacy & data leakage

Real PAX / DAX / MEX names, phone numbers, booking IDs, and case content must never leak into public AI tools unprotected. Bedrock Guardrails enforces redaction; steering rules in Cowork enforce the rule per project.

→ Module 7 has the interactive Guardrails demo with PAX redaction examples
💸

Cost runaway

The same case-summary task can cost 1¢ or $1 depending on model choice and conversation length. At 400k MIWI cases / month, that's the difference between a fundable Cyborg pilot and a budget incident.

→ Module 6 · Tokenization & Pricing has the cost calculator at GS scale

🎓 Where this workshop takes you next

You've now seen the full GenAI landscape — the hierarchy, what it can do, the foundation models, the AWS toolkit, ML vs GenAI, and the three biggest risks. From here, the rest of Day 1 makes you fluent and Day 2 makes you operational.

Day 1 — get fluent
M2 use cases · M3–M5 how LLMs work · M6 pricing · M7 governance · M8 prompts · M9 RAG · Exercise
Day 2 — get operational
Workflow patterns · Cowork stack · Skills · Cheat sheet · Build first agent · Agent canvas

Traditional ML vs Generative AI

Both are valuable — the right choice depends on your task.

AspectTraditional MLGenerative AI
ArchitectureTask-specific models (XGBoost, Random Forest)Foundation models (Claude, GPT, Nova)
TrainingOne model per task, your dataPre-trained on massive data, adapted to your task
Best forStructured data, predictions, scoringText generation, summarization, reasoning
SpeedFast inference (milliseconds)Slower (seconds), more compute
CostLow per predictionHigher (token-based pricing)
GS exampleDUI / Safety scoring: flag a true Safety case in milliseconds when it landsCase narrative: generate the structured case context summary explaining the score for IRT
💡 Key insight for builders: You don't choose one or the other. The best Cyborg builds combine both — ML for fast, cheap scoring (is this a true Safety case? what's the severity?) and GenAI for rich, contextual output (write the case context summary). The Day 2 build pattern demonstrates this: SQL / scripts for the datalake pull + LLM for the narrative.