Claude to reply to wedding vendors with price pauses

Youssef Hounat used Claude Code to handle repeated wedding vendor questions from a shared Markdown brief. That document held the event scope, guest count, dates, reference material and budget, giving replies a consistent source of information.

He ran an hourly Python job on his Mac to check Gmail threads on an allowlist. The workflow answered routine coordination questions and attached reference files when making an initial response. He turned the arrangement into a reusable skill so later replies could draw on the same brief.

The interesting part was deciding where automatic replies should stop. Messages involving prices, quotations, contracts or deposits were held as drafts. A manual reply from Hounat also paused the workflow, preventing the agent from continuing a conversation he had taken over. These were reported rules in his setup, rather than a general claim that a wedding agent could handle every negotiation.

He added exclusions for bounced messages and out of office replies after an unwanted response to a bounce exposed that gap. The result was a recurring vendor correspondence workflow with explicit financial and human intervention boundaries. His account describes the email handling system; it does not report a completed wedding, total savings or autonomous contract signing.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: www.linkedin.com · Youssef Hounat CA