<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Loops blog</title>
  <link>https://useloops.ai/blog</link>
  <atom:link href="https://useloops.ai/blog/rss.xml" rel="self" type="application/rss+xml"/>
  <description>Guides for teams running AI voice agents in US collections, insurance and healthcare: FDCPA, Reg F, TCPA, HIPAA, call QA and release testing.</description>
  <language>en-us</language>
  <lastBuildDate>Wed, 23 Sep 2026 17:45:00 -0400</lastBuildDate>
  <item>
    <title>How to audit AI voice agent calls against your own SOP</title>
    <link>https://useloops.ai/blog/audit-ai-voice-agent-calls</link>
    <guid isPermaLink="true">https://useloops.ai/blog/audit-ai-voice-agent-calls</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>QA and audit</category>
    <description>To audit AI voice agent calls, split your standard operating procedure into numbered, testable rules that your compliance lead approves, then grade every call against each rule. Every verdict should carry the quoted transcript line, the tool-call record, the rule version and the grader version. Send calls a transcript can&#x27;t settle to a person, calibrate against your own reviewers, and compare miss rates between releases.</description>
  </item>
  <item>
    <title>FDCPA and Regulation F rules for AI collection calls: a call-by-call checklist</title>
    <link>https://useloops.ai/blog/fdcpa-reg-f-ai-collection-calls</link>
    <guid isPermaLink="true">https://useloops.ai/blog/fdcpa-reg-f-ai-collection-calls</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Collections compliance</category>
    <description>An AI collection agent follows the same FDCPA and Regulation F (12 CFR part 1006) rules as a human collector. On each call it must confirm the right party before any account detail, give the 1692e(11) debt collector disclosure, call only between 8 a.m. and 9 p.m. in the consumer&#x27;s time zone, stay within the seven-in-seven call presumption, leave only limited-content voicemails, and honor stop, dispute and attorney requests.</description>
  </item>
  <item>
    <title>TCPA consent for AI voice calls after the FCC&#x27;s 2024 ruling: what&#x27;s settled and what isn&#x27;t</title>
    <link>https://useloops.ai/blog/tcpa-consent-ai-voice-calls</link>
    <guid isPermaLink="true">https://useloops.ai/blog/tcpa-consent-ai-voice-calls</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Collections compliance</category>
    <description>Under the FCC&#x27;s February 2024 declaratory ruling (FCC 24-17), AI-generated voices are &quot;artificial&quot; voices under the TCPA, so AI voice calls need the same consent as prerecorded calls: prior express consent for informational calls to cell phones, prior express written consent for telemarketing, and limits on calls to residential lines. Each message must identify the caller, and consent can be revoked by any reasonable means.</description>
  </item>
  <item>
    <title>Why a voice agent release that passes its tests can still break a rule</title>
    <link>https://useloops.ai/blog/voice-agent-release-regression</link>
    <guid isPermaLink="true">https://useloops.ai/blog/voice-agent-release-regression</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Release testing</category>
    <description>Voice agent regression testing checks that a new release doesn&#x27;t break rules the last one followed. Simulated suites catch many breaks but can&#x27;t reproduce real callers, live tool failures or every rule a prompt change touches. So tag every live call with its agent version and compare each rule&#x27;s miss rate between versions on the same weeks, call mix and grader version, with a confidence interval.</description>
  </item>
  <item>
    <title>Grading calls with your own LLM judge, and what an examiner will ask</title>
    <link>https://useloops.ai/blog/llm-judge-call-qa</link>
    <guid isPermaLink="true">https://useloops.ai/blog/llm-judge-call-qa</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>QA and audit</category>
    <description>An LLM judge can grade every call transcript against written rules, and strong models agree with human raters often enough to be useful for triage and trends. It falls short when an examiner asks who approved each rule, which grader version produced a verdict, what line it relied on, what happens when a transcript can&#x27;t settle a rule, and how often it passed calls your reviewers failed.</description>
  </item>
  <item>
    <title>HIPAA and AI voice agents in patient access: a call-level checklist</title>
    <link>https://useloops.ai/blog/hipaa-ai-voice-agents-patient-access</link>
    <guid isPermaLink="true">https://useloops.ai/blog/hipaa-ai-voice-agents-patient-access</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Healthcare</category>
    <description>A HIPAA-compliant AI voice agent verifies the caller&#x27;s identity and authority before disclosing any protected health information, keeps its tools and transcripts to what the call needs, tells family only what relates to their role, honors confidential-communication requests, keeps voicemails minimal, and runs under a business associate agreement with every vendor that stores audio or transcripts. HIPAA sets these outcomes; your standard operating procedure sets the script.</description>
  </item>
  <item>
    <title>AI voice agents on insurance claims calls: what the agent must get right</title>
    <link>https://useloops.ai/blog/ai-voice-agents-insurance-claims-calls</link>
    <guid isPermaLink="true">https://useloops.ai/blog/ai-voice-agents-insurance-claims-calls</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Insurance</category>
    <description>An AI voice agent on insurance claims calls must verify the caller before discussing a claim, state coverage only from the policy record, never promise an outcome, treat a reported loss as notice and log it so the acknowledgment deadline is met, point disputes to appeal and insurance department review, and disclose recording where all-party consent applies. Most states base these duties on NAIC model law #900.</description>
  </item>
  <item>
    <title>How to measure what an AI voice agent release earned</title>
    <link>https://useloops.ai/blog/ai-voice-agent-revenue-by-release</link>
    <guid isPermaLink="true">https://useloops.ai/blog/ai-voice-agent-revenue-by-release</guid>
    <pubDate>Wed, 23 Sep 2026 17:45:00 -0400</pubDate>
    <category>Measurement</category>
    <description>Measure AI voice agent ROI from payment records, not minutes or containment. Credit each payment to the release that handled the account&#x27;s last call before it posted, within a fixed window such as 30 days. Compare releases on the same weeks, clients, and balance and age bands, put a 95 percent range on every difference, and count human transfer and review time in cost per resolved call.</description>
  </item>
</channel>
</rss>
