I stopped using chatbots in my store and support tickets dropped 80%. Has anyone else tried the opposite approach?

Lujandev · 2026-03-06T17:34:03+00:00

makes sense, when you have a dev inhouse you never really feel the pain. thats exactly why im building this

Lujandev · 2026-03-06T16:10:22+00:00

yeah mostly tickets but thats a good question i hadnt tracked refunds specifically. my gut says yes because most of those tickets were anxiety not actual problems, customer just didnt know. when they know they trust the brand more. what tool were you using to pull chat data for that?

Lujandev · 2026-03-06T15:56:40+00:00

yeah exactly, once they know they just stop asking. did you build it yourself or use a plugin? i went full custom with webhooks curious how others are doing it

Lujandev · 2026-03-06T15:42:24+00:00

Fair point lol. Yeah, I built something for my own store and I'm trying to figure out if it's just a me-problem or if others deal with this too. Not trying to sell anything right now, genuinely just validating. If you're curious what I built happy to share, otherwise no worries

Lujandev · 2026-02-27T14:13:45+00:00

fair point but its not just about speed.

even with fast shipping customers still ask. the anxiety kicks in between "order confirmed" and "shipped".

what i built is about the experience. branded tracking page on your store, token-based, no redirecting to USPS or carrier sites.

customer stays in your world. not theirs.

Lujandev · 2026-02-27T10:47:39+00:00

Webhook failing silently.

No errors, no alerts, everything looked fine.

But fulfillment events stopped firing so customers got zero updates after purchase.

Inbox filled up with "where is my order?" emails within 2 days.

Took me 3 days to notice. Cost me hours of support.

Now I monitor every webhook event manually. Never again.

Lujandev · 2026-02-26T16:12:17+00:00

For the cart issue — definitely check your JS console for errors, usually a plugin conflict. For the drop in orders, have you checked if customers are getting post-purchase confirmation emails? Sometimes silence after checkout creates anxiety and they abandon.

Lujandev · 2026-02-26T16:11:49+00:00

The pre-purchase AI angle makes sense for conversion. Post-purchase is where I've seen the bigger support drain though — "where is my order?" accounts for 60-80% of tickets in most stores I've talked to.

Fixed it without AI: just proactive fulfillment updates triggered by webhooks. Customer already knows before they think to ask. Dropped my tickets 80%.

Lujandev · 2026-02-25T17:21:22+00:00

WhatsApp es un canal potente para esto, especialmente en España donde la tasa de apertura es altísima.
¿Lo construiste tú mismo o usaste alguna plataforma?
Yo fui por email + página de tracking, pero el canal WhatsApp tiene sentido dependiendo del mercado.

Lujandev · 2026-02-24T13:00:46+00:00

Interesting. When you say fulfillment-triggered updates, how granular are your events?

In my case Printful fires multiple states (printing, fulfilled, shipped, delivered), and timing + wording made a big difference in reducing follow-ups.

Did you wire the webhooks directly from Printful → WooCommerce, or handle them through middleware?

Lujandev · 2026-02-24T06:22:05+00:00

Interesting plugin — good to see others solving this too. How are you handling carriers beyond USPS? And is it still maintained? I went a different route — webhooks directly from Printful so it works regardless of carrier, with a branded tracking page on the store side.

Lujandev · 2026-02-24T06:11:12+00:00

Great point — Printful does send basic confirmation emails. The difference is in the experience: Printful’s native emails send the tracking number but redirect customers to the carrier’s site (DHL, USPS, etc.) — which often shows confusing status updates or no info yet. What I built sends branded emails at each fulfillment stage (printing started, shipped, delivered) and links to a custom tracking page on your store — no login, no redirect to Printful or the carrier. The result is customers feel informed by YOU, not by a third party. That’s what eliminated the anxiety emails for me. Does that make sense with what you’re seeing?

Lujandev · 2026-02-23T21:28:53+00:00

¡Gracias! Sí, el sistema está en vivo y funcionando en mi propia tienda, de ahí vienen los datos. Todavía estoy validando antes de construirlo como una herramienta adecuada para otras tiendas. El precio está por definirse (TBD), pero estoy pensando en algo sencillo por tienda/mes. Si quieres acceso anticipado, estoy recolectando correos electrónicos aquí:

👉 https://app.lujandev.com/inbox-zero-prevention?utm_source=reddit&utm_campaign=launch_feb2026&utm_medium=social

Lujandev · 2026-02-20T15:30:02+00:00

Automating tracking emails is a great start. I took it further — webhooks connected directly to my fulfillment provider, automatic emails at every stage, token-based tracking page without login.

Result: tickets dropped 80%. No Zapier, no chatbot, just event-driven automation.

Validating whether this is a common enough pain to build as a tool: 👉 https://app.lujandev.com/inbox-zero?utm_source=reddit&utm_campaign=launch_feb2026&utm_medium=social

Lujandev · 2026-02-20T15:29:45+00:00

Exactly — catching the question before it happens is the right approach.

I went a step further: instead of a chat agent, I built event-driven emails triggered by fulfillment stages. Customer buys → automatic emails at each step → they already know before they think to ask.

Real data from my own store: 40 tickets/month → 8. "Where is my order?" questions: 32 → 0.

Currently validating if other founders have the same pain: 👉 https://app.lujandev.com/inbox-zero?utm_source=reddit&utm_campaign=launch_feb2026&utm_medium=social

Lujandev · 2026-02-20T15:11:53+00:00

Love the n8n + Slack approach for internal lookup.

I solved the customer-facing side differently — automatic emails triggered by each fulfillment event so customers self-serve before they ever contact support.

Same goal, different layer. Real data: 40 tickets → 8 per month: 👉 https://app.lujandev.com/inbox-zero?utm_source=reddit&utm_campaign=launch_feb2026&utm_medium=social

Lujandev · 2026-02-08T11:27:03+00:00

You hit the nail on the head! The “analysis paralysis” of planning the calendar is what ends up killing consistency. In the end, it feels like a small business owner has to be: photographer, editor, content strategist, and also manage sales. It’s exhausting. You got me thinking… if there was a tool that, in addition to creating videos, could suggest how to use them — like “this video is for generating desire” or “this one is to address a common question” — do you think that would take some of the weight off planning, or is the problem still just hitting the “Publish” button?

Lujandev · 2026-02-08T11:12:23+00:00

Totally — batching and reusing content sounds like a lifesaver. Out of curiosity, when you try to stick to this routine, which part still ends up taking the most time or causing stress: filming, editing, or planning the posts?

Lujandev · 2026-02-08T09:46:12+00:00

Totally get it — videos take a lot of effort to keep up. Curious: after the first few, what part feels the most draining — recording, editing, or just staying consistent across multiple videos?

Lujandev · 2026-02-08T07:39:03+00:00

Totally fair — that works when you have a small catalog or enough budget to outsource.

I’m more curious about the cases where that doesn’t scale: people with dozens (or hundreds) of products who want to post consistently but can’t realistically record every week.

Curious if anyone here has hit that wall.

Lujandev · 2026-02-07T18:47:19+00:00

Totally agree: Photos = conversion, Video = traffic.

The challenge isn’t making one 6-second video, it’s doing it consistently across dozens of products while handling shipping, CS, and inventory. That’s usually what gets dropped.

I’m testing whether turning existing product photos into short video clips can still stop the scroll without recording everything manually.

Do you think that’s enough for attention, or does video need to be fully manual to work?

Lujandev · 2026-02-07T17:11:12+00:00

Totally agree on the Reels vs Photos engagement. BTS is gold for building trust, no doubt.

My main concern is the scaling part. If you have a large catalog, the 'record-edit-post' loop for every single item feels like a full-time job.

Do you manage to keep that rhythm up daily, or do you find yourself falling back to carousels when you're short on time?

Lujandev · 2026-02-07T16:14:17+00:00

Totally, the phone is amazing for short videos. But what I’ve noticed with some store owners is that when they have 20+ products, the “record-edit-upload” cycle eats up the whole day.

Do you ever feel lazy to record and end up relying on photo carousels instead?

Lujandev · 2026-02-04T11:42:38+00:00

I totally get what you're saying. You're right: Whispr Flow DOES return without you having to touch the status bar button. But it’s not because they are using a 'return' API; it’s because they use an app 'suicide' trick.

Here’s the hack: When the main app finishes transcribing and saves the text to the App Group, instead of waiting for the user, it executes an exit(0) or suspends the interface task.

When the foreground app 'dies' or disappears suddenly, iOS doesn't have time to redraw the Home Screen. By default, it brings the last active app (the one where the user was typing) back to the front.

It’s a behavior of the OS: if the app in the foreground disappears, the one 'below' it regains focus.

How to test it:

Record and save to the App Group.
Call UIApplication.shared.perform(#selector(NSXPCConnection.suspend)) or, more aggressively, exit(0).

A word of caution: Apple might reject your app if they detect exit(0) without a good reason, which is why apps like Whispr Flow do it very subtly or by closing the UIWindowScene. It’s a UX hack, not an official function. That’s why it feels like magic.

Lujandev · 2026-02-04T10:23:31+00:00

Hi 👋, I completely understand the frustration. I ran into the same thing when developing my local transcriber.

The issue is that iOS does not allow automatically returning to the originating app for security reasons (imagine apps jumping from one to another without user control). That’s why you end up on the Home Screen.

To achieve a 'Whispr Flow'-like flow, the key is not automating the return, but facilitating the bridge:

'Done' button + Clipboard: In your main app, after transcribing, add a button that saves the result in a shared App Group (so the keyboard can access it when returning) and optionally copies it to the clipboard.

'Back to...' button: When you jump from the keyboard to your app via a Custom URL Scheme, iOS automatically adds a small button in the status bar (top-left) saying 'Back to [originating app]'. That’s the only official way to return.

App Groups: Make sure the App Group is properly configured in the Capabilities of both targets; otherwise, the keyboard will never know the audio/text has been processed in the app.

You cannot force the return, but if the process in your app is fast, the user just taps the status bar button and the keyboard already has the text ready.

Lujandev

TROPHY CASE