Back to results
Explore the library298 guides total · goals, work & tasks
By goal

Choose what you want to achieve.

By work or interest

Choose a setting you work or spend time in.

By task

Choose the kind of help you want.

Counts show all available guides. Filters combine to narrow your results.

Build a workflowGuide

Hand over guest-service requests without losing their status

Distinguish a received request from a completed delivery in the next shift’s notes.

Illustrative resourceNot tool-testedFront-desk teams handing over routine service requests
What you’re working towards

A token-based relay log distinguishing received, in progress, delivered and unresolved requests

Download playbook .md

Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides

Saving needs JavaScript. Reading and downloading this guide does not save it.

Make a start

One step at a time.

3 steps

Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.

Start with the synthetic example, then adapt each prompt to your task.

01

Open a chat and use the complete sample

A relay log is a short record for the next shift showing what is still open. Open https://chatgpt.com. If you have access, choose New chat. Copy all the instructions below (the prompt), including the SAMPLE INPUT, into the message box and send it. You do not need to upload a file. You should see four traceable service-request rows with four different statuses. The wording can differ from the worked example, but the facts and constraints must agree. If you cannot access this service, use another text assistant available to you; account requirements and limits may differ.

Your starting prompt
Make a shift relay log with token, request, exact status, evidence and next information needed. Do not convert acknowledgement into delivery. Include a one-line count of each used status. Use only the supplied facts; mark missing information rather than inventing it. Return written text only. Do not send, publish or change anything in another service.

SAMPLE INPUT
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional guest-service notes use request tokens only. H1: extra blanket requested; service team acknowledged; no delivery confirmation. H2: two towels requested; delivered, with confirmation recorded in the supplied note. H3: guest asked whether a reading lamp can be borrowed; availability not checked. H4: guest withdrew the request for an extra hanger before any work started. Rules: statuses are Received, In progress, Delivered, Awaiting information, Withdrawn. Use In progress when service team acknowledged but completion is unconfirmed. Awaiting information for an unanswered availability question. Keep all four tokens; do not add guest identities, rooms, deadlines or delivery promises.
02

Compare, correct and save

Compare the answer with the complete sample input and the checks below. H1 remains In progress rather than Delivered. If a fact is missing, changed or invented, paste the correction prompt below into the same chat. Read the revised result again; if it still fails, correct the text yourself before using it. Copy the reviewed result into a new note or text document. Keep real publication, decisions and sending for a separate human review.

Your starting prompt
Check your previous answer against the SAMPLE INPUT in my first message. Test each point below. For a failure, show the problem and then return a complete corrected answer; for a missing source fact, keep it explicitly unknown. Do not invent a successful check.
- H1 remains In progress rather than Delivered.
- H3 has no availability claim and H4 is retained as Withdrawn.
- All four tokens appear once, with no invented guest details or response times.
03

Optional: use your own facts

Open a new chat. Copy the prompt below and replace [PASTE YOUR INPUT HERE] with your own non-sensitive source text, facts and limits for this task. Include any desired headings, count or length. Send the whole message. Expect the same kind of written result, using your facts. Check every source fact and limit yourself; the example’s names and totals do not apply. If a detail differs, show the exact mismatch and ask for a complete correction. Save the checked draft before any separate decision to use or send it.

Your starting prompt
Make a shift relay log from the records below with token, request, exact status, evidence and next information needed. Preserve every record and derive totals from this list. Do not convert acknowledgement into delivery or claim to contact staff.

Use only my input. Ask for information needed to finish rather than guessing. Return written text only; do not send, publish, book, submit or change another service.

MY INPUT
[PASTE YOUR INPUT HERE]
Optional: improve the result

Write a brief spoken handover

Summarize only what the next shift needs to resolve. This extension uses the worked example. Return to that example chat, or paste its input and your checked example answer into a new chat first. Do not apply its sample values unchanged to your own input.

Advanced prompt
Write a spoken handover under 65 words focusing on H1 and H3. Mention H2 and H4 as closed states without reopening them, and do not add a deadline. Keep the same SAMPLE INPUT from my first message unless I explicitly replace it.
Show, then try

See the shape of the result.

This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.

The starting point

Synthetic input
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional guest-service notes use request tokens only. H1: extra blanket requested; service team acknowledged; no delivery confirmation. H2: two towels requested; delivered, with confirmation recorded in the supplied note. H3: guest asked whether a reading lamp can be borrowed; availability not checked. H4: guest withdrew the request for an extra hanger before any work started. Rules: statuses are Received, In progress, Delivered, Awaiting information, Withdrawn. Use In progress when service team acknowledged but completion is unconfirmed. Awaiting information for an unanswered availability question. Keep all four tokens; do not add guest identities, rooms, deadlines or delivery promises.

Copies text only. For image or file tasks, use the source files named in the steps too.

Download source .txt

The intended result

Illustrative output
Worked example written for this guide, not output recorded from a live AI session.

H1 | Extra blanket | In progress | Service team acknowledged; no delivery confirmation | Need confirmation of whether the blanket was delivered.
H2 | Two towels | Delivered | Supplied note confirms delivery | No further information needed for this request.
H3 | Reading lamp loan question | Awaiting information | Availability has not been checked | Need a confirmed availability answer before replying.
H4 | Extra hanger | Withdrawn | Guest withdrew before work started | No delivery action remains requested.

Counts: In progress 1; Delivered 1; Awaiting information 1; Withdrawn 1.
Download result .txt
You’re the final check

Check the worked example.

These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.

Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.

A few things to watch for.

  • Acknowledged, assigned and delivered are different states. Preserve the evidence for the one you use.
  • Do not use this practice log as an operational guest-record system.

What has been checked?

Documentation
No dated source review recorded.
Included files
No scoped artifact-check record.
AI workflow
Not run in a recorded consumer-AI workflow.
Time savings
Time savings not measured

Copy these instructions

Your browser blocked automatic copying. Select the text below and copy it.