DobroDesk made sense before I needed it.

What I tried

I have reviewed close to ten products recently, and DobroDesk is the only one where I did not come away with a complaint about how the website explains the product. I understood what it does, how it fits into support work and what it costs. Email and website chat come into one inbox; AI can draft replies for review, or the team can choose another reply mode. The homepage puts a product example and the starting price right beside that explanation. A short look through the public demo also makes the workflow concrete: a sample billing case shows the draft, its sources and why a person needs to check the payment before replying. That is a demo, not a test with my own customers.

Where I got stuck

I did not get stuck trying to understand the offer. My personal projects simply do not have enough traffic or support volume to need this yet. As a technical founder, I usually look at a tool like this and immediately wonder whether I could build it myself. Then I saw the price. The listed €15 monthly base includes 300 accepted support conversations and unlimited teammates. Extra conversation packages and optional capabilities cost more, and applicable taxes are separate. For the starting use case, that price makes spending my own time building and maintaining an equivalent difficult to justify.

One thing I'd change

I would explore a specific audience: trading businesses running several niche B2B websites. They are not necessarily manufacturers. They attract buyers through search, often using WordPress sites focused on different product categories, then coordinate with suppliers. Managing inquiries across those sites is the opportunity I would investigate. Imagine one small team receiving a packaging inquiry on one site, a request for branded promotional products on another, and a parts drawing on a third. These are illustrative scenarios, not tests I ran. Could DobroDesk bring those conversations together while preserving the originating website, product page and attachments? Could each site keep its own sender identity and approved product information, so a buyer gets the right reply from the right business? I would show how a WordPress form or chat enters the inbox, how missing quantity and destination details are collected, and how a salesperson takes ownership and follows up while waiting for a supplier quote. Timely acknowledgment helps, but the team also needs to see which inquiries still need a useful answer. Quotes and delivery promises should be confirmed with the supplier before being sent. The existing shared inbox and ownership controls look relevant; I have not verified this multi-site workflow, WordPress form intake or separation of each site’s knowledge and identity. A demo of one team handling several sites would make the fit much easier to judge. The current website already explains its support offer well; this is a concrete audience I would explore next.

Would I pay

Yes, when my projects need it. I am not buying today because the support volume is not there yet. At the advertised starting price, I would rather pay for this than spend time building my own version. I would still need to test it with real support conversations before relying on it.

■

Roger HE is building PersonWise — The presentation presents itself.

Respond to this review →