What Delvra did with 196 real customer requests.
Measured on 196 real customer requests at a live service desk running Delvra, 28/9 to 23/10/2026. We run it every day too.
- 3,797WhatsApp messages from 77 customers and leadsIncoming messages from contacts with a customer or lead request
- 196real requests, 175 closed (89%)Customer and lead requests, excluding thank you notes and duplicates
- 2.3 hmedian from request to closedAcross the 175 closed requests
- 323logged actions, about 49.5 hours of logged work7/10 to 23/10 only. Work time logged, not time saved
- 32%went to the owner for a decision (62 of 196)It knows when to ask you
- 76%Hebrew, 21% EnglishScript of incoming customer messages
- 14%arrive outside business hoursSaturday, Friday after 14:00, weekdays before 08:30 or after 18:00
Measured 23/10/2026, window 28/9 to 23/10/2026
What the 196 requests were
- Site fixes75
- Content changes23
- Meetings21
- How to questions16
- New leads14
- Thank you notes12
- Data reports5
- Billing4
- Catalog2
- Other24
How we measured
Window: 28/9 to 23/10/2026. Measured on 23/10/2026. The desk serves the customers of one web agency: site maintenance, content and meetings. It does not sell products or issue refunds.
Messages: incoming WhatsApp messages from contacts who had a customer or lead request. Requests: those conversations grouped into requests, without thank you notes and duplicates.
Closed and time to close: a request counts as closed when it was marked done. The median runs from the first message of the request to that mark.
Logged actions: logging of actions started on 7/10, so that number covers 7/10 to 23/10 only. Hours are logged work time, not time saved.
Owner decisions: requests that were passed to the business owner to decide. Language: the script of incoming messages. After hours: Saturday, Friday after 14:00, and weekdays before 08:30 or after 18:00.
What these numbers do not show
Time saved. We log the time work took, not the time it would have taken without Delvra.
Customer satisfaction. We did not run a survey in this window.
Results for a store. This desk has no orders or refunds, so store numbers will be published once they are measured.
Hand over one workflow. We set it up and run it with you.
Pick a plan and tell us which requests eat your team’s day. We connect it with you, run a quiet week where nothing reaches a customer, and billing starts only when you go live. No card needed.
Measured on 196 real customer requests at a live service desk running Delvra: 89% closed, median 2.3 hours to close (28/9 to 23/10/2026). How we counted
What people ask before they start
- Will it embarrass me in front of a customer?
- It answers only from what you approved and never makes up a price, a date or a refund. When it isn’t sure, it hands the conversation to your team with a summary. And before anything reaches a customer, you read every answer in a quiet week. How it works
- Can my customers still reach a person?
- Always. A customer can ask for a person at any point, and anyone on your team can step into a conversation and take it from there, with the whole history in front of them. What stays in your control
- How long until it’s working?
- We set it up with you, and you don’t need a developer. It starts with a quiet week on your real requests where nothing is sent, so you see what it would do before it does anything. How it works
- What does it cost?
- A monthly plan counted by finished tasks, with a hard cap so the bill doesn’t jump. Starter is from $149 a month, and billing starts only with your first live task. See pricing
