Linq Launched iMessage Apps — Payments, Tickets and Games for AI Agents Directly in Chats

Linq launched iMessage Apps — payments, tickets, and games for AI agents directly in messaging

Linq presented iMessage Apps — a format of interactive message cards imessage_app that launch payments, ticket purchases, flight bookings, and games directly within iMessage chat; information about this appeared on June 30, 2026.

What iMessage App cards can do

iMessage App cards are interactive elements that embed directly in a chat thread and allow you to perform a functional action without leaving the chat or switching to a separate application or website.

• Payments — conducted directly in the chat through an iMessage App card
• Tickets — buying tickets to events inside the chat
• Flights — booking flights without switching to another application
• Games — interactive game cards directly in the iMessage thread

Why AI agents need this

Linq describes iMessage Apps specifically as a tool "for agents" — that is, for AI assistants that conduct dialogue with users inside iMessage. If an agent is chatting with a person and over the course of the conversation a specific action needs to be completed — paying a bill, buying a concert ticket, or booking a flight — the iMessage App card allows you to do this directly in the chat, without switching to a browser or separate mobile application.

This approach eliminates an unnecessary step between the user's intention and completing the action: the agent doesn't need to send a link and ask to open it separately — the entire operation remains within a single dialogue window.

Why the card format matters for chat agents

Before such cards appeared, the typical scenario for an AI agent working inside a chat looked like this: the agent recognizes the user's intention, formulates an answer, and sends an external link — to an airline website, payment service, or ticket office. Each such transition is a point where a user might change their mind, get distracted, or encounter a separate login and payment form on someone else's website. An interactive iMessage App card reduces this path to a single action within an already open dialogue.

According to Linq's description, cards cover four types of scenarios right away — payments, ticket purchases, flight bookings, and launching games — meaning they cover both transactional and entertainment tasks. This distinguishes the approach from narrow-focus bots that are typically limited to a single function: only payments or only booking.

What is known and what isn't

In the available description, Linq does not disclose the exact launch date for public access to iMessage Apps, nor does it list partner-providers of services whose tickets, flights, or payment services are already integrated with iMessage App cards. The name imessage_app indicates that this is a technical implementation within the messaging platform itself, not a separate application that needs to be downloaded and installed additionally — that is, the card appears directly in the existing dialogue window, rather than opening a new window on top of the chat.

What this means

The emergence of interactive cards within iMessage is part of a broader agentic commerce trend, where AI agents need native ways to complete real actions — payments, bookings, purchases — directly in the chat interface rather than through switching to a browser or third-party applications. Given how widespread iMessage usage is, turning messaging into a platform for such cards could accelerate the transfer of everyday transactional tasks to the dialogue interface with an AI agent: users no longer need to leave the chat to complete a purchase or booking started in a conversation with an agent. If the format catches on, interactive cards could become for messengers what embedded payment forms once became for the web — a standard way to bring a dialogue to a completed action rather than just a text response.