Changelog

# Manage automations from an AI client

• Connected AI clients can now list, create, update, and delete automation rules on standalone workspaces, and inspect run history.
• Call describe-automation-options first so triggers, conditions, and actions stay valid.
• New rules over MCP require an explicit enabled/disabled choice so nothing goes live by accident.
• How-to: Manage RagChat from an AI client (MCP) and Set up automations.

# Delayed automations and Events since trigger

• Rules can wait up to 30 days after a trigger before they run (Run → After a delay).
• Conditions are checked when the trigger fires and again when the delay ends. Turning a rule off cancels waiting runs.
• New condition Events since trigger (include / do not include) looks at events that landed between the trigger and the run, so you can nudge only if something has not happened yet.
• See Set up automations.

# Fix: AI clients can see message attachments

• Connected AI clients now receive message attachments when they read a thread (screenshots, PDFs, image-only messages).
• See Manage RagChat from an AI client (MCP).

# Contact events in the inbox and automations

• Connected apps can post named events for a contact (install, uninstall, import, and similar).
• Open a conversation and check the shopper panel for an Events timeline when any have arrived.
• New automation trigger Event received. Condition on Event name (and optionally Event data) to react to one event.
• How-to: Manage conversations in the inbox · Set up automations

# Run automations when a conversation needs attention

• New trigger: Conversation needs attention. It fires at the same moment as the alert email (customer asked for a human, the AI could not answer, or a message is waiting with AI off), even if that email is turned off. Use Alert reason to narrow it.
• Send a webhook actions can now include an optional bearer token (Authorization: Bearer). The URL must be https when a token is set.
• How to build a rule: Set up automations.

# Fix: unread and unresolved counts were higher than the inbox list

• Opening the chat widget starts a conversation before the visitor types anything. The inbox has always hidden those empty chats, but the unread and unresolved counts were still adding them up, so the number could be much higher than the list it pointed at.
• Counts now follow the same rule as the inbox list, so a count can no longer outnumber the conversations you actually see.
• This includes the workspace counts a connected AI client reads. See Manage RagChat from an AI client (MCP).

# Run your inbox from Claude and other AI clients

• Connect an AI client to RagChat and let it read conversations, reply, add internal notes, resolve threads, edit tags, and block contacts.
• Setup moved to Settings → General → MCP server. No token to copy: you approve the client in your browser once, and that approval covers every workspace you belong to.
• Shopify stores can connect now too. Help center tools stay standalone-only.
• Review or revoke connections from your name menu on app.ragchatai.com, under Connected apps.
• Full guide: Manage RagChat from an AI client (MCP).

# Conversation tags now show in the inbox list

• Tags appear on their own line in each conversation row, so you can spot a topic without opening the thread.
• Every tag carries its own colour dot, assigned automatically when the tag is created.
• Rows stay tidy: the first three tags show, the rest collapse into a +N count.

See Manage conversations in the inbox.

# Fix: the AI read raw settings values out to customers

• When the assistant looked something up, it sometimes repeated the raw result to the shopper, field names and all ("import_limit: null", "notify_via_email is set to 0").
• It now translates what it finds into plain language, and never shows field names, codes, IDs, or raw true/false values in a reply.

# You now get told when email sending is paused

• If your bounce or spam-complaint rate gets high enough that we pause email sending, we now email your store contact address to explain what stopped and why. Before this, sending just went quiet.
• A red banner appears above the email toggles in Settings → General and Settings → Notifications while the pause is on.
• Once support restores sending you get a second email, and your delivery record starts fresh from that day so the old bounces cannot pause you again.
• Read the guide

# Fix: the AI could still reply after you blocked someone

• Blocking a contact while the assistant was already working on a reply could let that one last reply through.
• The assistant now re-checks the block right before it answers, and again before it sends, so nothing reaches someone you have blocked.
• Read the guide: Block a contact.

# Block a contact

Spammers and abusive visitors can now be shut out of your inbox.

• Open their conversation, then More actions → Block contact.
• Their chat messages, email replies, and support emails stop arriving, and the AI never answers them.
• They aren't told they were blocked, so an anonymous visitor has no reason to come back with fresh browser data.
• Unblock at any time. Everything they wrote while blocked is handed back to the thread.

Read the guide

# Fix: long code blocks stretched chat messages in the widget

A message containing a long code snippet made every message in that chat thread render too wide, with the right side cut off and no way to scroll to it. Code blocks now stay inside the message bubble and scroll on their own.

# Custom data on contacts

• Define your own fields on contacts (text, number, yes/no, or date) under Settings → Contact attributes.
• Fill them in per contact from the Custom data section in the inbox sidebar, so your team keeps the context it needs.

Read the guide

# Contacts page: see and message everyone you've talked to

• A new Contacts page lists everyone who has chatted with you or shared their details, most recently active first.
• Search by name, email, or website, and filter by All, Customers, or Leads.
• Click any contact to open their conversation, even starting a brand-new one so you can reach out first.

Read the guide