Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the State Government edition of September 30, 2026

Government evaluationEmergingNew this fortnight

Michigan LARA launches AI website chatbot (live Sep 25; announced Sep 28) for licensing navigation

Michigan Department of Licensing and Regulatory Affairs (LARA) · State licensing and regulatory services / citizen digital experience · Michigan — LARA public website (Michigan.gov/LARA); part of statewide Michigan.gov chatbot rollout

Publisher
Michigan Department of Licensing and Regulatory Affairs
Original publication
2026-09-28
Source retrieved
2026-10-01
Event date
2026-09-25
Read original source

What happened

On 2026-09-28 LARA announced a new AI-powered website chatbot that became available 2026-09-25, offering 24/7 help finding forms, understanding application steps, and linking to Michigan.gov content. Director Marlon I. Brown frames it as supplementing staff for routine questions. The release states responses use Michigan.gov information, urges users to verify answers, and warns not to enter sensitive/PII. It notes an early launch phase that will improve as the statewide platform evolves, pointing readers to Michigan.gov/Chatbot for program details.

Why it matters

Fresh state licensing chatbot launch three days before this edition and one day before the prior archive cutoff—citizen-services GenAI without published accuracy metrics yet. Why now: published 2026-09-28; not in archive; complements Michigan’s broader chatbot phases and tonight’s award-week measured projects with a just-live operating example.

Evidence and measured results

Opened the LARA news release via WebFetch (curl returned 403); confirmed Sep 28 announcement, Sep 25 availability, 24/7 forms/process guidance, Michigan.gov grounding, verify/no-PII warnings, and early-launch framing. Also opened Michigan.gov/Chatbot for phase context (UIA spring 2025; statewide summer–fall 2026) and beta disclaimer on errors/inaccuracies.

Limitations and uncertainty

Agency press release, not an outcome audit; no deflection %, accuracy, or CSAT published in the announcement; statewide platform still evolving.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Licensing agencies need 24/7 navigation help without flooding staff, but must prove accuracy before scale claims.
Stakeholders
  • LARA leadership
  • DTMB/eMichigan
  • Contact center
  • Privacy
  • Licensed professionals/public
Discovery questions
  • What accuracy sample is planned in the first 60 days?
  • Which journeys are in/out of bot scope?
  • How is feedback routed to content owners?
  • What happens when the bot is wrong?
Value hypothesis
A grounded licensing chatbot can reduce routine navigation friction if accuracy sampling and escalation are operating from day one.
Potential engagement
30–60 day post-launch measurement plan for accuracy and containment on priority forms.
Unsupported claims
  • Guaranteed call-volume drop
  • Error-free licensing guidance
  • Early launch equals mature service
  • Bot replaces caseworkers

Pre-sales engineering

Role takeaway
Fit
Grounded generative navigation chatbot with source links and human escalation.
Architecture and integration
Michigan.gov content index to chatbot to source URLs to feedback store to content CMS updates.
Prerequisites
  • Content inventory
  • Disclaimer/UX
  • Feedback pipeline
  • PII controls
Constraints
  • No published accuracy yet
  • Beta inaccuracies acknowledged
  • Evolving statewide platform
Security
Block sensitive inputs where possible; short retention; no training on user chats without policy.
Proof of value
  • Sampled accuracy vs source pages
  • Containment/deflection rate
  • PII incident count

Delivery

Role takeaway
Work
Stand up weekly sampling; fix top miss routes; train contact center on bot handoffs.
Dependencies
  • LARA content owners
  • Platform team
  • Contact center
  • Privacy
Ownership
Program content owners accountable for answer correctness; platform team owns runtime.
Skills and adoption
Short guides for staff on when to override bot guidance.
Governance checkpoints
  • Week-2 accuracy sample
  • Month-1 feedback review
  • Scope expansion gate
Acceptance criteria
  • Sampling method published internally
  • Escalation path documented
  • No PII collection by design
Risks
  • Wrong form guidance
  • PII pastes
  • Launch without metrics

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Site-grounded generative chatbot with session context and source links; keep transactions and eligibility decisions out of the bot; provide staff escalation paths as stated.

Governance

Who approves, reviews and stays accountable for outcomes?

Early-launch + verify warnings imply incomplete evaluation—require accuracy sampling and feedback review before claiming service-level success.

Security and privacy

What data, permissions and controls need testing?

Explicit no-sensitive/PII guidance; still risk users pasting license numbers—add input filters, retention limits, and monitoring for sensitive data.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Desktop/mobile chat plus microphone input can improve access if keyboard/screen-reader paths and multilingual options (per statewide chatbot page) are validated; staff remain needed for individualized help.

Procurement

What should contracts, pricing and exit terms secure?

Enterprise chatbot platform expansions should include accuracy SLAs, logging, and content-refresh obligations as LARA onboards program pages.

Operating model

Which teams own the service once it runs?

Treat LARA as a phase-2 agency onboard to a statewide bot: content owners must maintain source pages and review thumbs feedback, not only launch the widget.

Publication history

  1. 2026-09-30State Government · Issue 255 resources
Read preserved resource versions (JSON)

Stable resource ID: michigan-lara-ai-chatbot-launch-20260928