Function

Automated emails

Reminder, confirmation and feedback emails go out from go~mus without daily intervention, via time-based and event-based triggers.

Overview

Recurring emails like pre-arrival info, reminders, feedback prompts or daily reports run on triggers in go~mus. You define once when a trigger fires and which template it uses, then the system takes over.

Time-based triggers

Send X days before or after a date, a booking or an order date. Typical cases: pre-visit info two days before a tour, feedback request the day after a visit, reminder for open payments.

Event-based triggers

Send on a specific system event, such as „order paid", „booking rescheduled", „booking cancelled". This way, your emails always reflect the real state of the order.

Daily report triggers

Daily reports to your team, for example a list of tomorrow's bookings to the front desk or a summary of today's admissions to management. You pick the recipients and the format.

Preview and test

Before activating a trigger, you can send a sample email to yourself. This avoids embarrassing placeholder slip-ups in real sends.

Transactional delivery via go~mail

All emails from go~mus go through a dedicated sending layer with its own domain, SPF/DKIM/DMARC and bounce handling. go~mail manages IP reputation, throughput and deliverability, so that confirmation emails and tickets arrive instead of landing in spam. On request, sending runs under the museum's own domain.

Get to know go~mus

Schedule a personal presentation. We will help you integrate go~mus into your workflow and support you in connecting your existing infrastructure.

Get in touch