Email your service team a forecast of upcoming requests

1. Open the email report page

In the Service module, the page sits in the list down the left — but it is not one of the pinned entries, so you have to choose Show more before Email report appears. That single step is where most people give up looking.

A subscription is a standing instruction: this report, this often, to these people, about these rooms and services. You can have as many as you like — a daily one for the catering team and a weekly one for the facilities head are two separate subscriptions, not one compromise.

2. Add a subscription

Choose Add. The dialog opens on Report, where Upcoming service forecast is the single card — it is the only report the service module publishes, so there is nothing to choose. Its frequency is the pill beneath the name.

Everything else is on the rail down the left — Schedule, Recipients and Scope — under a pill reading Active. Choosing that pill pauses the report: it keeps every setting and every recipient and sends nothing until you turn it back on, which is how you stop a report for a month without losing who it went to.

3. Choose how often it arrives

Send time and the day of week or month are on Schedule, which also lists the next four sends and the period each one reports on — the quickest check that the schedule is what you meant.

Send time is honoured to the hour. Minutes are ignored, so 09:30 and 09:00 both send during the 9 o’clock hour. The hour is read in the system time zone, not the reader’s, so a manager abroad receives it at their local equivalent of your working morning rather than theirs.

Day of month stops at 28 deliberately — 29, 30 and 31 do not exist in every month, and a report scheduled for a day that never comes never arrives.

4. Choose who receives it

Recipients, on the rail, offers two modes:

• All service managers — everyone holding Service manager or Global administrator, resolved fresh at the moment each report is sent. People joining or leaving that role are picked up without anyone editing the subscription. This is the right choice for a standing operational report.
• Specify recipients — name individual people, user groups, or both. From 4.5.9 a user group is expanded to its members when the report is sent, so a group stays current as people join and leave it.

Either way, recipients are filtered to people who hold Service manager or Global administrator. Naming someone without those rights, directly or through a group, does not add them — a subscription is a convenient way to address managers, never a way to grant sight of service requests to somebody who cannot otherwise see them.

5. Choose what it counts

Scope, on the rail, holds two switches, and both default to everything. Leave All bookable resources on and the report covers every room; turn it off to pick specific ones. All service items works the same way for the services themselves — turn it off and pick just the tea service to give the kitchen a report about tea and nothing else.

6. Read the mail before you save

Go back to Report. Under the card the dialog builds the email this subscription would actually send — who it resolves to after the manager filter, the attachment, and the report itself — and rebuilds it whenever you change a setting. No one would receive this report there means nobody you named holds Service manager, which is the first cause in the list at the foot of this page, caught before the first send rather than after it.

Then choose Save.

7. Send one now to check

Select the subscription, and choose Send now in the panel on the right. The report goes out immediately, to its real recipients — this is a live send, not a preview, so expect the people you named to receive it.

What arrives

The email leads with the day it covers, then four counts:

• Total service items — service requests due in the window
• Total bookings — the bookings carrying them
• Total resources — how many distinct rooms are involved
• Service types — how many different services are being asked for

View details opens the admin Service requested page, where the requests are handled, and the full list rides along as a spreadsheet named service-items-<date>.xlsx — named after the day the report covers, not the day it was sent.

The report also inherits your email branding — logo, colours and footer — from the same settings every other Offision email uses.

If the report does not arrive

Work through these in order:

1. The recipients are not service managers. The commonest cause by far. Everyone named, directly or through a group, must hold Service manager or Global administrator; anyone else is dropped silently. If nobody on the subscription qualifies, nothing is sent at all.
2. The subscription is paused. The list shows its status as Disabled. Open it and choose the Paused pill on the rail to start it again.
3. The schedule can never come round. A weekly subscription with no day of week, or one whose hour has not occurred since you saved it, has simply not fired yet. Send now distinguishes the two: if that arrives and the scheduled send never does, the schedule is the problem, not the recipients.
4. Email sending is not set up. If no Offision email reaches anyone, the problem is the sender rather than this report.

An empty report is not a failure. When nothing is requested in the window the report still arrives, showing zeroes and carrying an empty spreadsheet — that is the schedule working, and it is how you tell “nothing on tomorrow” apart from “the report stopped coming”.