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.
linkedin.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Use this wedding brief to draft routine vendor answers in allowlisted Gmail threads. Hold prices, quotes, contracts and deposits, and pause whenever I reply manually.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Youssef Hounat CA
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- An hourly Gmail workflow answered routine wedding vendor questions, attached references and paused for financial decisions or a human takeover.
- Human involvement
- Hounat handled quotations, contracts and deposits, and a manual response paused the agent's activity on that thread.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Keep wedding dates, guest count, scope and references in a Markdown brief.
- Check only allowlisted Gmail threads through an hourly Python cron job.
- Answer routine questions; hold financial matters and pause after a manual reply.
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
Frequently asked questions
Which messages were held as drafts?
Prices, quotations, contracts and deposits were held for Hounat to handle.
Why exclude bounced messages?
An unwanted reply to a bounce exposed a missing rule; he then skipped bounces and out of office messages.
What stopped duplicate human and agent replies?
A manual reply by Hounat paused the agent on that thread.
More details
About this account
Claude Code generated routine vendor replies and used the shared brief and attachments within allowlisted Gmail conversations.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Youssef Hounat CA
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Gmail · Python · macOS cron
Wedding vendors · Gmail · Reply rules · Markdown brief
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.