# Tyra — Full Site Content ## Home (/) **Title:** Tyra - WhatsApp Business Platform for Customer Communication ### Your AI-Powered Customer Communication Hub Unify WhatsApp, Instagram & Facebook in one inbox. Automate with visual workflows, collect feedback with CSAT surveys, and let AI handle the rest. ### FAQ **How easy is it to migrate to your system?** Switching to Tyra is simple and hassle-free. Our team ensures a smooth and secure transition, assisting with data migration and system setup. With comprehensive guides and dedicated support, you'll be up and running in no time - so you can focus on engaging your customers, not technical hurdles. **How do you ensure the security of customer data?** Tyra prioritizes data security with end-to-end encryption, ensuring that all customer conversations remain private and protected. We comply with industry-leading security standards, implement strict access controls, and regularly update our systems to safeguard against threats—so your business and customer data stay secure. **Can Tyra manage customer messaging for businesses in different countries?** Absolutely! Tyra supports international messaging, enabling businesses to connect with customers worldwide. Our AI-powered translation feature automatically translates incoming messages into the agent's language and translates responses back to the customer's language in real time. **What kind of customer support does Tyra offer?** We provide customer support via email, live chat, and an extensive help center with detailed guides and tutorials. Our team is always ready to assist with troubleshooting, setup, and best practices. **Can Tyra handle messaging compliance across different regions?** Yes! Tyra supports region-specific messaging compliance, ensuring that your business adheres to local regulations on platforms like WhatsApp, Instagram, and Facebook. ### Ready to transform your customer communication? Start your free trial today. No credit card required. --- # Instagram DMs for European Shopify brands **URL:** `tyra.ai/instagram` **Meta title:** Instagram DMs for Shopify Brands in Europe | Tyra **Meta description:** Tyra pulls Instagram DMs, story replies, mentions, and comments into one EU-hosted inbox with WhatsApp, email, and SMS. Shopify-native, Ireland data, AI grounded in your live catalog. # Instagram DMs for European Shopify brands Tyra puts WhatsApp, Instagram, email, and SMS in one inbox, hosted in Ireland and wired into your Shopify catalog so the AI agent answers from real stock instead of guesses. Book a demo: https://cal.com/tyra/demo ![Hero — Tyra inbox showing Instagram DM with Shopify product context](/screenshots/hero-instagram.png) ## Your support lead is tab-switching between Gmail, the WhatsApp web app, and Instagram on her phone That is not a workflow. That is a person remembering, by hand, that the customer who emailed about a wrong size on Tuesday is the same one who DM'd on Sunday about the original order. She gets it right most of the time. The cost of the times she does not is a refund, a one-star review, or a customer who quietly stops opening the newsletter. Every Shopify brand we onboard has some version of this person, and every one of them is doing heroic work to compensate for software that treats four channels as four problems. ## The DM tab gets checked at 9am and at 6pm, and that is the whole reply SLA Meta's own merchant research keeps landing on the same number: shoppers expect a reply inside an hour on social, and most brands answer somewhere between four hours and the next morning. The gap is where the cart gets abandoned. The DM that asked "is this back in stock in 38?" at 2pm gets answered at 9am the next day, by which point the customer has either bought from someone else or moved on. Notifications are not an inbox. A notification badge that reads 47 is a synonym for "nobody has triaged this since lunch." ## Story mentions vanish in 24 hours and so does the goodwill A customer reshares your product to her story. That is the cheapest, warmest UGC you will ever get, and the window to reply is the lifetime of the story. Miss it and you have lost the moment to send a thank-you, a code, a repost permission ask. Most brands miss it because story mentions live in a separate notifications tray that nobody opens before the 24 hours are up. We see this on almost every audit: dozens of mentions a month, near-zero replies, no UGC pipeline downstream. ## A reel goes viral and the inbox is unusable for a week A creator posts about you, or one of your own reels takes off. Comments pile up, half of them ask "where can I buy this?", a third are friend tags, the rest are influencer pitches and the occasional scam. Real buying intent gets buried under noise. The team either burns a day reading every comment, or gives up and lets the post coast. Both options cost money. There is no manual moderation strategy that scales past a few hundred comments on a single post, and "we will get to it on Monday" is not a strategy at all. ## EU-built Tyra runs in AWS Ireland, eu-west-1. Conversation bodies, customer attributes, order history, agent transcripts, audit logs: all stored in the EU, no replication to US regions for storage. Meta still processes the underlying Instagram traffic under its own DPA before it reaches us via the Graph API, and we are precise about that distinction in our own DPA so your DPO does not have to translate marketing copy into a real answer. Right-to-be-forgotten requests are scrubbed from Tyra's systems inside 24 hours. Sub-processors are listed, named, and dated on a public page; when one changes you get an email rather than a footnote update. For a Shopify brand selling into Germany, France, or the Nordics, this is the difference between a procurement review that closes in a week and one that drags into the next quarter. ![Pillar — EU-built infrastructure with Ireland hosting and sub-processor transparency](/screenshots/eu-built-instagram.png) ## WhatsApp first-class Instagram is the discovery channel. WhatsApp is where the conversation often continues, especially in Germany, Italy, Spain, the Netherlands. A customer DMs on Instagram, then a day later messages your WhatsApp number from the link in your bio. In most tools those are two unconnected threads with two unconnected histories. In Tyra they are the same customer record with both channels stacked in one timeline, and the next reply can go on whichever channel the customer last used. We are an official BSP through 360dialog, so WhatsApp templates, interactive buttons, product messages, and the 24-hour service window all work the way Meta intends. Outbound order updates, abandoned cart nudges, and post-purchase flows go on WhatsApp where they get opened, not buried in promotional email. None of this is bolted on after the fact: WhatsApp was the first channel we built, and Instagram was added once the inbox primitives could carry it properly. ![Pillar — WhatsApp and Instagram threads unified per customer with channel badges](/screenshots/whatsapp-first-instagram.png) ## Shopify-native When a DM comes in, the right-hand panel renders the live Shopify customer: past orders, lifetime value, current cart, address, tags. When the AI agent or a human sends a product card, the image, price, and variant stock are pulled from Shopify at send time, not from a cached export that went stale last Thursday. If a variant drops to zero between selection and send, Tyra rechecks and either swaps the variant or offers the customer a back-in-stock opt-in. Instagram's Messaging API caps product carousels at 10 cards. We respect that cap. We also link the "buy" action to your real Shopify checkout rather than an in-app shopping surface that is not available in most EU countries. Refunds, order edits, and cancellations execute against Shopify with one click from the side panel, and the action shows up in the conversation timeline so the next agent or the AI knows it happened. ![Pillar — Shopify side panel with live inventory, order history, and one-click actions](/screenshots/shopify-native-instagram.png) ## AI that actually works The agent is grounded in your Shopify catalog, your help center, your shipping policy, and your return policy. It is not grounded in the open internet, and it cannot name a product that does not exist in the connected store with positive stock. We learned that lesson the hard way in the first build, when the agent confidently recommended a SKU we had discontinued six months earlier. The rewrite fails closed: no catalog match, no product name, full stop. Intent classification routes refunds, complaints, legal mentions, and any message where the model's own confidence drops below threshold straight to a human queue. The agent replies in the language the customer wrote in, across the twelve EU languages we currently support. It will not promise a shipping date it cannot verify, will not argue with an upset customer, and will not extend a conversation past a second clarifying question without offering a human handoff. On the brands we have measured, it closes between 40 and 60 percent of inbound DMs without escalation, and the share is higher for stores with clean catalog data and a real returns page. ![Pillar — AI agent reply drafted from live Shopify data with confidence and escalation controls](/screenshots/ai-instagram.png) ## FAQ ### Does Tyra work for personal Instagram accounts? No. Meta requires an Instagram Business or Creator account linked to a Facebook Page for Messaging API access. If yours is not set up yet we walk you through the conversion during onboarding, which usually takes about ten minutes. ### How does Tyra stay inside Instagram's 24-hour messaging window? We track the window per conversation and show the remaining time in the inbox. After 24 hours we will not let you send a free-form message; the only outbound options are approved message tags, mainly HUMAN_AGENT for verified support cases. The system enforces this so a tired agent at 11pm cannot accidentally torch your account's standing with Meta. ### Can Tyra send cold DMs or broadcast promotions outside the window? No, and any tool promising this is either lying or actively risking your account. Comment-to-DM automation works because the user's comment opens a messaging window. Cold DMs to people who have not engaged are a policy violation. We get asked to bypass this monthly and the answer is always no. ### What happens when a viral post or campaign floods the inbox with influencer pitches? The agent classifies inbound DMs into buckets like real customer question, press or collab pitch, fan message, and spam. Customer questions get the full agent treatment with catalog grounding. Press pitches route to a dedicated queue for a human to handle on their own schedule. Fan messages get a templated thank-you. The point is to keep the buying-intent DMs from drowning. ### How do story mentions get handled? Tyra catches the story mention webhook in real time and triggers whatever flow you configure: a thank-you with a discount code, a permission-to-repost request for your UGC pipeline, or a follow-up offering a referral code. The reply lands while the story is still live, which is the only window where any of it matters. ### Where exactly is customer data stored? Conversation content, customer attributes, and order context are stored in AWS Ireland, eu-west-1, with no replication to US regions for storage. Meta processes the underlying Instagram traffic under its own DPA before it reaches us through the Graph API. We publish a current sub-processor list and notify customers by email when it changes. ### Can the AI agent answer in Italian or Swedish if the customer writes in those languages? Yes. Language is detected per message and replies match. We currently support twelve EU languages with first-class quality. If a customer switches mid-thread the agent switches with them. ### Does Tyra replace Meta Business Suite or sit alongside it? Both tools can read the same DMs since Meta's API allows multiple readers. Most teams use Tyra as the primary inbox for triage, agent replies, and Shopify actions, and dip into Business Suite occasionally for things outside our scope like ad creative review. We do not schedule content; tools like Later and Buffer own that category. ## Book a demo https://cal.com/tyra/demo --- # Cart recovery on WhatsApp for European Shopify brands **URL:** `tyra.ai/shopify/cart-recovery` **Meta title:** WhatsApp cart recovery for European Shopify brands | Tyra **Meta description:** Tyra catches abandoned Shopify carts on WhatsApp, answers the shipping question that caused the drop-off, and keeps your German checkout compliant. EU-built, Shopify-native, EU-hosted. # Cart recovery on WhatsApp for European Shopify brands Tyra is one inbox for WhatsApp, Instagram, email, and SMS, built for European Shopify merchants and hosted in Ireland. This page is about what we do for abandoned carts. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra cart recovery message and Shopify order context](/screenshots/hero-cart-recovery.png) ## The Klaviyo email that gets opened at 9am tomorrow The thing that actually happens with email cart recovery in 2026 looks like this. A customer adds a €140 jacket to cart at 8:47pm, gets distracted by a notification, closes the tab. Klaviyo fires the abandoned cart flow at T+1h. The email lands in Promotions at 9:47pm, behind seventeen other newsletters. The customer opens Gmail the next morning, scrolls past it, and the intent is gone. Baymard's 2024 cart abandonment research puts the average abandonment rate at 70.19%, and the chunk that ever gets recovered through email sits around 4-10% depending on list quality. The rest is just lost. WhatsApp does not have this problem because the phone is two centimetres from the customer's face and the open rate Meta publishes is 98% with a sub-three-minute median time to read. The catch is that you have to be on it the moment the cart drops, and you have to answer when the customer writes back. ## The shipping question nobody answers The second failure mode is more annoying. A customer abandons because they could not work out whether shipping was free to Austria, so they replied to the recovery email asking. The reply went to a noreply@ address, or it went to a support inbox that gets cleared once a day by someone in a different timezone. By the time anyone sees it, the customer has bought from a competitor. Baymard has shipping cost and delivery time as the number one and number two stated reasons for abandonment for six years running, and most cart recovery tools still treat the message as a one-way broadcast. ## Coupon codes leaking to Honey and RetailMeNot The third one is the discount you generated for one customer ending up on a coupon aggregator within hours. If your cart recovery flow uses a static code like `COMEBACK10`, it is on RetailMeNot by next Tuesday and every full-price customer who installs the Honey extension now gets 10% off. The merchants we work with were losing more margin to leaked codes than they were recovering through the discount drops themselves. ## German checkouts that will not survive an audit The last one is specifically European. A German Shopify store with a pre-ticked WhatsApp opt-in box at checkout is collecting consent that is not consent. The Planet49 ruling at the CJEU in 2019 made that explicit, and German competitors have been using §7 UWG complaints as a marketing weapon ever since. We have seen merchants get a formal Abmahnung over a single pre-ticked box, with five-figure legal costs attached. Most non-EU cart recovery tools ship with pre-ticked defaults because that is what optimises US conversion rates. ## EU-built Tyra runs in Ireland on eu-west-1. Customer data, conversation history, consent records, message content, none of it leaves the EU. The DPA we send merchants is the standard SCC-free one because there is no third-country transfer to begin with, which makes the legal review at any brand with a competent DPO take an afternoon instead of three weeks. The opt-in flow at checkout uses a Shopify checkout extension we wrote, and the checkbox is unticked by default with channel-specific wording ("I agree to receive cart and order updates on WhatsApp from {brand}"), separate from the order T&Cs. We capture the timestamp, the IP, and the exact wording version per customer, and we export the lot as a CSV for audits. STOP replies unsubscribe within one second across every future template, and the audit log shows when. ![Pillar — Tyra GDPR-compliant opt-in at Shopify checkout](/screenshots/eu-built-cart-recovery.png) We also will not send marketing messages to phone numbers that did not opt in, even if the merchant asks. One German skincare brand asked us to enable "all customers with a phone number" as the eligible segment last autumn. We said no, they were annoyed for a week, and then their lawyer ran an audit two months later and the merchant thanked us. The fines are not worth it for them and the Meta suspension is not worth it for us. ## WhatsApp first-class WhatsApp is the channel Tyra was built around, not a tab we bolted on next to email. We use the WhatsApp Business Platform directly, which means template messages for the outbound recovery and free-form replies within the 24-hour customer service window for everything that comes back. Templates are pre-translated into the twelve EU languages most of our merchants ship to, pre-approved with Meta, and the language is picked from the browser locale Shopify captured at checkout. The first recovery message goes out at T+1h, with the product image, the cart resume link, and the shipping threshold inlined. Something like: > Hi Lena, your cart at Vanami is saved. Free shipping over €75 to Austria, 2-4 business days. Resume here: vanami.com/c/... If that does not recover, the second message at T+24h carries a single-use discount code generated through Shopify's `priceRule` and `discountCode` APIs at send time, scoped to that customer's email, valid for 24 hours. It cannot leak to Honey because it does not exist until we send it and it stops working once the customer uses it. We stop after two messages. Message three recovers under 1% incrementally in our data and the STOP replies it generates hurt your Meta sender quality, which then drags down deliverability on the messages that actually work. ![Pillar — WhatsApp cart recovery thread with one-tap checkout](/screenshots/whatsapp-cart-recovery.png) ## Shopify-native Tyra is a Shopify app, installed from the App Store, authenticated through Shopify OAuth. We listen to `checkouts/update` for the abandonment trigger and `orders/create` to cancel queued messages if the customer completes between abandonment and T+1h. Median webhook-to-inbox latency is around 800ms. Every conversation in the Tyra inbox shows the full Shopify customer context next to the messages: lifetime order count, last order date, current cart contents with variant and SKU, fulfilment status if there is an open order, and the shipping address. The recovery links carry a UTM tag (`utm_source=tyra&utm_medium=whatsapp&utm_campaign=cart_recovery`) plus the Shopify checkout token, so recovered revenue lands in your Shopify reports under the right campaign without you wiring up anything. ![Pillar — Shopify customer and cart context inside the Tyra inbox](/screenshots/shopify-native-cart-recovery.png) Discount codes, customer tags, and order notes all round-trip into Shopify. If the AI agent promises a discount or applies a tag during a conversation, it shows up on the customer record in Shopify admin within seconds. ## AI that actually works The agent is grounded in your live Shopify catalogue and your shipping and returns policies, which is the part that matters. When a customer replies "is shipping free to Austria" the agent reads the real shipping zones from your Shopify settings and answers with the actual number, not a hallucinated one. When they reply "when does it ship" the agent checks inventory and your stated dispatch lead time and gives a real date range. About 12-18% of our WhatsApp cart recoveries involve a reply before checkout, and most of those replies are one of three questions: shipping cost, shipping time, or "does this come in size M." > Customer: is shipping free? > Agent: Free over €75 to Austria, otherwise €4.90. Your cart is at €58 right now, one more item gets you free shipping. Want me to send a couple of suggestions under €20? The agent escalates to a human inbox the moment a message mentions a refund, a complaint, a damaged item, or anything that looks like a chargeback risk. It also escalates on explicit anger and on anything it is not confident about. The escalation rules are visible and editable, not a black box. We would rather over-escalate than have the agent invent a returns policy. ![Pillar — AI agent answering a shipping question grounded in Shopify](/screenshots/ai-agent-cart-recovery.png) It is not magic and we do not pretend it is. The agent handles roughly 70% of replies fully autonomously across our current merchant base, the rest land with a human. The 70% is what frees a small team to actually run the brand instead of typing "shipping is €4.90" into WhatsApp forty times a day. ## FAQ ### How long after abandonment does Tyra send the first message? One hour by default. We have tested 15 minutes, 30 minutes, one hour, two hours, and six hours across our merchant base. One hour wins on recovery rate consistently, and it is far enough away from the abandonment that customers do not feel watched. ### Do I need WhatsApp Business API, or is the regular WhatsApp Business app enough? You need the API, what Meta calls WABA. The regular WhatsApp Business app does not support template messages, automation, or webhooks. Tyra walks you through Meta's Embedded Signup during onboarding, which takes about eight minutes and does not require talking to a Meta sales rep. ### What happens to customers who do not give a phone number at checkout? Shopify makes phone optional at checkout by default. Without a number there is no WhatsApp recovery, so those customers fall back to your existing Klaviyo email flow. We recommend making phone a required field for shoppers in countries where WhatsApp adoption is over 80%, which in the EU means Spain, Italy, Germany, the Netherlands, and most of Eastern Europe. ### Does this replace Klaviyo? No. Klaviyo is still better for newsletters, brand storytelling, and anything long-form. We tell merchants to run WhatsApp at T+1h and T+24h on Tyra, then let Klaviyo's email flow take over at T+72h as a longer-tail fallback. Both attribute correctly in Shopify. ### What does WhatsApp cost per message? Meta charges per-conversation, not per-message, with the rate set by recipient country and updated quarterly. For the EU it currently runs roughly €0.04-€0.08 for a marketing conversation initiated by your brand, with the 24-hour service window after a customer replies being free. Tyra passes Meta's rate through with no markup. ### How do you stop messages if the customer checks out between abandonment and T+1h? Automatically. The `orders/create` webhook fires, Tyra cancels any queued recovery message for that cart, and the customer never gets it. The cancellation shows up in the audit log next to the original queue event. ### Is the AI agent going to invent a returns policy or hallucinate a product? No, and this is what most of the early agent demos got wrong. Our agent is grounded in your Shopify catalogue and policy documents, with retrieval at every turn. If it does not have a confident answer, the escalation rules send the conversation to a human. We would rather miss a recovery than have the agent promise something you cannot deliver. ### What about B2B Shopify stores? The recovery flow described here is built for B2C. B2B carts on Shopify behave differently, with longer cycles, multiple stakeholders, and often manual payment terms, and the same one-hour nudge does not fit. Tyra supports B2B but the flows look different. Worth a conversation if that is your model. ### How long does setup take? About 30 minutes of active work. Three minutes to install the app from the Shopify App Store, eight for Meta's Embedded Signup, five to review the prefilled templates, five for the checkout opt-in extension, five to configure the flow. Then a wait of one to four hours for Meta to approve your first templates. [Book a demo](https://cal.com/tyra/demo) --- # Tyra for Shopify **URL:** `tyra.ai/shopify` **Meta title:** Customer conversations for European Shopify brands | Tyra **Meta description:** Tyra unifies WhatsApp, Instagram, email, and SMS into one inbox for Shopify stores. EU-hosted in Ireland, Shopify-native, and grounded in your live catalog. --- ## Customer conversations for European Shopify brands WhatsApp, Instagram, email, and SMS in one inbox, wired into your Shopify store and hosted in Ireland. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra inbox showing a WhatsApp thread next to order #1023 and the customer's last three orders](/screenshots/hero-shopify.png) --- ## Your support reps juggle Gmail, WhatsApp, and the Instagram app Most of the Shopify brands we talk to are running customer service across four or five browser tabs and a phone on someone's desk. A return question comes in on Instagram DMs, the answer lives in a Gmail thread from three weeks ago, and the order itself is in Shopify admin. Nothing connects. The same customer gets answered twice, in two different tones, by two different people. We built Tyra because that mess is the actual job, and nobody was solving it for European Shopify stores specifically. One inbox. Every channel. The order context sitting right next to the message, so your team stops alt-tabbing to find out what someone bought. ## Your DPO won't sign a US-hosted DPA anymore Schrems II didn't go away. The Trans-Atlantic Data Privacy Framework is one court case from being unwound again. If your data protection officer has started flagging US-hosted tools, they are right to. We've watched merchants get six months into a Gorgias or Zendesk rollout and then have to rip it out because legal won't sign. Tyra runs in AWS Ireland. Message content, customer profiles, and conversation history never leave the EU. Our DPA is the kind your DPO can actually read and sign without a back-and-forth that lasts a quarter. ## Klaviyo doesn't speak Dutch the way your customers do If you sell in Sweden, the Netherlands, Germany, France, or Italy, you already know the gap. English-first tools translate, but they translate badly, and your brand voice gets flattened into Google Translate prose. Customers notice. Open rates drop. Replies get curt. Tyra's agent and template library are built in the languages your customers actually use. Not auto-translated. Reviewed by native speakers. The difference shows up in reply rate within the first week. ## Your WhatsApp setup is stuck in a sales-led queue somewhere Every other WhatsApp tool we know of routes you through a Business Solution Provider sales motion before you can send a message. That's two weeks of emails and a discovery call to send a shipping update. Because Tyra is a Meta BSP directly, you go through Embedded Signup inside our product and you're sending the same afternoon. --- ## EU-built Tyra is hosted in AWS Ireland (eu-west-1). All message storage, customer data, and conversation history stays in the EU. We don't route through US sub-processors for core data, and we don't rely on the Trans-Atlantic Data Privacy Framework holding up in court for our compliance story to work. The LLM calls our AI agent makes run through EU endpoints where the providers offer them, and we'll tell you exactly which model handled which call if you ask. Our DPA is public, signed before you start a trial, and written in language a lawyer can finish in one sitting. This matters because European Shopify merchants are increasingly the ones getting audited. Your customers' phone numbers are personal data under GDPR, and a US-hosted inbox treats that lightly. We don't. ![Pillar — Tyra DPA and data residency page showing Ireland region and EU sub-processor list](/screenshots/eu-built-shopify.png) ## WhatsApp first-class We are a Meta Business Solution Provider directly. There is no reseller in the middle, no second support queue, no waiting on a partner to escalate a template approval. When Meta suspends a WABA at 2am, we have a line to their team and we're usually back up the next business day. WhatsApp inside Tyra isn't a tab next to "real" channels. It's the spine. Abandoned cart recovery, order confirmations, shipping events, post-purchase reviews, and the AI agent's first-line replies all flow through it natively. Templates are submitted from inside the product in the EU languages your customers read, and the approval status shows up in your inbox the moment Meta responds. The WhatsApp open rate in our customer base sits around 95-98%, which matches what Meta publishes publicly. Email is doing something different. WhatsApp is where the conversation actually happens. ![Pillar — Tyra WhatsApp template manager with EU language tabs and Meta approval status](/screenshots/whatsapp-shopify.png) ## Shopify-native Tyra is a proper Shopify app. Install it from the App Store, authorize the scopes, and your catalog, orders, customers, abandoned checkouts, and fulfillment events stream in over webhooks. No Zapier in the middle. No CSV exports. No "we'll have that on the roadmap next quarter." Every conversation in the Tyra inbox shows the order context on the right: line items, fulfillment status, the customer's last three orders, their lifetime value, the tags you've set in Shopify. Your team stops switching tabs to figure out what happened. Discount codes and draft orders can be generated from inside a chat, so a hesitant customer gets a working link in WhatsApp without anyone leaving the conversation. The AI agent reads the same Shopify catalog your storefront does, in real time. It doesn't get confused about whether something is in stock because it isn't working from a snapshot. ![Pillar — Tyra inbox conversation with Shopify order panel showing line items, fulfillment, and customer LTV](/screenshots/shopify-native.png) ## AI that actually works The Tyra agent is grounded in your live Shopify catalog, your help center, your shipping and returns policies, and your past resolved conversations. It answers in the customer's language. It queries Shopify in real time for stock and tracking, so it doesn't make up an ETA or promise a product you haven't had in months. It also refuses to do the things AI agents shouldn't do. It won't approve a refund. It won't argue with someone who is angry. It hands off to a human the moment a complaint, legal mention, or edge case appears, in under a second. Across our Shopify customers, the agent resolves somewhere between 50% and 65% of inbound questions end-to-end. The rest should always be a person, and we don't pretend otherwise on a sales call. You stay in control of which intents the agent handles, which it escalates, and what tone it uses. You can also turn it off entirely and run Tyra as a pure shared inbox. Plenty of our customers start there. ![Pillar — Tyra AI agent settings page with intent routing rules and live Shopify catalog grounding](/screenshots/ai-agent-shopify.png) --- ## FAQ ### Do I need a WhatsApp Business account before I start? No. We run you through Meta's Embedded Signup inside Tyra during setup. As long as you have a phone number that isn't already on personal WhatsApp, you can be sending in under thirty minutes. Meta's business verification badge is a separate process they run on their side and usually takes one to three business days, but Tyra works fully without it. ### Where does my customer data actually live? In AWS Ireland, eu-west-1. Message content, customer profiles, and conversation history stay in the EU. We publish our sub-processor list and update it whenever it changes, and our DPA is available before you sign anything. ### Will the AI agent message my customers without my approval? Only on the conversations and intents you've routed to it. You set the rules: which questions it answers, which it escalates to a human, and what tone it uses. You can turn it off completely and use Tyra as a regular shared inbox if you'd rather start there. ### Does Tyra replace Klaviyo? Not really. Klaviyo is email-first and built around campaigns and flows. Most of our customers run both, with Klaviyo handling newsletters and email automation while Tyra handles the WhatsApp, Instagram, and SMS layer plus the shared support inbox. We're honest about that overlap rather than pretending we're a one-for-one swap. ### What happens if Meta suspends my WhatsApp Business Account? It happens, sometimes for reasons Meta won't initially explain. Because we're a Meta BSP directly, we have an escalation line to their team and we usually resolve suspensions within a business day on our side. We don't promise faster than that because Meta is the one making the decision. ### How does the AI agent handle languages? It replies in the language the customer wrote in. Swedish, German, French, Dutch, Spanish, Italian, English, and a handful more are first-class, meaning the prompts and templates were written and reviewed by native speakers rather than auto-translated. If a customer switches languages mid-thread, the agent follows them. ### Can I export my data if I leave? Yes. Full export to JSON or CSV, including all conversations, customer profiles, and audit logs. No lock-in clauses in our contracts and no charge for the export. ### What does it cost? Pricing scales with the number of contacts you have, not the number of seats. WhatsApp conversation fees are passed through at Meta's published rates with no markup. Book a demo and we'll give you a real number against your store volume rather than making you guess from a pricing page. --- ## Book a demo Thirty minutes with someone who has actually set this up for a Shopify brand in your market. [Book a demo](https://cal.com/tyra/demo) --- # Order confirmations on WhatsApp for European Shopify brands **URL:** `tyra.ai/shopify/whatsapp-order-confirmation` **Meta title:** WhatsApp order confirmations for Shopify brands in Europe | Tyra **Meta description:** Send Shopify order confirmations, shipping updates, and delivery alerts on WhatsApp. EU-hosted, Shopify-native, with an AI agent that reads the live catalog and replies to post-purchase questions in the same thread. ## Order confirmations on WhatsApp, in the same inbox as Instagram, email, and SMS Tyra is the customer conversations platform European Shopify brands use to send order confirmations, shipping updates, and delivery notifications on WhatsApp, with Instagram DMs, email, and SMS landing in the same EU-hosted inbox. One CTA, one place to reply, one AI agent reading the live Shopify catalog. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra post-purchase WhatsApp thread with tracking](/screenshots/hero-order-confirmation.png) ## The order confirmation email is not doing the job you think it is A customer just paid you. They want one thing in the next ninety seconds: confidence that the order worked. The Shopify default emails this confirmation to them, and then Gmail decides where it goes. In our merchant data, between forty and fifty percent of those confirmation emails land in the Promotions tab on Gmail accounts, which is where customers do not look until they are bored on a Saturday. The brand-loyalty moment, the one you paid acquisition cost to earn, gets pushed out by eighteen hours of inbox decay. The second pain shows up two days later. The customer cannot find the tracking link, so they email support, or DM the Instagram account, or fill in the contact form. This is the WISMO ticket, and at most Shopify brands we onboard it is somewhere between eight and fifteen percent of all inbound support volume. Every one of those tickets is a customer who received a perfectly good shipping email and could not locate it again. The information existed. The channel failed. The third pain is the one merchants rarely see until it is expensive. Carrier delivery exceptions, a failed delivery attempt, a customs hold, an address mismatch, get reported by the carrier API but never relayed to the customer in a channel they actually read. The package sits in a depot for nine days, gets returned to sender, and three weeks later the customer files a chargeback for non-delivery. The merchant pays the chargeback fee, eats the shipping cost twice, and loses the customer. All of this was preventable with a single message on the channel the customer actually opens. The fourth pain is structural. Email is a one-way notification, so when the customer reads the confirmation and thinks "actually, can I change the size?", they have to start a new thread on a different channel. Most of them do not bother. The order ships in the wrong size, comes back as a return, and the brand absorbs the return logistics cost on a problem that could have been fixed in fifteen seconds before fulfillment. ## EU-built, EU-hosted in Ireland, written for European data rules Tyra runs on AWS Ireland (eu-west-1). Customer data, conversation history, consent records, and AI prompt logs stay in the EU. There is no transatlantic data hop, no US sub-processor on the critical path for message delivery, and our DPA is signed under Irish law with German DPO contact. For the German and Austrian merchants we work with, this is the difference between a procurement conversation that takes three weeks and one that takes three months. We default to explicit consent on the WhatsApp opt-in, even for transactional UTILITY templates, because the strictest reasonable interpretation of GDPR plus the ePrivacy Directive treats Meta's underlying data processing as requiring its own consent basis. The unticked checkbox at Shopify checkout captures timestamp, IP, and the exact consent wording, exportable as a CSV if a DPO ever asks. STOP replies are honored across every future message within sixty seconds of receipt and logged against the customer record. ![Pillar — Tyra EU data residency dashboard showing Ireland region](/screenshots/eu-built-order-confirmation.png) ## WhatsApp as a first-class channel, not a notification bolt-on Most Shopify apps treat WhatsApp as an outbound notification pipe. Send the template, close the loop, done. That model breaks the moment the customer replies, because the reply lands in a Meta Business Manager tab nobody on the support team has open. Tyra is built the other way around. The WhatsApp thread is a real conversation in the shared inbox, indistinguishable in the agent UI from an email or an Instagram DM, with the full Shopify order context loaded on the right-hand panel. When a shipping notification goes out, the customer sees something like this in their WhatsApp: > Hi Anna, your Order #4821 from Marais Linen is on its way. DHL Express, tracking DHLE-99172, expected Tuesday. Track it: dhl.com/track/DHLE-99172. Reply here if anything changes. When Anna replies "can you change the delivery to my office address?", that reply lands in Tyra's inbox routed to whoever owns post-purchase, with the order, the original shipping address, the carrier, and the cutoff time for address changes already in the side panel. No tab switching, no "let me look that up", no copy-pasting the order number into Shopify Admin. Template management lives inside Tyra. We pre-fill the six post-purchase templates in twelve EU languages, you tweak wording in your language, and we submit to Meta. UTILITY-category templates usually clear approval in one to four hours. Tyra tracks per-template performance, delivery, read, reply, opt-out, in the same dashboard so you can see which language variants are actually working. ![Pillar — WhatsApp thread in Tyra inbox with order context panel](/screenshots/whatsapp-first-class-order-confirmation.png) ## Shopify-native, fulfillment webhooks included Tyra installs as a Shopify app and subscribes to the order and fulfillment webhooks directly. `orders/create` fires the confirmation, `orders/paid` handles deferred-capture flows like Klarna Pay Later, `fulfillments/create` triggers the shipping message with the tracking number and carrier the fulfillment record was actually written with. Median latency from Shopify event to WhatsApp message delivery sits at three to five seconds in production. We measure it because customers notice the difference between five seconds and forty-five. Carrier-level events ("out for delivery", "delivered", delivery exceptions) come from direct carrier integrations on top of the Shopify fulfillment record. We have working integrations with PostNord, DHL, GLS, UPS, DPD, FedEx, Royal Mail, Bring, Hermes/Evri, Colissimo, Posti, and Correos. For carriers we do not integrate with, you still get the Shopify-level "shipped" event with tracking link, which covers about seventy percent of the WISMO reduction on its own. The Shopify checkout extension is one click to install and adds the WhatsApp opt-in checkbox to the contact step at checkout. The wording defaults to GDPR-compliant phrasing in the storefront language. Multi-warehouse, split shipments, and partial fulfillments each fire their own messages with their own tracking links, so the customer knows which items shipped from where, instead of getting one confusing "your order has shipped" email when only half of it has. ![Pillar — Shopify webhook configuration and fulfillment event log in Tyra](/screenshots/shopify-native-order-confirmation.png) ## An AI agent that reads the live Shopify catalog and handles the replies The interesting thing about WhatsApp order confirmations is not the outbound message. It is what happens when eight to fifteen percent of customers reply. The replies are mostly the same five questions repeated across thousands of orders: when will it arrive, can I change the address, can I add another item, did you include the gift note, can I swap the size. Tyra's AI agent answers these in the same WhatsApp thread, grounded in the live Shopify catalog, the order record, the fulfillment status, and the carrier tracking event stream. The grounding matters. The agent does not freelance about inventory or shipping times. When a customer asks "do you have this in medium?", the agent reads the live variant inventory for the product on that order, checks the warehouse the order ships from, and gives a real answer. When a customer asks "can I swap to a large?", the agent checks the fulfillment status, and if the order has not yet been picked, offers the swap and writes the modification back to Shopify through the Admin API. If the order is already at the carrier, the agent says so and offers the easy return as the alternative. When the agent does not know, it says so and routes to a human. We measure escalation accuracy, the proportion of agent-handled conversations that did not need a human follow-up, and target eighty-five percent on order-modification replies and ninety-two percent on tracking-status replies. Below those thresholds the agent escalates by default. The honest failure mode we have seen is on multi-item partial-modification requests ("change item one to a medium, cancel item three"); the agent currently escalates those, which is correct but adds inbox load. ![Pillar — AI agent reply in WhatsApp thread with Shopify catalog grounding](/screenshots/ai-agent-order-confirmation.png) ## FAQ ### Do I have to turn off the Shopify email confirmation? No, and most brands do not. Email stays on as the permanent legal-receipt record, which matters for accounting and for the customers who prefer email. WhatsApp runs on top, on the moments where engagement and reply rate matter most. The two channels coexist without conflict, and the customer reading both is a feature, not a bug. ### What happens to customers who did not opt in to WhatsApp at checkout? They get the standard Shopify email flow only. Tyra checks the consent record before every outbound message, and a missing or revoked consent means the message never sends. The opt-in capture rate at checkout sits at thirty to fifty percent for most of our merchants, which is the realistic adoption ceiling. ### Can the AI agent actually modify orders, or does it just answer questions? It can modify, within rules you set. Address changes, variant swaps, item additions, and discount applications all write back to Shopify through the Admin API. You set the cutoff (typically: until the fulfillment is created, no changes after that) and the discount ceiling. Anything outside those rules escalates to a human in the Tyra inbox with the full context preloaded. ### How does Tyra handle the German WhatsApp consent debate? We default to explicit, unticked-checkbox opt-in for every message category including UTILITY transactional, which satisfies the strictest German and Austrian DPO readings. The consent record is timestamped, IP-logged, and stores the exact wording shown to the customer. If your DPO concludes WhatsApp is too risky for transactional, you can disable the channel per market without affecting other channels in the Tyra inbox. ### What does this actually cost per order? WhatsApp UTILITY-category conversations are priced by Meta per recipient country. For a typical European order running the full sequence (confirmation, shipped, delivered, day-seven review), the all-in cost is around thirteen to sixteen cents per order in most EU markets. Tyra passes Meta pricing through without markup. The WISMO ticket reduction alone usually covers it; everything else is upside. ### How long does setup actually take? The install, WhatsApp Business connection, template submission, and Shopify checkout extension takes about thirty minutes of active work. Then Meta sits on the template approvals for one to four hours for UTILITY category. So same-day live, but not same-hour live. ### What about cancelled or refunded orders? Configurable. Most brands send a cancellation confirmation and a refund-processed notification as additional UTILITY templates. The agent also handles "where is my refund?" replies by checking the Shopify refund record and the original payment method's typical clearing time. ### Does this work with subscriptions? Partially. Standard one-time orders are fully supported. Subscription order confirmations work for the initial order; recurring renewal notifications require additional template approvals and a separate consent capture for the recurring nature of the messaging. We are deepening this for the Recharge and Shopify Subscriptions APIs through 2026. ### What if a customer replies in a language the agent does not know? The agent handles English, German, French, Spanish, Italian, Portuguese, Dutch, Swedish, Danish, Norwegian, Finnish, and Polish at production quality. Replies in other languages get translated for the agent and escalated to a human, with the original-language reply preserved in the thread for the human to read. ### Can I A/B test confirmation templates? Within Meta's constraints, yes. Pure inline A/B testing is not possible because Meta approves templates per version. Tyra supports running two approved templates against a customer-segment split, which is the practical equivalent. The honest read is that template optimization gains are smaller than channel-mix optimization gains; spend the time on which events get WhatsApp vs email, not on word-level template tweaks. [Book a demo](https://cal.com/tyra/demo) --- # Tyra for Shopify brands using Stripe **URL:** `tyra.ai/stripe` **Meta title:** Tyra for Shopify brands on Stripe — Recover failed payments on WhatsApp **Meta description:** European Shopify brands using Stripe for subscriptions or B2B invoicing recover failed payments and chase invoices on WhatsApp. EU-hosted in Ireland, native Stripe and Shopify apps, GDPR by default. ## One inbox for Shopify brands billing through Stripe Tyra is the customer conversations platform for European Shopify brands that run subscriptions or B2B invoicing through Stripe. WhatsApp, Instagram DM, email and SMS land in one inbox alongside the Shopify order and the Stripe invoice, so the person handling the conversation is looking at the same context the customer is talking about. There is one call to action on this page, and it is to [book a demo](https://cal.com/tyra/demo). ![Hero — Tyra inbox showing a WhatsApp failed-payment recovery thread with Stripe context](/screenshots/hero-stripe.png) ## The problems this page is about Somewhere between twenty and forty percent of SaaS and subscription churn is not customers leaving on purpose. It is cards that expired, banks that declined a renewal, and customers who changed banks without remembering to update the payment method on file. ProfitWell has been publishing the twenty-to-forty number for years and Recurly's data lands in the same band. Stripe's Smart Retries claws back some of it, but the customer often has no idea anything went wrong until access is already gone. The reason recovery rates are so bad is that dunning lives in email. The first dunning email goes out, sits in the promotions tab, gets opened eighteen hours later if at all, and by then Stripe has already burned through two of its retry attempts. By the third email the subscription is canceled and the customer has moved on. The retry logic is fine. The channel is the problem. The B2B side of Stripe is worse. A Shopify brand selling wholesale finalises an invoice in Stripe, the PDF gets emailed to an accounts payable address, and it sits there for thirty days while DSO climbs and the founder spends Friday afternoons writing polite chase emails. The procurement contact is a person who reads WhatsApp on their phone all day and email on their laptop twice a week, and the invoice is going to the wrong channel. The common thread is that founders are losing real money every month to a communication problem they have stopped noticing because it has always been this way. The fix is not better email copy. It is a channel customers actually read, wired into the events Stripe is already firing. ## EU-built Tyra is built and hosted in the European Union. Message data, attachments and customer records live in AWS Ireland (eu-west-1) and the core message pipeline does not transfer to US sub-processors. The DPA is available before signup and gets countersigned during onboarding, not six weeks after a procurement back-and-forth. Right-to-be-forgotten requests run automated and complete inside twenty-four hours. For a Shopify brand selling across Germany, France, the Nordics and the Benelux, this matters in two ways. The first is the obvious GDPR one: if a customer asks where their conversation history is stored, the answer is Ireland, not a region in Virginia. The second is language. Tyra ships in more than a dozen European languages out of the box and detects the customer's language from Stripe's `preferred_locales` field, the Shopify customer locale, or the language of the last few messages in the thread, so a German customer who failed a renewal gets a German message and a French customer gets a French one. ![Pillar — EU-built, showing Ireland hosting and DPA flow](/screenshots/eu-built-stripe.png) ## WhatsApp first-class Tyra is a Meta Business Solution Provider directly, not a reseller sitting on top of someone else's WhatsApp connection. That means template approval, number migration, sender quality and the embedded signup flow all run through us, and when something goes wrong with Meta we are the ones on the phone to them rather than a layer in the middle pointing fingers. For a brand that wants WhatsApp to be the primary recovery channel rather than a bolted-on extra, the BSP relationship is the difference between a working system and a Zapier chain that breaks on Black Friday. The practical version is this. When `invoice.payment_failed` fires from Stripe, Tyra sends a WhatsApp message within about thirty seconds with a one-tap link to Stripe's hosted retry page. The message is a pre-approved UTILITY-category template, which Meta typically approves in an hour or two rather than the days that MARKETING templates can take. Open rates on WhatsApp sit around ninety-eight percent and most recoveries happen inside four hours rather than four days, which is the gap between catching the customer before Smart Retries gives up and not. Tyra listens to the obvious Stripe events on the subscription and invoicing side, including `invoice.payment_failed` for cards that decline at renewal, `invoice.payment_action_required` for SCA challenges that European customers miss in their bank app, `invoice.upcoming` for renewal warnings, `invoice.finalized` for B2B invoice delivery, `customer.subscription.trial_will_end` for trial nudges, `customer.subscription.updated` for plan changes, `customer.subscription.deleted` for cancellation saves, and `charge.dispute.created` for chargeback intercepts. Each event maps to a template and a delay in a drag-and-drop screen, and Tyra ships sensible defaults so the system works on day one without anyone having to design a sequence from scratch. ![Pillar — WhatsApp first-class, BSP status and template flow](/screenshots/whatsapp-stripe.png) ## Shopify-native and Stripe-native Tyra is a native Shopify app that renders order history, fulfilment status and customer lifetime value next to the conversation, and it is also a native Stripe App that installs from the Stripe App Marketplace and lives inside the Stripe dashboard on the customer, invoice and subscription pages. For a Shopify brand using Stripe for subscriptions or B2B invoicing this matters because the agent answering a WhatsApp message about a failed renewal can see the Shopify order that started the subscription, the Stripe invoice that just failed, the WhatsApp thread itself, and the customer's opt-in status, all in one place rather than three browser tabs. The Stripe App side adds a Send-via-WhatsApp button on the invoice page, conversation history on the customer page, and the dunning sequence visible on the subscription page. Tyra never stores card details and never sits inside PCI scope. Card retries always go through Stripe's hosted payment page and Tyra simply sends the link, which is a deliberate choice that keeps both us and the merchant out of PCI scope and is not going to change. On the comparison question, Tyra is complementary to Stripe Smart Retries rather than a replacement. Smart Retries decides when to re-attempt the card and Tyra handles the customer communication around those retries. Against the email-first dunning vendors that the Shopify-plus-Stripe crowd usually compares against, the honest pitch is that Tyra is the EU-hosted, WhatsApp-first, Shopify-native option, and if your customers actually read email and you do not care about the channel mix then the existing tools are fine. ![Pillar — Shopify-native and Stripe-native, dual dashboard embed](/screenshots/shopify-native-stripe.png) ## AI that actually works The AI agent is grounded in the live Shopify catalog and the live Stripe customer record, which means it answers questions about whether a product is in stock, when an order is shipping, what the customer's current plan is, and what the failed invoice was actually for, rather than hallucinating a generic answer that sounds plausible. When a customer replies to a failed payment message asking why they were charged a different amount than last month, the agent can see the Stripe subscription, the proration line, and the plan change, and can answer the question without a human ever touching it. The agent is built to hand off cleanly rather than to pretend to be a person. It handles the high-volume repetitive questions that show up around dunning and invoicing, which is mostly "what was this charge for", "can you send me the invoice again", and "I updated my card, did it work", and it routes anything that involves a refund decision, a discount, or an unhappy customer to a human with the full context attached. The honest scope is that the agent reduces ticket volume on the predictable questions and does not replace the person who handles the messy ones, and any vendor claiming otherwise is selling a demo rather than a production system. ![Pillar — AI agent grounded in Shopify and Stripe context](/screenshots/ai-stripe.png) ## FAQ ### Does Tyra replace Stripe Smart Retries? No, and it is not trying to. Smart Retries decides when to re-attempt a declined card using Stripe's own machine learning, and that part is good. Tyra handles the customer-facing communication around those retries so that the customer actually knows their card failed and can fix it on their phone in the time it takes Smart Retries to schedule the next attempt. The two run in parallel and recovery rates are highest when both are on. ### What happens if a customer has not opted in to WhatsApp? Tyra falls back to email for that customer and flags the missing opt-in in the dashboard so you can decide whether to prompt for it at checkout, in the Shopify customer account, in the Stripe customer portal, or in a one-time email campaign. The opt-in itself is a one-click extension on the Stripe customer portal and a small block in the Shopify checkout, so building up coverage over a few weeks is straightforward rather than a project. ### How does SCA fit into this? When Stripe fires `invoice.payment_action_required` because a European card needs a 3DS challenge, Tyra sends a WhatsApp message with a link to the SCA challenge page. This is one of the highest-impact use cases for EU merchants because most SCA failures are customers not noticing the bank app challenge rather than actively rejecting the charge, and a WhatsApp nudge with the challenge link converts a meaningful share of those failures into completed payments. ### Will customers find WhatsApp messages about failed payments annoying? In the data the opposite is true. Customers prefer being told their card failed over silently losing access to a subscription or a wholesale account they actually want to keep, and the unsubscribe rate on dunning WhatsApp templates sits below one percent. The messages are framed as helpful rather than promotional and they fall under Meta's UTILITY category, which is the category Meta itself designs for transactional notifications of exactly this kind. ### Does this work for B2B invoicing or only for subscriptions? Both, and the B2B invoicing use case is genuinely underserved in Europe right now. When `invoice.finalized` fires from Stripe Invoicing, Tyra sends the invoice to the accounts payable contact on WhatsApp with a tap-to-pay link, the amount, the due date, and the PDF as an attachment, and overdue reminders fire on a schedule you configure. This works for SMB and mid-market B2B where the AP contact actually uses WhatsApp personally, and it does not work for enterprise procurement that routes everything through SAP, Coupa or Ariba, in which case keep emailing PDFs into those systems. ### How long does setup actually take? About thirty minutes of active work plus a couple of hours waiting for Meta to approve the message templates. Installing the Stripe App, connecting the Shopify store, running the Meta embedded signup for the WhatsApp number, approving the pre-filled UTILITY templates, mapping events to messages, and adding the opt-in to the customer portal are all sequential steps that any operator can do without an integrator. The first failed payment or finalised invoice after that triggers the first message automatically. ### What about chargebacks and disputes? When `charge.dispute.created` fires, Tyra sends a WhatsApp message prompting the customer to reach out before the dispute escalates. A meaningful share of disputes get resolved informally in that thread rather than going through the full chargeback process, which is the kind of thing that is easy to dismiss until you add up the per-dispute cost over a year. The honest version is that the data on this is still thin and we do not promise a specific recovery rate. ### Is Tyra a good fit for a brand outside the EU? Tyra works globally but the positioning and the infrastructure are EU-first. If most of your customers are in the US or APAC, a tool hosted closer to them is probably a better fit, and we will say so on the demo call rather than try to sell into a poor fit. ## Ready to stop losing subscribers and invoices to a channel problem? [Book a demo](https://cal.com/tyra/demo). --- # WhatsApp for European Shopify brands **URL:** `tyra.ai/whatsapp` **Meta title:** WhatsApp for European Shopify brands | Tyra **Meta description:** Tyra runs WhatsApp, Instagram, email, and SMS in one inbox for Shopify brands. Direct Meta BSP, EU-hosted, AI agent grounded in your live catalog. ## WhatsApp for European Shopify brands Tyra is one inbox for WhatsApp, Instagram, email, and SMS, built for European Shopify brands that have outgrown the patchwork of apps their support team currently has open in different browser tabs. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra inbox showing a WhatsApp conversation with Shopify order context](/screenshots/hero-whatsapp.png) ## The four-tab support desk Walk behind any European DTC brand doing eight figures and the support lead has Gmail open, the WhatsApp Business app on a second monitor, the Instagram inbox on her phone, and a fourth tab for whichever helpdesk the company bought in 2022 and never fully adopted. The customer who DMs on Instagram on Monday and emails on Wednesday is two tickets, answered by two people, with no shared history. The brand pays for this in repeated questions, contradicted promises, and a CSAT number nobody wants to read out loud on the Monday call. ## DPAs that fail review Procurement at a mid-market German or French brand will refuse a US-hosted data processing agreement on sight, and most WhatsApp tools in this market are either headquartered in Hong Kong or running on US infrastructure with a Frankfurt label slapped on top. Tyra is incorporated in the EU, hosts customer data in Ireland on AWS eu-west-1, and is not subject to the CLOUD Act. The DPA is published before signup, not handed over at the end of a sales cycle, which is the part DPOs actually care about. ## The demo-before-pricing wall Every other WhatsApp platform in this category routes a buyer who wants to evaluate the product into a 45-minute discovery call with an SDR who will not quote a price until call three. The vendor calls this enterprise sales. The buyer calls it Tuesday afternoon wasted. Tyra publishes pricing, lets you connect your number through Meta's Embedded Signup yourself, and gets the first message out the door before anyone from our side has spoken to you. ## The BSP markup tax Meta charges per conversation at a published rate that anyone can look up on developers.facebook.com/docs/whatsapp/pricing. Wati, Sleekflow, and most of the APAC-headquartered resellers mark that rate up by 30 to 50 percent and bury the math in a credit system. Tyra is a direct Meta Business Solution Provider, not a layer on top of one, and passes Meta's rate through at cost. The software fee is the software fee. The conversation fee is whatever Meta charges that quarter for the country you sent to. ## EU-built Tyra is incorporated in the EU and runs on AWS eu-west-1 in Ireland. Every sub-processor is listed publicly, every LLM call routes through an EU endpoint where the provider offers one, and deletion requests resolve in under 24 hours through the API rather than a support ticket queue. The honest part most vendor pages skip is that WhatsApp itself is Meta, and Meta is a US company, so the message your customer sends touches Meta's infrastructure before it reaches any BSP on the planet. Nobody escapes that. What a BSP can control is where the conversation lives once it arrives, who processes it, and which legal regime the processor sits under. A US-headquartered BSP storing data in Frankfurt is still subject to the CLOUD Act. We are not. That is the only clean geographic argument in this market, and it is the one DPOs will actually defend in writing. The DPA, the sub-processor list, and the SCCs are public links, not gated assets. ISO 27001 audit is in progress with a target of Q4. Annual third-party penetration testing, results summarised on request. ![Pillar — EU data residency settings in Tyra showing Ireland region and sub-processor list](/screenshots/eu-built-whatsapp.png) ## WhatsApp first-class Tyra is a Meta Business Solution Provider directly. Numbers provision through our BSP account, templates submit through our integration with Meta's Cloud API, and the conversation pricing you see is the rate Meta publishes for that quarter. There is no second vendor in the chain taking a cut, which is why the math works without markup. Being a direct BSP also means template approvals, quality rating signals, and messaging-tier upgrades land in the product in real time instead of being relayed through a partner's support team. When Meta rejects a Marketing template for urgency baiting, the rejection reason appears in Tyra within minutes with a plain-English explanation and a suggested fix, not three days later as a forwarded email. When your quality rating drops from Green to Yellow because a campaign got too many blocks, Tyra warns you the same day, not at the end of the month when the messaging tier has already been cut. The 24-hour customer service window, the four conversation categories, the Embedded Signup flow, the difference between Cloud API and the deprecated On-Premises API, the messaging-tier ramp from 1,000 to 10,000 to 100,000 unique recipients per day, the business verification process and its 1-to-3 business-day wait, the per-country rate card that updates quarterly: these are not edge cases, they are the daily reality of operating on this platform, and they shape every workflow in the product. ![Pillar — Template manager in Tyra showing approval status, rejection reasons, and 12-language variants](/screenshots/whatsapp-first-class-whatsapp.png) ## Shopify-native Tyra is a Shopify app, not a Shopify integration. It installs from the Shopify App Store, authenticates through Shopify's OAuth, reads the live catalog through the Admin API, and writes back to orders, customers, and discount codes when an agent or the AI takes an action. When a customer asks on WhatsApp whether the navy version of a hoodie is back in stock, the answer comes from inventory at that moment, not from a nightly export that is already stale. Order context sits next to the conversation. The agent sees the last three orders, the current cart if the session is live, the fulfilment status with the carrier tracking, the lifetime value, and the customer's marketing consent state, all without leaving the inbox. Discount codes generate inline through the Shopify API with the right rules attached. Returns and refunds initiate from the same panel, subject to whatever authorisation rules the brand has configured. Abandoned cart recovery is a webhook from Shopify into a Tyra automation, not a third bolt-on app that needs its own subscription. ![Pillar — Conversation view with live Shopify order panel showing inventory, fulfilment, and customer LTV](/screenshots/shopify-native-whatsapp.png) ## AI that actually works Most AI for WhatsApp is a flow builder with a chatbot skin. Keywords trigger branches, branches lead to canned replies, and the word AI is doing marketing work it was not engineered to support. Customers can tell within two messages. The agent fails, the conversation escalates, and the brand quietly stops using the AI features it is paying for. Tyra's agent is an LLM grounded in the brand's live Shopify catalog, the help centre content, the shipping and returns policies, and the anonymised embeddings of past resolved conversations. It answers in the customer's language, recommends products from inventory that actually exists, generates discount codes through the Shopify API when authorised, and hands off to a human the moment a refund, a complaint, or anything past its confidence threshold appears. It does not invent stock, does not promise refunds it has no authority to issue, and does not keep talking past a second clarifying question without offering a human. The configuration is per-intent, per-language, per-channel, and per-time-of-day. After 6pm the agent can handle everything; during business hours it can be limited to product questions while humans take the rest. The defaults work for most stores. The granular control is there for the brands that have an opinion about every intent. ![Pillar — AI agent reply drafted with live catalog context and a "hand off to human" button](/screenshots/ai-that-actually-works-whatsapp.png) ## FAQ ### How fast can we go live? If your business is already verified with Meta, most brands send their first message within an hour of signing up. The Embedded Signup flow, number provisioning, and the first batch of templates are the active work. Meta's template approvals run anywhere from one hour for Utility to a full day for Marketing. Business verification, if you do not already have it, is a separate 1-to-3 business-day process with Meta that we submit on your behalf. ### Are you actually a direct Meta BSP, or are you reselling someone else's BSP access? Direct. Tyra is approved by Meta as a Business Solution Provider, the conversation pricing is Meta's published rate without a reseller in the middle, and template submissions and quality-rating signals flow straight from Meta's API into the product. ### Where does our customer data live? In Ireland, on AWS eu-west-1. Processing happens in the EU. LLM calls route through EU endpoints where the provider offers one, and the sub-processor list is published. WhatsApp itself is Meta infrastructure, which is true for every BSP, so the messages transit Meta before they reach us; what we control is everything after that point. ### How does the AI agent know about our products? Tyra installs as a Shopify app and reads the catalog through the Admin API. Inventory, prices, variants, and product descriptions are queried at the moment the agent answers, not from a cached export. When you change a price in Shopify, the agent uses the new price on the next reply. ### Do you mark up Meta's conversation fees? No. The rate you pay per conversation is Meta's published rate for the recipient country and category that quarter. Our revenue is the software subscription. Marking up messaging misaligns the incentive, because the vendor then wants you sending more whether or not it converts. ### Can we keep our existing WhatsApp number? Usually yes. A number on a different BSP can be migrated to Tyra through Meta's standard transfer process, which takes 24 to 72 hours and needs confirmation from both BSPs. A number on the free WhatsApp Business app has to be removed from that app first, which deletes the personal chat history on that number, so most brands use a dedicated business number rather than migrating a personal one. ### What happens to Instagram, email, and SMS? They sit in the same inbox as WhatsApp. A customer who DMs on Instagram on Monday and emails on Wednesday is one thread, one history, and the agent picking it up on Wednesday sees the Monday conversation. Routing rules, AI handoff, and templates work across all four channels. ### Is there a contract? Monthly billing, cancel any time. Annual plans are available if you want a discount, but nothing is locked in by default. The 14-day trial does not require a card. ### How do you compare to Wati, Charles, 360dialog, and Respond.io? 360dialog is the closest in spirit on pricing transparency but is mostly API with a thin UI, so it suits engineering teams rather than support teams. Charles is the strongest German-market sales-led product but is priced for enterprise and has no Shopify-native install of the depth we ship. Wati and Respond.io are APAC-headquartered with messaging markup and English-first product experiences. The combination of direct BSP, EU residency, Shopify-native install, and an AI agent grounded in live inventory is the position none of them occupy. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs 360dialog **URL:** `tyra.ai/vs/360dialog` **Meta title:** Tyra vs 360dialog: WhatsApp BSP vs Full Customer Platform **Meta description:** Honest comparison of Tyra and 360dialog. API-first WhatsApp BSP from Berlin versus a Shopify-native inbox with AI agent, both EU-hosted and both without message markup. ## Tyra vs 360dialog 360dialog is the API-purist WhatsApp BSP out of Berlin, beloved by engineering teams who want to build their own thing on top. Tyra is a full customer conversations platform for European Shopify brands, with WhatsApp as a first-class channel alongside Instagram, email, and SMS. Both are EU-hosted, both are direct Meta BSPs, and neither marks up message pricing. The choice comes down to whether you want to build the product yourself or buy one that already works. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and 360dialog side by side](/screenshots/vs-360dialog.png) ## Choose Tyra if You run a European Shopify brand and want a working inbox, AI agent, and automation the day you sign up, not eight weeks of engineering later. You want WhatsApp alongside Instagram, email, and SMS in a single thread per customer, so a support rep is not switching tabs to figure out who they are talking to. You want the AI to actually know your Shopify catalog, your stock levels, your policies, and your past conversations, rather than hallucinating product names. You want a Shopify-native app that respects how Shopify merchants actually work, with order context, abandoned-cart triggers, and discount-code generation built in. And you want all of this from an EU-built vendor with data hosted in Ireland, no Meta markup on messages, and an operator-friendly UI your team can run without an engineer on call. ## Choose 360dialog if You have an engineering team and you want to build a custom WhatsApp product on top of one of the cleanest BSP APIs in the market. 360dialog has been a Meta-approved BSP since the very early days of the WhatsApp Business API, the German engineering credibility is real, and their infrastructure has the kind of maturity you only get from years of running WhatsApp traffic at scale. Like Tyra, they do not mark up messages, so on raw BSP cost the two are essentially the same. If you are an ISV embedding WhatsApp into your own SaaS, or an agency building a bespoke product for a single large client, or an enterprise that wants the BSP layer and nothing else because everything else is already built in-house, 360dialog is genuinely the better answer. ## API-first BSP vs full product 360dialog is, by design, a BSP and an API. They give you a clean pipe to Meta, a webhook for inbound messages, template management, and not much else. That is the entire product philosophy and they execute it well. If you want an inbox you build the inbox. If you want an agent you build the agent. If you want analytics you build the analytics or wire in a third-party tool. For a team with engineers and specific requirements no platform can meet, this is exactly right. Tyra ships the whole stack. The inbox, the agent, the automations, the template management, the Shopify integration, the Stripe integration, the multi-agent routing, the analytics, the embedded signup flow, the EU-language UI. The BSP layer underneath is the same kind of direct Meta integration 360dialog runs, but it is a means to an end rather than the product itself. For most non-software-company buyers the math is straightforward: building a custom inbox and agent on 360dialog costs at least one engineer for two months upfront and ongoing maintenance after, while Tyra is sending real messages within the hour. The honest framing is that these are different products for different buyers. 360dialog is infrastructure. Tyra is an application. Picking the wrong one is what causes the actual pain, not the price. ## WhatsApp-only vs unified inbox 360dialog is WhatsApp. That is the scope and they are good at it. If your customers only ever message you on WhatsApp and you never want to support Instagram DMs, email, or SMS in the same place, the focus is a feature rather than a limitation. Tyra unifies WhatsApp, Instagram, email, and SMS into one inbox with one customer profile per person across channels. For a European Shopify brand this matters more than it sounds. A customer asks a product question on Instagram, gets the shipping confirmation via email, replies to a delivery problem on WhatsApp, and the rep handling them sees one thread with the order context attached. With 360dialog you would stack a separate Instagram tool, a separate email helpdesk, and a separate SMS provider on top, then try to glue them together. That is a real cost and it shows up in your team's daily workflow. ## Shopify-native depth This is where the two products are not really comparable. 360dialog does not have a Shopify app because they do not have an application layer at all. You build the integration yourself, or you pay an agency to build it, or you buy a separate tool that sits between 360dialog and Shopify. Tyra is in the Shopify App Store with a native integration that reads orders, customers, products, inventory, and fulfillment status in real time. The AI agent uses this data directly rather than a stale export. Abandoned-cart messages trigger from Shopify events. Discount codes are generated inside Shopify and sent through WhatsApp without copy-paste. Order status updates are sent without templates needing per-order data injection by hand. For a Shopify brand this is the work you would otherwise be doing in code or in Zapier, and it is the reason most Tyra customers came from a stacked setup that included a raw BSP and a pile of glue. ## AI agent grounded in your catalog 360dialog has no built-in AI agent. You bring your own. That means picking an LLM vendor, designing the prompts, building the retrieval over your catalog, wiring it into the WhatsApp message flow, handling escalation to humans, and maintaining all of it as your catalog and policies change. It is doable, and engineering teams do it, but it is a real project. Tyra's agent is built in and grounded in the live Shopify catalog, your knowledge base, and your conversation history. It knows what is in stock right now, what your return policy is, what the customer ordered last month, and when to hand off to a human. It uses Meta's WhatsApp formatting directly without markup translation layers, so messages render the way Meta intends. For a brand without a machine learning team, the gap between "no agent" and "agent that actually works on your catalog" is the entire reason to pick a platform over a BSP. ## Self-serve onboarding, compared honestly Both products onboard fast for what they are. 360dialog is among the quickest BSPs to get a number provisioned and an API key in your hands. If you are an engineer, you can be making API calls the same afternoon you sign up. That is genuinely impressive and most BSPs cannot match it. Tyra's onboarding measures something different: time from signup to your support team actually answering customer messages. Connect Shopify, connect WhatsApp via embedded signup, import templates, configure the agent on your catalog, and you are live. Most brands do this in under an hour without writing code. The two onboarding stories are not in competition, they are aimed at different people. An engineer at 360dialog and an operations lead at Tyra both feel the product was built for them, because it was. ## FAQ **Is 360dialog cheaper than Tyra?** At the BSP layer the message cost is essentially the same because neither company marks up Meta's pricing. 360dialog charges a per-number subscription on top, Tyra charges a software fee that includes the inbox, agent, and integrations. If you compare 360dialog plus the engineering and third-party tools you would need to match Tyra's surface area, Tyra is usually cheaper. If you only need the BSP layer because everything else is built in-house, 360dialog is cheaper. **Can I use 360dialog as my BSP and Tyra as my UI?** No. Tyra is a direct Meta BSP, and a WhatsApp number is registered with exactly one BSP at a time. You are either on Tyra or on 360dialog. Switching between them is a standard Meta BSP-to-BSP transfer and takes a few days end to end. **I am building a SaaS that needs WhatsApp as a feature. Should I use Tyra or 360dialog?** Probably 360dialog. They are built for ISVs embedding WhatsApp into another product. Tyra is built for end customers running their own brand. We will tell you the same thing on a sales call. **Has 360dialog been around longer than Tyra?** Yes, considerably. They were one of the first Meta-approved BSPs in Europe and that operational history is a real asset. Tyra is newer and focused on a narrower customer profile, European Shopify brands, where the depth of integration matters more than the breadth of the partner network. **How does data hosting compare?** Both are EU-hosted. 360dialog is in Germany, Tyra runs on AWS in Ireland. Both are GDPR-native and both can answer the procurement questions a German or French enterprise buyer will ask. **What does migration from 360dialog to Tyra look like?** The number itself transfers via Meta in roughly one to three days. Templates are resubmitted on Tyra and approved by Meta within a few hours to a day each. If you have built a custom UI on 360dialog, the harder question is whether your team is ready to move to Tyra's interface and rebuild any custom logic as Tyra automations. We will be honest on a call about whether that switch is worth it for your situation. **Do I have to pick one forever?** No. Both companies do BSP-to-BSP transfers. The cost of switching is real but bounded, and the WhatsApp number, the customer history with Meta, and the template approvals all carry over. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Charles **URL:** `tyra.ai/vs/charles` **Meta title:** Tyra vs Charles: EU WhatsApp commerce for Shopify brands **Meta description:** Honest comparison of Tyra and Charles for European Shopify brands running WhatsApp, Instagram, email, and SMS. Self-serve and Shopify-native vs sales-led German D2C. ## Tyra vs Charles ![Hero — Tyra and Charles side by side](/screenshots/vs-charles.png) Charles is the polished, sales-led German WhatsApp commerce platform built for established D2C; Tyra is the self-serve, Shopify-native alternative that hands you one inbox for WhatsApp, Instagram, email, and SMS without a procurement cycle. [Book a demo](https://cal.com/tyra/demo) ### Choose Tyra if You run a European Shopify brand and want to be live this week, not next quarter. Tyra is self-serve, EU-hosted in Ireland, and works as a Meta BSP directly, so WhatsApp is first-class rather than bolted on. The AI agent is grounded in your live Shopify catalog, which means answers about stock, sizes, and prices reflect what is actually on the shelf right now. Pricing is published, contracts are monthly by default, and the team ships changes weekly. If you want to evaluate the product before you talk to a salesperson, and you want one inbox that covers WhatsApp, Instagram, email, and SMS across twelve EU languages, Tyra is the straightforward choice. ### Choose Charles if Charles is the right answer for a particular kind of buyer, and worth being honest about it. They have deep roots in the German D2C scene, a customer list full of premium German skincare, fashion, and supplement brands, and a sales-led onboarding motion that includes a dedicated implementation manager who builds your first journeys with you. Their campaign and journey designer is one of the most mature in the category, with a visual builder that marketing teams genuinely enjoy using. If you are a larger German D2C brand with formal procurement, a marketing team that wants agency-style support, and a budget that comfortably absorbs four-figure monthly software spend plus implementation fees, Charles is a credible and well-built choice. ### Sales-led premium pricing vs self-serve Charles sits firmly in the sales-led premium segment. You request a demo, you talk to an account executive, you go through a scoping conversation, and eventually you get a quote that typically lands somewhere between a thousand and a few thousand euros a month, often with a one-time implementation fee on top. For brands that want a partner rather than a tool, that motion makes sense. The trade-off is time and price visibility: weeks of evaluation, no public pricing, annual contracts. Tyra takes the opposite approach. You sign up, connect Shopify, plug in your WhatsApp number, and start sending messages the same afternoon. Pricing is on the pricing page, the entry tier is mid-market rather than enterprise, and the contract is monthly unless you choose otherwise. This is not better or worse in the abstract; it is a different bet about how brands want to buy software in 2026. If your team prefers to evaluate by using the product and read pricing before any conversation, Tyra fits how you already work. ### Campaign-led marketing vs conversational commerce Charles is, at heart, a campaign and journey platform that happens to live in WhatsApp. The product is shaped around marketers who think in flows, segments, and broadcast sends. The visual journey builder is the centrepiece, and a marketing team with a clear lifecycle plan can do impressive work inside it. Tyra is shaped around the conversation. The inbox is the centrepiece, the AI agent handles the long tail of pre-sales and post-purchase questions using your live Shopify catalog, and campaigns and automations exist to support those conversations rather than dominate them. Both philosophies can drive revenue. If your growth model is mostly broadcast campaigns and structured lifecycle journeys, Charles plays to that strength. If your bottleneck is the volume of inbound messages you cannot answer fast enough, and you want an agent that actually knows your catalog, Tyra is built for that problem. ### DE-focused vs broader EU Charles is a German company that has built a strong German business. Their team, their case studies, their contracts, and their best-known features are anchored in the German market. For a German brand selling primarily to German customers, that local depth is a real asset. Tyra is built for European Shopify brands across the bloc. The product ships with twelve EU languages as first-class citizens, hosting is in Ireland under EU jurisdiction, and the AI agent handles multilingual conversations without language-specific tuning per market. If your customer base spans Germany, the Nordics, France, the Netherlands, Italy, and Spain, the language and localisation work is already done. If you sell almost exclusively into the DACH region, Charles's German focus is closer to your shape; if you sell across Europe, Tyra is closer to yours. ### Shopify catalog grounding in AI The AI gap is the place where the two products diverge most sharply in practice. Charles's automations and AI assists are largely template- and rule-driven, which is well-suited to structured marketing flows but limited when a customer asks something specific about a product. Tyra's agent queries the Shopify catalog at the moment of the conversation, so when someone asks whether the medium is back in stock, what the linen blend feels like compared to the cotton, or whether the new colour ships to Belgium, the answer comes from live data rather than a knowledge-base snapshot. For brands where pre-sales questions block conversions, that difference shows up directly in revenue. ### FAQ **Is Charles overpriced?** No. Their pricing reflects a sales-led service model that includes dedicated implementation and ongoing account management. For brands that want and use that service, it is fair value. For brands that want software they can run themselves, it is more than they need. **Can I migrate my WhatsApp number from Charles to Tyra?** Yes. It is a standard BSP-to-BSP transfer through Meta, usually completed within a few days. The harder part is rebuilding any journeys you have invested in inside Charles, since there is no export path between the two platforms. **Does Tyra work well for German brands specifically?** Yes. German is one of the strongest languages in the agent, Ireland hosting and EU contracts satisfy German procurement requirements, and several German Shopify brands run on Tyra today. Charles has more German brand-name customers; that is a fair point in their favour, not a reason Tyra cannot serve a German brand well. **Is Tyra only for small brands?** No. The self-serve motion makes it easy for smaller brands to start, but the platform serves Shopify brands well into eight-figure GMV. The mid-market positioning is about pricing and how you buy, not about a ceiling on what the product can handle. **What about Instagram, email, and SMS?** Tyra handles all four channels in one inbox, including the AI agent and automations across them. Charles is strongest on WhatsApp with email and Instagram as supporting channels. If WhatsApp is your only channel, the difference matters less; if you want one place for all customer conversations, it matters more. **Do I need to talk to sales to try Tyra?** No. You can sign up, connect Shopify, and use the product on a trial without a sales call. A demo is available if you want one, and a migration call is the right starting point if you are moving from Charles or another platform. **How long does onboarding take?** For a typical Shopify brand setting up Tyra from scratch, the first conversations go out within an hour or two. A full migration from another platform, including templates, contact lists, and rebuilt automations, generally takes two to six weeks depending on complexity. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Churnkey **URL:** `tyra.ai/vs/churnkey` **Meta title:** Tyra vs Churnkey: WhatsApp Recovery vs Cancel-Flow Retention **Meta description:** Honest comparison of Tyra and Churnkey for subscription retention. WhatsApp-first failed payment recovery from an EU-built inbox versus Churnkey's mature cancel-flow and dunning suite. ## Tyra vs Churnkey Tyra is a WhatsApp-first customer conversations platform built in the EU that recovers failed Stripe payments inside an inbox your team already uses; Churnkey is a US-built retention suite with the most mature cancel-flow product on the market and a long track record in email dunning. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Churnkey side by side](/screenshots/vs-churnkey.png) ## Choose Tyra if Your subscribers are reachable on WhatsApp, which is the default in most of Europe, Latin America, India, and the Middle East. You want failed payment recovery to happen in the same channel where the customer already talks to you, with a human able to step in mid-conversation. You care about EU data residency because your finance team, your DPO, or your enterprise customers ask about it. You run on Stripe and Shopify (or Stripe alone) and would rather one tool handled subscription recovery, support, and conversational commerce than stitch three vendors together. You want an AI agent that can answer "why did my card fail" and "can I pause instead" with the actual subscription state pulled from Stripe. ## Choose Churnkey if You sell SaaS to a primarily US customer base where email is still the channel of record and in-app surfaces drive most of the cancel intent. You want the deepest cancel-save library on the market: segmented offers, exit interviews, pause and downgrade alternatives, multivariate testing on save offers, and reason-coded analytics that have been refined across thousands of SaaS deployments. You value a vendor whose entire product is retention rather than a broader inbox that happens to do recovery. Churnkey has been in this space longer than almost anyone and the polish shows; if cancel-flow is the lever you most need to pull, they are the safer bet. ## WhatsApp and multi-channel reach versus email and in-app Churnkey's recovery model assumes the customer reads email or returns to your product. For US SaaS that assumption is mostly fine. Email open rates on dunning sequences sit in the 20 to 35 percent range, and the in-app cancel widget catches the rest at the moment of intent. It is a coherent stack for a customer base that lives in their inbox and your app. Tyra starts from a different premise. WhatsApp messages get opened at roughly 95 percent, usually within minutes, and the reply is a conversation rather than a click. For a failed payment, that means the customer reads "your June charge for €49 failed, want to retry with the same card or update it" while they are still holding their phone, and either taps the Stripe-hosted link or messages back. The same thread carries support questions, 3DS confirmation links for SCA-challenged charges, and the eventual win-back. Email and SMS fallbacks exist for customers without WhatsApp opt-in, but the channel is the point. Neither approach is universally right. In Frankfurt or Madrid, Tyra's channel mix wins on raw reach. In Austin or Toronto for a B2B SaaS selling to engineering teams, Churnkey's email and in-app model fits the audience better. ## EU-hosted and GDPR-native versus US-hosted Tyra is incorporated in the EU and runs on AWS Ireland (eu-west-1). All customer conversations, Stripe webhooks, and AI processing stay in EU regions. For European subscription businesses this removes a procurement step: there is no Standard Contractual Clauses paperwork, no Schrems II analysis, no CLOUD Act exposure to argue through with a security team. Churnkey is US-incorporated and US-hosted. They serve European customers under SCCs and are GDPR-compliant in the conventional sense, but the data lives in the US and the company is subject to US legal process. For most US SaaS this is a non-issue. For an EU brand selling into regulated verticals or to enterprise buyers with strict data-residency clauses, it shows up as friction during procurement. This is less a feature comparison than a fit question. If your buyers do not ask where the data lives, Churnkey's hosting story is fine. If they do, Tyra removes the conversation. ## Conversational inbox versus outbound recovery Churnkey is, by design, not a support tool. It runs cancel flows, dunning sequences, and the analytics around them. When a customer responds to a dunning email with a question, that lands in whatever support tool you already use (Zendesk, Intercom, Front, Help Scout), and a human picks it up there. The handoff works but it is a handoff. Tyra is an inbox first. The failed payment message and the customer's reply and the eventual "actually can you cancel my subscription" all sit in the same thread, visible to the same agent, with the Stripe subscription, the order history, and any Shopify context attached. The AI agent handles the routine retries and the simple questions; a human takes over when the conversation needs it, in the same window. For brands where retention and support are done by the same small team, this collapses a workflow that Churnkey leaves split. The trade-off is real. Churnkey's narrower scope means more depth in the part it owns. Tyra's breadth means recovery sits inside a conversation rather than running as a separate program. ## SaaS-only versus Shopify and Stripe dual ICP Churnkey serves subscription SaaS. The product, the analytics, the case studies, and the integrations are all built around that ICP. If you are a pure-play SaaS company, that focus is a feature. Tyra was built for European Shopify brands first and added the native Stripe App for subscription recovery as the same customers asked for it. That means Tyra speaks both Shopify (orders, refunds, abandoned checkout, catalog grounding for the AI agent) and Stripe (subscriptions, invoices, failed charges, dunning, 3DS recovery, B2B invoice delivery on WhatsApp). For a brand that runs Shopify for physical goods and Stripe Billing for a subscription tier, or a B2B SaaS that wants to send Stripe Invoices over WhatsApp instead of email, the dual fluency matters. For a pure SaaS shop with no commerce surface, Churnkey's tighter focus is the cleaner fit. ## FAQ **Is Tyra a direct replacement for Churnkey?** For the cancel-flow product specifically, no. Churnkey's cancel-save UX, offer experimentation, and reason analytics are deeper than anything Tyra ships today. For failed payment recovery, Tyra often outperforms email-only dunning because the WhatsApp channel reaches the customer faster, but the comparison depends on whether your subscribers are on WhatsApp in the first place. **Can I run both?** Yes, and several brands do. The common pattern is Churnkey owning the in-app cancel flow and reason analytics while Tyra handles failed payment recovery and customer conversations on WhatsApp. The two products do not conflict at the data layer because both read from Stripe. **How well does WhatsApp actually recover failed payments?** In our deployments with EU subscription brands, WhatsApp recovers a meaningful share of failed charges within hours rather than days, with most of the lift coming from SCA and 3DS-challenge cases where a fast confirmation link matters. The exact number depends on your opt-in rate, your customer geography, and how aggressive your existing email dunning already is. We are happy to walk through the math on your Stripe data. **What about cancel flows in Tyra?** Tyra supports basic cancellation conversations through the WhatsApp thread and through the AI agent, including pause, downgrade, and offer alternatives. It is not as deep as Churnkey's dedicated cancel-flow product, and we do not pretend otherwise. If voluntary churn is your primary problem and you want multivariate offer testing, Churnkey is the right tool. **Is Tyra a good fit for a US-only SaaS company?** Probably not. WhatsApp penetration in the US is too low for the channel advantage to carry, and Churnkey's email and in-app model fits the audience better. Tyra's sweet spot is European subscription brands, Shopify brands with a subscription tier, and B2B SaaS sending Stripe Invoices internationally. **How does data residency work with Tyra?** All Tyra infrastructure runs in AWS Ireland (eu-west-1). Conversation data, AI processing, and Stripe webhook handling stay in EU regions. We are a Meta WhatsApp BSP directly, which means the WhatsApp data path does not transit through a third-party aggregator outside the EU. **Does Tyra integrate with Stripe the same way Churnkey does?** Tyra is a native Stripe App, installed from the Stripe App Marketplace, with access to subscriptions, invoices, customer portal events, and failed charge webhooks. The integration is built for recovery and for B2B invoice delivery rather than for cancel-flow optimization, so the shape is different from Churnkey's even though the underlying Stripe surface is the same. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Gorgias **URL:** `tyra.ai/vs/gorgias` **Meta title:** Tyra vs Gorgias for European Shopify Brands **Meta description:** An honest comparison of Tyra and Gorgias for Shopify brands in Europe. WhatsApp-first vs ticket-first, EU vs US hosting, AI grounded in the live Shopify catalog. # Tyra vs Gorgias ![Hero — Tyra and Gorgias side by side](/screenshots/vs-gorgias.png) Gorgias is the established US ticketing helpdesk for Shopify support teams, and Tyra is the EU-built customer conversations platform for Shopify brands that lead with WhatsApp; if your volume is mostly inbound email tickets handled by a large agent team, Gorgias is the safer pick, and if your volume is conversational across WhatsApp, Instagram, email, and SMS for a European brand, Tyra is built for that shape of work. [Book a demo](https://cal.com/tyra/demo) ## Choose Tyra if You are a European Shopify brand and the bulk of your customer conversations happen on WhatsApp and Instagram rather than in an email queue. You want data stored in Ireland, under EU law, without the CLOUD Act hanging over your processor agreements, and you want your WhatsApp number on a direct Meta Business Solution Provider instead of routed through a second vendor. You think of customer messaging as a revenue channel as much as a cost centre, so you need outbound flows like abandoned cart, back-in-stock, and post-purchase alongside the inbound inbox. You sell in several European languages and you want the AI agent, the UI, and the templates to be first-class in all of them, grounded in your live Shopify catalog so it quotes real stock and real prices rather than a stale knowledge base. ## Choose Gorgias if Email is still your dominant channel and you have a support team large enough that mature helpdesk machinery genuinely earns its keep, including detailed rule engines, SLAs, queues, CSAT instrumentation, and a deep macro library refined over years. You want a vendor that has invested heavily in performing Shopify actions inside the ticket itself, so agents can issue refunds, cancel orders, edit line items, and change addresses without leaving the conversation, and you want that to work the same way it did last quarter. You operate primarily in North America, your peer brands already run Gorgias, and you value the breadth of their third-party integration directory across reviews, loyalty, subscriptions, and shipping. Gorgias has been building this product since 2017 and the depth shows; if your operation is shaped like a classic Shopify support desk, that depth is what you are buying. ## EU hosting and the CLOUD Act Tyra is incorporated in the EU and runs on AWS Ireland (eu-west-1) with EU-only storage for customer data, conversation history, and the embeddings the AI agent uses. Gorgias is a US-incorporated company and its production data lives primarily in the United States, which means transfers to the EU rely on Standard Contractual Clauses and the vendor sits under US jurisdiction including the CLOUD Act. That is legally workable and many European brands accept it; SCCs are a real legal instrument and Gorgias publishes its DPA. The honest question is not whether Gorgias is compliant, because it is, but whether your DPO, your enterprise customers, or your own legal team are comfortable with a US-controlled processor handling conversational data that often contains order details, addresses, and identity information. For a B2C brand selling sneakers in three EU countries this is usually a shrug. For a brand selling regulated goods, doing significant B2B, or fielding procurement reviews from larger European retailers and marketplaces, the answer often gets stricter over time, and the difference between an EU-incorporated processor in Ireland and a US-incorporated one in Virginia stops being theoretical. If your business does not have anyone asking these questions today, this section probably should not move you. If it does, the architectural difference is real and not something a contract clause papers over. ## WhatsApp depth and the BSP question Tyra connects to WhatsApp as a direct Meta Business Solution Provider, which means your WhatsApp Business Account, your phone number, your template library, and your conversation billing all sit on infrastructure Tyra operates and supports. Gorgias supports WhatsApp through partner BSPs, most commonly 360dialog, so your number lives on a third party and Gorgias is the interface on top. In day-to-day messaging this is mostly invisible, but it shows up at the edges that matter: template approvals, number migrations, conversation pricing transparency, support escalations when Meta changes a policy, and the speed at which new WhatsApp features (Flows, Calling, richer commerce surfaces) reach you. Beyond the BSP layer, Tyra treats WhatsApp as the centre of the product rather than a channel bolted onto an email helpdesk. That means template management, opt-in handling, 24-hour service window logic, marketing message limits, and the new outbound categories are first-class concepts in the UI rather than concepts borrowed from email and renamed. Brands that run heavy WhatsApp volume in DE, NL, ES, or IT tend to feel this immediately. The trade-off is fair to name. If your WhatsApp volume is light and email is the real workload, Gorgias-via-partner-BSP is perfectly adequate and you get their mature ticketing on top. If WhatsApp is the channel you are actually betting on, the direct-BSP model is the right shape. ## Ticket model vs conversational model, and per-contact vs per-ticket pricing Gorgias is, at its core, a ticketing system. An inbound message opens a ticket, an agent resolves it, the ticket closes, metrics roll up, and pricing is metered against ticket volume above the plan allowance. That model is excellent for post-purchase support where each interaction has a clear start and end, and the per-ticket pricing rewards efficient resolution. The downside is that a viral spike, a shipping incident, or a seasonal surge can move your bill substantially in a single month, and a single multi-day WhatsApp conversation does not always map cleanly to "one ticket". Tyra is built around the conversation rather than the ticket. A customer threads in and out across WhatsApp, Instagram, and email over weeks, asks about a product before buying, gets a recommendation grounded in live Shopify stock and pricing, completes the purchase, then comes back with a returns question, and the whole thread stays as one ongoing conversation tied to one contact. Pricing follows that shape: per active contact per month, with predictable steps as you grow rather than overage charges that move with traffic. Neither model is universally better. If your business is mostly inbound email tickets with clean open-and-close arcs, the ticket model and per-ticket pricing reward what you actually do. If your business is mostly long-running WhatsApp threads that mix pre-purchase questions, transactional updates, and post-purchase support, the conversational model and per-contact pricing fit better and make the monthly bill easier to forecast. ## Shopify actions inside the inbox This is the area where Gorgias is genuinely deeper and where Tyra is still catching up. Gorgias has spent years building Shopify-native actions into the agent workspace: refunds, partial refunds, order cancellations, line-item edits, address changes, duplicating orders, and a long tail of less common operations, all performed inside the ticket without context-switching to the Shopify admin. For a support team that runs ten or more agents handling hundreds of order-modification tickets a day, that depth compounds into real time savings and fewer mistakes. Tyra covers the core Shopify actions that the majority of conversations actually need: pulling live order context, generating discount codes, surfacing stock and product information, and the everyday operations that come up in a WhatsApp thread. Where Tyra is stronger is on the grounding side of the AI agent, which queries the live Shopify catalog so answers about stock, price, variants, and availability are current rather than drawn from a static knowledge base; where Gorgias is stronger is on the breadth of destructive and corrective actions an agent can take from the conversation view. If your operating model leans on agents performing a wide range of Shopify mutations from inside the helpdesk, Gorgias is the better tool today and it would be dishonest to claim otherwise. If your operating model leans on conversations that are mostly informational, transactional, or commerce-driven with occasional order tweaks, Tyra covers what you actually use. ## FAQ ### Is Gorgias not GDPR-compliant? Gorgias is GDPR-compliant and operates under Standard Contractual Clauses for EU-to-US transfers, with a published DPA. The substantive question is jurisdictional rather than compliance-formal: a US-incorporated processor sits under US law including the CLOUD Act regardless of where individual workloads run. Whether that matters depends on your customers, your sector, and your own legal posture, and for many European brands it genuinely does not move the needle. ### Can we run both Tyra and Gorgias? Yes, and a fair number of brands do exactly that during a transition or permanently. The common shape is Gorgias handling email-heavy post-purchase support while Tyra handles WhatsApp, Instagram, and outbound commerce flows, with Shopify as the shared source of truth for customer and order data. It is not the cheapest setup but it is a reasonable way to keep the maturity you have on email while moving conversational volume onto the right tool. ### How does Tyra's AI agent compare to Gorgias AI Agent? Gorgias AI Agent is more battle-tested across traditional Shopify support intents and benefits from years of macro and rule data feeding its behaviour. Tyra's agent is grounded in the live Shopify catalog, so questions about stock, price, variant availability, and current promotions are answered against real data at query time rather than a synced knowledge base, which matters more on pre-purchase WhatsApp conversations than on returns tickets. The honest framing is that they are optimised for different intents. ### What about per-ticket overages on Gorgias? Gorgias plans bundle a ticket allowance and charge per ticket above it, where an inbound customer message generally counts as a ticket. For brands with stable, predictable volume this is fine and often economical. For brands prone to spikes, viral moments, or seasonal surges, it can produce uncomfortable monthly variance, and it is worth modelling against a realistic worst-month scenario before committing. ### Will we lose email quality if we move to Tyra? If email is the channel where most of your volume lives and where your team has built years of macro, rule, and routing investment, you will give something up moving off Gorgias and it is worth being clear-eyed about that. Tyra's email is competent and integrated into the same conversational thread as WhatsApp and Instagram for a given contact, which is genuinely useful, but if email is 80% of your workload the move should be driven by a real reason to consolidate rather than by feature comparison alone. ### Does Tyra do outbound, or only inbound support? Tyra supports outbound on the same rails as inbound, including abandoned cart recovery, back-in-stock notifications, order and shipping updates, and broadcast campaigns within Meta's marketing message rules. Gorgias is primarily inbound and outbound use cases typically go through a separate tool. If you want messaging to be a revenue channel as well as a support channel, that difference is part of the decision. ### We are a North American brand. Should we even be looking at Tyra? Probably Gorgias is the more natural fit, honestly. Tyra is built for European Shopify brands and the product investment reflects that: EU hosting, EU language coverage, WhatsApp-as-primary-channel, and a Meta BSP relationship that matters more in markets where WhatsApp dominates. North American brands can run Tyra and some do, but the centre of gravity of the product is European. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Klaviyo **URL:** `tyra.ai/vs/klaviyo` **Meta title:** Tyra vs Klaviyo for Shopify brands in Europe **Meta description:** An honest comparison of Tyra and Klaviyo. Why most European Shopify brands run both: Klaviyo for email and SMS marketing, Tyra for the WhatsApp and Instagram inbox layer. # Tyra vs Klaviyo Klaviyo is the default email and SMS marketing platform for Shopify; Tyra is the European conversational layer built around WhatsApp, Instagram, email and SMS in one shared inbox, and most brands end up running both rather than picking one. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Klaviyo side by side](/screenshots/vs-klaviyo.png) ## Choose Tyra if Choose Tyra if your customer conversations are spread across WhatsApp, Instagram DMs, email replies and SMS, and nobody on your team has a single place to answer them. Tyra is built as a shared inbox for European Shopify brands, hosted in Ireland, with WhatsApp wired directly into Meta as a BSP rather than through a third party. The AI agent reads from your live Shopify catalog so when a customer asks whether the navy hoodie is back in size M, the answer is grounded in real stock rather than a guessed reply from a generic chatbot. Honest framing first: Tyra is not really a Klaviyo replacement. Most of our customers keep Klaviyo for their marketing flows and add Tyra for the conversational side of the business, where Klaviyo was never designed to play. ## Choose Klaviyo if Choose Klaviyo if email is your primary revenue channel and you need the depth that comes from a decade of focused investment in email marketing for Shopify. Klaviyo's segmentation engine, predictive properties, template editor and deliverability infrastructure are genuinely best in class for D2C. If you are sending styled newsletters to fifty thousand subscribers, running predictive churn flows, or operating SMS marketing at scale in the US, UK, Canada or Australia where they have mature sender registration, Klaviyo is the right tool and Tyra is not trying to replace it. The free tier up to 250 contacts also makes Klaviyo a natural starting point for a brand new Shopify store before there is any meaningful conversational volume to manage. ## Email-first vs WhatsApp-first Klaviyo is an outbound marketing platform. The mental model is a marketer building a flow in a visual editor, scheduling a campaign to a segment, and watching open rates and revenue per recipient in a dashboard. Replies, when they happen, go to whatever inbox is set on the from address, and the workflow ends there. That model works because email is fundamentally a broadcast channel. Tyra starts from the opposite end. The default surface is an inbox with live conversations in it, shared across the team, with the AI agent handling routine product and order questions before a human sees them. Campaigns and flows exist, but they are second-class to the conversation itself. For a brand where WhatsApp is becoming the channel customers actually use to ask "where is my order" or "do you have this in black", the inbox model fits the work in a way a broadcast tool cannot. This is why running both makes sense. Klaviyo runs the broadcast layer; Tyra runs the conversation layer. They share customer data through the integration and stop fighting each other for the same job. ## EU hosting and GDPR posture Klaviyo is a US-incorporated company with US-based infrastructure. They have standard contractual clauses and a published data processing agreement, which is sufficient legal cover for most European brands. The architectural reality is that they sit under US law, including the CLOUD Act, and the data lives on US soil. Tyra is built in Europe and hosts customer data in AWS Ireland. The company is EU-incorporated, the subprocessors are documented, and there is no transatlantic data transfer for normal use. For a brand whose DPO has been asking pointed questions about US vendors, or for sectors like health, beauty with prescription overlap, or anything touching minors, this is a real distinction rather than a marketing line. Neither posture is wrong. Klaviyo is used by thousands of European brands without issue. The honest version is that Tyra removes a class of question that Klaviyo cannot, because the underlying jurisdiction is different. ## Shopify catalog grounding in AI replies Klaviyo's product roadmap has added AI features for content generation, subject line suggestions and segment naming. These are marketer-facing assistants, not customer-facing agents. Tyra's AI agent answers customers directly on WhatsApp, Instagram and email, and it does so by querying the live Shopify catalog: product titles, variants, current stock, prices in the customer's currency, and the customer's own order history. When someone asks about a sold-out item the agent knows it is sold out. When someone asks about delivery to Portugal the agent reads the shipping zones rather than inventing them. The replies are in the customer's language across the twelve EU languages Tyra ships with first-class. This is a different product surface from anything Klaviyo offers, and it is the part of Tyra that does not have a direct equivalent on the Klaviyo side regardless of how the email and SMS comparison plays out. ## European-language depth Klaviyo's UI, documentation, templates and case studies are English-led. Localization exists in the product but is not the centre of gravity. For an English-speaking team running campaigns to a multi-language audience, this is workable. Tyra ships with twelve EU languages as first-class surfaces: the agent replies, the template library, the customer-facing components and the merchant UI. For brands selling across DACH, the Nordics, France, Italy, Spain, the Netherlands and Poland from a single operations team, the language depth removes the constant translation tax that English-first tools impose. ## FAQ ### Is Tyra a replacement for Klaviyo? Not really, and we would rather be straight about it. About eighty percent of our Shopify customers keep Klaviyo running for email marketing and add Tyra for WhatsApp, Instagram and the shared inbox. The two tools share customer data through the integration and do different jobs. ### Klaviyo launched WhatsApp. Why use Tyra for it? Klaviyo's WhatsApp is a campaign feature delivered through a partner BSP, suitable for sending templated messages alongside email flows. Tyra is a direct Meta BSP with WhatsApp as the core product, including the multi-agent inbox, AI agent, catalog grounding and the Instagram and Facebook channels in the same view. If WhatsApp is a primary channel rather than a supplement to email, the depth difference shows up quickly. ### How does the Klaviyo integration work? You can sync WhatsApp opt-ins from Tyra into Klaviyo properties for segmentation, trigger Tyra conversation flows from Klaviyo events, and pass conversation outcomes back to Klaviyo for reporting. In practice this means a Klaviyo segment can fire a WhatsApp campaign in Tyra, and a Tyra conversation outcome can suppress a Klaviyo email so the customer is not contacted twice for the same thing. ### Will running both cost more than running either alone? Yes, the combined spend is higher than running one tool. The pattern we see is that the WhatsApp layer typically recovers fifteen to thirty percent of abandoned carts within two hours, and the Klaviyo email layer adds another four to eight percent over the following day or two. For most brands the incremental recovered revenue covers the combined cost inside the first month. ### Is Klaviyo's GDPR posture good enough for a European brand? Legally, in most cases yes. Klaviyo has SCCs and a DPA and is used widely across Europe. Architecturally they are a US vendor under US law. Whether that matters for your brand is a judgement your DPO has to make, and different European DPOs answer it differently. ### Does Tyra do email marketing? Tyra handles transactional email and lightweight marketing email well, and it lives in the same inbox as WhatsApp and Instagram, which is useful for support and one-to-one sales. For newsletter operations, deep segmentation and predictive flows, Klaviyo is the better tool and we are not pretending otherwise. ### Can the AI agent handle conversations in our customers' languages? Yes. The agent replies in the customer's language across the twelve EU languages Tyra supports as first-class, grounded in your Shopify catalog and order data so the answers are accurate rather than plausible-sounding. ### What happens if Klaviyo builds a full WhatsApp inbox? They might, over time. The current investment looks focused on email deliverability and SMS, with WhatsApp as a campaign feature rather than a conversation surface. If that changes, the Tyra advantages around EU hosting, language depth, Shopify catalog grounding and the wider Instagram and Facebook coverage are still there. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs ManyChat **URL:** `tyra.ai/vs/manychat` **Meta title:** Tyra vs ManyChat for Shopify Brands in Europe **Meta description:** Honest comparison of Tyra and ManyChat for European Shopify brands. Catalog-grounded AI agent and EU hosting versus a mature Instagram flow builder. ## Tyra vs ManyChat ![Hero — Tyra and ManyChat side by side](/screenshots/vs-manychat.png) ManyChat is the deepest Instagram flow builder on the market and a great fit for creators and SMBs running comment-to-DM playbooks; Tyra is a Shopify-native, EU-hosted customer conversations platform built around an AI agent that reads your live catalog and a shared inbox for WhatsApp, Instagram, email, and SMS. [Book a demo](https://cal.com/tyra/demo) ## Choose Tyra if You are a European Shopify brand and conversations are starting to feel like a real operational surface rather than a marketing tactic. You want one inbox where WhatsApp, Instagram DMs, email, and SMS land together, with an AI agent that actually knows whether the medium black tee is in stock in your Frankfurt warehouse right now. You care about where customer data lives, because procurement, your DPO, or your own instincts tell you that Ireland is a better default than Virginia. You run WhatsApp seriously, with Meta as your BSP rather than an extra layer in between. You want a small operations team to handle escalations alongside automation, not bolt a live chat module onto a flow tool. ## Choose ManyChat if ManyChat has been refining Instagram automation longer than almost anyone, and it shows. If your business runs on Instagram comment-to-DM mechanics, quiz funnels, lead magnets, and creator-led campaigns, their flow builder, template library, and integrations are hard to beat. They have years of pattern-matched playbooks, an active community sharing flows, and tutorials covering nearly every coaching, fitness, and creator niche. Their free tier and low entry pricing make them a sensible default for solopreneurs and small businesses, especially in the US and other English-led markets. If Instagram is your one channel and your customer journeys fit a tree of branches, ManyChat is the more mature product for that job. ## Flow builder versus an agent grounded in Shopify ManyChat treats a conversation as a flow you design ahead of time. You draw the branches, the customer picks an option, then another, then another. It works beautifully when the path is knowable, which is why quizzes, lead capture, and content-to-DM campaigns are where ManyChat shines. Their AI add-on can answer freeform questions inside a flow, but it does not query your Shopify catalog, your stock levels, or a specific customer's order history. Tyra inverts that. The agent reads each incoming message, reasons about what the customer actually wants, and calls into the live Shopify catalog, the order, the shipment, and your knowledge base before replying. "Do you have this in 38?" returns an answer based on current inventory, not a static product block someone last edited three months ago. Product carousels render from real-time data, including price, discount, and availability. When the agent is unsure, it hands the conversation to a human with full context. Neither model is universally better. Lead-gen quizzes and "comment X to get the link" campaigns are more naturally a flow. A retail customer asking three half-formed questions about fit, returns, and a previous order is more naturally a dialogue. Most Shopify brands have more of the second than the first. ## Instagram-first versus a unified inbox across IG, WhatsApp, email, and SMS ManyChat grew up on Messenger and Instagram and still treats those channels as the centre of gravity. WhatsApp arrived later and usually runs through a partner BSP such as Twilio, which means an extra layer of pricing and an extra layer of feature lag. SMS exists but is not where their investment goes. Email is not really their territory. Tyra is built around the idea that a European D2C brand serves the same customer across WhatsApp, Instagram, email, and SMS, and that the team handling those messages should see one thread per customer rather than four. WhatsApp is first-class because Tyra is a Meta BSP directly, so templates, interactive messages, catalog messages, and new Meta features arrive without a middleman. The inbox has assignment, internal notes, mentions, statuses, and audit trails of the kind a real support or CX team expects. For brands where WhatsApp has become a primary revenue channel, that depth matters more than another row of Instagram templates. ## US hosting versus EU hosting and GDPR posture ManyChat is a US company hosted on US infrastructure. They publish a DPA and rely on Standard Contractual Clauses, which is legally workable, and many European businesses use them without issue. The architectural fact remains: the data sits in the US, under a US-incorporated company, subject to US law including the CLOUD Act. Tyra is built in Europe and hosted in Ireland. There is no transfer of personal data outside the EU as part of normal operation, no SCC dance to manage, and the company answering a data subject request is a European entity. For brands whose DPO or legal team has flagged US-hosted SaaS as a procurement risk, that difference is the entire conversation. For brands where it has not, it is still a sensible default that becomes useful the day a regulator, an auditor, or an enterprise customer asks. ## European D2C operator focus versus US and global SMB ManyChat's centre of gravity is small businesses, creators, and coaches, with strong product depth for that audience and pricing tuned to it. Their roadmap, case studies, and community reflect that focus. It is a category-defining product for the segment it targets. Tyra is built for European D2C brands on Shopify that have moved past the solopreneur phase and now run customer conversations as an operational function. The product assumes you have a catalog with real inventory, orders that need looking up, returns that need handling, and an ops team that needs a real inbox. UI, agent, and templates are first-class in more than a dozen European languages rather than English with bolted-on translation. The fit is narrower than ManyChat's, deliberately, because the segment is what the product is shaped around. ## FAQ **Is ManyChat GDPR compliant?** They have a DPA and use Standard Contractual Clauses, which is the standard legal posture for a US SaaS serving European customers. Architecturally they remain US-incorporated and US-hosted, which different European businesses weigh differently. If your procurement or DPO is strict about EU residency, that is the question to answer first. **Can ManyChat's AI features do what Tyra's agent does?** For freeform text answering inside a flow, ManyChat's AI add-on works. For answers grounded in your live Shopify catalog, stock levels, and a specific customer's order history, no. The architectures are different: ManyChat's AI sits inside a flow, while Tyra's agent is the primary surface and calls into Shopify and your knowledge base on every turn. **What about Instagram comment-to-DM?** Both platforms do it. ManyChat has more pre-built templates and a deeper history with the pattern. Tyra handles it natively and shines once the DM leads to a product question that requires checking the catalog. **We use WhatsApp heavily. Does that change the answer?** Yes. ManyChat's WhatsApp runs through partner BSPs, typically Twilio, which adds cost and feature lag. Tyra is a direct Meta BSP, which usually means lower per-message cost passthrough and faster access to new WhatsApp features. If WhatsApp is a primary channel, the gap is noticeable. **Do you replace ManyChat or run alongside it?** Either works. Some brands cut ManyChat entirely once Tyra is handling their conversations and automations. Others keep a specific ManyChat flow running for a quiz funnel or a creator campaign and let Tyra handle the inbox, the AI agent, and WhatsApp. We are happy to tell you which approach makes sense for your setup. **How long does migration take?** For most brands, one to three weeks. Connecting Shopify, Instagram, and WhatsApp takes around half an hour. The real work is documenting the ManyChat flows worth recreating, configuring the AI agent on your knowledge base, and running both in parallel for a couple of weeks to validate coverage before sunsetting ManyChat. **Is Tyra cheaper than ManyChat?** Not at the bottom of the market. ManyChat is free up to a thousand Messenger contacts and inexpensive at the entry tier, which is hard to beat for a creator or very small business. Once you are running WhatsApp at volume, paying Twilio markups, and asking your tool to handle real customer service rather than campaign flows, the comparison shifts. **Are you trying to win ManyChat's core audience?** No. Creators, coaches, and Instagram-led SMBs are better served by ManyChat, and we will tell you that on a call. The brands we are built for are European Shopify operators where conversations across WhatsApp, Instagram, and email have grown into an operational surface that needs a real inbox and an agent that knows the catalog. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Recart **URL:** `tyra.ai/vs/recart` **Meta title:** Tyra vs Recart for Shopify: EU WhatsApp Inbox vs US SMS Marketing **Meta description:** Honest comparison of Tyra and Recart for Shopify. Tyra is the EU-built, WhatsApp-first inbox with an AI agent grounded in your catalog. Recart is the established US chat marketing tool. ## Tyra vs Recart Tyra is an EU-built, Shopify-native customer conversations platform that puts WhatsApp, Instagram, email, and SMS into one inbox, with an AI agent that reads your live catalog. Recart is a mature US chat marketing tool with a long Shopify track record, strong SMS and Messenger automation, and a large library of pre-built flows aimed at outbound revenue. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Recart side by side](/screenshots/vs-recart.png) ## Choose Tyra if You sell to European customers and you want a conversational system rather than a broadcast tool. Tyra is hosted in Ireland, built around GDPR from day one, and connects directly to Meta as a WhatsApp Business Solution Provider, so there is no reseller between you and the channel your customers actually use. The inbox unifies WhatsApp, Instagram DMs, email, and SMS into one thread per customer, and the AI agent answers questions grounded in your live Shopify catalog, including stock, variants, and prices. Pricing starts low enough that a brand doing a few hundred orders a month can run the whole stack without a sales call. If your team handles inbound conversations as a core part of the buying experience, Tyra is built for that shape of work. ## Choose Recart if You are a US Shopify brand where SMS is the centre of gravity and you want a vendor with a long track record on that channel. Recart has been in the Shopify ecosystem for years, originally as a Messenger Marketing pioneer and now as a chat marketing platform with mature WhatsApp and Facebook Messenger automation alongside SMS. Their enterprise plans, around $299 a month and up under the Concierge model, include hands-on flow building, a deep library of pre-built flows, and the kind of US-focused account support that larger D2C brands often want. If your goal is to push outbound campaigns and recover carts at scale in the North American market, and you do not need a heavy inbound inbox or EU data residency, Recart is a credible choice with real social proof behind it. ## EU hosting and GDPR vs US-hosted SaaS Tyra runs in AWS Ireland under an EU-incorporated entity. Customer data, message history, and AI context all stay inside the EU, and the company is not subject to the US CLOUD Act. For European brands with a DPO, an in-house legal review, or enterprise customers asking pointed questions on a DPA, that is one fewer thing to defend. Recart is US-headquartered and US-hosted. European customers are served through Standard Contractual Clauses, which is the normal pattern for US SaaS but is increasingly something European procurement teams push back on, especially in regulated categories or for brands selling to large retailers. Neither approach is wrong; they reflect where each company built its product and where its core customers sit. ## Conversational inbox and AI agent vs broadcast and flow tool Recart is, at its core, a marketing automation tool. The product is shaped around outbound flows, abandoned cart sequences, welcome series, and campaign sends, with templates and a flow library built up over years. Inbound conversations exist, but the centre of gravity is the campaign builder and the revenue it produces. Tyra is shaped around the inbox. Conversations from WhatsApp, Instagram, email, and SMS land in one thread per customer, with assignment, internal notes, and audit logs that a support team can actually run a shift on. The AI agent, Tyra, sits in that inbox and answers product questions, order questions, and routine support using your live Shopify catalog as ground truth. It hands off to a human when it should, and a human can take over a thread mid-conversation without losing context. If your brand treats customer conversations as part of the product rather than as a separate marketing channel, that difference matters more than any single feature. ## Unified inbox across WhatsApp, Instagram, email, and SMS vs WhatsApp and Messenger focus Recart covers WhatsApp, SMS, and Facebook Messenger well, with Messenger being the channel where it has the deepest history. Email and Instagram DMs are not the focus, and most Recart customers pair it with a separate email tool such as Klaviyo. Tyra is built around the four channels European Shopify brands actually use day to day: WhatsApp, Instagram DMs, email, and SMS. Because the inbox is unified, a customer who messages on Instagram, then emails the next day, then asks a follow-up on WhatsApp shows up as one person with one history, not three disconnected conversations. For brands that have given up trying to stitch this together across Gorgias, Klaviyo, and a WhatsApp tool, this is usually the thing that closes the decision. ## Pricing accessibility for smaller brands Recart's Concierge model starts at around $299 a month and scales up from there, with custom pricing at higher tiers. That positions it firmly as a mid-market and up product, which is consistent with the kind of brands featured in their case studies. Tyra's entry tier is meaningfully lower, designed so a brand doing a few hundred orders a month can adopt WhatsApp, an AI agent, and a real inbox without a procurement conversation. At scale the two products end up in similar territory once message volume and Meta passthrough costs are included, but the entry point is very different. If you are early in your WhatsApp journey and want to prove the channel before committing, the gap is real. ## FAQ **Is Recart available in Europe?** Yes. Recart serves European brands and supports WhatsApp as a channel. The product itself works fine from Europe; the open questions are usually around data residency, EU-language support depth, and whether SMS-led playbooks transfer to a market where WhatsApp dominates. **Does Tyra do outbound campaigns and abandoned cart flows like Recart?** Yes. Tyra supports WhatsApp campaigns, abandoned cart recovery, welcome flows, and post-purchase sequences. Recart's flow library is larger and more battle-tested on the SMS side, so if pre-built SMS templates are central to your plan, that is a real Recart advantage. On WhatsApp specifically the gap is much smaller. **How does the AI agent compare?** Tyra's agent is grounded in your live Shopify catalog, so it answers product questions using current stock, variants, and prices rather than a static knowledge base. Recart has added AI capabilities focused on copy generation and flow optimisation. They are solving different problems: one is an inbound conversation agent, the other is a marketing assistant. **Can I migrate from Recart to Tyra?** Yes, and it is usually straightforward because most of the migration is channel-by-channel. You export your contacts and consent records, set up Tyra against your Shopify store, rebuild your core flows in Tyra, run both in parallel for two to four weeks, and sunset Recart once Tyra is carrying the same revenue contribution. Most brands plan three to six weeks end to end. **What about WhatsApp pricing?** Tyra connects directly to Meta as a BSP, so WhatsApp conversation costs are Meta passthrough with no reseller markup. Recart also supports WhatsApp; their exact passthrough terms vary by plan and region, so it is worth getting both quotes against your expected volume. **Is Tyra a good fit for a US brand?** Honestly, less so today. Tyra is optimised for European Shopify brands where WhatsApp is the dominant channel and EU data residency matters. If you are a US brand running SMS-led campaigns at volume, Recart is a better match for your market. **Do I still need Klaviyo if I use Tyra?** Many Tyra customers consolidate email into Tyra and retire their separate email tool. Some keep Klaviyo for deep marketing automation and use Tyra for the inbox and AI agent on WhatsApp, Instagram, and email support. Both patterns work; it depends on how much you rely on Klaviyo-specific features today. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Respond.io **URL:** `tyra.ai/vs/respond-io` **Meta title:** Tyra vs Respond.io: EU Shopify Inbox vs Global Multi-Channel **Meta description:** Honest comparison for European Shopify brands. Tyra is EU-hosted, Shopify-native, WhatsApp first. Respond.io covers more channels and has a deeper workflow builder. ## Tyra vs Respond.io Respond.io covers more channels and ships a more elaborate workflow builder; Tyra goes narrower and deeper on the channels European Shopify brands actually sell on, with EU hosting and an AI agent that reads your live catalog. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Respond.io side by side](/screenshots/vs-respond-io.png) ## Choose Tyra if Your customers reach you on WhatsApp, Instagram, email, and SMS, and you run the business on Shopify. You want data stored in Ireland under EU law without a Standard Contractual Clauses paper trail, and you want your AI agent to answer "do you have the 38 in stock?" with the actual variant rather than a polite hedge. You would rather have one company on the hook for WhatsApp delivery (Tyra is a Meta BSP directly, not through a reseller) than a chain of providers. You value being live in an afternoon over having a workflow canvas that takes a quarter to master. Most of the brands we onboard fit this shape: 20 to 500 SKUs, one to fifteen agents, Shopify checkout, a real WhatsApp install base in Germany, France, Spain, the Nordics, or Italy. ## Choose Respond.io if Your customers are on channels we do not support, and that gap is structural rather than aspirational. LINE in Japan and Thailand, Telegram in Eastern Europe and the Gulf, Viber in parts of Central Europe, WeChat in China; if any of those is a real revenue channel, Respond.io has direct integrations and we do not. Their visual workflow builder is genuinely more capable than ours: branching, parallel paths, async waits, and a level of conditional logic that suits ops teams with a dedicated automation owner. If you run a large support floor (twenty-plus agents across multiple departments) their role and permission model is more granular, and their reporting dashboards are more customisable. None of this is faint praise; it is where they have invested for years and it shows. ## EU hosting vs Hong Kong hosting Respond.io is headquartered in Hong Kong and runs on global cloud infrastructure with region selection. For European brands this means Standard Contractual Clauses, a non-EU primary entity, and a data protection conversation that ends with "it is compliant, but." For a DPO at a German cosmetics brand or a French DTC food company, "but" is not a good word. Tyra is incorporated in the EU, hosts core message processing in AWS Ireland, and uses EU sub-processors for the parts of the stack that touch message content. There is no transatlantic transfer to argue about for the message body, the customer profile, or the order context the agent reads from Shopify. It is the same WhatsApp, the same Meta rails, but the operator of record sits inside the GDPR perimeter. This matters less if you are a global business with a Hong Kong or Singapore parent. It matters a lot if you are a European brand and procurement, legal, or your retail partners ask where the data lives. ## Horizontal breadth vs Shopify-vertical depth Respond.io is built to be the inbox for any channel anywhere. That is a real product strategy and it serves their largest customers well. The cost is that every channel is a connector among many, and depth on any single one is bounded by what the most generic abstraction can express. Tyra picks the channels European Shopify brands actually run revenue through (WhatsApp, Instagram, email, SMS) and builds the surface area that matters underneath them. WhatsApp gets product carousels rendered from your live Shopify catalog, single-use discount codes generated on demand, abandoned checkout recovery wired to Shopify's checkout events, and order status replies that read from the actual fulfilment record. Instagram DM threads carry the same context. Email lives in the same inbox with the same customer timeline rather than as a bolt-on. If your roadmap requires LINE or WeChat, none of this depth helps you. If your roadmap is "sell more on WhatsApp in Germany next quarter," depth is the thing. ## Workflow builder vs catalog-grounded LLM agent Respond.io's workflow builder is the centre of gravity in their product. You compose triggers, branches, conditions, AI nodes, and human handoffs into a canvas that can model most support and sales flows. It is powerful and it rewards investment. Tyra leans the other way. We ship event-triggered automations for the common cases (welcome flows, abandoned cart, post-purchase, review requests, ticket routing) and put the intelligence in an AI agent that is grounded in your Shopify catalog at query time. It reads stock, price, variants, collections, and the customer's order history, and answers in your brand voice. When a shopper asks "is the linen blazer still in the sand colour, size M?", it checks the variant, confirms, and offers to send a checkout link. When they ask "where is my order?", it pulls the tracking from the fulfilment record. Neither approach is universally better. A team with a dedicated automation engineer and complex non-commerce flows will get more out of Respond.io. A team that wants the agent to handle the long tail of "is this in stock, how do I return it, when will it ship" without anyone hand-authoring branches will get more out of Tyra. ## Pricing model Respond.io publishes a tiered SaaS plan (Starter, Growth, Advanced, Enterprise) priced per workspace with contact caps and feature gates, plus per-channel costs and, on some channels, a markup on top of the underlying carrier or Meta fee. The Enterprise tier is custom and sales-led. Tyra publishes a per-seat price with Meta WhatsApp conversation fees passed through unchanged, no markup on Meta charges, and no contact-count gate. Shopify and the WhatsApp Business API are included in every plan rather than locked behind a higher tier. Whether this is cheaper for you depends on your seat count, contact volume, and channel mix; for most European Shopify brands in the 1,000 to 50,000 monthly conversations range it works out lower, but the honest answer is run the numbers against your own volume. ## FAQ **Is Respond.io a worse product than Tyra?** No. They are older, broader, and have invested heavily in a workflow canvas and channel coverage that we have not matched. They are a better fit than us for businesses whose channel mix sits outside Meta plus email and SMS, or whose ops team wants a deep visual builder. We win in a specific segment: European Shopify brands who want depth on the channels they actually use and EU data residency without caveats. **Can I keep my WhatsApp number if I move from Respond.io to Tyra?** Yes. Both companies are direct Meta BSPs, so the number transfer goes through Meta's BSP-to-BSP process without a third party in the middle. Templates re-approve under our BSP, typically within a day. The slowest part is usually rebuilding workflows you authored in Respond.io, since visual canvases do not export cleanly between vendors. **Does Tyra support Telegram, LINE, Viber, or WeChat?** No. We support WhatsApp, Instagram, email, and SMS. If any of those four are essential revenue channels for you, Respond.io is the correct choice and you should not switch. **How does Tyra's AI agent compare to Respond AI?** Respond AI is a general-purpose LLM layer you can train on documents and slot into workflow nodes. Tyra's agent is purpose-built for commerce: it reads the Shopify catalog and order graph at query time rather than relying on a static knowledge base, so answers about stock, price, variant availability, and order status are always current. For non-commerce support use cases the two are closer; for commerce-specific replies Tyra's grounding tends to produce better answers with less configuration. **We are a large support org with twenty-plus agents. Is Tyra a fit?** We have customers in that range, but Respond.io's permission model and reporting customisation is more mature for organisations with multiple departments and complex access requirements. If your structure demands fine-grained role design across many teams, evaluate both honestly; if your team is up to roughly fifteen agents on a single brand, Tyra's standard roles cover the common cases. **How long does onboarding take?** Most Tyra customers are live in under an hour for the inbox and within a day for the agent and core automations. Respond.io's depth means a typical implementation takes two to four weeks if you use the workflow builder seriously. Neither timeline is wrong; they reflect different product philosophies. **Where is my data stored?** Tyra stores message content and customer data in AWS Ireland with EU sub-processors. Respond.io is Hong Kong-headquartered and runs on global cloud infrastructure with region selection and Standard Contractual Clauses for EU customers. If EU data residency is a procurement or DPO requirement, the difference is material. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Stunning **URL:** `tyra.ai/vs/stunning` **Meta title:** Tyra vs Stunning: Stripe Dunning and WhatsApp Recovery Compared **Meta description:** Honest comparison of Tyra and Stunning. Stunning is a focused US email dunning specialist. Tyra is an EU-built customer conversations platform with WhatsApp, email, SMS and Instagram in one inbox. # Tyra vs Stunning Stunning has spent more than ten years building one focused thing, email-based Stripe dunning, and they do it well; Tyra is a broader EU-built customer conversations platform that recovers failed payments over WhatsApp and email as one part of a wider inbox. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Stunning side by side](/screenshots/vs-stunning.png) ## Choose Tyra if You run a European Shopify brand, or a Stripe subscription business with subscribers who actually open WhatsApp, and you want one tool that handles support and recovery together. Tyra is built in the EU, hosted in Ireland, and integrates as a native Stripe App and a Shopify-native install. The AI agent is grounded in the live Shopify catalog, so when a customer asks about an order or a charge in the same thread where you ask them to update their card, the answer is real. If you would rather have one inbox for WhatsApp, Instagram, email and SMS than three separate vendors for support, marketing and dunning, Tyra is the closer fit. If GDPR and EU data residency are non-negotiable for your legal team, Tyra is the closer fit on that as well. ## Choose Stunning if Stunning has been doing Stripe email dunning since around 2013. They have outlasted most competitors in the category, and the product reflects that focus: deliverability discipline, sender reputation, template quality, and a tight loop with Stripe webhooks. Pricing is simple and the entry tier is cheap. If your subscribers are mostly in the US and Canada, if email is the only channel you can realistically use, and if you already have separate tools handling customer support, marketing and the rest of the lifecycle, Stunning solves the narrow problem well and does not ask you to adopt a broader platform. That narrowness is a feature, not a flaw, and for many US SaaS businesses it is exactly the right shape of tool. ## Email-only recovery versus WhatsApp and email together Stunning recovers failed payments through email. That is the channel, and the product is built around squeezing the most out of it: deliverability, retry cadence, copy, branded receipts, the things that move the needle when email is all you have. For a US SaaS business with a customer base that lives in inboxes and rarely opens WhatsApp, that is a reasonable bet. Tyra recovers failed payments on WhatsApp first and falls back to email when WhatsApp is not available or not opted in. The reason is open rates and time-to-read, not better copy. A WhatsApp message about a failed charge gets read in minutes; an email gets read in days, if at all. For European subscribers and for any market where WhatsApp is the default messenger, that channel difference is the entire argument. For markets without WhatsApp adoption, the advantage collapses and Stunning's email depth will hold up well. The honest framing is that the channel decision dominates. If your customers are on WhatsApp, recovering them there is meaningfully better than recovering them by email. If they are not, the comparison is much closer and Stunning's decade of email-specific work counts for a lot. ## EU hosting and GDPR posture versus US infrastructure Tyra is incorporated and operated in the EU, with data hosted in AWS Ireland. There are no Standard Contractual Clauses to sign, no transatlantic transfer paperwork, no awkward conversations with a European DPO about where customer messages are stored. For a Shopify brand in Germany, France, the Nordics or the Netherlands, that is the path of least friction. Stunning is US-headquartered and US-hosted. They are a serious company with a long track record, and for US customers that is simply not a concern. For European customers it means working through SCCs and explaining the transfer to a privacy team that is increasingly unwilling to wave it through. Neither posture is wrong; they are built for different home markets. ## A pure dunning tool versus a full conversation platform Stunning solves one problem. When a Stripe charge fails, Stunning sends the recovery emails, tracks the outcome, and tells you what was recovered. It does not try to be your support inbox, your marketing channel, or your B2B invoice delivery system. If you already have Zendesk or Front for support, Klaviyo for marketing and something else for invoicing, you do not need Stunning to do those things, and the focused scope keeps the product easy to evaluate and easy to live with. Tyra is a customer conversations platform that happens to do dunning very well. The same inbox handles support tickets across WhatsApp, Instagram, email and SMS; the same AI agent that answers product questions also handles the conversational side of a failed payment; the same system can deliver Stripe invoices over WhatsApp for B2B and track read status. For a team that is currently paying for three or four overlapping tools, the consolidation is the point. For a team that already has a stack they like, that breadth is overhead they do not need. ## Two-way conversational inbox versus notify-only Stunning sends messages. If a customer replies to a dunning email asking why their card was declined, the reply lands in whatever shared inbox your team uses for support, and someone has to pick it up, look up the Stripe customer, and answer. The dunning tool does not close the loop on questions. Tyra is built around two-way conversation. When a customer replies to a WhatsApp dunning message asking what they were charged for, the AI agent answers from the live Shopify catalog and the Stripe data, in the same thread, without a human picking it up. When the question is genuinely hard, a human on your team takes over in the same inbox. The recovery message and the support reply are the same conversation, which is how customers experience it anyway. Stunning is a good tool for the half of that conversation it covers; Tyra covers both halves. ## Shopify and Stripe dual ICP versus Stripe-only Stunning is a Stripe tool. That is the ICP, that is the integration depth, and that is the customer they understand. If you are a pure Stripe subscription business with no Shopify dependency, Stunning will fit your shape neatly. Tyra serves European Shopify brands as the primary ICP, and Stripe subscription businesses as a Stripe App for the dunning and lifecycle messaging side. The Shopify-native install means the AI agent is grounded in your real catalog, your real orders, your real customers, with no extra plumbing. For a Shopify brand that also runs Stripe subscriptions on the side, the two integrations sit in one tool. For a Stripe-only business, Tyra works as a Stripe App but you are paying for breadth you may not use. ## FAQ **Is Stunning still a good choice in 2026?** For US SaaS businesses that need email dunning and nothing else, yes. The product is mature, the focus is real, and the team has been doing this for over a decade. The honest reason to pick Tyra over Stunning is that you want WhatsApp recovery, EU hosting, or a broader platform, not that Stunning has stopped being good at what it does. **My subscribers do not use WhatsApp. Will Tyra still beat Stunning on recovery?** Probably not. Tyra's recovery advantage depends on WhatsApp open rates, and that only materialises for customers who have opted in and actually use WhatsApp. Without that, Tyra falls back to email, where Stunning's decade of deliverability work is a real strength. Test on your own customer base before assuming the lift. **Can I run both?** Yes. Some teams keep Stunning on the email side and add Tyra for WhatsApp and support. Stripe webhooks fire to both. You will need to handle attribution carefully so you do not double-count recoveries, but the setup is straightforward and lets you measure the WhatsApp lift directly on your own data. **How does Tyra handle GDPR compared to Stunning?** Tyra is EU-incorporated, EU-hosted in Ireland, and the data never leaves the EU by default. Stunning is US-hosted and relies on Standard Contractual Clauses for European customers. Both are workable; one is less work. **Will WhatsApp messaging cost more than Stunning's email?** Per message, yes. Stripe transactional emails are essentially free; WhatsApp utility conversations cost a few cents in EU markets. The number that matters is cost per recovered euro, and at typical open-rate differences WhatsApp recovery is cheaper per recovered euro even though it is more expensive per message sent. **Does Tyra replace my support tool?** For most Shopify brands, yes. The inbox handles WhatsApp, Instagram, email and SMS with the AI agent grounded in your catalog. For Stripe-only SaaS using Zendesk or Intercom, Tyra can run alongside as the WhatsApp and dunning layer without forcing you to migrate support. **How long does it take to switch from Stunning to Tyra?** Three to six weeks is realistic, mostly depending on whether you need to run a WhatsApp opt-in collection campaign first. The Stripe App install itself takes about fifteen minutes. Running both in parallel for one billing cycle is the safe path. [Book a demo](https://cal.com/tyra/demo) --- # Tyra vs Wati **URL:** `tyra.ai/vs/wati` **Meta title:** Tyra vs Wati: EU-built Shopify inbox or APAC WhatsApp veteran **Meta description:** An honest comparison for European Shopify brands choosing between Tyra and Wati. EU hosting, no message markup, unified inbox versus APAC reach and a deep template library. ## Tyra vs Wati Wati is the mature WhatsApp-only product with APAC roots and a huge template library; Tyra is the EU-built, Shopify-native inbox that unifies WhatsApp, Instagram, email, and SMS without marking up Meta's per-conversation rates. [Book a demo](https://cal.com/tyra/demo) ![Hero — Tyra and Wati side by side](/screenshots/vs-wati.png) ## Choose Tyra if You run a Shopify brand in Europe and the people you sell to expect replies in their own language from a company that stores their data under EU law. You want WhatsApp handled properly as a first-class channel through a direct Meta BSP relationship, with Meta's conversation prices passed through at cost rather than re-sold with a margin on top. You also want Instagram DMs, email, and SMS landing in the same inbox so a customer who first asked about sizing on Instagram and later emailed about a return is one conversation, not three. You want an AI agent that actually reads your live Shopify catalog, inventory, and order history rather than a flow tree guessing at intent. If an EU-hosted, Shopify-native, Meta-direct setup matches how you operate, Tyra is the closer fit. ## Choose Wati if You operate primarily in India, Southeast Asia, the Middle East, or Latin America, where Wati has years of local sales presence, support hours that line up with your team, and pricing tuned to those message corridors. You want the largest available library of pre-built WhatsApp templates, including niche verticals like dental clinics, tuition centres, and real estate brokers, because most of your sends are transactional and template-led. You are buying a WhatsApp-only product on purpose and do not need Instagram, email, or SMS in the same inbox. You are budget-sensitive at the very bottom of the market and want a low entry tier from a vendor with a mature, well-known WhatsApp Business product. In those cases Wati is a genuinely strong choice and we would not try to talk you out of it. ## APAC hosting and HK incorporation versus EU hosting under GDPR Wati is headquartered in Hong Kong and runs on global cloud infrastructure with EU Standard Contractual Clauses layered on top for European customers. That arrangement is legally workable and Wati is not non-compliant, but architecturally the data, the company, and the legal regime all sit outside the EU. For a German or French DPO reviewing sub-processors, that means more diligence, more questions, and a harder internal sell. Tyra is incorporated in the EU and hosts customer message data in AWS Ireland (eu-west-1) with EU-based sub-processors for storage. The point is not that one is legal and the other is not. The point is that an EU company storing EU customer data in Ireland under EU law is a shorter conversation with procurement and legal than a Hong Kong company explaining its SCC posture. For brands selling into Germany, the Nordics, the Netherlands, and France in particular, this difference shows up in how quickly contracts get signed and how comfortable the brand is talking publicly about its data practices. ## WhatsApp-only versus a unified inbox Wati is a WhatsApp Business product. That is its strength: the team has spent years building deep WhatsApp tooling, template flows, and broadcast features. If WhatsApp is genuinely the only channel that matters to you, that focus is an advantage. Tyra treats WhatsApp as first-class through a direct Meta BSP relationship, but puts Instagram DMs, email, and SMS into the same inbox and on the same customer timeline. For a Shopify brand, this matters because customers do not stay on one channel. They ask about a product on Instagram, get an order confirmation by email, message on WhatsApp when the parcel is late, and reply to an SMS shipping update. In Wati, those are separate systems or separate tools entirely. In Tyra, an agent sees the whole thread. If you are consolidating Gorgias or Front plus a WhatsApp tool plus an Instagram inbox, Tyra replaces that stack. If you only ever want WhatsApp, Wati does that one thing well. ## Message markup versus pass-through Meta pricing Most WhatsApp BSPs charge a margin on top of Meta's per-conversation rates. It is a normal business model and Wati is transparent that it operates this way. For a brand sending modest volume, the markup is a manageable line item. Tyra passes Meta's conversation rates through unchanged and makes its money on software. The arithmetic matters once volume grows: at fifty thousand marketing conversations a month into Germany at Meta's published rate, a thirty percent BSP markup is roughly an extra eleven hundred euros every month, recurring, on top of the software fee. For a brand running serious WhatsApp marketing, that adds up to a meaningful budget line over a year. This is worth checking against Wati's current quote for your specific corridors before you decide. The principle holds regardless: Tyra's incentive is to make the software better, not to make you send more billable messages. ## Templates, languages, and the Shopify-native depth Wati's pre-built template library is the largest in the market, built up over years of community contributions across a huge range of verticals. If your business depends on having a starting point for transactional templates in a niche category, that breadth is real and useful. Tyra ships a smaller, curated set of templates focused on European Shopify use cases, and the UI, the AI agent, and the template tooling all ship in twelve-plus European languages as first-class citizens rather than as translations bolted onto an English product. For a brand selling across Germany, France, Italy, Spain, the Netherlands, and the Nordics, agents replying in native languages and an AI agent that understands those languages is the baseline, not an upgrade. The Shopify integration is where the depth shows up most. Tyra's AI agent queries the live Shopify catalog when a customer asks about a product, reads current inventory before promising availability, and pulls real order history when handling a "where is my order" question. Wati integrates with Shopify but the agent layer is closer to keyword routing with a GPT add-on rather than a model grounded in your live store data. ## FAQ **Is Wati GDPR compliant?** Yes, Wati operates with Standard Contractual Clauses for European customers and is not in violation of GDPR. The honest distinction is architectural rather than legal: Wati is a Hong Kong company using global infrastructure with EU SCCs layered on, while Tyra is an EU company hosting EU data in Ireland under EU law. Both can be defended to a regulator; one is a shorter conversation with your DPO. **Can I keep my WhatsApp number if I move from Wati to Tyra?** Yes. WhatsApp Business Platform numbers are portable between BSPs through Meta's standard migration process. Your number is not locked to Wati. Templates do need to be re-approved by Meta under the new BSP, which Tyra can pre-load to speed up. Plan for one to four hours of unreachability during the actual BSP switch. **Does Tyra's AI agent really read my Shopify catalog live?** Yes. The agent queries product data, inventory, and order history at the moment of the customer message rather than relying on a periodically synced knowledge base. That means if a product just went out of stock, the agent will not promise it, and if an order shipped this morning, the agent can tell the customer the tracking number without a human in the loop. **Where is Wati genuinely better than Tyra?** APAC market presence, the size of the pre-built template library, support hours that match Indian and Southeast Asian working days, and pricing tuned for high-volume APAC message corridors. If you are an Indian D2C brand sending mostly transactional templates to Indian customers, Wati is the more natural pick. **What does Tyra cost compared to Wati?** Tyra's software pricing is published and sits in a similar range to Wati's mid-tier plans, but the total cost picture is different because Tyra passes Meta's conversation rates through at cost and Wati adds a markup. At low volumes the difference is small. At fifty thousand marketing conversations a month into the EU, the markup gap becomes the dominant line item. Get a quote from both for your actual volume. **Do I need to talk to sales to start with Tyra?** No. Onboarding is self-serve at every tier, including the embedded WhatsApp signup with Meta. A demo call is available if you want a walkthrough, but it is not a gate. **Can I run Tyra and Wati on the same WhatsApp number?** No. Meta allows only one BSP per WhatsApp number. You can run them on different numbers in parallel during a migration period, but most brands consolidate onto one BSP once they have decided. [Book a demo](https://cal.com/tyra/demo) ---