Property administrators, service teams and residents who operate payments, requests and follow-up through WhatsApp.
CASE 07 · PRIVATE DEMO MULTI-TENANT OPERATIONS
PPH Bot
WhatsApp turned into an operating layer for residential property management.
PPH Bot combines conversations, receipt OCR, transcription, service requests, role-based permissions and multi-tenant administration. The case shows how an everyday interface can connect with controls and operational traceability.
PROJECT CARD / RECRUITER VIEW
The project's technical dossier.
I designed the product and its multi-tenant architecture, integrating the conversational channel, OCR, transcription, permissions, back office and traceability.
Backend, APIs, deployment, testing and controls.
- DEPLOYMENT
- Bot Orchestrator deployed on Oracle behind Nginx; /health returns HTTP 200.
- BACKEND / APIS
- Meta WhatsApp API, FastAPI OCR, PostgreSQL, Redis/BullMQ, worker and human escalation.
- ASYNC / DATA
- Queue for processing, sessions and persistence; queue_depth 0 in the observed health.
- RELIABILITY
- Webhook idempotency, OCR fallback and escalation traceability designed as explicit controls.
- SECURITY
- Fail-closed on missing webhook secrets; panel access not published because of its mutation capability.
- 01WhatsApp
- 02OCR + transcription
- 03Operational API
- 04Tenant + RBAC
- 05Admin panel
- Deployed backend
- Configured operational data
- Demonstrable deck
- OCR, service-request and admin workflows
- Separate conversation from authorization
- Isolate data by property
- Never turn an operational credential into a public demo password
- DEMO
- Coordinated private access
- SCREENSHOTS
- Commercial deck with a product walkthrough
- VIDEO
- Pending recording
- The deck is a product and commercial-proposal demonstration; it does not expose private administration data.
- Panel access is delivered privately because the available roles allow operational actions.
- The figures correspond to configured data; alone they do not equal active users or commercial adoption.
Open product deck
OPEN / REQUEST01 / PROBLEM
The conversation is simple; the operation behind it is not.
Payments, requests, residents, administrators and properties require identity, permissions, states and evidence. Solving only the chat would leave the critical work outside the system.
02 / DESIGN DECISION
A conversational front connected to a multi-tenant back office.
WhatsApp receives the interaction; OCR and transcription structure the inputs; access rules separate organizations and roles; the panel allows reviewing, resolving and auditing.
SYSTEM / END TO END
The product as an explicit flow.
Each phase has a distinct responsibility. That separation makes it possible to observe, test and fix the system without relying on intuition.
- 01CHAT
Receive
Capture the request as text, audio or image from the everyday channel.
- 02AI
Interpret
Transcribe, extract fields and classify intent with explicit controls.
- 03RBAC
Authorize
Apply tenant, identity and permissions before reading or modifying information.
- 04OPS
Resolve
Create or update the operational record and return an understandable state.
- 05TRACE
Audit
Preserve the history needed for administrative follow-up.
PROOF / WHAT IS ACTUALLY SHOWN
Evidence, not decoration.
The labels indicate whether the data was observed, comes from the artifact or belongs to the professional record of the case.
SCOPE / HONEST BOUNDARIES
What is demonstrated and what still needs validation.
A technical portfolio must also show where the available evidence ends.
- The deck is a product and commercial-proposal demonstration; it does not expose private administration data.
- Panel access is delivered privately because the available roles allow operational actions.
- The figures correspond to configured data; alone they do not equal active users or commercial adoption.
CASE 07 / PPH BOT