Customer support and analytics for an app built with v0

You can already see how many people came. What you cannot see is what any of them wanted and gave up on. Deacon answers your visitors from your own pages and keeps a record of everything they asked, from one tag in your root layout.

Last reviewed September 2026

Two different questions

Analytics answers

  • How many people came, and from where
  • Which pages got read, and which ones nobody reached
  • How many left without going past the first page
  • Whether yesterday was better than the day before

Deacon answers

  • What each of those people was actually trying to do
  • Which question comes up most, across every wording of it
  • What your documentation does not cover at all
  • Who needs a reply from you, with their address and the transcript
  • And the page views, sources and countries too, if you would rather run one tag

Try Deacon for free

Install Deacon

Where the overlap ends

How many people visited

Deacon
Counted by the same tag, with sources, pages, countries and devices.
Analytics alone
Covered, if you turned analytics on.

What those people wanted

Deacon
Every question they asked, grouped by meaning into topics.
Analytics alone
Not measured anywhere. A page view does not say what somebody was looking for.

What your docs do not cover

Deacon
Listed as it happens, with a box to write the answer in.
Analytics alone
Discovered when somebody finally bothers to email you.

The visitor who cannot find it

Deacon
Gets an answer from your pages, with the source linked.
Analytics alone
Leaves. A bounce looks identical whether they found it or gave up.

Cost of finding out

Deacon
50 answers a month on one seat, at no cost.
Analytics alone
Free until you want the part that answers people.

Worth knowing before you start

A chart cannot tell you what somebody wanted

Knowing that four hundred people read your pricing page is useful. Knowing that eleven of them wanted to know whether it works with their existing setup is what changes the pricing page. Only one of those is on a chart.

It is a Next.js app, so this is a one-line edit

v0 gives you the whole file tree and a real root layout. The snippet goes in `src/app/layout.tsx`, either as a plain script tag in the body or through next/script with the afterInteractive strategy, and it runs once for every route.

v0 builds the interface, not the words

v0 is very fast at the interface and says nothing about the words. Deacon answers from the pages you point it at, so whatever documentation you have, even a single readme-shaped page, starts doing work the moment you add it.

Read the unanswered list once a week

Every question Deacon could not answer goes on a list. Read it once a week and you have a ranked account of what your product fails to explain, written by the people it failed.

Adding it to a v0 project

The snippet goes in your root layout, src/app/layout.tsx, as a plain script tag in the body or through next/script with the afterInteractive strategy. That is one edit and it covers every route.

v0 does not document third-party scripts anywhere, so this is our instruction rather than a quote from theirs. It is the standard Next.js answer, and it is what the file tree v0 hands you is for.

Add the domain you deploy to in Deacon before you test, including the preview address if you want the widget there. The install guide covers the rest of the dashboard.

Deacon on a v0 app, answered

In the root layout, src/app/layout.tsx. Put it as a plain script tag in the body, or use next/script with the afterInteractive strategy. v0 gives you the full file tree, so this is an ordinary edit and it covers every route at once.

They overlap on traffic figures. What Deacon adds is the conversation, so it answers the people in that traffic, keeps what they asked, groups it into topics and shows you the questions your documentation cannot answer. Run both if you like the Vercel numbers, or take the traffic figures from Deacon and have one fewer thing installed.

50 answers a month on one seat costs nothing, with no card taken and no trial clock running. The traffic figures are unmetered on every plan.

Yes. The tag is a plain script in the layout, so nothing about it depends on whether your components render on the server or the client. The loader handles client-side route changes on its own.

From the pages and files you give Deacon, with a link to the one it used. Nothing outside that material ever reaches a visitor.

That happens by itself. When Deacon cannot answer, it asks for an email address and the transcript lands in your dashboard marked unanswered. You reply from there and your answer reaches the visitor by email.

The counting side sets none and stores no visitor address. The widget does set a first-party cookie as it loads, so ask whoever wrote your notice to cover that one.

Try Deacon for free

One line in your layout, and the pages you already have. After that you are reading what your visitors actually came for.

See what Deacon does, or read the plans and prices.

READ NEXT