The current top priority
K1 is the delivery path of the whole project: the sales team works where they already work. Each rep gets their own WhatsApp business number on the official Cloud API — not a shared bot persona, not a parallel app.
What it consumes and produces
K1 takes the rep business number, the rep’s identity, and customer/lead attributes, and produces the structures everything else builds on — the rep registry, human + agent teams, customer segments, and session lifecycle events.
Where it stands
The channel’s transport is live: the edge unit for WhatsApp egress, the bridge with commit-before-ack semantics, and sends gated on a human authorisation row. The 1:1 enquiry loop is measured end to end. Team formation and segmentation have a delivered design — the work of K1 now is turning that design into the product surface: managers viewing and assigning within their team, and segments defined on the right corpus.