100 Best Claude Florist Order Confirmation Prompts for Florists

Direct Answer

The best Claude prompts for florist order confirmation for florists are designed to produce precise, customer-friendly confirmations that cover order details, delivery windows, payment status, substitutions, and care instructions. They guide tone, channel, and localization while ensuring clarity and compliance. Use placeholders for order data and tailor outputs per channel.

Introduction

This page collects the most practical Claude prompts for florist order confirmation. It helps florists streamline customer communications, reduce errors, and maintain brand voice across channels.

Whether you run a single-shop storefront or a multi-location operation, these prompts give your team reliable templates that can be adapted to your workflows.

How to Use These Claude Prompts

• Replace placeholders with real order data such as [order_id], [customer_name], [delivery_date], and [bouquet_list]. Add constraints like tone, length, or channel, and request outputs in your preferred format. Specify the exact sections you want in the output, such as Confirmation and Delivery Details. Verify outputs by spot-checking against the actual order details before sending to customers.
• When needed, ask Claude to translate the confirmation into a customer’s language or adjust for accessibility by requesting plain language output. Use the three-step approach: confirm basics, present any substitutions, then add care tips or policy notes. Save the final version as a reusable template.
• bestPractices is not allowed to be empty and must be a list of strings.
• commonMistakes must be a list of strings.

100 Best Claude Florist Order Confirmation Prompts for Florists

1. Basic order confirmation: You are a florist operations assistant. Task: craft a concise order confirmation message for a customer after they submit an order. Context: the order includes [order_id], [customer_name], [delivery_date], [delivery_address], [bouquet_list], [special_requests]. Output format: provide a short confirmation paragraph and a bullet list of key details with exact fields in order: order ID, delivery date, delivery address, items, total price, estimated delivery window. Constraints: keep tone professional, friendly, and clear. Do not mention processing times beyond two sentences.
2. Confirmation with payment status: Role: florist customer service agent. Task: confirm order and payment status to the customer. Context: order [order_id], customer [customer_name], payment status [payment_status], items [bouquet_list], total [total_price], delivery details [delivery_date], [delivery_address]. Output: two sections labeled Confirmation and Payment Details. In Confirmation, confirm items and delivery. In Payment Details, clearly state whether payment is complete or pending, and any next steps if pending. Include a call to action to contact support if mismatches arise.
3. Delivery window precision: Role: operations coordinator. Task: provide a precise delivery window for the order. Context: delivery_date [delivery_date], location [delivery_address], time window preference [time_window], traffic note [traffic_note]. Output: one paragraph confirming date and a 2-hour delivery window, followed by a brief note on any potential delays and how to contact the florist if the customer needs to adjust time.
4. Upsell addon prompts: Role: sales associate. Task: present optional upgrades after confirming order basics. Context: [order_id], [customer_name], items confirmed [bouquet_list], base_total [total_price], available_upgrades [upgrades], delivery_date. Output: list three to five upsell options with final prices, plus a gentle recommendation tailored to the customer’s preferences inferred from order items. Do not pressure, keep it friendly.
5. Locale-aware confirmation: Role: regional coordinator. Task: tailor confirmation language to local dialects. Context: customer locale [locale], preferred language [language], order details [order_id], [delivery_date], [bouquet_list]. Output: provide the confirmation in the customer’s language if available; otherwise, present bilingual option with clear labels. Include a note about local delivery areas and contact if issues arise.
6. Accessibility-friendly confirm: Role: accessibility reviewer. Task: ensure the confirmation text is accessible. Context: order_id [order_id], customer_name [customer_name], items [bouquet_list], delivery_date [delivery_date], delivery_address [delivery_address]. Output: provide a plain-language confirmation in 1–2 short paragraphs and a readable list of details. Avoid jargon, use high-contrast formatting hints in the output, and include an accessible call-to-action.
7. Order with substitutions: Role: florist manager. Task: communicate substitutions if requested items are unavailable. Context: original_items [original_items], substitutions [substitutions], reason [reason], order_id [order_id], delivery_date [delivery_date]. Output: clearly state substitutions, why they were made, impact on appearance and value, and offer to adjust if the customer disagrees. Provide a final total after substitutions.
8. Confirmation for corporate order: Role: corporate orders agent. Task: confirm a bulk floral order for a business event. Context: corporate_client [client_name], order_id [order_id], items [bouquet_list], quantity [quantity], delivery_date [delivery_date], delivery_address [delivery_address], budget [budget]. Output: provide a formal confirmation with a brief summary of items, total cost, delivery schedule, and point of contact for changes.
9. Seasonal greeting tone: Role: floristry communications specialist. Task: craft confirmation with warm seasonal tone. Context: order_id [order_id], customer_name [customer_name], items [bouquet_list], delivery_date [delivery_date], delivery_address [delivery_address], season [season]. Output: a friendly message that acknowledges the season, confirms all details, and includes a seasonal note or offer.
10. Refund or cancellation info: Role: customer support agent. Task: include clear policy notes on refunds or cancellations if requested. Context: order_id [order_id], customer_name [customer_name], request_type [request_type], policy_details [policy_details], delivery_date [delivery_date]. Output: confirm current status and provide exact steps to pursue refund or cancellation, including deadlines and contact methods.
11. Multi-address order: Role: order processor. Task: confirm orders that involve multiple delivery addresses. Context: order_id [order_id], deliveries [deliveries], items_per_delivery [items_per_delivery], total [total_price]. Output: confirm each delivery address, each item assigned, and a consolidated total. Include guidance on updating any one delivery without affecting others.
12. Pickup option confirmation: Role: store operations. Task: confirm if the customer opted for pickup instead of delivery. Context: order_id [order_id], customer_name [customer_name], items [bouquet_list], pickup_time [pickup_time], pickup_location [pickup_location]. Output: confirm pickup readiness, location, and any required ID or contact for pickup.
13. Custom message length: Role: copywriter. Task: adjust the length of the confirmation to fit a specific channel. Context: channel [channel], max_length [max_length], order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: provide a version tailored to the channel with the exact character count limit respected.
14. Tone: professional to friendly: Role: brand voice guide. Task: adapt confirmation tone across customer types. Context: customer_segment [segment], order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: provide two variants: professional and friendly, both with the same factual details.
15. Language preference: Role: language service assistant. Task: convert confirmation into preferred language. Context: language [language], order_id [order_id], customer_name [customer_name], items [bouquet_list], delivery_date [delivery_date]. Output: provide translated confirmation with accurate floral terminology and a short note about translation accuracy.
16. After-approval follow-up: Role: customer success agent. Task: draft a post-confirmation follow-up message after a customer approves an order. Context: order_id [order_id], customer_name [customer_name], delivery_date [delivery_date], items [bouquet_list]. Output: a polite follow-up asking if the customer needs any changes before production begins.
17. Sustainable sourcing note: Role: sustainability coordinator. Task: include eco-friendly notes where relevant. Context: order_id [order_id], items [bouquet_list], supplier_info [supplier_info], delivery_date [delivery_date]. Output: mention sustainable sourcing and recyclable packaging where applicable; provide contact for more details.
18. Rush order confirmation: Role: operations lead. Task: confirm a rush floral order. Context: order_id [order_id], delivery_date [delivery_date], items [bouquet_list], urgency [urgency]. Output: confirm rush handling, revised delivery window, and any extra fees if applicable.
19. Warranty and plant health: Role: quality assurance. Task: include a brief note on plant freshness or floral warranty where offered. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], policy_details [policy_details]. Output: mention freshness guarantees and how to contact if flowers arrive past freshness window.
20. Customer note inclusion: Role: orders coordinator. Task: include customer-provided notes in the confirmation. Context: order_id [order_id], customer_notes [customer_notes], items [bouquet_list], delivery_date [delivery_date]. Output: present a confirmation that clearly lists customer notes and confirms if they were applied.
21. Delivery instructions check: Role: delivery supervisor. Task: verify special delivery instructions. Context: order_id [order_id], delivery_address [delivery_address], instructions [instructions], delivery_date [delivery_date]. Output: confirm instructions are understood and add a final check for access details or gate codes.
22. Floral care tips: Role: florist educator. Task: add brief care instructions for the recipient. Context: items [bouquet_list], delivery_date [delivery_date]. Output: provide easy care tips in two to three bullet points.
23. Attachment-ready confirmation: Role: communications admin. Task: produce confirmation text suitable for attachment to email or message. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], total_price [total_price]. Output: plain text with header that can be copied into an email body.
24. Gift note inclusion: Role: customer experience. Task: incorporate a gift note where provided. Context: gift_note [gift_note], order_id [order_id], customer_name [customer_name], items [bouquet_list]. Output: confirmation that the gift note is attached and readable by the recipient.
25. Event pickup coordination: Role: events planner. Task: coordinate florals for an event with delivery to multiple rooms. Context: order_id [order_id], event_name [event_name], rooms [rooms], items [bouquet_list], delivery_date [delivery_date]. Output: confirm per-room delivery plan and any setup notes.
26. Invoice linkage: Role: billing specialist. Task: link confirmation to invoice status. Context: order_id [order_id], invoice_id [invoice_id], total_price [total_price], payment_status [payment_status], delivery_date [delivery_date]. Output: confirm invoice status and provide next steps for payment if needed.
27. Compliance note: Role: compliance officer. Task: include required legal or policy notes. Context: order_id [order_id], region [region], delivery_date [delivery_date]. Output: state applicable policy or regulatory notes briefly and clearly.
28. Photos of arrangement: Role: marketing assistant. Task: offer to provide photos of the arrangement after fulfillment. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: ask for consent to share photos, and outline delivery of the photo file.
29. Recurring customer cue: Role: loyalty program manager. Task: tailor confirmation for returning customers. Context: customer_id [customer_id], order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: acknowledge prior orders and invite to join loyalty benefits.
30. Damage policy reminder: Role: customer support. Task: remind about damage policies if delivery arrives damaged. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], policy_details [policy_details]. Output: brief reminder of how to file a claim and expected response time.
31. Accessibility alt-text: Role: content creator. Task: generate alt text for confirmations used in images. Context: order_id [order_id], items [bouquet_list]. Output: provide clear, descriptive alt text suitable for screen readers.
32. Channel-specific formats: Role: channel specialist. Task: adapt confirmation to different channels. Context: channel [channel], order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: three format variants suitable for email, SMS, and chat.
33. Conflicting delivery times: Role: operations analyst. Task: handle conflicting delivery times. Context: preferred_time [preferred_time], available_times [available_times], order_id [order_id], delivery_address [delivery_address]. Output: propose the best alternative window and explain the trade-offs.
34. Cancellation prevention: Role: customer success. Task: include proactive note to prevent cancellation. Context: order_id [order_id], customer_history [customer_history], delivery_date [delivery_date]. Output: a brief reassurance and a proactive question about any concerns.
35. Localization taxes and fees: Role: finance clerk. Task: mention taxes or delivery fees when applicable. Context: location [location], total_price [total_price], tax_details [tax_details], delivery_date [delivery_date]. Output: clear breakdown and confirm final amount.
36. Scent sensitivity note: Role: florist consultant. Task: note if any fragrance might affect sensitivities. Context: items [bouquet_list], customer_sensitivity [sensitivity], delivery_date [delivery_date]. Output: mention if fragrance is light, moderate, or heavy and offer alternatives.
37. Return to stock notice: Role: inventory manager. Task: inform about items that will be returned to stock if not collected. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: brief note on policy and next steps if unclaimed.
38. SLA alignment: Role: service level manager. Task: align confirmation with SLA. Context: order_id [order_id], region [region], delivery_date [delivery_date], expected_response_time [response_time]. Output: state SLA terms and confirm commitment.
39. Partner florist coordination: Role: partner liaison. Task: coordinate with partner florists if shared orders exist. Context: order_id [order_id], partners [partners], delivery_date [delivery_date]. Output: summarize coordination plan and contact points.
40. Digital gift card tie-in: Role: product specialist. Task: suggest linking a digital gift card with the order. Context: order_id [order_id], items [bouquet_list], gift_card_available [gift_card_available], delivery_date [delivery_date]. Output: brief suggestion with steps to add to the order.
41. Cross-sell with care tips: Role: sales trainer. Task: propose safe cross-sell options that fit the order. Context: order_id [order_id], items [bouquet_list], customer_preferences [preferences], delivery_date [delivery_date]. Output: three relevant, low-pressure options with rationale.
42. Language-neutral confirmation: Role: translator. Task: craft a language-neutral confirmation that remains clear in any language. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: base text and notes on how to localize without losing meaning.
43. Voice channel prompt: Role: voice assistant designer. Task: generate confirmation for voice-activated interfaces. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], channel_voice [channel_voice]. Output: script with natural pauses and confirmations.
44. Emergency contact line: Role: operations lead. Task: include an emergency contact line in case of urgent changes. Context: order_id [order_id], delivery_date [delivery_date], contact_line [contact_line]. Output: concise emergency contact instruction.
45. Confirmation with delivery notes: Role: delivery coordinator. Task: attach delivery notes to confirmation. Context: notes [notes], order_id [order_id], delivery_date [delivery_date]. Output: include notes and a short acknowledgement.
46. Non-floral substitutes: Role: florist supervisor. Task: explain non-floral substitutes if requested items unavailable. Context: requested_items [requested_items], substitutes [substitutes], reason [reason], order_id [order_id]. Output: describe substitutes, impact on appearance, and value.
47. Compliance-safe data handling: Role: data compliance officer. Task: ensure customer data handling is compliant. Context: order_id [order_id], data_sensitivity [data_sensitivity]. Output: brief note on data handling practices and privacy.
48. Follow-up request for changes: Role: customer relations. Task: ask for any changes after confirmation but before production. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: polite inquiry about adjustments and a deadline for changes.
49. Satisfaction survey prompt: Role: marketing analyst. Task: invite to a short satisfaction survey after order confirmation. Context: order_id [order_id], customer_email [customer_email]. Output: sentence inviting survey with link and optional incentive.
50. Inclusive language check: Role: copy editor. Task: ensure inclusive language. Context: order_id [order_id], customer demographics [demographics], items [bouquet_list]. Output: confirm usage of inclusive terms and offer alternative phrases if needed.
51. Data-driven upsell: Role: analytics lead. Task: base upsell suggestions on past orders. Context: customer_history [customer_history], order_id [order_id], items [bouquet_list], available_upgrades [upgrades]. Output: three personalized upgrade prompts with justification.
52. Temperature and timezone: Role: support agent. Task: state time zone and local time for delivery window. Context: delivery_date [delivery_date], delivery_address [delivery_address], timezone [timezone]. Output: confirm local time equivalents and offer a range of options.
53. Seasonal inventory note: Role: inventory supervisor. Task: note seasonal limitations in confirmation. Context: season [season], items [bouquet_list], available_stock [available_stock]. Output: brief note on stock status and alternatives if needed.
54. Gift wrapping option: Role: shop assistant. Task: confirm gift wrapping as an option. Context: order_id [order_id], gift_wrap [gift_wrap], items [bouquet_list], delivery_date [delivery_date]. Output: confirm selection and any extra fees.
55. Delivery carrier details: Role: logistics coordinator. Task: provide carrier and tracking info when available. Context: order_id [order_id], carrier [carrier], tracking_number [tracking_number], delivery_date [delivery_date]. Output: share carrier name and tracking link.
56. Feedback request prompt: Role: service quality analyst. Task: request feedback on the confirmation experience. Context: order_id [order_id], channel [channel], delivery_date [delivery_date]. Output: brief feedback request with a simple rating option.
57. Digital receipt attachment: Role: admin assistant. Task: note that a digital receipt is attached. Context: order_id [order_id], total_price [total_price], delivery_date [delivery_date]. Output: confirm attachment and how to access it.
58. Cross-border order: Role: international logistics. Task: confirm international order details. Context: order_id [order_id], destination_country [destination_country], items [bouquet_list], duties_and_tees [duties_and_taxes], delivery_date [delivery_date]. Output: outline duties, estimated delivery time, and contact for issues.
59. Customer preferences recap: Role: customer success. Task: recap known customer preferences. Context: customer_id [customer_id], preferences [preferences], order_id [order_id], items [bouquet_list]. Output: concise recap and a note on how it influenced item selection.
60. Accessibility color contrast: Role: UI/UX engineer. Task: ensure contrast in confirmation visuals. Context: platform [platform], text_content [text_content], contrast_requirements [contrast_requirements]. Output: quick contrast guidance and color suggestions.
61. Order tracking prompt: Role: order tracker. Task: provide live status for the order. Context: order_id [order_id], status [status], update_time [update_time], delivery_date [delivery_date]. Output: a concise status update and next steps if any delays.
62. Add-on delivery pairing: Role: product advisor. Task: suggest compatible add-ons for the delivery. Context: items [bouquet_list], add_ons [add_ons], delivery_date [delivery_date]. Output: three paired add-ons with brief justification.
63. Customer privacy note: Role: compliance auditor. Task: include a privacy note in the confirmation. Context: customer_data [customer_data], order_id [order_id]. Output: short privacy tip and how to request data deletion.
64. Color palette confirmation: Role: design lead. Task: confirm color palette of bouquets. Context: bouquet_list [bouquet_list], preferred_palette [palette], order_id [order_id]. Output: confirm palette and offer alternatives if conflicts arise.
65. Floral care reminders for recipients: Role: education specialist. Task: add two floral care reminders for recipients. Context: items [bouquet_list], delivery_date [delivery_date]. Output: two clear care tips with illustrations if applicable.
66. Voice assistant script: Role: voice UI designer. Task: script for confirming orders via voice assistant. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: natural, concise confirmation script with confirmation prompts.
67. Template for team handoff: Role: operations lead. Task: provide a handoff note to production team. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], notes [notes]. Output: structured handoff summary with checkpoints.
68. Backorder notice: Role: fulfillment coordinator. Task: inform customer of backordered items and ETA. Context: order_id [order_id], backordered_items [backordered_items], eta [eta], delivery_date [delivery_date]. Output: clear explanation and revised delivery plan.
69. Delivery confirmation checklist: Role: delivery supervisor. Task: provide a checklist for delivery confirmation. Context: order_id [order_id], items [bouquet_list], delivery_address [delivery_address], delivery_date [delivery_date]. Output: bulleted checklist of required confirmations.
70. Confirmation for designer-led bouquets: Role: design coordinator. Task: confirm designer-led bouquets with client approval. Context: order_id [order_id], items [bouquet_list], client_approval [client_approval], delivery_date [delivery_date]. Output: confirmation with any design notes and approval status.
71. Recurring reminder for upcoming date: Role: automated assistant. Task: remind customer of upcoming delivery date. Context: order_id [order_id], delivery_date [delivery_date], time_left [time_left]. Output: concise reminder with a CTA to modify details if needed.
72. Temperature-controlled delivery: Role: logistics manager. Task: confirm if temperature control is required. Context: order_id [order_id], items [bouquet_list], temp_requirement [temp_requirement], delivery_date [delivery_date]. Output: confirm temperature controls and any extra charges.
73. Language-friendly math: Role: finance assistant. Task: show a simple cost breakdown in the confirmation. Context: total_price [total_price], tax_details [tax_details], delivery_fee [delivery_fee], discount [discount]. Output: provide a transparent, easy-to-read breakdown.
74. Emergency change handling: Role: escalation manager. Task: outline steps for urgent order changes. Context: order_id [order_id], requested_changes [requested_changes], deadline [deadline], delivery_date [delivery_date]. Output: step-by-step process and required approvals.
75. Multiple payment methods: Role: billing agent. Task: confirm accepted payment methods. Context: payment_methods [payment_methods], order_id [order_id], total_price [total_price], payment_status [payment_status]. Output: list available methods and how to switch if needed.
76. Loyalty tier perks: Role: loyalty program manager. Task: mention loyalty perks for florist customers. Context: customer_id [customer_id], loyalty_tier [loyalty_tier], order_id [order_id], delivery_date [delivery_date]. Output: brief mention of perks and how to redeem.
77. Webhook-ready data: Role: developer advocate. Task: format confirmation data for a webhook payload. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], total_price [total_price]. Output: plain text JSON-ready payload outline.
78. SLA breach notice: Role: service delivery manager. Task: alert if delivery misses SLA window. Context: order_id [order_id], sla_window [sla_window], actual_delivery_time [actual_delivery_time], impact [impact]. Output: brief breach notice and escalation steps.
79. Customer signature request: Role: compliance officer. Task: request customer confirmation receipt. Context: order_id [order_id], delivery_date [delivery_date], channel [channel]. Output: ask for approval of delivery confirmation and provide sign-off options.
80. Event-driven prompt: Role: event coordinator. Task: confirm florals for a scheduled event with setup notes. Context: event_name [event_name], order_id [order_id], items [bouquet_list], setup_time [setup_time], delivery_date [delivery_date]. Output: confirmation and a checklist for event setup.
81. Replacement policy: Role: operations policy. Task: communicate replacement policy if flowers arrive damaged. Context: order_id [order_id], delivery_date [delivery_date], policy_details [policy_details]. Output: clear steps and timelines for replacements.
82. Seasonal palette options: Role: design advisor. Task: propose seasonal color palettes for order. Context: season [season], items [bouquet_list], customer_preferences [preferences], delivery_date [delivery_date]. Output: three palette options and rationale.
83. florists-only note: Role: internal auditor. Task: include a note for internal staff about order nuances. Context: order_id [order_id], staff_notes [staff_notes]. Output: concise staff-facing note.
84. Delivery address validation: Role: data quality. Task: validate address accuracy before dispatch. Context: delivery_address [delivery_address], order_id [order_id], validation_status [validation_status]. Output: confirm validated address or request correction.
85. Customer sentiment cue: Role: customer experience researcher. Task: include a sentiment cue for the recipient. Context: customer_name [customer_name], order_id [order_id], items [bouquet_list]. Output: brief positive sentiment cue and optional emoji guidance.
86. Language tone map: Role: brand strategist. Task: provide tone variations by channel. Context: channel [channel], order_id [order_id], items [bouquet_list], delivery_date [delivery_date]. Output: tone map for email, SMS, and chat.
87. Anniversary or milestone note: Role: marketing copywriter. Task: add a note for anniversaries or milestones if relevant. Context: occasion [occasion], order_id [order_id], delivery_date [delivery_date], items [bouquet_list]. Output: brief celebratory note and placement guidance.
88. Return-to-sender policy: Role: logistics manager. Task: include a return-to-sender note if undelivered. Context: order_id [order_id], address [address], delivery_date [delivery_date], policy_details [policy_details]. Output: clear return instructions and timelines.
89. Geographic delivery restrictions: Role: compliance officer. Task: confirm delivery availability by region. Context: region [region], order_id [order_id], delivery_date [delivery_date]. Output: confirm service availability and alternatives if restricted.
90. Photo consent toggle: Role: marketing compliance. Task: confirm whether customer consent is given for using floral images. Context: order_id [order_id], consent_status [consent_status]. Output: note consent status and usage rights.
91. Sensible payload summary: Role: data summarizer. Task: present a compact summary of the order in the confirmation. Context: order_id [order_id], items [bouquet_list], total_price [total_price], delivery_date [delivery_date]. Output: one short paragraph and a bullet list of key details.
92. Back-office handoff: Role: operations lead. Task: provide an exhaustive handoff to the back office. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], notes [notes], price_details [price_details]. Output: structured handoff with sections.
93. Customer query ready: Role: customer service agent. Task: pre-answer common customer questions in the confirmation. Context: order_id [order_id], common_queries [queries]. Output: provide concise answers to three typical questions.
94. SLA-compliant escalation: Role: service delivery lead. Task: outline escalation path for urgent issues. Context: issue [issue], order_id [order_id], sla_window [sla_window]. Output: step-by-step escalation guide.
95. Digital signature guidance: Role: compliance auditor. Task: include guidance on digital signatures for confirmations. Context: order_id [order_id], channel [channel]. Output: instructions for obtaining and recording digital acknowledgement.
96. Climate-friendly delivery: Role: sustainability officer. Task: highlight eco-friendly delivery options. Context: order_id [order_id], options [options], delivery_date [delivery_date]. Output: brief note on options and impact.
97. Gift bouquet personalization: Role: creative consultant. Task: confirm personalization options for gift bouquets. Context: order_id [order_id], personalization_details [personalization_details], delivery_date [delivery_date]. Output: confirm available personalization and any extra costs.
98. Accessibility companion note: Role: accessibility advocate. Task: include a note about accessibility for customers with disabilities. Context: order_id [order_id], accessibility_needs [needs]. Output: provide contact and accommodations offered.
99. Post-delivery follow-up: Role: customer success manager. Task: draft post-delivery follow-up message. Context: order_id [order_id], delivery_date [delivery_date], items [bouquet_list]. Output: brief follow-up asking for feedback and future needs.
100. Final confirmation template: Role: template engineer. Task: provide a final confirmation text that can be reused across many florists. Context: order_id [order_id], items [bouquet_list], delivery_date [delivery_date], customer_name [customer_name]. Output: reusable confirmation template with placeholders and guidance on customization.

Best Practices

• Keep prompts specific with concrete placeholders for all order attributes.
• Validate the final output against the actual order data to prevent miscommunication.
• Maintain a consistent brand voice and channel-appropriate length for all confirmations.
• Use modular prompts to separate core confirmation from optional add-ons or policies.
• Test prompts across channels (email, SMS, chat) to ensure formatting remains clear.

Common Mistakes to Avoid

• Using vague terms like 'soon' or 'as soon as possible' instead of exact delivery windows.
• Forgetting to include essential order details such as order_id, delivery_date, and items.
• Ignoring accessibility or language preferences in confirmations.
• Overloading prompts with too many requested formats or sections, making output hard to parse.
• Failing to proofread for accuracy after inserting dynamic order data.

FAQ

What makes a good florist order confirmation prompt?

A good prompt clearly defines the required fields, specifies the channel and tone, and instructs the model to include order details, delivery window, payment status, substitutions if needed, and care tips.

How can I tailor prompts for corporate orders?

Include fields like corporate_client, event_name, delivery_schedule, and per-delivery notes. Specify formal tone and a structured layout suitable for emails to executives.

Can I customize prompts for different florists in a chain?

Yes. Create a base template and add a location-based variable for each shop. Ensure brand voice remains consistent while allowing local delivery nuances.

How do I handle substitutions in prompts?

In the prompt, specify original_items and substitutions, explain why substitutions were made, and clearly show the impact on appearance and value.

What channel formats should prompts support?

Prompts should produce outputs suitable for email, SMS, and chat, with concise summaries for SMS and longer, structured messages for email.

How do I ensure accessibility in confirmations?

Ask Claude to generate plain-language text, include alt text if images are used, and avoid complex jargon or long sentences.