Shortwave vs Twilio
Side-by-side trajectory, velocity, and editorial themes.
Shortwave keeps folding autonomy into the inbox, one AI action at a time.
Shortwave has moved decisively from an AI-assisted email client to an inbox that acts on the user's behalf. The assistant reads, drafts, organizes, and — via the Tasklet integration — triggers automated workflows across thousands of apps, with its work surfaced inside Shortwave rather than buried in Gmail. Every release since late 2024 has pushed more of the email workflow out of the user's hands and into the model's.
The direction is a steadily widening action surface: MCP connectors to external tools, AI Memories, voice, and now trigger-based automation all frame email as an agent runtime rather than a reading pane. Model choices track the frontier closely — Claude 3.7 to Sonnet 4 to the 4.6 family — keeping capability tied to whatever the best available model can do. The team ships broadly across web, desktop, iOS, and Android each cycle.
The next moves most likely deepen autonomous execution — more trigger types and tighter loops where the assistant acts with less confirmation — rather than adding new surface features.
Twilio grinds through platform-maturity work: RCS error hygiene, WhatsApp usernames, org-level identity APIs
Twilio's changelog this window is dense with the unglamorous work of a mature CPaaS: RCS and OTT error-code cleanup, WhatsApp feature parity as Meta ships new capabilities, geo-expansion of Branded Calling, and organization-level identity governance (OAuth client credentials GA, SCIM, Roles APIs). There is no single directional bet here — it reads as steady maintenance across messaging, voice, and account-management surfaces.
The throughline is Twilio hardening the platform for large, regulated, multi-account customers: clearer failure signals developers can route on, ISV-aware notification routing, standards-based identity, and long-lead infrastructure migrations telegraphed years out. Voice AI (Conversation Relay) shows up at the edges as a reference component rather than a core release, suggesting it is still in developer-adoption mode.
Expect the RCS/OTT error-code standardization and WhatsApp identifier support to keep expanding channel-by-channel, and Branded Calling to add more non-US regions as the public beta matures.
See more alternatives to Shortwave →
See more alternatives to Twilio →