Moltbook, Meta, and the Inbox as Human Router

Agents do not need a friend graph. They need a handoff.

March 2026’s Meta and Moltbook headlines read like science fiction pitched as strategy: a social layer where agents discover each other, post, vote, and build a new graph alongside the human one. TechCrunch’s coverage frames the acquisition as part of a broader “agentic web” bet. TechCrunch on Meta’s Moltbook deal and AI agents

It might work. It might also be the wrong abstraction for how your company coordinates with vendors, regulators, and customers who still speak SMTP.

Why SMTP keeps winning the boring wars

Harvard Business Review’s 2025 piece on generative AI time savings is less about models and more about where the minutes actually go: savings disappear when teams do not redesign work, not when the model gets slightly smarter. HBR: how teams spend time saved by gen AI

OECD firm surveys in 2025 keep showing uneven adoption and skills constraints, which is another way of saying most organizations will not operationalize twelve new relationship graphs this quarter. They will operationalize “email the person who can say yes.”

NIST’s generative AI profile content is a quiet reminder underneath the hype: automated content without clear accountability chains is a governance problem, not a growth hack. NIST Generative AI profile

The intent stack for a product leader watching agent social experiments

Primary question: Do agents need their own social network, or better handoffs to people?

Layer two: Cross-company coordination still routes through mail because federation is already solved.

Layer three: Chasing every viral agent demo multiplies surfaces without multiplying judgment.

Layer four: Pick three workflow agents and run them only through threads.

A human-scale router: named specialists at addresses

Think Through This helps you decide what kind of help you actually need before you forward the wrong packet to the wrong team. Email think.through.this@via.email.

Qualify Inbound Leads turns messy inbound mail into structured next steps for humans who still own the reply. Email qualify.inbound.leads@via.email.

Prep Meeting Brief compresses long threads into something you can use in a room, which is still how most cross-functional alignment happens. Email prep.meeting.brief@via.email.

Digest Vendor Updates is the antidote to “every vendor launched an agent this week” email volume. Email digest.vendor.updates@via.email.

via.email is not an agent social graph. It is a directory of specialists you reach the same way you reach a colleague: an address, a thread, a human on send.

Related reads

For capital markets betting on mail-native routing, Why VCs Fund Agent Inboxes While Humans Still Live in Gmail is the direct counter-thesis. AI Agent Sprawl 2026: Every Vendor Adds a Dashboard names the fatigue curve. The Copy-Paste Tax: Why Your AI Workflow Is the Real Bottleneck explains why another surface rarely fixes throughput. Gmail and Outlook Have AI. Your Inbox Can Do More. is the reminder that generic inbox AI and specialist agents solve different jobs.

The takeaway

A social network for agents is a fascinating lab. Your operations are not a lab.

If you want adoption that survives contact with reality, route work through protocols people already trust, keep accountability visible, and let models accelerate drafting inside threads instead of inventing a parallel internet.