Changelog
Every update to Arbyn, newest first. Features, improvements, fixes, and behind-the-scenes work, all in one place.
A toggle next to a conversation's message log now translates the whole thread into a language you choose, for your reading only. It does not touch what gets sent to the customer, only what you see on screen. Each translated message carries a small note and a one click way to see the original, and switching the toggle off reverts the whole thread instantly with no delay.
Your admin now has an Integrations page. The first entry on it is your Shopify Markets setup: a single control for whether the chat widget should automatically follow the language of the storefront each shopper is browsing. Everything else on this page is a connection to an outside service; this one is built into Shopify itself, which is why it comes first.
A shopper in Germany writing "Ich moechte von meinem Widerrufsrecht Gebrauch machen" is exercising a statutory right to withdraw from a purchase. Arbyn was reading that as a question about your policy, so it answered by explaining the policy and asking for an order number, instead of treating it as the cancellation request it is. The same sentence in English worked. That difference is the part worth explaining, because it was not a translation gap. Arbyn knew plenty of ways customers say "return" and "cancel" in nine languages. Nobody had taught it how people say "exercise" a right, in any language at all. English happened to pass for an unrelated reason, which made the whole thing look healthy from the outside. Both halves are fixed. Arbyn now recognises the request across German, French, Spanish, Italian and Dutch, and the withdrawal link is attached on its own terms rather than depending on how the reply happened to be worded. A shopper who is genuinely just ASKING how long they have to change their mind still gets a straight answer, with no request for an order number.
The markets section of your Knowledge area now lists every market you sell into, along with its currency, storefront address, product catalog and tax or duty treatment, so you can see at a glance which markets are genuinely active and how they differ from each other.
Every email Arbyn sends you now follows the language you chose inside the app. If you set Arbyn to Portuguese, your welcome letter, your alerts and your digests arrive in Portuguese, not just the buttons around them. One email already worked this way. The rest could not, for a reason worth being honest about: the part of Arbyn that builds those emails was never given the ability to translate them. It was not a setting anyone had switched off. It simply could not, and nothing reported that. Twenty one emails now speak all twenty one languages Arbyn supports. If a phrase has not been translated yet, that line falls back to English rather than arriving blank. We also found and fixed a Thai email that had our own name written into it by hand, so a store that had renamed its assistant saw the wrong name. It now uses yours.
When Arbyn detects that your chat widget is not loading, it emails you and tells you to open your theme editor and toggle the app embed off and on. Opening the theme editor renders your storefront, and rendering your storefront is exactly what tells Arbyn the widget is alive. So following our own instructions marked the problem solved whether or not it was. A real merchant did exactly that, and every screen in Arbyn turned green while no customer could still see the widget. The check now ignores the theme editor entirely, using Shopify's own signal for it. The editor preview still works and still shows you the widget. It just no longer counts as a customer having seen it. Alongside that, the daily storefront check Arbyn already ran was being recorded and read by nothing. Three screens now read it: the setup step on your Command Center, its warning banner, and the widget status in Settings. A store that rendered the widget once in July used to read as live forever. A fresh check taken today now outranks that. Only a confirmed failure counts against you, because a storefront we could not reach, or one behind a password, is not evidence that anything is broken.
This card in your Knowledge Center read from a field that nothing has ever filled in, so it has been empty on every store since it shipped. Rather than leave a card that can only ever say nothing, it is gone until Arbyn genuinely records where your customers order from.
Arbyn now has three plans instead of two. Starter is still free with 150 AI conversations a month. Agent is still 99 dollars a month for unlimited. Between them sits Arbyn Growth, 59 dollars a month or 600 dollars a year, for 500 conversations. It exists because the step from free to 99 dollars was too big for a store that outgrows 150 and does not need unlimited. Every feature is still on every plan. The plans differ by how many conversations the AI handles for you and by nothing else, which is the same promise Arbyn has always made, just with a step in the middle. Nothing is metered per resolution, per seat or per message, and there are still no overage charges of any kind. At your limit, new conversations queue for your team until the first of the month or until you upgrade. Yearly billing is a real discount on both paid tiers: 600 dollars against 708 on Growth, and 990 against 1188 on Agent, which is exactly two months free. The email Arbyn sends when you reach your limit now points at the right next step rather than always naming the most expensive one, and the plans article in the help centre has been rewritten.
The Translate button in the reply box named no language, so you had to click it to find out what you would get. It now names the language before you click, written in your own admin language, and a picker beside it lets you choose the language you want when the detected one is not what you want. Shorten was also added to that toolbar. It had existed for some time and no button had ever been connected to it.
Arbyn was reading the first hundred of your metaobjects in alphabetical order and showing eight of each type. On a store with 266 metaobjects across 33 types, 18 of those types never reached it at all, including every question and answer pair the merchant had written by hand. That is worse than being cut short. Arbyn could not learn those types existed, so it never knew to go and fetch them. It now sees a complete index of every type and how many of each you have, samples the most recently updated of each, and is told by name which tool retrieves the rest.
The customer profile part of your Knowledge score was only counting an older kind of stored note, and could not see the newer, more detailed customer information Arbyn has been building, like preferences, sizes and relationships. That meant the score could tell you your customer knowledge was thin at the very moment it had grown, and point you toward work that was already done. It now counts both, and still ignores anything that has expired or been replaced by a more recent detail, so the number cannot be propped up by something Arbyn no longer believes.
When a customer asks for something under a certain price, from a certain brand, in a certain category, or in stock only, that constraint is now applied across your entire catalog before Arbyn ranks results, instead of only to the handful of products a first pass happened to surface. Previously a shopper could ask for anything under 200 dollars on a store that carried dozens of qualifying products and be told there was nothing, an answer that was only true about the few products Arbyn happened to look at. This update also adds typo tolerance, so a misspelled product type still finds real matches, and accent insensitive matching, so shoppers typing in any of Arbyn's supported languages reach the same products regardless of accents. Searches also no longer come back completely empty handed: when nothing matches exactly, Arbyn now offers the closest real products and says plainly what they do not meet, instead of a bare "we don't have that."