Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform →
← Back to news
ai

All the AI agents that can live in your text messages

A fragmented ecosystem of AI agents designed for text-based interaction has emerged across consumer and professional domains, with over fifteen notable platforms now competing to embed themselves into messaging apps rather than requiring dedicated downloads. These agents—ranging from Instinct's $10 billion valuation to niche players like Stanley for content creators and Town for professional workflows—share a common architecture: they integrate with existing calendars, email systems, and third-party services whilst operating through iMessage, WhatsApp, Telegram, SMS, or proprietary channels. The market has stratified by use case, with family-focused assistants (Fambot, Ohai, Ollie, Orbits) addressing household coordination, travel-specific agents (Miso) handling trip logistics, and general-purpose platforms (Folk, Martin, Pally, Rene) attempting broader task automation. Funding patterns reveal investor confidence in this category—Instinct's $1 billion Series C, Town's $55 million Series A, and multiple seed rounds across competitors signal that messaging-native AI agents are no longer experimental.

For CX teams, this proliferation creates both opportunity and complexity. The shift toward autonomous agents capable of handling tasks without human intervention—from booking reservations to managing email accounts with dedicated addresses—fundamentally challenges how support organisations should position themselves. If consumers increasingly delegate routine tasks to AI agents operating through familiar messaging channels, what does this mean for teams already managing high-volume transactional support through traditional ticketing systems like Zendesk or Freshdesk? The emergence of agents with their own identities, payment methods, and communication channels (as seen with Wajo's Fo and Instinct's dedicated email addresses) suggests that customer interactions may increasingly occur between machine and business rather than human and customer, potentially reducing inbound support volume but requiring new protocols for escalation and exception handling.

The security and compliance landscape remains uneven across this ecosystem, presenting both risk and differentiation opportunity. Whilst Ollie has achieved SOC 2 compliance and Wajo emphasises credential isolation through agent-owned identities, many platforms remain in beta with limited transparency around data handling—a critical gap given that these agents access calendars, emails, and personal financial information. For support leaders evaluating whether to integrate agent-native channels into their CX strategy, the question becomes whether to wait for standardised compliance frameworks or move early into partnerships with compliant players. The related concerns about AI agents requiring active management rather than one-time configuration and Apple's tightening of system access controls suggest that organisations cannot simply deploy these agents and assume they will operate autonomously—ongoing monitoring, permission management, and policy updates will become operational necessities.