Ninjo Operator is a dedicated Slack channel per client where Ninjo acts as a real-time sales and operations co-pilot. The operator (human) and Ninjo work in the same channel to manage leads, analyze conversations, iterate on agents, and coordinate commercial actions with speed.
Launched ~2 weeks ago (first activity: Feb 10, 2026; full rollout: week of March 3, 2026), the product went from 2 users in W09 to 38 active users in W11 β 19Γ growth in three weeks.
With 32 channels deployed, 370 sessions, 4,474 messages and 41 unique users, the system is already running in production with external clients in 11 active channels, validating the real-time co-pilot model.
The 78% re-engagement rate and 78 deep sessions (>15 msgs) demonstrate that users aren't just trying the channel β they're using it for real work, habitually and with increasing intensity.
| Metric | Value |
|---|---|
| Channels created | 32 |
| Channels with external (client) activity | 11 |
| Silent channels | 0 |
| Total messages (30 days) | 4,474 |
| Total sessions | 370 |
| Total unique users | 41 |
| Avg. active days / week | 4.7 of 7 |
| Week | Unique Users | Change |
|---|---|---|
| W09 (Feb 24β28) | 2 | β |
| W10 (Mar 3β7) | 18 | +800% |
| W11 (Mar 8β12) | 38 | +111% |
| Week | Messages | Sessions | Ξ Msgs | Ξ Sessions |
|---|---|---|---|---|
| W09 | 93 | 12 | β | β |
| W10 | 1,898 | 122 | +1,941% | +917% |
| W11 | 2,483 | 236 | +31% | +93% |
Key read: The massive W09βW10 jump reflects the official rollout launch. Consolidation in W11 (+31% msgs, +93% sessions) signals sustained organic growth post-launch β not a novelty spike.
| Category | Sessions | % of total |
|---|---|---|
| Short (<5 msgs) | 225 | 60.8% |
| Medium (5β15 msgs) | 67 | 18.1% |
| Deep (>15 msgs) | 78 | 21.1% |
21% deep sessions indicates real work and extended collaboration β not just quick lookups. "Short" sessions include bot auto-notifications and rapid check-ins, which explains their volume.
| Channel | Avg. Duration (min) | Total Messages | External? |
|---|---|---|---|
| ninjo-operator-dani | 49.0 min | 595 | β |
| ninjo-operator-marcos-razzetti | 41.8 min | 419 | β Yes |
| ninjo-operator-juanmahuss | 29.2 min | 583 | β Yes |
| ninjo-operator-lolo | 27.8 min | 520 | β |
| ninjo-operator-robertoyvalen | 17.6 min | 514 | β Yes |
The following 11 channels have external user participation (clients / Slack guests), validating the co-pilot model in front of the end client:
Qualitative data from the channels reveals 5 consistent usage patterns:
Ninjo analyzes sales call recordings (via Fathom or similar tools) and identifies closing patterns. In Lolo's channel, Ninjo reviewed 8 recorded calls and found that the only 2 successful closes (Nadezda and VicuΓ±a) corresponded to prospects with an urgent, active, and costly problem β while the rest lacked that present pain. Ninjo also proposed qualification questions to filter these profiles before entering the sales process.
Operators query Ninjo about the status of specific leads directly in the channel. Ninjo checks Ninjo Studio, reports automatic closes (e.g. @paumarenco closed at 6pm, meeting booked for Monday), identifies leads in active qualification, and diagnoses sync issues (e.g. @gisela.balboa not found β possible sync delay on outbound).
Ninjo proactively detects high-value leads that didn't receive follow-up at the agreed time and generates urgent alerts. In the case of Patricio Paolisso (a fitness coaching lead with real budget for marketing and visual production), Ninjo flagged that the 4pm call never happened and escalated to Daniel Czaplinski with full context so he could act before the lead lost interest.
Operators use the channel to rapidly iterate on agent behavior. In Escalamos, 3 concrete fixes were identified and documented for the sales flow: (1) don't assume prior knowledge of locations, (2) add a personalizing question before showing the activity grid, (3) present 6- and 12-month plans upfront (reserving monthly for objection handling). All three changes were ready to deploy in a single session.
Channels also function as technical operations rooms. Agus used his channel to coordinate the GHL (GoHighLevel) integration with Ninjo, review Calendly schedules, identify a table error in the initial query, and define the required credentials (API Key + Location ID) for full access. The lolocappucci script was used as a reference implementation.
| Metric | Value |
|---|---|
| Messages with satisfaction signals | 41 |
| Channels with detected satisfaction | 13 of 32 |
| Messages with emotional signal | 64 |
| Channels with emotional signal | 16 of 32 |
Closing pattern identified by Ninjo:
"The prospects who closed arrived with an urgent, active, and costly problem. Nadezda with 1,000+ messages/day overwhelming her setters; VicuΓ±a with clarity about her need. The others lacked that present pain." β Thread 2026-03-12, ninjo-operator-lolo
Automatic lead close:
"@paumarenco (Paulina Marenco, clothing/footwear store) was automatically closed by the agent at 6pm. Meeting booked for Monday at 8:30pm." β Thread 2026-03-12, ninjo-operator-cuentas-claras
Urgent no-show alert:
"Lead Patricio Paolisso was not called at the scheduled time (4pm). He has real interest β budget for marketing and professional visual production. Meeting confirmed by email for March 16. Requires immediate human contact before interest fades." β Thread 2026-03-12, ninjo-operator-marcos-razzetti
Flow optimization in one session:
In a single conversation with Julian Mercurio, Ninjo identified and documented three conversational flow fixes (locations, personalization, pricing) and left them ready to deploy β no tickets, no review cycles. β Thread 2026-03-12, ninjo-operator-escalamos
Conversational integration of complex systems:
Agus Oroquieta: "I want to give full access to my GHL account" β and in that same session Ninjo reviewed the reference script, identified the active schedule, and defined exactly which credentials are needed to proceed. All in one Slack channel. β Thread 2026-03-12, ninjo-operator-agus
The compounding growth over the last 3 weeks positions the product to surpass 100 active users in the next 4β6 weeks if the pace of new channel onboarding holds.
The Operator model validates a unique proposition: Ninjo doesn't replace the operator β it amplifies them. Each channel is an operations room where AI and human work in real time. The data shows:
Users stay β 78% re-engagement, 4.7 active days/week
Usage deepens β 21% deep sessions (>15 msgs), up to 240 min in key channels
Value is immediate β closes detected, no-shows alerted, flows optimized β same day
Scales outward β 11 of 32 channels already include external clients in real B2B scenarios