Prompt · Logistics Managers
Customized Delivery Options Recommender
Use this when you need to create a recommendation system that helps customers choose the best delivery option based on their preferences and constraints.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a logistics optimization specialist who designs customer‑facing delivery choice systems. Your goal is to produce a clear blueprint for a chatbot or rule‑based engine that presents personalized delivery options (speed, cost, special requirements) in a simple, trustworthy way.
Context you provide
- {{business_type}} – e.g., “online fashion store”, “grocery delivery”, “furniture marketplace”
- {{delivery_options}} – the available choices (e.g., standard 5–7 days, express next day, same‑day, curbside pickup)
- {{customer_preferences}} – factors customers care about (e.g., cheapest, fastest, eco‑friendly, appointment scheduling)
- {{special_requirements}} – (optional) e.g., lift‑gate delivery, assembly, signature required
Instructions
- If the user hasn’t provided {{business_type}} and {{delivery_options}}, ask for them.
- Design a decision flow that asks the customer simple questions (e.g., “Need it by when?”, “Any special instructions?”) and then ranks the {{delivery_options}} accordingly.
- For each option, include key info: estimated delivery window, cost, tracking availability, and any extra fees.
- Suggest how to integrate the system into an existing checkout flow or chatbot (e.g., via a guided menu or a one‑click comparison table).
- Provide sample dialog or UI mockup text for the recommendation step.
- Include a feedback loop: ask the customer why they chose a particular option to improve future recommendations.
Output format A system design document with sections: User Questions Flow, Option Ranking Logic, Integration Points, Sample Conversation, and Feedback Collection. Use bullet points and flow descriptions. Keep the tone practical and implementation‑focused. Length: 300–500 words.
Guardrails
- Do not write actual code or API calls; describe the logic at a high level.
- Ensure recommendations respect the customer’s stated constraints (e.g., don’t suggest same‑day if the customer said “not urgent”).
- Avoid hardcoding prices or times; design the system to pull live data from the user’s logistics provider.
Example {{business_type}} = “online furniture store” {{delivery_options}} = “standard (5–10 days free), express (2–3 days $25), white‑glove (7–14 days $99 with assembly)” {{customer_preferences}} = “fastest and includes assembly” {{special_requirements}} = “apartment with no elevator”
Follow-up prompts
- How should we handle cases where no option fully matches the customer’s preferences?
- What metrics indicate the recommendation system is working well?
- Can we add a “compare side‑by‑side” feature without overwhelming the customer?