Summarise the hotel service inbox automatically
At 08:00 every open request is grouped by topic, oldest first.
- Trigger
- daily at 08:00
- Guide value
- ≈ 10 minutes per property and day (estimate)
- Systems
- Service inbox
Today
Scroll through the service inbox every morning to see what is open and what is urgent.
Afterwards
At 08:00 every open request is grouped by topic, oldest first.
How to set it up
- 01
Describe the task
In plain language, the way you would explain it to a new colleague. The description below is a starting point.
- 02
Review the first run
Discontinue shows you the result before anything runs on a schedule.
- 03
From then on it runs
On a schedule or when something happens. You can change it in chat at any time.
Every morning at 8:00, summarise the open requests in our service inbox: one sentence per request, grouped by topic (invoice, booking change, lost property, other), oldest first. Where a reservation number is mentioned, add the arrival date from the PMS. Don’t reply yourself.
Step by step in the documentation: Create a report in chat and Schedule a report or Create an agent in chat.
What the result looks like
The agent works from your description and reports what it did and what is open.
What stays with you
Your team writes the replies to guests. Discontinue doesn’t reply itself.
- Open
- 17 · oldest waiting 3 days
- Invoices
- 6
- Booking changes
- 5 · 2 arriving this week
Sample data. Your output uses your property’s data.
Systems and permissions
| Software, any one of them | Access | What for |
|---|---|---|
| Service inbox | read | Read open conversations and threads |
| PMS (optional) | read | Match the request to a reservation |
| Team channels (optional) | write | Deliver the result to the team inbox or channel |
Help Scout
Intercom
Apaleo
Oracle OPERA Cloud
Cloudbeds
Beds24
Hospitable
Slack
TelegramWhich data and actions are available depends on each system’s interface. When you connect a system you decide what is granted; every run is logged.
Frequently asked questions
Can the summary be split by property?
Yes, if your requests sit in separate inboxes or carry tags per property. You describe that when you set it up.
Which permissions does “Service inbox digest” need?
Service inbox (Help Scout or Intercom): read, Read open conversations and threads. When you connect a system you decide which areas and actions are granted. Everything else stays off-limits.
What happens when a rule does not apply?
Agents only work with the systems and actions you granted. Where a rule does not apply, a person decides, and every step is logged.