Shared WhatsApp team inbox
Every conversation to your business number arrives in one place. Your staff see the same threads, the same history and the same customer, instead of forwarding screenshots to each other.
Features
Software companies usually describe a roadmap as though it had already shipped. We would rather you knew exactly what you are buying, so every capability below carries its real status.
Available — built and working today In development — being built now Planned — on the roadmap, not started
You can use all of this from the first day of your account.
Every conversation to your business number arrives in one place. Your staff see the same threads, the same history and the same customer, instead of forwarding screenshots to each other.
Each person signs in with their own email and password. Invite a colleague and they set their own password from a single-use link, so nobody shares credentials.
Four roles. An owner runs the business, a manager runs the team, an agent answers messages, and a read-only account can watch without replying. The server enforces this on every request, not just in the interface.
Take a conversation so your colleagues can see it is handled, and hand it back to the queue when you are finished. The assignment and the person's name stay on the thread.
Leave a note on a conversation that the customer never sees, so the next person has the context without asking.
Your business name and brand colour on the inbox your staff use. They see your company, not ours.
Each business's conversations are reachable only by that business. This is enforced in the data layer and tested by deliberately attempting to cross it.
Partly built. Do not choose K3Bot today on the strength of these alone.
WhatsApp only allows free-form replies for 24 hours after a customer writes. After that you need a Meta-approved template. Sending templates works; the screen for managing and choosing them does not yet.
Phone number, previous conversations and notes gathered beside the thread. The conversation history is there; a proper contact record is not.
Response times, volumes and per-person activity. The reporting engine is built and running, but it currently answers to our support team rather than to you. The customer-facing screen is the missing piece.
A business can hold more than one number and messages route to the right inbox. What is missing is the screen for you to add and label them yourself.
Running the inbox inside your own product under your own brand. The embedding and credential layer exists; it is not yet something you can switch on without us.
On the roadmap and honestly not started. Listed so you can tell us which matter most.
Opening-hours messages, away replies and simple routing rules you configure yourself.
Connecting your WhatsApp Business account yourself through Meta's onboarding. Today we do this step with you.
A documented API with self-service keys, so your own software can read and send through K3Bot.
Creating an account and paying online without talking to us.
A short demonstration, with the unfinished parts pointed out rather than skipped over.