Original Summary

I run SeatSwiper, which watches restaurant reservations and books a table when one opens. This is an operations point rather than a product pitch, because the result was the opposite of what I expected and I have not seen it discussed much. The product is four states. Draft, armed, running, booked. There is a race log you can read if you want to, and that is the entire interface after setup. No analytics, no weekly summary, no engagement surface, nothing to check. I assumed that would generate support volume. People cannot see what is happening, so they will ask. Every instinct I had said add a progress view, add notifications, tell them something is being done. What actually happened is that the support I do get is almost entirely about the thing I can fix. Questions are specific: this restaurant is not on a platform you cover, this date is outside the release window, my login stopped working. Those are real problems with real answers. My read, and I hold it loosely, is that a dashboard on a system that mostly does nothing visible is an invitation to ask why nothing is happening. Most of the time nothing happening is correct behaviour. A progress view would have manufactured a support category consisting entirely of me explaining that the absence of news is the product working. There is a caveat and it is not small. This only holds because the outcome is unambiguous. You either have the table or you do not, and you find out by getting the confirmation from the restaurant, not from me. If the outcome were fuzzy, or slow, or something a customer had to interpret, visibility would stop being optional and I would have to build it. So not a general rule. But worth checking whether your dashboard exists because users need it or because you could not tolerate them not knowing.   submitted by   /u/carval [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/29 00:45:59