Order confirmations on WhatsApp, in the same inbox as Instagram, Facebook Messenger, 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, Facebook Messenger, and SMS landing in the same EU-hosted inbox. One CTA, one place to reply, one AI agent reading the live Shopify catalog.
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 tracking link they cannot find
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.
Delivery exceptions that become chargebacks
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 size change that never happened
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.
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.
- AWS Ireland data residency
- No US sub-processors on critical path
- DPA under Irish law with German DPO
- Explicit consent capture with full audit trail
- STOP replies honored within 60 seconds
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.
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.
- Replies land in unified inbox, not Meta Business Manager
- Full Shopify order context in side panel
- Template management with 12 EU languages
- Per-template performance tracking
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.
- 3-5 second median event-to-delivery latency
- Direct carrier integrations (PostNord, DHL, GLS, UPS, DPD, FedEx, Royal Mail, Bring, Hermes/Evri, Colissimo, Posti, Correos)
- One-click checkout extension for WhatsApp opt-in
- Multi-warehouse and split shipment support
orders/createConfirmation sent
orders/paidPayment confirmed
fulfillments/createShipping notification sent
carrier/deliveredDelivery confirmed
"Yes, I can swap your order to a Large. I've checked and the order hasn't been picked yet, so the change is confirmed. You'll receive the Large instead of Medium. Anything else I can help with?"
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: 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 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.
- Real-time inventory and variant checks
- Order modifications written back to Shopify
- 85% escalation accuracy on order modifications
- 92% accuracy on tracking status replies
- 12 EU languages at production quality
Frequently asked questions
- 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.
- 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.
- 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.
Send order confirmations customers actually see
Move post-purchase notifications to WhatsApp. EU-hosted, Shopify-native, with AI that handles the replies.