Out of Office in Clockwise

Frame_12.png

 

Clockwise can help you handle the logistics of going OOO automatically through a number of features:

  • Slack status sync – Clockwise will automatically update your Slack status to show that you are unavailable using the ⛔️ do not enter emoji.
    mceclip0.png 
  • Team availability calendar – Clockwise automatically generates a Google calendar for your Clockwise Team with everyone's availability. To learn more, check out this article.

Below you will find some common questions about managing your out of office in Clockwise.

How does Clockwise know I'm out of office?

Clockwise uses the names of the meetings on your calendar to identify when you are out of office. We identify words and phrases in the title of your meetings (for example, "OOO" or "Out of Office") and then automatically categorize the meeting as an out of office event.

How do I edit the out of office setting?

OOO in Clockwise is based on the meetings on your calendar, and the category those meetings fall into. So to tell Clockwise you are going to be OOO, all you have to do is edit the category of the event on your calendar. You can find the category dropdown in the extension (below) or in the pop-up window after clicking on a meeting in your calendar.

Screen_Shot_2022-01-19_at_12.17.49_PM.png

What should I do if Clockwise shows me as out of office when I'm not?

First, check your calendar - do you have any meetings on your calendar (especially all-day meetings) that could be categorized as "out of office"? For example, did someone invite you to their OOO event? Or did you leave a note to yourself in your calendar that someone else will be out of office? Click on the events to check their categorization.

If you find an event that is categorized as OOO when it shouldn't be, the easiest way to correct is to change the event category to a different category than OOO, such as a Hold or Other, or remove yourself from the event invite if it's an OOO event for your colleagues.  

Screenshot_2023-01-11_at_11_13_44_PM.png

 

Updated

Was this article helpful?

/