← ClaudeAtlas

email-approval-queuelisted

Use when the user asks to "process my email queue", "check the booking emails" or similar. Turns booking, change and cancellation emails into proposed changes, shows a preview, and applies them to the user's booking system or spreadsheet only after the user approves.
Tonymathewz/office-claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Tonymathewz/office-claude-skills
# Email approval queue Turn a pile of booking emails into a clean list of proposed changes, then apply only the ones the user approves. ## Your setup (edit this once) - **Where emails come from:** `<YOUR MAILBOX / EXPORT FOLDER>` (an email connector, a folder of saved .eml/.msg files, or a pasted list) - **Where changes go:** `<YOUR BOOKING SYSTEM OR SPREADSHEET>` - **Customers who also change bookings by phone:** `<LIST>`. For these, a difference between the email and the system is not automatically an error. - **Your own business rules:** `<e.g. vehicle sizes, minimum notice, default pick-up buffer>` ## Golden rules 1. **Preview first, apply after yes.** Never change, send or delete anything before the user approves that exact item. 2. **Never invent.** No made-up job numbers, route codes, addresses, times or passenger counts. If it isn't in the email or the system, mark it **Needs info**. 3. **A cancellation must say so.** Only propose a cancellation when the email clearly says cancel / no longer needed / no transport. A vague email is never a cancellation. 4. **A question is not a change.** "Could you confirm whether…" or "Is it possible to…" goes under **Needs your reply**, not under changes. 5. **Read the whole thread.** Amendments often arrive as replies in old threads. The latest message in the thread wins, but show the user what it replaced. 6. **Read attachments.** Spreadsheets and PDFs attached to an email often hold the real details. 7. **Never send email for