For teams that run on RotaCloud
RotaCloud memos with who has opened them
RotaCloud memos go out by email, and the memo history shows what share of people read each one. The help centre notes that it does not show which staff opened it.
How it goes today
- Send the memo and open the memo history a day later.
- See the read percentage without the names behind it.
- Ask each team in person or in a group chat whether they saw it.
- Keep your own list of who confirmed.
How it can go
Know which people have not opened an important memo.
You write the notice once and pick the people or a location. It goes out as a RotaCloud memo, and two days later you get a list of who has not opened it, with their location and manager, so you follow up with those people only. The list is kept with the memo.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your RotaCloud key in the portal, never in the chat.
With Hypamoon, when I write a notice, send it as a RotaCloud memo to the people or location I choose. Two days later, email me and each location manager a list of who has not opened it yet.
You create the RotaCloud API key yourself in your account settings, under API and Webhooks. It opens the whole account, so give it a name you will recognise. It stays yours.
More for teams on RotaCloud
- I want wage cost against takings for each site, week by week, without rebuilding it by hand.
- I rework the payroll export every month before it goes to payroll.
- I want to see who left early or did not clock in, as well as who was late.
- At the end of the leave year I change each allowance one by one.
- Our rota starts in a spreadsheet and I retype it into RotaCloud.
- I want one clear email per person with their week, in our own words.
- When I delete someone who leaves, their future shifts disappear with them.
- Everything for RotaCloud