WeMakeDevs × AWS · First Commit

Support.
Redefined.

The support line that already knows what you bought.

Live demo How it works

The problem

When something breaks, you hunt for the model number, wait on hold, and explain it all three times — to a company that already has your purchase on file.

There's a better way, and it lives in WhatsApp.

Five things you
never do again.

🔍

Before

Hunt for model numbers

Aftercare

One message. It already knows what you own.

🏷️

Before

Register the warranty by hand

Aftercare

Registered at the point of sale. A WhatsApp confirmation, instantly.

💬

Before

Call centres and hold music

Aftercare

A reply on WhatsApp, not a place in a queue.

📖

Before

Generic copy-paste answers

Aftercare

Every step from your product's own manual. Section cited.

📋

Before

Explaining it three times

Aftercare

A pre-filled ticket. The human is already briefed.

Step 0 · The brand plugs in

One CSV.
Every brand, live.

One sales file. That's the whole setup.

1

Upload the sales file

The export your point of sale already makes.

sales_export.csv Uploaded
customerphoneproductserialpurchased
Priya Sharma +91 98765 ····· AquaSpin FC-700 Washing Machine WM-FC-78234 2025-06-05
Priya Sharma +91 98765 ····· AquaSpin FL-900 Front Loader WM-FL-90012 2026-01-18
Ravi Kumar +91 98123 ····· ArcticAir 1.5T Split AC AC-CB-78901 2024-11-12
Ananya Iyer +91 98450 ····· AquaSpin FC-700 Washing Machine WM-FC-79345 2025-08-20
Sameer Khan +91 99001 ····· ArcticAir 1.5T Split AC AC-CB-77102 2023-03-15

Try it: this checks a real file, row by row

2 Multi-brand stores only

Sorted into the right brand, automatically

Every product code files under its brand. One brand never sees another's customers.

  • AquaSpin FC-700 Washing MachineWM-FC-78234 AquaSpin
  • AquaSpin FL-900 Front LoaderWM-FL-90012 AquaSpin
  • ArcticAir 1.5T Split ACAC-CB-78901 ArcticAir
  • AquaSpin FC-700 Washing MachineWM-FC-79345 AquaSpin
  • ArcticAir 1.5T Split ACAC-CB-77102 ArcticAir
Aq AquaSpin 3 products · 2 customers
Ar ArcticAir 2 products · 2 customers
3

Connect the WhatsApp line

Point the support number at Aftercare. Every customer is known from the next message, and the brand gets a private dashboard.

AqAquaSpin
  • WhatsApp support lineConnected
  • Agent, grounded in AquaSpin's manualsReady
  • Dashboard, private to AquaSpinReady
ArArcticAir
  • WhatsApp support lineConnected
  • Agent, grounded in ArcticAir's manualsReady
  • Dashboard, private to ArcticAirReady

Steps 1–6 · The customer's side

Months later, something breaks.
One message is all it takes.

‹
Aq
AquaSpin Support
Usually replies instantly
01
Registration

Registered before
you leave the store.

Registered at the counter. A WhatsApp message with your warranty arrives. Nothing to fill in.

🏷️ QR sticker on your product
📱 WhatsApp warranty confirmation
0️⃣ Zero action required from you
02
Lookup

One message.
No triage.

One message. Aftercare knows who you are from your number and asks which product. No model numbers. No triage.

🔍 Identified by phone number
📦 All your products shown
⏱️ 0 minutes of triage
03
Manual

Real help from
the actual manual.

One real step from the product's own manual, with the section shown. No generic FAQ.

📖 Grounded in your product's manual
🎯 One specific, actionable step
🔗 Source section shown
04
Back & forth

It follows up.
It doesn't forget.

It waits for your reply. Fixed, and that's it. Not fixed, and you get the next step.

🔄 Adapts to your responses
💬 Full conversation memory
✅ Resolved with no ticket if possible
05
Human handoff

Not fixed?
A person takes over.

Two steps fail? Not in the manual? The same problem back? A person takes over. The ticket says what was tried, and why.

🔁 Two steps tried, still broken
📖 Not in the manual — no guessing
↩️ Same problem back after a fix
06
Safety

When it's serious,
people take over.

A burning smell skips the AI. The manual's own warning goes out and a technician is dispatched.

⚠️ Safety flag triggers instantly
📋 Pre-filled ticket, no re-explanation
👤 Human technician dispatched

Architecture

Five AWS tools. One job each.

The model only words a step. Code decides the rest.

  1. CustomerWhatsApp · simulated
  2. API Gatewayone front door
  3. Lambdaone function, 26 routes
  4. Four serviceseach does one thing
01

API Gateway + Lambda

Serves every page and API route.

Why
Stateless: a chat survives any restart.
Trade-off
Cold starts. A code change needs a rebuild.
checking…
02

Strands Agents

Words one manual step. Reads a vague reply.

Why
A small model on narrow jobs, timed by hooks.
Trade-off
Local model is slower, so rules do the rest.
checking…
03

OpenSearch

Finds the manual section. Spots repeat faults.

Why
Ranked search and time-window queries in one engine.
Trade-off
Heavier than a database. Keywords, not meaning.
checking…
04

Cedar

Decides who may view, reply, resolve.

Why
Rules as policy files. Each answer names its policy.
Trade-off
One more language to learn.
checking…
05

DynamoDB

One table: customers, chats, tickets, cases.

Why
Known access patterns. Fast, and an atomic ticket counter.
Trade-off
Queries are designed up front. Ad-hoc ones go to OpenSearch.
checking…

Never left to the model: safety, next step, two tries then a person, warranty dates, who sees what.

Runs locally, no account. Deploy path: Bedrock · OpenSearch Service · Verified Permissions · DynamoDB.

Now see it run.

Eight customers. Real replies. A person taking over. Recorded from the running tool.

Open live demo Back to the top