Greeting & Hospitality Micro-Lesson

A brief, practical training module that aligns hosts and servers around a warm, repeatable greeting ritual. Now includes an interactive peer-review scorecard and quick implementation tracker to collect practice results, track improvements, and support follow-up coaching.

{ "Title": "Greeting & Hospitality Micro-Lesson", "IntroductionHtml": "
\n

Welcome

\n

This micro-lesson gives hosts and servers a simple, repeatable greeting ritual that feels authentic, scales across shifts, and helps every guest feel noticed and cared for. It’s designed for quick practice (5–10 minutes), easy peer feedback, and fast adoption on the floor.

\n\n

Why this matters

\n

First impressions shape guest perceptions long before the first bite. A consistent, genuine greeting reduces confusion, improves guest satisfaction, and helps teams work confidently together. The ritual below focuses on clarity, warmth, and a small personal touch that’s safe to repeat across staff and service styles.

\n\n

Learning objectives

\n
    \n
  • Deliver a brief, warm greeting within 5 seconds of a guest arriving.
  • \n
  • Convey helpful information clearly (wait time, seating options, special notes).
  • \n
  • Use one small personalization or hospitality touch to make the encounter feel human without slowing service.
  • \n
  • Practice giving and receiving peer feedback using a short scorecard.
  • \n
\n\n

Time and setup

\n

Suitable for a 5–10 minute pre-shift huddle. You’ll need 2–4 people for role-play and one printed/visible scorecard for quick peer reviews. The interactive scorecard below lets observers submit results and capture one compliment plus one coaching suggestion for each practice round.

\n\n

Greeting ritual (scripted micro-role-play)

\n

Structure the greeting into four short moves: Notice, Welcome, Help, Close. Each move should take about 1–2 seconds when paced naturally.

\n\n
    \n
  1. Notice — Make eye contact or a visible nod within 3–5 seconds.\n

    Example: Host looks up, smiles, nods.

    \n
  2. \n
  3. Welcome — A brief, warm line to set tone.\n

    Example: “Hi—welcome to [Restaurant Name]!”

    \n
  4. \n
  5. Help — Give the key next-step information (wait time, seating choice, request for party size, or a quick offer).\n

    Examples:\n

      \n
    • “Table for two? We have a table ready now or a 5-minute wait at the bar.”
    • \n
    • “Do you prefer a booth or a table?”
    • \n
    • “We have a highchair available—would you like one?”
    • \n
    \n

    \n
  6. \n
  7. Close — Confirm the action and end with a human touch.\n

    Example: “Great—right this way. My name is Jamie; I’ll get you settled.”

    \n
  8. \n
\n\n

5-minute role-play script (two people)

\n

Run the role-play twice so each person plays the greeter and the guest.

\n
    \n
  1. Greeter practices the full four-move ritual once (Notice, Welcome, Help, Close) while partner times and watches for warmth and clarity.\n

    Greeter script sample: “Hi—welcome to (name)! Table for two? We have a table ready now or a few seats at the bar. This way, please—my name’s Alex.”

    \n
  2. \n
  3. Observer uses the quick scorecard (interactive form below) and gives one specific compliment and one coaching suggestion.\n

    Example: “Nice eye contact and brisk pace. Try pausing 1 beat before offering the seating option so it feels less rushed.”

    \n
  4. \n
\n\n

Peer review scorecard (use during role-play)

\n

Use the form below to capture practice results and a short coaching note. Score each item 1–5, where 5 = excellent, 3 = acceptable, 1 = needs work. Submissions are stored so teams can track improvements over time.

\n\n

Scoring rubric (quick guidance)

\n
    \n
  • 5 — Smooth, natural, consistently warm; guest clearly knows the next step.
  • \n
  • 3 — Functional and polite; could be warmer or clearer but not harmful.
  • \n
  • 1 — Missed key moves (no eye contact, confusing seating info, robotic delivery).
  • \n
\n\n

Coaching tips for tone and personalization

\n
    \n
  • Keep it brief. The goal is a warm connector, not a long conversation at the door.
  • \n
  • Use a humanizing detail once (guest’s small children, weather comment, or a sincere “thanks for coming”). Avoid personal probing.
  • \n
  • Match energy to the guest. Calm smiles and steady tone for older guests; brighter energy for families and groups. When in doubt, choose friendly and composed.
  • \n
  • Practice neutral personalization lines that are safe and inclusive: “Great to have you,” “Thanks for choosing us tonight.”
  • \n
  • Use names of staff when handing off: “Jamie will get you seated,” so the guest hears a clear owner for the next step.
  • \n
\n\n

Variations for different service styles

\n
    \n
  • Quick-service / counter: Faster Notice + Welcome + one-line Help (“Order at the counter—right this way.”)
  • \n
  • Full-service: Slightly slower, add brief personal closure (“If you need anything, just wave.”)
  • \n
  • High-turn or rush hours: Prioritize clarity of wait time and seating options; keep personalization minimal but genuine.
  • \n
\n\n

Common mistakes to avoid

\n
    \n
  • Starting with logistics only (“How many?”) without a welcome.
  • \n
  • Rushing and clipping words—feels curt.
  • \n
  • Over-personalizing with intrusive questions or assumptions.
  • \n
\n\n

Implementation plan (quick wins)

\n
    \n
  1. Run this micro-lesson in a 5–10 minute pre-shift huddle twice this week so every host and server practices the script once.
  2. \n
  3. Use the scorecard for peer feedback—each person gives one compliment and one coaching tip.
  4. \n
  5. Pick one measurable check: speed of first acknowledgement (goal: within 5 seconds) and a weekly spot-check of guest feedback mentions of greeting/warmth.
  6. \n
  7. Repeat the micro-lesson monthly and share any small improvements or memorable guest responses in the next huddle.
  8. \n
\n\n

Quick reference (one-line prompts)

\n
    \n
  • Notice: Eye contact / nod within 3–5s
  • \n
  • Welcome: Short warm line ("Welcome to [Name]")
  • \n
  • Help: Key next step (wait time / seating / offer)
  • \n
  • Close: Confirm action + name handoff
  • \n
\n\n

Reflection prompts for teams

\n
    \n
  • What felt natural? What felt forced?
  • \n
  • Which small personalization lines work best for our guests and culture?
  • \n
  • What one change could make our greeting noticeably warmer by next week?
  • \n
\n\n

Use this guide as a starting ritual—adapt the exact words to fit your brand voice and guest profile, but keep the four moves consistent. Small, practiced rituals build trust across shifts and make excellent service repeatable.

\n
", "SubmitLabel": "Save Practice Result", "SuccessMessage": "Thanks — your peer review was saved. Bring one coaching idea to the next huddle.", "DataType": "GreetingMicroLessonPractice", "SchemaVersion": "1.0", "Fields": [ { "Key": "observer_name", "FieldType": "text", "Label": "Observer name", "HelpText": "Your name (who is giving the feedback).", "Required": true }, { "Key": "participant_name", "FieldType": "text", "Label": "Greeter name", "HelpText": "Name of the person playing the greeter in this role-play.", "Required": true }, { "Key": "shift_role", "FieldType": "select", "Label": "Service style / role", "HelpText": "Pick the service style this practice simulates.", "Options": [ { "Value": "full_service", "Label": "Full-service" }, { "Value": "quick_service", "Label": "Quick-service / counter" }, { "Value": "rush_hours", "Label": "High-turn / Rush hour" }, { "Value": "host_only", "Label": "Host / Greeter role" } ], "Required": true }, { "Key": "time_to_acknowledge_secs", "FieldType": "number", "Label": "Seconds to first acknowledgement", "HelpText": "How many seconds from arrival until eye contact or audible greeting? (goal: ≤5s)", "Required": false, "Min": 0 }, { "Key": "score_notice", "FieldType": "scale", "Label": "Notice — eye contact / acknowledgment", "HelpText": "1 = missed; 5 = prompt and natural", "Required": true, "Min": 1, "Max": 5 }, { "Key": "score_welcome_tone", "FieldType": "scale", "Label": "Welcome tone — warmth and genuineness", "HelpText": "1 = robotic; 5 = warm and natural", "Required": true, "Min": 1, "Max": 5 }, { "Key": "score_clarity_help", "FieldType": "scale", "Label": "Clarity of help — wait time & seating options", "HelpText": "1 = confusing; 5 = clear and actionable", "Required": true, "Min": 1, "Max": 5 }, { "Key": "score_personalization", "FieldType": "scale", "Label": "Personalization — small human touch", "HelpText": "1 = intrusive / absent; 5 = natural and appropriate", "Required": true, "Min": 1, "Max": 5 }, { "Key": "score_close_handoff", "FieldType": "scale", "Label": "Close & handoff — confident direction and name handoff", "HelpText": "1 = unclear handoff; 5 = confident and clear", "Required": true, "Min": 1, "Max": 5 }, { "Key": "overall_comment", "FieldType": "textarea", "Label": "Overall comment (one sentence)", "HelpText": "A concise summary comment for the participant (e.g., 'Good eye contact; slow down before options').", "Required": false }, { "Key": "compliment", "FieldType": "textarea", "Label": "One compliment", "HelpText": "Highlight one thing the greeter did well.", "Required": false }, { "Key": "coaching_tip", "FieldType": "textarea", "Label": "One coaching suggestion", "HelpText": "Give one concrete action the greeter can try next shift.", "Required": false }, { "Key": "implementation_checks", "FieldType": "checkbox", "Label": "Implementation actions taken / planned", "HelpText": "Select the items you ran or plan to run this week.", "Options": [ { "Value": "ran_pre_shift_twice", "Label": "Ran the micro-lesson twice this week" }, { "Value": "used_scorecard_peer_feedback", "Label": "Used scorecard for peer feedback" }, { "Value": "measured_ack_time", "Label": "Measured first-acknowledgement time" }, { "Value": "scheduled_monthly_repeat", "Label": "Scheduled monthly repeat lesson" } ], "Required": false }, { "Key": "follow_up_scheduled", "FieldType": "yesno", "Label": "Is a follow-up coaching huddle scheduled?", "HelpText": "Mark Yes if a follow-up huddle is scheduled to review results.", "Required": false }, { "Key": "follow_up_date", "FieldType": "text", "Label": "Follow-up date (optional)", "HelpText": "Optional: date for the follow-up (YYYY-MM-DD).", "Required": false }, { "Key": "repeat_frequency", "FieldType": "select", "Label": "How often will the team repeat this micro-lesson?", "HelpText": "Choose a cadence to build practice into shifts.", "Options": [ { "Value": "weekly", "Label": "Weekly" }, { "Value": "biweekly", "Label": "Every 2 weeks" }, { "Value": "monthly", "Label": "Monthly" }, { "Value": "quarterly", "Label": "Quarterly" } ], "Required": false } ] }

Discussion

Comments and conversation will live here.