Guest Community Agent
Moderates and grows the loyalty members' community and the hotel's social comments.
- Industry
- Hotel
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Assistant
- Approver
- Guest Relations Manager
- Code
- CUS-11
It moderates the loyalty members' community forum and the comments on the hotel's social pages, answering questions about stays, points and events, removing spam and hiding posts that expose guest data. It tags the right hotel or loyalty specialist on unanswered questions and passes complaints to guest relations as cases.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the guest messaging and CRM platform: the community and social posts with their reports, and the authors' membership age and loyalty tier..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Guest Relations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the guest messaging and CRM platform: it posts the replies, hides or removes posts, tags specialists and opens guest relations cases. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The community guidelines: posting rules, what counts as personal data, the moderation steps, approved answers on loyalty and hotel policies, and the specialists to tag by topic.
Reads from
the guest messaging and CRM platform: the community and social posts with their reports, and the authors' membership age and loyalty tier.
Acts in
the guest messaging and CRM platform: it posts the replies, hides or removes posts, tags specialists and opens guest relations cases.
Hands back
A list with one entry per post, each with post_id, action (reply, hide, remove, hold, tag, open_case or none), reply (text or null), tag (or null), case_note (or null) and reason.
Asks a person when
A post alleges injury, illness, discrimination or a safety issue, a ban is proposed, or a reply would be public about a named guest's stay.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Answer or tag after (hours) | 12 | A question without an answer after this time is answered or a specialist is tagged. |
| Reports that hide a post | 3 | A post reported this many times is hidden until a person reviews it. |
| Hold links from new members | On | When on, posts with links from members younger than 7 days are held for review. |
| May ban members itself | Off | When off, a ban is proposed to the approver, never applied. |
| Specialists to tag | Loyalty Desk, Hotel Guest Relations, Events Team | Who it tags for questions it cannot answer from the guidelines. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Remove obvious spam, and hide any post that shows personal data such as a confirmation number, room number, phone, email or card detail, telling the author why.
- Hide a post reported by 3 or more members until a person reviews it.
- Answer stay and points questions only from the approved answers; tag one of Loyalty Desk, Hotel Guest Relations, Events Team after 12 hours when it cannot.
- Never discuss a guest's stay or complaint in public; invite them to a private message and open a guest relations case.
- Hold link posts from new members when on is true, and propose a ban to the Guest Relations Manager unless off is true.
See the Guest Community Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.