Vercel Connect Adds Linq Messaging for Apps and Agents.

Vercel is giving apps and AI agents a direct line to mobile messaging. In an August 25 changelog update, the company introduced a managed Linq connector for Vercel Connect, allowing software deployed on its platform to send and receive messages through iMessage, RCS, and SMS.

The integration is less about synchronizing contact records and more about turning messaging into an application interface. A customer could text a phone number, for example, while an app or agent processes the message and responds through Linq. That creates potential uses in customer support, lead qualification, appointment management, order updates, and other workflows where users are more likely to send a text than open another app.

The new connector is classified as a Vercel Managed Connector. According to Vercel’s connector documentation, this model puts setup and credential handling behind Vercel rather than requiring developers to manually create secrets, copy API keys, and maintain authentication settings.

For Linq specifically, Vercel says it can create both a Linq account and phone number on the user’s behalf. Teams that already have a Linq account can link it instead. In either case, Vercel handles the credentials, reducing the number of sensitive configuration values that builders need to store or rotate themselves.

Developers can create the connection in two ways:

• Through the Vercel Connect dashboard
• From the command line using the Vercel CLI

The company’s example creates a connector named my-agent, then attaches it to the production environment of a project:

vc connect create linq --name my-agent
vc connect attach linq/my-agent --project my-app --environment production

Separating connector creation from project attachment should be useful for teams managing multiple applications or environments. It lets developers provision the messaging resource first, then explicitly decide which project and deployment environment can access it.

Vercel also positions the connector as a way to give an eve agent a phone number. The Linq channel provides the messaging layer, while the agent can handle the conversation and application logic. That potentially moves an agent beyond a website chat box and into the messaging apps customers already use.

The launch expands the role of Vercel Connect, which acts as an integration layer between Vercel-hosted software and external services. As previously covered, Connect already lets applications built with v0 reach more than 100 services. Linq adds a communications-focused endpoint where inbound and outbound messages can become part of an automated workflow.

For small businesses, the practical appeal is consolidation. A builder could deploy an application, connect a phone number, and manage access within the same Vercel project structure instead of wiring together separate hosting, messaging, and credential systems. The announcement does not describe templates or prebuilt business workflows, so teams will still need to implement the agent behavior, routing rules, data storage, and safeguards appropriate to their use case.

Vercel has not disclosed separate pricing for the connector in the announcement. Builders should also evaluate Linq’s service terms, messaging availability, and any carrier-related requirements before using the integration for production customer communications.

What is the Vercel Connect Linq connector?

It is a managed integration that lets apps and agents on Vercel send and receive messages through iMessage, RCS, and SMS. Vercel can create a Linq account and phone number or connect an existing account, while handling the credentials.

How can developers set up the Linq connector?

Developers can create it from the Vercel Connect dashboard or with the vc connect create linq CLI command. They must then attach the connector to a project and specify an environment, such as production.

How much does the Vercel Connect Linq integration cost?

Vercel’s announcement does not provide connector-specific pricing or identify a required plan. Teams should consult the current Vercel and Linq pricing information before deploying a production messaging workflow.