How it’s built
N°
N°003
Name
How it’s built
Client
Turbo Diesel Engine Parts
Year
2024–2026
Type
System architecture
Stack
Python web service, a session store, a relational database, Anthropic Claude, Twilio WhatsApp, one cloud server
Outcome
Seven parts on one monitored server; 27 checks on every message; 426 journeys tested; 12× throughput on the same load
About
The system is one web service on one server, split into seven parts that each do one job: the conversation, the assistant, enquiries and the catalogue, the hand-off to a person, quotes, messaging and privacy. A WhatsApp message arrives, is checked before anything answers it, and moves the customer along a mapped conversation. The assistant takes the enquiry down; it never quotes. A person decides and prices, and the quote goes back as a PDF on the same thread. Every route a customer can take is walked by a test before a customer walks it, the server is monitored with alerts, and changes reach it only through a versioned deploy.
The app is one web service on one server. Every WhatsApp message arrives through Conversation, which checks it, reads where the customer is and moves the conversation on. The slow part is queued: the Assistant asks Claude for the reply, and Messaging sends it back through WhatsApp. Part numbers go to Enquiries, which searches the catalogue and puts new requests on the price-request sheet. When a person is needed, Hand-off brings in a representative, who builds and sends a quote in Quotes. Privacy keeps the permanent record and the customer's rights over it, and a shared platform underneath holds settings, connections, the background worker and the nightly jobs.
Press play to walk through it, or tap a part on the map.
The friction today
What the design does
What your people get
Integrations
What the system connects to, and why. Each one is documented in a full API reference.
WhatsApp, through Twilio
Messages in, replies out, and a delivery report for every one, on the business’s own WhatsApp number.
Catalogue feed
A live parts feed the storefront reads, so the shop and the assistant work from the same prices and stock.
Price-request sheet
New enquiries land as rows on the sheet the team already works from, each under one reference number.
Voice
Speech in and out for the assistant and the team’s console: questions read aloud, answers spoken back.
Team console
Live feeds for the representatives’ dashboard: who is waiting, what was said, and each quote as it goes out.
Running it
What it costs and how it is kept safe, day to day.
About $6 a month
The whole system runs on one small server. The bill is for messages and the assistant’s words, not for idle machines.
One door in
Only one entrance faces the internet. The databases and the monitoring cannot be reached from outside at all.
Rebuilt from a file
The server is written down, not hand-configured, so it can be rebuilt quickly and exactly if it is ever lost.
Backed up, changed carefully
Nightly backups, and changes go live only through a tested, versioned release, never by hand on the server.
