Skip to content

Post-Stay Feedback and Review Request

Example prompt: "Two days after I mark a booking as 'Checked Out' in our Google Sheet, send the guest a 1-to-5 Typeform survey by Gmail. Whatever the rating, draft a friendly public-review request for the host to send. If the rating is 3 or below, also draft a private manager email offering a phone call and post a heads-up in #manager on Slack."

The Problem

A guest who had a bad stay tells the world before they tell us. By the time the one-star review has gone up on Saturday morning, the kitchen tap we did not know was dripping has become the headline a thousand future bookers will read. We want to hear about it first — but not by quietly choosing who we ask for a public review, and not by leaking guests' raw words into team chat. Asking only happy guests for reviews is the kind of pattern review platforms explicitly forbid; pasting a guest's verbatim complaint into a shared Slack channel is the kind of small slip that erodes trust the moment one screenshot leaves the room.

How GloriaMundo Solves It

We build a workflow that watches the bookings sheet for any row changing to 'Checked Out'. Two days later, an integration step sends a short Typeform survey through Gmail. When the response comes back, the rating and the verbatim comment are written to the 'Feedback' tab — the only place verbatim free-text lives. An LLM step drafts the same public-review email for every guest regardless of rating, and that draft goes out on the host's normal review-ask cadence — identical for every guest. In parallel, when the rating is low (1, 2, or 3), a second branch drafts a private manager Gmail and posts a #manager Slack red-flag containing a one-line sanitised paraphrase of the concern (never the verbatim text) plus links to both drafts. The manager phones the guest on their own timeline; the workflow never holds the public-review ask waiting for that call.

Example Workflow Steps

  1. Trigger (integration): A row in the 'Bookings' tab changes to status 'Checked Out'.
  2. Step 1 (schedule): Wait two days.
  3. Step 2 (integration): Send a short Typeform survey to the guest via Gmail with a 1-to-5 rating and one free-text comment box.
  4. Step 3 (integration): When the Typeform response arrives, append the rating and the verbatim comment to the 'Feedback' tab — the access-controlled sheet where verbatim free-text stays.
  5. Step 4 (llm + integration): For every guest regardless of rating, draft a warm public-review thank-you in Gmail referencing something specific from the stay, with a one-click link from the 'Active Review Platform' cell. The host sends this on their normal cadence; nothing else in the workflow gates or delays it.
  6. Step 5 (conditional): When the rating is 1, 2, or 3, run a parallel escalation branch (it does not block Step 4).
  7. Step 5a (llm + integration): Draft a private manager Gmail that acknowledges the free-text concern and offers a phone call.
  8. Step 5b (llm): Generate a one-line sanitised paraphrase of the concern for Slack — no verbatim text from the guest.
  9. Step 5c (integration): Post a red-flag message in #manager on Slack with the booking, the rating, the sanitised paraphrase, and links to both the manager draft and the public-review draft.
  10. Step 6 (integration): Log the loop in the 'Feedback' tab with the rating, the drafts produced (public_review always; manager_escalation when rating ≤ 3), the sanitised paraphrase posted to Slack, and the date drafted.

Integrations Used

  • Google Sheets — the bookings register, the feedback log (the access-controlled home for verbatim free-text), and the active review platform setting
  • Typeform — the one-question post-stay survey
  • Gmail — sends the survey and drafts the public-review email and, on low ratings, the manager email
  • Slack — the #manager channel receives the sanitised red-flag paraphrase and links to both drafts; verbatim text is never posted

Who This Is For

Small hotel and B&B operators who want a public review profile that reflects every stay rather than a curated subset, who care about handling guests' raw words discreetly, and who would rather have the manager phone an unhappy guest on their own timeline than have a workflow hold the public ask hostage to a phone call that may not happen.

Time & Cost Saved

Sending every guest a personal post-stay email and tracking whether they wrote anything publicly is the kind of work that gets done in batches once a fortnight and then forgotten. A run of forty stays a month, with five-minute emails and a five-minute Slack message for every low rating, is three to five hours that nobody has. The workflow drops that to a fifteen-minute review of the day's drafts, and surfaces every low rating to the manager the same day — with the verbatim text staying off team chat and the public ask going out on the same cadence for every guest.