Frontline staff messaging
The last mile is reaching frontline staff where they already talk, with AI reading and structuring underneath.
Housekeepers, maintenance, and some managers do not live in dashboards. They live in group chats. For the operating layer to actually reach the frontline, it has to meet them on the channel they already use, with AI doing the reading and structuring beneath it.
The wall I hit
I assumed WhatsApp groups would be the interface. They cannot be. The official WhatsApp Cloud API gates group features to huge business accounts and will not let a bot join an existing staff group at all. The only way to read an existing group is unofficial linked-device automation, which violates the terms and risks a permanent number ban.
- Telegram's Bot API does exactly this, free and official, and is the fallback surface
- The pilot route is unofficial WhatsApp automation on a dedicated burner number, isolated on the automation host, treated as a throwaway experiment
- The consent layer is non-negotiable: disclosed AI as a party, a one-time written staff acknowledgment, no voice notes, and guests on a separate disclosed line
Knowing this boundary before building around it is the whole value of the research. It stops me from architecting the frontline interface on a platform that would wall me off mid-build. Read messages also get treated as untrusted input, because prompt injection is real once an agent is reading a group.
Planned, with the interface question still open. The frontline seat is the hardest one to fill with software, because it is the one where the humans and the agent have to share the same room. Getting the consent and the channel right comes before the cleverness.