After your shop has been installed for a week and the AI has answered enough shopper conversations, RagChat may show Shopify's own App Store review modal while you are idle in the Dashboard or Inbox.
Shopify owns the modal wording and rate limits. Declining stays quiet, so you are not asked again on the same visit.
#
AI clients can read contact events and update AI instructions
new
A connected AI client can now read the event timeline for the contact behind a conversation (installs, imports, plan changes), the same events shown in the inbox Events panel.
It can also read and update your AI's custom instructions from Settings → AI, on any workspace. An update replaces the whole text and returns the previous version so it can be undone. Updates need a plan with custom instructions.
#
Fix: welcome-only conversations counted as unresolved
fixed
A conversation that holds only automated messages, such as an install welcome or a follow-up nudge from an automation, now stays resolved, so it no longer inflates your unresolved count.
It reopens as soon as the contact writes back.
These threads don't ask for a satisfaction rating or fire a Conversation resolved trigger.
Immediate automations with Block the contact now run before the AI starts a reply, so spam is blocked without burning a generation or getting an answer.
Message subject conditions match the real subject on inbound email (including mail to your support address).
Empty cold emails (no body and no attachments) are dropped before a contact or conversation is created.
#
Fix: contact-form emails from no-reply addresses were dropped
fixedimproved
Emails that arrive from a no-reply address with the real person in Reply-To (like the Shopify App Store contact form) now reach your inbox, filed under that person, with a via label showing the address they came through.
Automated email (out-of-office replies, helpdesk updates, no-reply notices) now lands in your inbox labelled Automated email, no AI reply instead of being discarded. The AI never answers it. Only bounce notices are left out.
#
Automated emails only go to contacts who have emailed you
improved
Automated messages (welcome and follow-up automations, and rating cards) are now emailed only after a contact has emailed you at least once. A chat message alone is no longer enough for those emails.
Your replies and AI replies are unchanged: they still email offline contacts who have written by chat or by email.
Automated messages still appear in the widget for chat-only contacts.
#
Email replies only go to contacts who have written
improved
Outbound email (offline replies, automation messages, and rating cards) now goes only to contacts who have sent you at least one message by chat or email.
Messages still appear in the widget for contacts who have never written. Once they write, earlier unread messages go out in the next email.
#
Fix: automations could fail when many events arrived at once
fixed
Automations that fire on contact events could stop running when a host posted many events at once. Those jobs now wait their turn and skip rules that already ran or no longer match.
#
Connect the widget on page load for identified visitors
new
Hosts that embed the widget with a signed identity can set data-auto-connect="true" on the embed script so the widget connects on page load instead of waiting for the first open.
That lets a message you send first (for example an onboarding automation) show a badge, preview, and chime before the visitor opens chat.
Off by default. Without a signed identity the flag is ignored, so anonymous storefront visitors are never connected just from loading a page.
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.
#
Run automations when a conversation needs attention
new
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.