Customer Service
Every Request Has an Owner and a Deadline
Requests arrive on WhatsApp, by email, through the site and by phone, and they live in whoever happened to answer. I build the system that puts all of them in one queue with an owner, a priority and a due time - so nothing depends on someone remembering, and you can finally see what customers keep asking for.
Key takeaways
- One queue across every channel is the whole win. A request in a personal inbox is invisible to the business.
- Ownership beats process. A ticket with a named owner and a due time gets closed; one in a shared queue drifts.
- The recurring-question report is the real payoff: it tells you what to fix in the product or the site.
- Off-the-shelf helpdesks are excellent and cheaper. Build only when the workflow or the integration is genuinely yours.
What I build
- One queue collecting WhatsApp, email, web forms and phone notes
- Assignment, priority, due times and escalation when one is missed
- Canned replies and templates in Hebrew and English
- Full history attached to the customer record, not to a person's inbox
- Reporting on volume, response time and recurring topics
- Optional AI triage that classifies and drafts, with a human approving
How it works
A short scoping call
What hurts today, what you already use, and what "done" looks like.
A written fixed-price quote
Scope, price and timeline in writing, approved before any work starts.
Built in stages, on your real data
You see a working first version early, not a demo at the end.
Handover with documentation and monitoring
You own the code and the data, and a support window follows launch.
Working with me from the US or Europe
- Most of my client work is for companies in the US, UK, Germany, the Netherlands and Australia.
- Calls are in English and scheduled in your time zone. My working day covers most of the European one and the US East Coast morning.
- A fixed price in US dollars, agreed in writing before any work starts.
- Pay me directly, or hire me through Upwork if you prefer to work through a platform.
- You own the code and the data, with documentation and a support window after launch.
Guides on this
Practical guides from real client work.
Custom Software vs Off-the-Shelf: When a Small Business Needs a Custom System
Custom software vs off-the-shelf is rarely about features. I break down when SaaS is right, when you have outgrown it, and a clear build vs buy framework.
From Idea to MVP: How to Build an MVP (And What It Costs)
A practical guide to how to build an MVP: scoping must-haves vs later, realistic MVP development cost and timeline, and how AI now ships your idea in weeks.
Hiring a Developer to Build Your MVP: Freelancer vs Agency vs In-House
Hiring a developer to build your MVP? A practical comparison of freelancer vs agency vs in-house on cost, speed, risk, and control, plus red flags and how to structure the deal.
Signs Your Business Has Outgrown Spreadsheets (Time for a Custom App)
Has your business outgrown spreadsheets? The concrete signs it is time to replace spreadsheets with a custom app, the real cost and timeline to build one, and how AI made it affordable.
No-Code vs Custom Code for Building Your App or MVP
No-code vs custom code for apps: what each is good at, real cost and speed early vs total cost of ownership, the no-code ceiling and lock-in, and when to pick which.
How to Validate Your Idea Before You Build It
How to validate a startup idea before building: why validation saves money, talking to real customers, the smoke test, pre-sales, a manual concierge version, and the signals that justify building.
What Is an MVP, Really? Common Mistakes Founders Make
What is an MVP, really? A clear definition of minimum viable product, what an MVP is not, good vs bad examples, and the most common mistakes founders make.
How to Choose the Right Tech Stack for Your MVP
How to choose a tech stack for your MVP without overthinking it: the principles that matter, a sensible default stack, when to deviate, and what not to optimize for too early.
Is Vibe Coding Production-Ready? A Developer's Honest Take
Is vibe coding production-ready? An honest developer's take on what vibe coding is great at, where it breaks, and a prototype-vs-production checklist.
Frequently asked questions
How is this different from the AI chatbot page?
A chatbot is the conversation with the customer. This is what happens to the request afterwards: who owns it, by when, what the history is, and what the recurring themes are. They work well together - the bot deflects the easy questions and opens a ticket for the rest - but they solve different problems and either can exist without the other.
Should we not just buy a helpdesk?
Usually yes, and that is the honest default. Building makes sense when your service workflow has steps a product cannot model, when the ticket has to read and write to a system with no connector, or when per-agent pricing across a large team outgrows a one-time build.
Can it pull requests out of WhatsApp?
Yes, through the official Cloud API, which is the only way to do it without tying the business to one person's phone. Messages become tickets, replies go back out on the same thread, and the whole exchange stays on the customer record.
Sources
Official documentation you can verify the claims on this page against.
Let us scope your project
Tell me what you need and I will give you an honest scope, price, and timeline.