Skip to content
English
Log a ticket
  • There are no suggestions because the search field is empty.

How GuestRevu Works with Email

Email plays an important role in how GuestRevu communicates with both you and your guests. From automated surveys to daily performance summaries, a reliable email system ensures you never miss important insights.

This article explains how GuestRevu uses email, the different types of emails we send, why multiple domains are involved, and how our new Amazon Web Services (AWS) infrastructure makes delivery more reliable.

GuestRevu sends two broad categories of email

a) Emails sent to your guests

  • Survey invitations (pre-, during-, and post-stay invitations)
  • Survey reminders (pre-, during-, and post-stay reminders)
  • Thank-you messages (pre-, during-, and post-stay communication)

These emails are part of the guest journey and are designed to maintain your property's brand tone and reliability. Emails sent to your guests will continue to be sent from the @guestrevuapp.com domain during the rollout. In time, these will also be migrated to AWS in a separate phase to ensure a smooth transition.There is no change to the guest experience during this period. 

b) Emails sent to you and your team

  • Daily summary reports
  • Weekly and monthly summary reports
  • Review alerts (Low or high scoring reviews)
  • Survey review alerts (pre-, during-, and post-stay)
  • Other automated system notifications

These email notifications are designed to help you stay on top of your online reputation and guest experience, with the intention of migrating these user-facing notifications from our current email service provider to AWS for improved reliability and redundancy.

Why GuestRevu uses multiple sending domains

GuestRevu use several authenticated domains to maintain high deliverability, better inbox placement, redundancy (protecting you from blocked or throttled domains), and system resilience with close to zero downtime.

You may see different domains depending on the type of email, the stage of the migration, and system redundancy needs.

Our sending domains explained

Some user-facing notifications (eg Daily, Weekly, and Monthly summary reports) may come from one of the following new domains:

no-reply@grfeedback-a.com

no-reply@grfeedback-b.com

no-reply@grfeedback-c.com

These domains are all owned and managed by GuestRevu, and form part of our upgraded AWS email infrastructure. Please be assured that any communications from these domains are legitimate emails, and come from GuestRevu directly. 

Emails sent to your guests (eg. Survey Invitation and Reminder emails) will continue to be sent from the @guestrevuapp.com domain during the rollout. In time, these will also be migrated to AWS in a separate phase to ensure a smooth transition.

Domains that do not send email

grevu.link – This is used only as a link-shortening service to create clean, trackable URLs for surveys and review requests. It does not send email.

What is changing and when

Already completed

  • Daily summary reports are now sent from no-reply@grfeedback-b.com

In progress

  • Weekly and monthly summary reports migrating to AWS
  • Other user notifications migrating to AWS
  • Internal monitoring tools enabled for AWS-delivered email

Coming later

  • Migration of guest-facing emails (survey invitations and reminders)
    These will remain on @guestrevuapp.com until we have completed the internal notification migration. This ensures a smooth and gradual transition.

How we ensure email reliability

a) Deliverability safeguards

Using multiple domains reduces the risk of delivery interruptions caused by temporary provider-level blocks, spam filter changes, and high-volume throttling from specific inbox providers.

b) Redundancy

If one domain is affected, a secondary domain can be used safely without interrupting the email flow.

c) Advanced monitoring (AWS)

With the move to AWS, our support team now has detailed insight into email behaviour that enables faster troubleshooting and clearer guidance:

  • Confirmation that an email was sent
  • Whether it was sent, delivered, opened, clicked, bounced or rejected
  • A preview of the email content if a resend is not possible

What you may need to do

For most clients, no action is needed.

If your organisation uses strict IT policies (such as whitelisted domains), we recommend allowing the following domains:

  • guestrevuapp.com
  • grfeedback-b.com
  • grfeedback-a.com
  • grfeedback-c.com

This ensures both guest emails and system notifications can be delivered successfully.

Does this affect our guests?

No, guests will continue receiving communications from the same domain (@guestrevuapp.com) until the later phases of migration. The experience is unaffected.

Any future changes to guest email domains will be communicated well in advance.