<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fluxworks field notes</title>
    <link>https://flux-works.com/blog</link>
    <atom:link href="https://flux-works.com/rss.xml" rel="self" type="application/rss+xml" />
    <description>Practical guides on texting agents, phone answering, workflow automation and the systems small operators consider first. Worked examples, not case studies.</description>
    <language>en-us</language>
    <item>
      <title>The missed call is not the whole problem</title>
      <link>https://flux-works.com/blog/front-door-missed-call-sequence</link>
      <guid isPermaLink="true">https://flux-works.com/blog/front-door-missed-call-sequence</guid>
      <description>The failure usually happens across voicemail, text, calendar, and CRM. Fix the sequence, not one notification.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
      <category>front door</category>
      <category>missed calls</category>
    </item>
    <item>
      <title>Where automation should stop on purpose</title>
      <link>https://flux-works.com/blog/where-automation-should-stop</link>
      <guid isPermaLink="true">https://flux-works.com/blog/where-automation-should-stop</guid>
      <description>Money, anger, uncertainty, and promises in your name need a visible human gate, not a buried confidence score.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
      <category>control</category>
      <category>human gate</category>
    </item>
    <item>
      <title>Your CRM is a record. It is not the workflow.</title>
      <link>https://flux-works.com/blog/your-crm-is-a-record-not-the-workflow</link>
      <guid isPermaLink="true">https://flux-works.com/blog/your-crm-is-a-record-not-the-workflow</guid>
      <description>A record only matters when the next action, owner, and exception path move with it across the operating day.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
      <category>operations</category>
      <category>CRM</category>
    </item>
    <item>
      <title>The Sunday-night invoice pile: how a contractor can automate the paperwork</title>
      <link>https://flux-works.com/blog/contractor-invoice-pile</link>
      <guid isPermaLink="true">https://flux-works.com/blog/contractor-invoice-pile</guid>
      <description>How workflow automation can send a contractor's invoices the day a job closes, follow up on every quote, and hand back hours of weekly admin, under rules you sign off at setup. A worked example, not a case study.</description>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <category>workflow automation</category>
      <category>contractors</category>
    </item>
    <item>
      <title>How a restaurant can use AI to answer every phone call</title>
      <link>https://flux-works.com/blog/restaurant-ai-phone-answering</link>
      <guid isPermaLink="true">https://flux-works.com/blog/restaurant-ai-phone-answering</guid>
      <description>How AI phone answering can take reservations, answer the usual questions, and stop a restaurant losing covers to voicemail, with a person handling anything unusual. How it works, what it will not do, and how to tell if you need it.</description>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <category>AI phone answering</category>
      <category>restaurants</category>
    </item>
  </channel>
</rss>
