The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
For background email dispatch or a tax-credit estimation, “the cron ran” isn’t enough information.
I need to know which item ran, whether it failed, and whether retrying it will duplicate an effect.
That’s where Redis/BullMQ earns its place: per-job state, bounded concurrency, retries with backoff, and a failed-job queue I can inspect.
The worker still needs careful design. A retry must not send a second email or apply the same calculation twice. I use durable operation records and provider idempotency keys where available.
If a database write must produce a job, an outbox closes the gap between committing the record and enqueueing the work.
Cron remains useful for scheduling. The queue manages execution and recovery.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Your support team goes home at 6. Your customers don't. An online retailer we worked with had a simple problem.
Shoppers asked questions at 11pm, on weekends, on holidays.
The answers came the next morning, and by then a lot of them had bought somewhere else.
We built a 24/7 AI chat into their store. Not a FAQ bot that says "I didn't understand that" three times.
It handles the common questions on its own, recommends products inside the conversation, and drops every chat into their CRM with the full customer context.
When a person does step in, they aren't starting from zero. → 50% more conversions → 35% faster response time → 40% less support workload The part people underestimate is the CRM link.
A chat that sells but forgets who the customer is just moves the problem to your team. Support and sales turned out to be the same conversation.
Question for ecommerce founders. What share of your support questions come in outside working hours? Have you ever checked? It's usually the first number I ask for.
A system I designed for local service businesses that consistently lose out on Google reviews. Full build in progress
Automated Review Requests for Local Service Businesses
The Problem:
Google reviews are one of the strongest signals for local search ranking, this is well established across HVAC companies, cleaning services, salons, contractors, and landscaping businesses. Every owner in this space knows reviews matter. Very few of them ask for one consistently.
The reason isn't a lack of care, it's a lack of a system. Asking every customer, right after every job, every single time, is a small task with no natural trigger behind it. It depends entirely on someone remembering in the moment, usually right when the business is busiest and least likely to remember. The result is a steady stream of satisfied customers who were never actually asked, and a review count that grows far slower than it should.
The Solution👍
I designed a system that removes the dependency on memory entirely, so a review request goes out every time, without anyone having to think about it.
The moment a job is marked complete in the CRM, the system picks it up automatically. It waits a short period first, so the request doesn't feel rushed or robotic, the customer gets a little time to settle in before being asked. Then it sends a review request by SMS or email.
From there, the system tracks what happens next. If the customer clicks through and leaves a review, that's logged as a win and the process ends there, no further messages, no risk of annoying someone who already did what was asked. If there's no response after a few days, the system sends exactly one follow-up, never more than that, since a second or third nudge tends to do more harm than good. Whatever the outcome, sent, clicked, or reviewed, it's recorded in a tracking sheet, so the business owner always has a clear, accurate picture of where every customer stands.
The result is simple: every completed job gets a consistent, well-timed ask, with no manual list to maintain and no customer slipping through the cracks.
What's Next
The full workflow build, including the architecture and the tools behind it, is going up in the next few days.
That email trigger right after a job finishes should cut out the manual reminder step and keep reviews coming in.