I'm curious to hear from the founders as to what motivated the creation of the apps and whether WFH plays a significant part in the value proposition. Would you need either app in a traditional work-from-office environment?
I'm curious to hear from the founders as to what motivated the creation of the apps and whether WFH plays a significant part in the value proposition. Would you need either app in a traditional work-from-office environment?
Then we started extending the product around async work practices. Traditional work-from-office environments can indeed benefit from improving collaboration practices, getting more work done inside the chat, and (of course) decreasing the pointless meetings for things that could be written updates.
It could happen that teams use DailyBot improperly for micro-management purposes - that’s why we’re also creating a catalog of best practices and proper question templates; asking the right questions is key. We'll go further by adding more features to DailyBot so it becomes a highly useful personal assistant at work.
DailyBot lets you give kudos to teammates, have a watercooler in a chat channel, random 1:1 coffees, run a virtual commute that reminds you to disconnect from work each day, run countdowns, pomodoros, and more. You can even build public web forms that are connected to your chat channels through the bot. In the end, we want to make the chat 10x better and at the same time provide only one dashboard that connects all that data.
Our product is extendable: you can connect your check-in responses to over thousands of apps through Zapier, and build your own chat commands without technical knowledge. For example: you can create a command that responds with your predefined text, like to access information quickly inside the chat, or to trigger a form, or get data from your back office tools, kind of useful for chat-ops.
We created a 2min video that shows a bit of it: https://www.youtube.com/watch?v=zHZnGl4c-9g
Wow, back to high school. They don't track attendance in undergrad even. Why do companies need this sort of information? If the person is important to the meeting, them being a no show will be pretty evident. If they are so irrelevant to the meeting that they could just dip out and no one would be the wiser, why are they even wasting their time in the zoom meeting to begin with? Just email whatever information you need to get out if the zoom meeting is going to just be an announcement or one sided lecture.
It also wouldn't be hard to write a little script that automatically connects you to zoom meetings that are coming up. You probably only need a few lines of bash to write your own if you have a tool like icalbuddy where you can grep for upcoming zoom meetings in your calendar.
it's also useful to communities who want to learn how to better engage members and which types of zoom events drive the most engagement
https://www.eduhk.hk/ocio/content/faq-how-retrieve-attendanc...
Nothing you said precludes tracking the information. Yeah, I've missed meetings and it's been evident. But it's ok, because we have flexibility and the company knows it's rare.
If I miss every meeting, that's a concern.
> It also wouldn't be hard to write a little script that automatically connects you to zoom meetings that are coming up
You'd be the employee we're trying to get rid of. If you're lying about participation in things, saying you attended meetings when you didn't, I'd fire you.
You are literally proving why such a need exists.
You have it backwards. If this was happening in my team I would look at why there is a misalignment between company expectations and employee behaviour. If an employee needs to create a script to pretend to do something then there is most likely a deep cultural issue coming top down from management. It highlights an opportunity to refine and improve work practices and culture. The fact that an employee would lie is already a huge red flag that there is something wrong with the culture. Sure 5% of the time the employee is actually not fulfilling their duties but you will know this without the call logs because you would miss them on the call.