Customer support that lives on your site

One script tag puts a chat widget on your product. Every message — web or Telegram — lands in one inbox, and the ones that matter become tickets your team can track.

Installs on any stack, and answers from the channels your customers already use

Telegram
GitHub
Claude
Codex
React
Next.js
Plain HTML

One conversation.
However they reach you.

A customer starts in the widget on your pricing page, follows up on Telegram two days later, and by then whoever answers has usually lost the thread.

Lynq keeps every message, ticket and survey answer on the same customer, so the next person to reply picks up with the full history instead of asking them to explain it again.

Web and Telegram, one inbox. Same thread, same history, whichever channel they picked.

Announcements that reach them. Ship a banner or popup without redeploying your site.

Tickets from the conversation. Promote any chat to a tracked ticket without retyping it.

Ask before they forget. Fire a survey or NPS question right after the conversation ends.

See every conversation.
Who is waiting, and on what.

Wherever your visitors are. Lynq reads each visitor's timezone and browser, so you know who you are talking to before you reply.

Your widget, your brand. Colours, greeting and copy are yours, and changes apply live — nothing in it says it is not part of your product.

One script tag. That is the whole install.

Your inbox, updated in real time. Watch where volume comes from and catch a backlog building before customers start chasing you. Chart shown with sample data.

Fits the stack you already have

Install the widget on any framework, answer from the channels your customers already use, and drive your announcements and surveys from the AI coding agent you already have open.

Get Started

Every snippet in the docs comes pre-filled with your organization ID. Nothing to configure.

Telegram

Customers message your bot, you reply from the same inbox.

GitHub

Turn a report into a tracked issue on your project board.

Claude

Connect over MCP and have it write your announcements.

Codex

Same MCP endpoint, signed in with your Lynq account.

React & Next.js

Drop the widget in your root layout and you are done.

Plain HTML

One script tag before the closing body tag. No build step.

From chat to shipped fix.
Without leaving the inbox.

Tickets on a kanban board. Turn any conversation into a ticket and drag it through your workflow.

A bug report becomes a GitHub issue. Push it to your project board, then tell the customer when it ships.

Drag through your workflow. Columns you define, not the ones we picked for you.

Tied to the conversation. Open the ticket, read exactly what the customer said.

One workspace per team. Invite teammates and share the same inbox and board.

Close the loop. Ship the fix, announce it, and ask if it landed.

Support is not a six-tool problem. Chat, tickets, announcements and surveys share one inbox.

2 minutes

From pasting the snippet to your first answered message

1 inbox

Web chat and Telegram land in the same place, with the same history

0 redeploys

Change your widget, banners and surveys without shipping code

Start free.
Upgrade when support gets busy.

Free

For a single site, getting started

$0 /mo
Start for free
  • Chat widget on one site
  • Unlimited web conversations
  • Shared inbox for your team
  • Ticket board with your own columns
  • Full widget customization
Most popular

Pro

For teams answering every day

$29 /mo
Start for free
  • Everything in Free
  • Telegram in the same inbox
  • Announcement banners and popups
  • Surveys and NPS
  • GitHub issue tracking
  • Image attachments in chat

Business

For multiple products and brands

$99 /mo
Start for free
  • Everything in Pro
  • Multiple organizations
  • AI agents over MCP (Claude, Codex)
  • Priority support

Answer your first customer today

Start for free