Payment reminders

Remind guests when a payment is due.

Use the actual amount due and the booking’s payment schedule to send useful reminders without drafting every email yourself.

Automations
Balance reminderEvent triggered
Maya Patel€450 due · 14 May
  1. 01

    Due date

    Use the booking schedule

  2. 02

    Check

    Is a balance outstanding?

  3. 03

    Send

    Amount and payment link

  4. 04

    Resolve

    Paid or personal follow-up

In a real operating workflow

The same due date. A different message for each payment state.

Maya’s €450 instalment is due on 14 May. A reminder before that date should reach Maya only while the amount remains outstanding. A guest who has already paid should move on to preparation, without another request for money.

€450 remains due
ResultSend the amount, due date and payment link
Payment already received
ResultSkip the payment reminder
Guest pays after a reminder
ResultUpdate payment state for subsequent follow-up
A guest has a question
ResultTeam reviews the booking and replies

The due date starts the workflow. The current payment state determines whether a reminder is needed.

How it works

Set it up for the way you operate.

01

Choose the timing

Set a reminder before a balance is due and a follow-up for an overdue amount. The departure and due date supply the context.

02

Make the message useful

Include the amount, due date, booking reference and payment route. Use your business identity so the guest recognises the request.

03

Keep people out of the chase

Check the outstanding balance before sending. Once payment is recorded, the guest no longer belongs in the unpaid reminder sequence.

Marnie connects the routine steps

At the configured time

Check the outstanding amount and send the relevant message when a payment remains due.

After payment is recorded

Use the updated payment state so the guest is not chased for a completed step.

Your team stays in control

Timing and wording

Choose the reminder schedule, tone and instructions for your payment plan.

Personal exceptions

Handle changed arrangements or payment questions with the actual booking in front of you.

For the guest

What the guest sees.

Guests receive a clear request for the amount they still owe, with a direct route to pay and their trip details close by.

For your team

What your team sees.

Your team can review upcoming and overdue balances, see the reminder context and intervene personally when a booking needs different arrangements.

Part of the same operation

What happens around this step?

  1. Deposits & payment plans

    Collect a deposit, split the remaining balance into instalments and keep every payment attached to the reservation.

  2. Communications & automations

    Automate confirmations, preparation requests, payment reminders and trip follow-ups around the guest’s booking and departure.

  3. Payments & revenue visibility

    Review booking value, collected payments, outstanding balances and capacity across departures and locations.

Questions, answered

Practical questions about payment reminders

Can the reminder use our branding?

Yes. Use your sender identity and message copy, with booking details added to the message.

Can we see balances by departure?

Yes. Review the outstanding amounts in the context of the guests and dates your team is preparing.

Let’s talk about your operation

Show us how
your business works.

We’ll show you how Marnie brings your bookings,
guests and team together.

Request a demo
Read our cookie policy