Key Takeaways

  • Linq raised $20 million in Series A funding as demand spikes for AI agents inside messaging platforms
  • The startup’s API enables businesses to deliver native iMessage, RCS, and SMS experiences without traditional apps
  • Rapid adoption following viral AI agent Poke pushed Linq to shift from B2B communications tooling to agent infrastructure

Linq hasn’t had a straight-line journey. Few startups do, but this one seems to have zigzagged its way to a space suddenly heating up. After starting life as a digital business card product, then repositioning as a lead‑capture tool for sales teams, the Birmingham-based company discovered something more unexpected: businesses didn’t just want to send messages to their customers — they wanted those messages to look and feel like they came from a real person.

That’s where the blue‑bubble obsession began. Apple’s Messages for Business has been around for years, yet it clearly hasn’t solved the authenticity problem for many companies. Messages from brands still show up in gray, almost shouting “this is automated.” Linq’s customers wanted something closer to everyday texting. Blue bubbles, group chats, emojis, images — the works.

Last year, Linq launched an API enabling companies to message customers natively through iMessage, with full support for Apple’s messaging features. Within eight months, the company doubled the annual recurring revenue it had accumulated over four years. That kind of trajectory tends to make founders sit up straighter.

But the more consequential turn came when AI agents exploded into public consciousness. A small California outfit building an iMessage‑embedded assistant called Poke reached out to Linq before launch. They didn’t have a CRM, didn’t have much of the “enterprise” infrastructure you might expect — they just needed access to a channel where users already spend massive time.

Then Poke went viral. And suddenly Linq found itself inundated with inbound requests from AI companies hunting for exactly the same capability: a way to deliver conversational agents directly inside iMessage, RCS, or even SMS. No app installs. No onboarding funnels. Just a contact thread.

Here’s the thing: not every platform moment is obvious when it begins. Linq’s leadership had to decide whether they were simply another vendor in a broader enterprise messaging ecosystem or whether their API could become a foundational layer for an emerging category. The team chose the latter.

It wasn’t a small decision. Pivoting away from a proven B2B revenue stream toward an unproven AI‑agent infrastructure market carries meaningful risk. But the signals were hard to ignore. AI companies wanted native messaging channels. Developers didn’t want to build apps. And consumers — increasingly overloaded with app installs, updates, and logins — were more than happy to interact with assistants where they already live their digital lives.

Some might ask whether this shift overestimates how quickly users will abandon apps. Yet the early numbers tell their own story. Linq says its customer base expanded by 132% quarter‑over‑quarter, with account expansion averaging 34%. Its customers’ AI agents now reach 134,000 monthly active users, and the platform processes more than 30 million messages each month. Zero churn and 295% net revenue retention paint a picture of a company that found the right current and started swimming with it.

The fresh $20 million Series A, led by TQ Ventures with participation from Mucker Capital and several angel investors, gives Linq room to scale its team and refine its go‑to‑market motion. It’s likely to need both. Demand for messaging‑native AI experiences is only accelerating, and developers increasingly treat messaging interfaces as first‑class product surfaces.

That said, there is an elephant in the room. Linq is operating atop Apple’s platform. And history has shown that major platforms can quickly reshape rules when strategic priorities shift. Apple could decide tomorrow that it wants to restrict third‑party AI agents in iMessage, just as Meta has done in certain contexts. The global landscape is even more fragmented. WhatsApp dominates in many regions. WeChat, Telegram, and Signal each carry distinct behavior patterns and technical constraints.

Still, Linq’s leadership seems to recognize this. Messaging is the entry point, but not the finish line. The company already supports programmatic voice, and its longer-term vision is a unified infrastructure for conversational technology across whatever channels consumers happen to use. Slack, email, Discord, Telegram — places where conversations flow and tasks get done. The bigger question is whether the market truly consolidates around a small set of messaging-native interfaces or whether multi-channel fragmentation persists.

Amid all this, one thing feels certain: AI agents are becoming more useful and more integrated into daily workflows. Whether that’s scheduling, information lookup, customer service, or lightweight task execution, conversational interfaces are shedding the novelty factor. And as they do, the infrastructural plumbing enabling those interactions becomes strategically important. Linq has placed its bet that the messaging thread — not the app — is where the next wave of user interaction will occur.

For now, the company sits at a rare intersection of timing, demand, and technology shift. The next year will show whether its pivot becomes a defining move or simply one more step in a rapidly evolving market.