<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Neverclosed</title>
    <description>The latest articles on DEV Community by Neverclosed (neverclosed).</description>
    <link>https://dev.to/neverclosed</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F14475%2F8ffe7fc6-1cbf-4ac1-890e-e564bb2f515e.png</url>
      <title>DEV Community: Neverclosed</title>
      <link>https://dev.to/neverclosed</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/neverclosed"/>
    <language>en</language>
    <item>
      <title>Neverclosed: a 24/7 AI receptionist for small businesses — what it is, why we built it, and how it works</title>
      <dc:creator>Bryan Williams</dc:creator>
      <pubDate>Mon, 24 Aug 2026 09:36:35 +0000</pubDate>
      <link>https://dev.to/neverclosed/neverclosed-a-247-ai-receptionist-for-small-businesses-what-it-is-why-we-built-it-and-how-it-44jo</link>
      <guid>https://dev.to/neverclosed/neverclosed-a-247-ai-receptionist-for-small-businesses-what-it-is-why-we-built-it-and-how-it-44jo</guid>
      <description>&lt;h2&gt;
  
  
  What it is
&lt;/h2&gt;

&lt;p&gt;Neverclosed is an always-on receptionist for small businesses. It lives on a company's website as a chat widget and on their phone line as a voice agent. It answers the questions customers actually ask — hours, services, pricing, "do you handle X?" — captures leads, and books appointments straight into the business's calendar. When a conversation needs a person, it hands off to one. It runs 24/7, because the customer with a burst pipe at 11 p.m. isn't going to wait until morning — they're going to call the next result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we built it
&lt;/h2&gt;

&lt;p&gt;Small businesses lose customers in the gap between &lt;em&gt;someone reached out&lt;/em&gt; and &lt;em&gt;someone answered&lt;/em&gt;. The owner is on a job, it's after hours, the front desk is slammed — and the message sits. Decades of lead-response research (the MIT/InsideSales work among others) point the same direction: the odds of ever connecting fall sharply within the first few minutes. Most people don't leave a voicemail and wait. They move on.&lt;/p&gt;

&lt;p&gt;The usual fixes each have a catch. A human answering service is expensive and still misses the overflow. A generic chatbot answers instantly but will confidently invent a price or a policy it was never given — worse than silence, because now you've misinformed a customer and can't take it back. We wanted the instant-response half without the making-things-up half.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works (a little under the hood)
&lt;/h2&gt;

&lt;p&gt;Three design decisions do most of the work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. It answers only from the business's own facts.&lt;/strong&gt; The agent is grounded in one business's hours, services, prices, and policies, and it's built to say &lt;em&gt;"let me take a message and have someone follow up"&lt;/em&gt; rather than invent an answer. On top of that we run a second verification pass whose entire job is to catch the first one making a claim the business's facts don't support. Anti-hallucination isn't a slogan for us — it's a second agent checking the first.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Actions are verified at the data layer, not in the transcript.&lt;/strong&gt; The part we care about most as engineers. An agent &lt;em&gt;saying&lt;/em&gt; "you're booked Tuesday at 3" is not the same thing as a booking existing. So we don't trust the words — a booking counts only when the record actually lands in the calendar and reads back correctly. We hold our own tests to the same bar: the grader reads the database, not the chat log, and a "success" the agent narrates but never performed is scored as a failure. (There's a whole harness behind that sentence — the subject of our next post.)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. It's always on, and a human can step in instantly.&lt;/strong&gt; The system runs on Cloudflare Workers and Durable Objects — fast, always-on, no server to babysit, each business isolated. When an owner opens their console mid-conversation, the AI pauses and the human takes over seamlessly; the visitor just sees a teammate join. Close the console and the AI resumes. Every lead is saved the instant it's captured (a lead you don't persist is a lead you lost), and the owner is alerted the moment someone asks for a callback.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we refuse to do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;It always says it's AI.&lt;/strong&gt; No pretending to be a person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flat, transparent pricing — no per-minute meter.&lt;/strong&gt; You know the bill before the month starts. Much of this category runs on overage surprises; we don't.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proof before promises.&lt;/strong&gt; We'd rather show the agent handling a hard question than tell you it's good. We test ours hard enough to catch it failing — and we fix what we catch.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Who it's for, and where we are
&lt;/h2&gt;

&lt;p&gt;Neverclosed is built for the businesses that feel every missed call personally — home services, clinics, shops, practices — the ones where a single after-hours lead can be the week. It's live, and we're opening it up now.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open to collaboration — and building the distribution
&lt;/h2&gt;

&lt;p&gt;We're early, and we'll say so plainly: the product is live, and the work in front of us right now is distribution — getting Neverclosed to the businesses that need it, done the right way. We're building that deliberately, from ambition rather than urgency.&lt;/p&gt;

&lt;p&gt;We're also open to collaborators. If you're a developer who wants to build on or integrate with this, a partner who can help it reach the businesses it's for, or someone who believes an AI receptionist should be held to &lt;em&gt;prove it, don't promise it&lt;/em&gt; and wants to build that with us — we'd like to talk. We're not looking to contract the work out; we're looking for people who want to build it alongside us.&lt;/p&gt;

&lt;p&gt;We're building this in public, and the engineering runs deeper than one post can hold: the verification harness, the edge architecture, the honesty guardrails. This is the introduction. The rest is coming.&lt;/p&gt;

&lt;p&gt;— The Neverclosed team · tryneverclosed.com&lt;/p&gt;

</description>
      <category>ai</category>
      <category>serverless</category>
      <category>saas</category>
      <category>buildinpublic</category>
    </item>
  </channel>
</rss>
