Connect the evidence.

Your registered test customer

The owner explicitly enrolled a real test participant in the persistent local Resolve database. The registration email and provider acceptance were recorded. An existing test order was matched by its exact checkout email. This is an actual registration record, not a generated shopper or dissatisfaction story. The public profile excludes the email address and provider identifier; it is a saved projection, not a live cloud database.

Use the same registered email at Shopify test checkout. With the live Shopify reader configured, matching test orders show the Resolve participant reference and actual Shopify customer ID. Registration confirmation is separate from recovery messaging; it does not enable browsing tracking or automatic recovery emails.

What appears now

• Actual test orders read from Shopify, with creation, successful test payment, cancellation and refund timestamps.
• A recorded Gemini operator-preview message for an actual cancellation. The enrolled owner’s cancellation support email and saved provider receipt. General customer sending is disabled; provider acceptance is distinct from confirmed inbox delivery.
• A connection label and last-read time. “Recorded Shopify activity” means a saved snapshot. “Connected to Shopify” means the server read the store successfully.

Connect live test orders on Vercel

1. Open your Resolve project in Vercel, then Settings → Environment Variables.
2. Add the existing server-side values for SHOPIFY_SHOP_DOMAIN, SHOPIFY_CLIENT_ID SHOPIFY_CLIENT_SECRET and EMAIL_TEST_TO to Production. Never put secrets in browser code or a public repository.
3. Redeploy, open Customer activity, and check for “Connected to Shopify”. The reader is restricted to the authorized Resolve development store and orders explicitly marked as test orders.
4. Place an order using Shopify’s test payment gateway. If desired, cancel that order in Shopify. The open activity page checks for updated orders every 30 seconds. It creates no orders and sends no email when viewed.

If the connection is unavailable, the page retains the last recorded Shopify snapshot and identifies it as recorded. A saved record is not live tracking.

Browsing and cart activity

Order reads cannot show product browsing or an abandoned cart. These need the deployed Shopify storefront collector, analytics permissions, tested collection, and durable event storage. The current public workspace shows those connections as unavailable; it does not generate substitute events.

Automatic email

The enrolled owner trial runs on the operator’s computer every 60 seconds. A matching customer-cancelled test order triggers a Gemini support email to the enrolled address, reserved once in persistent local storage. The workspace displays the message and saved receipt; visiting it never sends an email. Keep the worker running for new owner tests. Other customer sending remains disabled. A complete automatic workflow needs customer identity and communication permission, persistent event and intervention history, a verified sender, a running scheduler, cooldowns, and delivery receipts. The older operator preview is separate from the enrolled owner support email. The local trial is not an always-on Vercel email worker.

A shopper leaving does not prove dissatisfaction. No outreach should be claimed without an eligible customer and recorded evidence.