FEATURES

Deacon features that answer your customers and show you what they need

Deacon is an AI customer support agent for founders who handle support themselves. It answers your customers in seconds from your own docs, gets better with every answer you write, and shows you what they’re stuck on and what they want next. Every feature is on every plan, the free one included. Follow one customer’s question below to see each one at work.

Free plan, no card. Paid plans from $40 a month, billed yearly.

The Deacon widget on Acme’s site. A visitor has asked whether Acme supports single sign-on with Okta, and Deacon is looking for the answer.

Tuesday, 09:14 · Sam has one question before buying

A widget that fits your site, with no badge to pay to remove

Customers ask their question right where they are, in a chat that looks like part of your site. Pick the colours, corner radius, position and greeting against a live preview, and publish when it looks right. Hide the launcher and open Deacon from your own Help button if you’d rather. There’s no “powered by” line on any plan, including the free one.

Sam’s team can’t buy without single sign-on through Okta, so Sam clicks Help on Acme’s pricing page and asks.

  • Your colours, corners, position and greeting
  • Nothing changes on your site until you publish
  • A full-width sheet on a phone
How to choose a website chat widget
The Appearance editor, with accent colours, corner radius, position and greeting, beside a live preview of the widget and its Help button.

Tuesday, 09:14 · Deacon searches what Acme gave it

Honest answers in seconds, or a plain “I don’t know”

The fear with any support bot is that it makes something up in front of a customer. Deacon writes each answer from the passages it finds in your own content, in seconds and in the language your customer wrote in, often with a link to the page it used. When your content doesn’t cover the question, Deacon says so and asks for their email, so nobody hits a dead end.

Most questions stop here, answered. Sam’s doesn’t, because Acme’s docs never mention Okta, so Deacon says it doesn’t know and Sam leaves an email address.

  • Only what your content says, never a guess
  • Answering at 3am while you sleep
  • One question back when a question is vague
How a knowledge base chatbot finds its answers
Two conversations side by side. One question is answered with a link to the docs page. The other gets a plain “I don’t have the answer to that” and a field for the visitor’s email.

Tuesday, 09:17 to 09:26 · you get an email and answer in the chat

Human handoff, straight into your customer’s chat

Nobody has to sit and watch the chat. When a visitor leaves their email or asks for a person, the owners on your team get an email about it. You reply from the Deacon dashboard, so there’s no helpdesk to set up. If the visitor still has the chat open, your reply appears there under your name. If they’ve left, it reaches them at the address they left in the chat.

Sam still had the chat open, so your reply landed right under Deacon’s. Deacon stayed out of the conversation until you handed it back.

  • No email if you’re already in the dashboard
  • Messages to you never count as answers
  • One button hands the chat back to Deacon
When a chatbot should hand over to a person
The email an owner receives. A visitor on Acme left their email, with the question they asked, the page they were on and a button to open the conversation.
The dashboard, where the founder’s reply has been sent and Deacon is paused, beside the visitor’s widget showing the same reply under the founder’s first name.

Tuesday, 09:30 · you teach Deacon the answer

Answer once, and Deacon gets better

Typing the same answer for the tenth time is time you should spend building. Each question your docs didn’t cover has an Answer this button in your dashboard. Write the answer once and it becomes part of what Deacon knows, so it can answer the next person who asks and needs you less over time. Save & check shows you the reply Deacon now gives, and how many other open questions your answer covers too.

Your two sentences answered Sam and three other open questions about Okta and SAML. On Wednesday another visitor asked, got the answer in seconds, and you never heard about it.

  • Answering as soon as you save
  • The reply Deacon now gives, shown to you
  • A count of the other questions it covers
How an FAQ chatbot learns new answers
The Answer this panel with the founder’s answer saved, Deacon’s new reply shown as proof and three other open questions now answered, beside another visitor getting that answer the next day.

Ask it your customers’ questions today

Add your website or a few files, then try the questions you answer every week in the Playground. The free plan has 50 answers a month and needs no card. No plan ever bills you past its answers.

Start free

Any day · you read what Deacon told people

Conversation logs of every word said for you

You’ll want to know what an AI told your customers, and it’s all here. Every conversation is saved in full, with the source each answer named, the page the visitor was on, the topic their question joined and whether they’ve chatted before. Details your app passes in, such as their plan, sit beside it.

Sam’s conversation sat under Unanswered until you wrote the answer. Then it moved to Answered.

  • Tags for Unanswered, Wants a person, Answered and more
  • Searchable by what visitors asked
  • A Translate button for any conversation
What to read in your chatbot analytics
One conversation in the dashboard, with the docs page each answer came from and a panel showing that the visitor is returning, the page they asked from, their plan, device, language and topic.

Wednesday · the Okta questions add up

Topics that show what customers want next

The customers who email you are the loud few. Deacon hears from everyone who asks, and groups their questions into topics with a count of the people behind each. Most topics get a type, such as a how-to, a feature ask, a bug report or a pricing question. Analytics › Widget adds how many people wrote in, the share Deacon answered and the languages they wrote in, and names the page where people get stuck once one stands out.

Sam’s question joined Okta and SAML SSO, third on the list with 27 people. It’s typed as a pricing question, which tells you single sign-on belongs on your pricing page.

  • Ranked by the number of people asking
  • Each topic opens on the questions in visitors’ own words
  • Mark a topic done once you’ve dealt with it
What your chatbot’s questions can tell you
The topics list, each topic with a type and how many people asked, with the single sign-on topic opened to show three visitors’ own questions.

Thursday · Sam comes back and signs up

Website analytics from the script you already added

The script that runs the chat also counts your visitors, so there’s no second analytics tool to add. See where people come from, which pages they read and what devices they use. Name the goals that matter to you, such as a sign-up, build funnels from them, and see which sources send the visitors who reach your main goal. Worth knowing points out what stands out, such as a new JavaScript error or a source that converts better than the rest.

Acme marked its sign-up button as a goal, so Sam’s sign-up is counted with the rest. Website analytics counts people and never names them or where they work.

  • Goals from a line of code, an attribute or a class
  • Funnels of two to five steps
  • Nothing extra to install
What website visitor tracking should count
Website analytics, with visitors, page views, sign-ups and time on site, a chart of visitors per day with sign-ups marked, a Worth knowing sentence about Product Hunt visitors, and a table of sources.

More features, on every plan too

Sam’s question didn’t need these, but your customers’ questions will. No feature is held back for a higher plan. The plans differ only in answers, content, pages from your website and seats.

  • Replies in their language

    Ask in German and Deacon answers in German, even when every doc you have is in English.

    Multilingual chatbot
  • Visitor context

    Your app can tell Deacon who’s asking, such as their plan or role, and it takes that into account when it answers.

  • One clarifying question

    A vague question gets one question back instead of a guess. After three, Deacon stops asking and passes it to you.

  • Four kinds of source

    Your website, uploaded files, pasted text and the answers you write. Files can be PDF, Word, Markdown, text, CSV or HTML, and a scanned PDF works too.

    Knowledge base chatbot
  • Instructions

    Tell Deacon in plain words how to talk to your customers. It can write a first draft from your landing page.

  • Playground

    Try the real widget as any kind of visitor before your customers see it. Playground chats never count against your answers.

  • Team seats

    A seat is one person who can read conversations and reply to customers. The free plan has one seat, Starter has three seats and Growth has 10 seats.

  • What Deacon doesn’t do

    It has no helpdesk, tickets or flow builder, and no phone or WhatsApp. It answers on your website and hands the rest to you.

Answering on your site within minutes

  1. Sign up

    Use your email or Google. The free plan needs no card, has no end date and isn’t deleted if you go quiet.

  2. Add your content

    Point Deacon at your website, upload files or paste text. There are no flows or decision trees to build.

  3. Paste one line

    Add the script tag before </body>, or copy the prompt for Claude Code, Cursor or Codex and your agent adds it and checks it’s live.

What Deacon does as the AI chatbot on your website

Free plan, no card. Paid plans from $40 a month, billed yearly.