Independent insurance agencies: what an AI agent can and can't do with your software

• Last verified October 28, 2026
• Updated Oct 28, 2026Published Oct 28, 2026

A small independent agency, whether it writes home, auto and small commercial policies or sells life and health coverage, usually rents a handful of systems: an agency management system for clients, policies and commissions, a comparative rater for quoting, carrier download to pull policy and claim updates in, an e-signature service for applications, a card processor, QuickBooks, and often a marketing CRM. Here we work out what Meta's Muse assistant, or another agent that runs on connectors, can get into today, which back-office chores are sensible to give it, and why customer files, state insurance data security laws, producer licensing and outbound calls, texts and email need a licensed person watching. It's aimed at agencies with one to a few offices. Carriers, MGAs, wholesalers, large brokers and the choice of an agency management system are out of scope.

Every claim carries a badge, and the badge tells you what backs that claim up:

Our method: we read the developer portals, API terms and help articles of the agency management, rating, download and e-signature vendors named below, the Muse and partner pages for Meta's own connectors, Meta's Muse terms and privacy policy, the Gramm-Leach-Bliley Act's privacy title and the CAN-SPAM Act on the House's U.S. Code site, the FTC's Safeguards, Privacy and CAN-SPAM rules on eCFR, the FCC's robocall rule and its newest amendment, Tennessee's 2021 insurance data security act, two Mississippi Insurance Department pages and an NAIC brief. Next to each source is the date we read it. We connected no assistant, Muse included, to an agency system, client list, carrier portal, card account or ledger, sent no client message and tested no tool. A vendor's documentation shows how a product is meant to work; it doesn't tell you whether your agency may lawfully use it that way.

Short version

• HighLevel, Stripe and Intuit QuickBooks appear among the Muse connectors in Meta's launch post, and none of the agency management, rating, carrier download or e-signature products on this page; it directs readers to the Muse app for the full roster, which we didn't open. (Confirmed by vendor 1)
• Momentum, the company behind NowCerts, documents an MCP server for AI assistants. Applied Systems, Vertafore, HawkSoft and QQCatalyst document APIs that open only after developer or partner registration, and HawkSoft, QQCatalyst and AMS360 each need the agency to enable or approve the integration. (Confirmed by vendor 9 10 11 13 14)
• Muse's terms bar using it as a substantial factor, without meaningful human review, in deciding whether someone gets or keeps insurance, and bar unlicensed regulated activity. Under its privacy policy, Meta may use your interactions to train its AI unless you switch that off, and the data Muse fetches through Connectors can be part of those interactions. (Confirmed by vendor 8)
• For anyone engaged in providing insurance, the Gramm-Leach-Bliley Act hands enforcement of its privacy and safeguards provisions to the insurance authority of the state where that person is domiciled, applying state insurance law. (Confirmed by Congress 20) Your state insurance department, not the FTC, is the usual place to look.
• New FCC rules on how people withdraw consent to robocalls and robotexts start Nov 25, 2026, so review your opt-out handling ahead of that date. (Confirmed by the FCC 28)

Stack map

Swipe the table sideways to see every column →

If you want a custom connector

Software Meta doesn't list needs a bridge: a vendor-run MCP server like Momentum's or Docusign's, an integration built through the vendor's partner program, or Zapier. Before anyone builds one, count who will see client data. Every hop, the vendor, the developer, any middle layer and the assistant's maker, becomes a service provider you're responsible for under your state's rules. According to Meta's help center, nobody at Meta vets a custom connector or its data practices, and Muse's memory and chat history can keep what it learned after you disconnect one. (Confirmed by vendor 2) Under Muse's builder guidelines each sensitive write needs its own approval, and a standing permission isn't allowed. (Confirmed by vendor 3) We found no Meta commitment about how Muse handles nonpublic personal information under GLBA or state insurance law; ask Meta for one in writing before any client file is shared. (Unverified)

Jobs you could hand off today

Each one keeps client files away from Muse.

Swipe the table sideways to see every column →

We haven't run any of these. Plan tier, user permissions and connector settings all affect the result, so start with a few records and check every output yourself.

Keep these out

• Client files, policies, applications and claims. Don't link your management system, rater, Ivans downloads or e-signature account to an AI assistant, or paste client details into a chat, until your security program accounts for each company that would touch the data, the assistant's maker too.
• Coverage advice and underwriting calls. Muse's terms say it doesn't give legal, financial, investment, tax or other professional advice, bar unlicensed regulated activity, and bar letting it substantially decide, without meaningful human review, whether a person receives or keeps insurance. (Confirmed by vendor 8) Recommending coverage, comparing policies for a client and binding stay with a licensed producer.
• Bulk calls and texts. The terms also forbid bulk calls or messages lacking the consent the TCPA, CAN-SPAM or state telemarketing laws require. (Confirmed by vendor 8)
• Premium payments and refunds. Muse's terms say it isn't a licensed financial advisor, broker, fiduciary, money transmitter or financial institution, and that the user carries the risk of loss from payments it makes. (Confirmed by vendor 8) A refund or outbound payment through Stripe's MCP doesn't complete until a person approves it. (Confirmed by vendor 7)
• Carrier portal logins. Don't hand an agent your carrier credentials.
• Breach decisions. Whether a misdirected email or a lost laptop has to be reported to the commissioner is for the owner and counsel, not an agent.

Risks to keep a person on

Customer information under GLBA

The Gramm-Leach-Bliley Act's privacy title treats as a financial institution any business engaged in the financial activities the Bank Holding Company Act describes, and that list includes insuring and acting as principal, agent or broker for insurance. (Confirmed by Congress 21) Each regulator named in the enforcement section has to set administrative, technical and physical safeguards standards for the institutions it oversees, to protect customer records against threats and unauthorized access. (Confirmed by Congress 19) For a person providing insurance, that regulator is the insurance authority of its home state acting under state insurance law, and the FTC is left with financial institutions no other listed regulator covers. (Confirmed by Congress 20)

The FTC's Safeguards Rule reaches only financial institutions that aren't under another regulator's enforcement authority under 15 U.S.C. 6805, and its examples, such as mortgage brokers, tax preparation firms and investment advisors not required to register with the SEC, don't include insurance agencies. The FTC's GLBA privacy rule in part 313 now covers only certain motor vehicle dealers. (Confirmed by the FTC 22) If your agency also prepares taxes, finances premiums or offers other financial services, part of the business may fall under a different regulator; we didn't research those cases, so ask a lawyer. (Unverified)

State insurance data security laws

According to an October 2026 NAIC brief, 28 jurisdictions have adopted the NAIC Insurance Data Security Model Law (#668), Mississippi and Tennessee among them, and the model exempts licensees with fewer than 10 employees. The NAIC is a group of state regulators, not a government body, and it says its list doesn't show whether a state's law matches the model in full. (Reported 26) Your own state's statute is what counts.

Tennessee. Tennessee's Insurance Data Security Law, Public Chapter 345 of 2021, effective July 1, 2021, doesn't apply to a licensee with fewer than 25 employees and independent contractors combined, less than $5 million in gross annual revenue, or less than $10 million in year-end assets. A covered licensee needs an information security program scaled to its size and complexity, and must tell the commissioner within 3 business days after determining a cybersecurity event occurred for a producer whose home state is Tennessee, when the event is reasonably likely to materially harm a Tennessee consumer or a material part of the licensee's normal operations, or when 250 or more Tennessee consumers are involved and another trigger in the act is met. Notice to consumers is due no later than 45 days after that determination. (Confirmed by the Tennessee General Assembly 23) We read the act as passed in 2021 and didn't check later amendments. (Unverified)

Mississippi. The Mississippi Insurance Department says the state's Insurance Data Security Law took effect July 1, 2019, at Miss. Code sections 83-5-801 to 83-5-825. Insurance producers, and licensees with fewer than 50 employees, under $5 million in gross annual revenue or under $10 million in year-end assets, are exempt from the information security program requirements and parts of sections 83-5-809 and 83-5-811, but the department's notification form covers all licensees, and a licensee must notify the commissioner no later than 3 business days after determining a cybersecurity event involving nonpublic information occurred. (Confirmed by the Mississippi Insurance Department 24) We read the department's summary, not the statute text. (Unverified)

Arkansas. We found no Arkansas statute or Arkansas Insurance Department page showing the NAIC data security model was adopted there, the NAIC brief's list leaves Arkansas out, and the department's site refused our requests. Ask the Arkansas Insurance Department. (Unverified)

We didn't check any other state. (Unverified) Even where your agency is exempt, a slip by an agent that has your client list is still your problem with clients and carriers.

Licensing and advice

Mississippi's licensing FAQ describes a non-active producer license as one held by someone who isn't selling, negotiating or soliciting. (Confirmed by the Mississippi Insurance Department 25) Selling, soliciting and negotiating are the activities a producer license exists for. We didn't read any state's producer licensing statute for this page, and we found no regulator statement on whether an AI assistant that explains coverage or quotes to a client is soliciting or negotiating. (Unverified) Until that's settled, every client-facing answer about coverage should come from, or be approved by, a licensed producer.

Calls and texts

Starting Nov 25, 2026, callers can pick a single method, from those the rule lists, as the only route for revoking consent, as long as its calls and texts disclose it, and a stop request aimed at one category of informational messages may be applied to just that category. (Confirmed by the FCC 28) Don't let an agent change opt-out keywords, merge renewal reminders with promotions, or move contacts onto a marketing list.

Email

Under the CAN-SPAM Act, a commercial email must say it's an advertisement unless the recipient agreed beforehand, carry an opt-out mechanism that still functions 30 days or more after the message goes out, include a valid postal address, and stop going to someone more than 10 business days after they opt out. (Confirmed by Congress 30) The FTC's rule says unsubscribing can't cost a fee or require more than the recipient's email address and opt-out choices, and treats an email mixing promotion with transactional or relationship content as commercial if its subject line reads as promotional or the transactional or relationship content doesn't appear, wholly or mostly, at the start of the body. (Confirmed by the FTC 29)

Treat this page as a summary of published sources, not as legal, licensing, privacy or compliance advice. Your state insurance department, your carrier and agency contracts and your software agreements may require more than what's here, so get an insurance regulatory lawyer's view before you link an assistant to anything with client data in it.

FAQ

Can Muse connect to Applied Epic or AMS360?

Does the FTC Safeguards Rule apply to my agency?

The rule itself excludes institutions that another regulator enforces against under 15 U.S.C. 6805. (Confirmed by the FTC 22) For insurance activity that regulator is your home state's insurance authority, so start with your state's data security law. Side businesses are the open question noted above.

If I turn off AI training, is Muse fine for client files?

The Data controls setting decides whether Meta uses your interactions to improve its AI, and Meta's terms say it may access and retain logs of the actions Muse takes. (Confirmed by vendor 8) Switching training off doesn't put Muse inside your security program.

How much Zapier usage does an agent burn?

Each successful MCP tool call counts as two Zapier tasks. (Confirmed by vendor 5) Budget for that if an agent will be logging NowCerts records through Zapier.

Changes to this page

Swipe the table sideways to see every column →

Found a mistake or a newer source? Send it through Corrections, with a link to the source, and we'll recheck the claim and record the change here.