Voice notes, in Hinglish
The engineer talks the way they already talk. Pakka transcribes, matches it to the exact task, and asks for a one-tap confirm. Never auto-closed.
Photos, auto-tagged
Every photo is tagged by room and trade, with an action menu — mark a task, raise an issue, post to the client, OCR an expense, or attach to a GRN.
Video walkthroughs
Narrate a walkthrough; each item you mention becomes its own task-done, issue, approval or decision.
Bulk capture
A long, multi-item voice note becomes a set of review cards with a native ✏️ edit form — fix anything before it’s logged.
Command deck
Type a slash. Get an answer.
For the people who want them, exact commands — engineers rarely need more than a voice note.
/drawingAsk the drawings from site — answer arrives with the cropped region/issueRaise a blocker or problem, with a photo/orderRequest material/receiveGRN form at the gate/cashPetty cash with bill-photo OCR/milestoneMilestone status and moves/paymentsPayment eligibility and release (PM)/vendorVendor lookup and actions (PM)/budgetBudget and BOQ snapshot (PM)/quoteQuote status (designer/PM)/variationLog a variation → BOQ/reportPull a report/broadcastMessage a group (PM)/inboxWhat needs you/pendingOpen items/blockersEverything blocked/askThe org brain — query your own historyWhy WhatsApp
WhatsApp won the site. We didn’t fight it.
PM apps die because engineers won’t open them — tickets are office culture, sites are voice culture. Pakka is deliberately not a chatbot to learn; it’s a listener that structures what your team was going to say anyway. On day one, their behaviour is unchanged. That is the whole difference.