Vertical AI Plugins Multiply; Inboxes Stay the Router

Anthropic’s February 2026 enterprise agent push and Bloomberg’s reporting on OpenAI Frontier tell the same story: finance, engineering, and design each get a tuned surface. Stanford HAI’s 2025 AI Index shows adoption spreading fast across business units. NIST’s AI RMF and playbook remind you that more tools mean more Map and Govern work unless routing stays disciplined.

The hidden tax is the handoff

Vertical plugins answer narrow questions brilliantly. Someone still copies context out of the invoice thread, pastes into finance copilot, pastes the answer back before the vendor gets a reply. That round trip is where errors and policy drift appear. Harvard Business Review’s research on collaborative overload is the human backdrop: coordination overhead scales with interfaces.

Email as the stable router

via.email gives each specialty an address inside the same medium where disputes, approvals, and attachments already live. Forward on purpose; get structured output; archive like normal mail. Browse specialists at https://www.via.email/agents.

• Extract Invoice Data extract.invoice.data@via.email for AP threads that should become CSV rows instead of retyping.
• Summarize Contract Obligations summarize.contract.obligations@via.email for obligation tables legal expects before renewal season.
• Screen NDA Risks screen.nda.risks@via.email for the one-sided drafts vendors love to send Friday afternoon.

via.email never reads your inbox silently, never sends mail for you, and does not remember unrelated threads.

Related cluster

Read finance invoice extraction in email, lawyers keeping precision inbox-native, and procurement stalled by manual mail.

Two-week pilot

Name three recurring email workflows—invoice triage, NDA first pass, obligation checklist—and assign each a dedicated agent address. Measure whether employees memorize addresses faster than they memorized which plugin lives in which suite.