# Booking hotels with Claude: one tax-inclusive total per site, reviews mined for hidden fees, deals broken down night by night, then a daily watch for a drop

Claude Duet · Reddit · No income, saving total, room rate or tool cost is disclosed anywhere in the original post.

## Business summary

Reddit user u/Efistoffeles described his four-step hotel routine in r/claude. First, get one real total per site: the same room shows different things on different sites - some include city tax, some do not, and resort, destination or 'community impact' fees are collected at the desk - so he has Claude pull the same room from several sites via connectors and get one tax-inclusive number for the whole stay. Second, let it read the reviews: nobody reads 300 reviews, but that is where the money is - parking at 40 a night, a 7 'safe fee', a minibar with sensors that billed someone for moving things, a family that drove nine hours to a hotel that had been closed for months. He asks Claude to extract only the money items and anything that sounds like overbooking or closure. Third, let it do the maths on deals: his example is someone else's, remembered from Reddit - a 'third night free' where night two was priced far higher plus a 19 percent destination fee, so the free night was simply spread across the other two; and, from a hotel he checked himself, 48 rates that were really only 7 rooms under different names - also his own observation, unverified. Fourth, keep checking after booking: prices move a lot - he has seen the same room go up 60 percent in hours - so he only books free-cancellation rates and sets a scheduled Claude task to check the same room daily until the cancellation window ends and tell him if it got cheaper so he can rebook. No saving total, room rate or tool cost appears in the post. His claim that almost half of a few thousand rates in one city had an at-hotel fee is his own observation, unverified, and the post ends with four connector links, which reads partly as promotion - both disclosed here.

## Business value

The hard part here is the unit of comparison, not the automation. Nightly rates across sites are not comparable once you account for city tax and at-hotel fees; normalise first, then compare. The second lever is review mining, because the things that actually cost money are buried in reviews nobody reads.

## Workflow

Fix the comparison basis first: whole stay, tax inclusive, at-hotel fees listed separately.

Pull the same room from a fixed site list; one number per site, each with a capture time. (Site list and connectors follow the original post; the capture-time rule is AgentFlow's.)

Read reviews for two things only: items that cost extra, and signs of overbooking or closure.

Break any promotion down night by night and merge rates that are the same room under another name.

Only book free-cancellation rates, then run a daily check that stops on the cancellation deadline.

Rebooking and cancelling stay with the person; the agent only flags. (AgentFlow's boundary; the original post does not describe an authorisation limit.)

## Preparation and limitations

The post gives no saving total, no room rate, no successful rebooking example and no subscription or connector cost. It does not say which sites were pulled for a given stay, how often the daily check actually fired, or whether any flagged drop was ever acted on. The statistics it quotes - almost half of a few thousand rates carrying an at-hotel fee, a 60 percent swing in hours, 48 rates that were really 7 rooms - are the author's own observations with no source given. The four connector links at the end read partly as promotion and no relationship between the author and those services was verified. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Starter prompt

````text
You are my hotel comparison assistant. You may organise prices, read reviews, compute promotions and report price changes by day. You do not book, do not modify or cancel an existing booking, and do not log into my accounts.

[INPUT]
- Hotel and room: [hotel name], [room and bed type], [check-in and check-out dates]
- Sites to compare: [site list]
- My basis: total for the whole stay, with tax split into included and payable-at-hotel
- If already booked: [total paid], [free cancellation yes/no], [cancellation deadline]

[STEPS]
1. Pull the same room and room type from each site and output a table: site / total for the stay / tax included / at-hotel items and amounts / capture time. If a site fails, write not retrieved and say why.
2. Read recent reviews and output only two categories: specific items that cost extra, with amounts and how often they are mentioned; and anything suggesting overbooking, closure or no room on arrival. Output nothing else.
3. If a promotion exists (third night free, stay-three-pay-two), output a night-by-night price table, merge rates that are the same room under a different name, and give the difference between taking and not taking the promotion.
4. If I have booked with free cancellation, run the daily check until the deadline: today's price / difference from what I paid / whether it crossed my threshold / days left before the deadline.

[OUTPUT]
1) per-site total table; 2) review extract limited to the two categories; 3) promotion comparison; 4) daily monitoring report including days remaining.

[NEEDS MY CONFIRMATION]
- Rebooking, cancelling or booking: advice only, I execute.
- At-hotel charges the site does not disclose: write not disclosed, never estimate.
- If a promotion difference depends on an assumption, state the assumption.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Blocked site, anti-bot wall, room type mismatch, missing price field: record it as not retrieved with the reason. Do not substitute another site's price and do not reuse yesterday's number as today's. On the cancellation deadline, stop the check and say so explicitly.
````

## Costs and pitfalls

The post gives no saving total, no room rate, no successful rebooking example and no subscription or connector cost. It does not say which sites were pulled for a given stay, how often the daily check actually fired, or whether any flagged drop was ever acted on. The statistics it quotes - almost half of a few thousand rates carrying an at-hotel fee, a 60 percent swing in hours, 48 rates that were really 7 rooms - are the author's own observations with no source given. The four connector links at the end read partly as promotion and no relationship between the author and those services was verified. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Source and attribution

Efistoffeles（Reddit 用户 u/Efistoffeles，原帖作者本人，自述常出差／旅行订房） (u/Efistoffeles)
https://www.reddit.com/r/claude/comments/1x8m80f/use_claude_to_save_on_booking_hotels_when/
2026-10-17
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
