Hebrew is not English with the direction flipped. An AI agent that treats RTL as a CSS afterthought breaks in ways that quietly cost sales — mixed-direction product names, prices on the wrong side, and intent that gets lost the moment a shopper writes the way people actually write.
Mixed RTL/LTR is the normal case, not the edge case
Real Hebrew stores are full of Latin brand names, model numbers and units inside Hebrew sentences. “שולחן Oak 90×60” has to render and be understood without the digits or the brand jumping to the wrong place. An agent built RTL-first handles this in the message, the product card and the cart — consistently.
Currency and numbers carry meaning
₪1,890 is not “1,890 ₪” rendered backwards. Placement, the shekel sign, thousands separators and the direction of the surrounding sentence all have to be right, or the shopper subconsciously trusts the store a little less. Multiply that across every reply and it shows up in conversion.
Intent detection across real languages
- Hebrew, Russian and Arabic shoppers often mix languages mid-sentence
- typos and transliteration are the norm, not noise to reject
- the agent must keep intent when the script and direction change
- fallback should be a graceful handoff, never a dead end
WooAI is built and tested on Hebrew RTL stores before anything else, then extended outward. RTL is not a theme setting bolted on at the end — it is the assumption the agent starts from.