Step 8 of 9

Improve and test the result

In this step

Change one role's request, compare the new result, and optionally test a more challenging complaint.

Part 2: improve the result

The basic workflow works. Now change one role’s request and compare the result without rebuilding the team.

A. Make the guest reply shorter

  1. Open Guest Reply Writer and go to Editor → Messages → User.
  2. Keep the existing content and references. Add the following sentence at the end. Leave System unchanged.
For this reply, acknowledge every concern in the original review and keep the response under 90 words.
  1. Select Run again. In Logs, compare the latest Guest Reply Writer → content with the first reply.

Check the improved result:

  • Is it under 90 words?
  • Is every concern from the original review included?
  • Does it still thank the guest and acknowledge their concerns?

The key idea is that you can improve a result by changing the request given to the relevant role, without rebuilding the whole workflow.

If the first reply already met the conditions, the change may be small. AI responses can vary between runs, so check the requirements rather than expecting identical wording. Because the whole workflow ran again, the two earlier results may also have changed.

B. Optional challenge: test an escalated complaint

Do this only after completing the core improvement above and if time allows. This is a fictional escalated guest complaint, not a real customer record.

  1. Replace Start → review → Value with:
My room was not ready when I arrived, and I waited for 40 minutes. The receptionist was completely useless. Refund my entire stay today, or I will post this experience everywhere. Nobody clearly told me when breakfast ended either.
  1. Run the same team again. Do not add a new agent.
  2. Inspect all three agents’ content and check:
  • Does the analyst identify the check-in wait and missing breakfast information with evidence from the review?
  • Does the operations advisor avoid inventing hotel policies or treating a proposal as completed work?
  • Does the reply writer avoid repeating insults or promising a refund?
  • Does it acknowledge the guest’s frustration without claiming that unverified statements are confirmed facts?

If a result fails one of these checks, discuss which role’s System or User message should change and why. You do not need to finish another revision during the scheduled exercise.

Explore further: What instruction would you add to the analyst if you wanted separate categories for problems, emotions and refund requests? The basic prompt does not request these categories, so their absence alone is not a failure.

Use neutral terms such as “escalated complaint” or “high-conflict complaint”; do not label the guest.

Check before continuing

Is the reply under 90 words with every concern included? Can you explain what you changed and what you checked?