Skip to content
EnaChat

Changelog

September 2026 — hand-off delivery status and safer staff access

  • Hand-offs: each hand-off shows whether the email to the citizen office was sent, is pending or failed, and the panel warns clearly when email notifications are not active. The chat only tells citizens their question “was passed to the office” when it really was sent; otherwise it says the question was logged.
  • Technical errors: if the AI model does not answer in time, the citizen gets a clear message with the option to talk to a person instead of an error.
  • Staff access: temporary lockout after repeated failed logins, and password change from the panel (key icon).
  • The chat’s contact forms are protected against automated submissions, without cookies.
  • The panel shows dates and times in the chosen language (Catalan, Spanish or English).

September 2026 — one address: app.enacast.chat

  • The old service address (chatapp.enacast.com) now redirects automatically to app.enacast.chat: saved links and panel bookmarks keep working.
  • No action for councils with the widget installed: the old embed code keeps being served unchanged.
  • The CNAME target for custom domains is now app.enacast.chat; already-verified domains need no change.

August 2026 — our own domain: enacast.chat

  • The service moves to its own domain. Marketing site at enacast.chat, documentation at docs.enacast.chat, admin panel at app.enacast.chat.
  • Per-town public chats get their own address: yourtown.xat.enacast.chat (and …chat.enacast.chat).
  • No action for councils that already installed the widget: the previous service address keeps working, and improvements ship behind /v1.js as always.
  • The installation instructions and the admin guide now point at the new addresses.

July 2026 — pilot launch

  • Embeddable widget (/v1.js) with AI disclosure, dated citations, always-visible human hand-off and OAC phone/hours footer.
  • Hybrid search over official sources with nightly re-indexing.
  • Honest refusal + automatic hand-off email to the citizen office.
  • Admin panel: sources, conversation review, hand-offs and the unanswered-questions report.
  • Languages: ca/es/en widget; answers in the citizen’s language.
  • Per-IP rate limiting and per-town API keys.

Service updates deploy behind /v1.js: no action ever needed from councils.