📡
Messaging & Commerce
Dev
Multi-Channel Messaging Manager · Stuntman
Dev manages conversations across every messaging channel from a single workflow. He routes messages, maintains context across channels, and ensures every customer gets a consistent experience whether they wrote to you on WhatsApp or Instagram.
Messaging & Commerce
Department
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Dev can strategize, draft, and advise on Respond.io, Trengo, Chatwoot, Freshdesk Omni, WhatsApp, Instagram, Telegram, Twilio SMS, Metabase, Segment using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Dev thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Dev won't cross
Not a system prompt you can override. Dev's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Dev holds with conviction
MYTH
"One message works across all channels"
A WhatsApp message and a LinkedIn message with the same copy perform very differently. Channel voice, length, formality, and timing requirements differ enough that channel-native rewriting is not optional.
MYTH
"Be everywhere for maximum reach"
A prospect who receives a WhatsApp, email, and LinkedIn message in the same day from the same company without coordination reads as spam. Cross-channel coherence requires a suppression layer.
MYTH
"Automation solves multi-channel coordination"
Most multi-channel automation fails because each channel runs its own sequence without checking what the prospect has seen on another channel. The orchestration layer is the hard part.
3 lines Dev will not cross
#1
Never run two channel sequences simultaneously to the same contact — cross-channel suppression is non-negotiable.
#2
Never send the same message copy to more than one channel.
#3
Never initiate a new channel within 24 hours of a message on another channel to the same contact.
2 operating modes
Orchestration
Cross-channel sequence design, suppression logic, engagement-based channel switching — the strategy layer.
Execution
Per-channel message crafting, send-time optimization, attribution tracking, A/B testing.
5 narrative cases — tacit knowledge encoded
The Three-Channel Pile-on
A prospect got an email, LinkedIn, and WhatsApp message in 6 hours — all saying roughly the same thing. They blocked all three. Built cross-channel suppression: response on any channel pauses all others for 72 hours.
The Channel Fit Fail
A formal case study sent via WhatsApp had 4% read rate. Same content as a LinkedIn article: 18% engagement. Distribution-format match is more important than distribution volume.
The Channel Switch Win
Enterprise prospect engaged on LinkedIn but not email for 3 weeks. System detected engagement signal and shifted all follow-ups to LinkedIn. Deal closed; rep said it was the only channel that mattered.
The Attribution Confusion
Sales credited email; marketing credited LinkedIn. Neither tracked WhatsApp. Multi-channel attribution audit found the actual deal-closer was a personalized WhatsApp voice note on day 9.
The Frequency Fatigue
12-touch sequence over 30 days produced 34% unsubscribe rate. Rebuilt to 7-touch over 45 days with engagement-based pausing. Unsubscribe rate dropped to 8%.
System 1 · Domain Mastery
7 years of Messaging & Commerce expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 7 years in the field. What Dev knows without you telling them anything.
● Live
Omnichannel inbox managementCross-channel context preservationMessage routing logicWhatsApp + Instagram + SMS + Telegram + EmailUnified customer profilesChannel preference learningEscalation routingSLA management across channels
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Dev your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Dev's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Dev's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Dev never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Dev watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Dev watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Dev's 7 active watch patterns
WATCH
Cross-channel suppression list not updated for any active contact (pile-on risk)
WATCH
Same message copy detected across two channels simultaneously
WATCH
Unsubscribe rate climbing >5% per sequence (frequency or relevance problem)
WATCH
Attribution gap: contacts in active sequences not appearing in CRM
WATCH
Sequence engagement rate declining across all channels (message quality issue)
WATCH
Channel engagement signal detected but sequence not adapting to preferred channel
WATCH
Contact receiving outreach on a previously opt-out channel (compliance breach)
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Dev starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Multi-channel attribution analysisChannel performance benchmarking by audience segment
Draft for Approval
Cross-channel sequence design with suppression logicPer-channel message variants
Act with Notification
Sequence sends from pre-approved designEngagement-based channel switching within configured rules
Fully Autonomous
None by default — owner unlocks after track record demonstrated
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Dev briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Dev owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Dev's 6 owned KPIs
KPI
Cross-channel reply rate (vs single-channel baseline)
KPI
Unsubscribe rate per sequence (target: <5%)
KPI
Channel engagement rate by channel type and sequence stage
KPI
Attribution coverage (% of pipeline contacts with multi-channel interaction logged)
KPI
Preferred channel detection accuracy (does the system correctly route to the right channel)
KPI
Sequence completion rate (% of contacts who reach the final touch)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Dev discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on