How To Write Guidance: A Repeatable “When, If, Then” Framework for AutoCallFlow Ecommerce Support

TL;DR: Guidance Is Only as Good as the Instructions

AutoCallFlow helps ecommerce teams scale customer support with consistent, fast responses—but the quality of that support depends directly on the Guidance you provide.

When you write clear, structured Guidance, your support agent framework can follow those instructions in the right situations—before it reaches other knowledge content or fallback steps. That means fewer escalations, faster resolutions, and a more consistent customer experience.

The easiest way to write effective Guidance is with the “When, If, Then” framework:

• WHEN = the scenario (the trigger)
• IF = the conditions (details that affect the outcome)
• THEN = the specific actions (what to do and what to send)

In this guide, you’ll learn exactly how to write Guidance, see examples for common ecommerce support questions (returns, cancellations, promo codes, order status), and troubleshoot when your Guidance doesn’t trigger as expected.

What Is Guidance in Ecommerce Support Automation?

Guidance is how you tell your AutoCallFlow support workflow what to do in specific customer situations. Think of it as a set of instructions that defines:

• When a certain type of request should be handled a specific way
• Which conditions change the outcome (timing, order status, eligibility, etc.)
• What actions must happen (links, steps, confirmations, next best options)

When Guidance is available, the system follows it first. This priority matters because it prevents your customer from receiving vague or incorrect answers that would otherwise cause escalations.

Why this is critical: In ecommerce support, customers don’t just ask questions—they ask questions with context. Without Guidance that accounts for that context, your automated responses may:

• Escalate unnecessarily (creating more work for your team)
• Skip the right resolution path (leading to frustrated customers)
• Provide incomplete steps (causing repeat messages)

Simple example: A customer asks to return an item. A human agent typically checks eligibility and sends a return portal link plus instructions. If your Guidance doesn’t include those eligibility conditions (like return window), the support workflow may escalate instead of resolving the request quickly.

Clear, step-by-step Guidance is how you create repeatable excellence—like giving every “support teammate” the same playbook.

Introducing the “When, If, Then” Framework

Most teams don’t struggle with support topics—they struggle with writing the instructions consistently. The “When, If, Then” framework removes guesswork by turning messy support knowledge into a structured, easy-to-follow format.

It mirrors how support automation needs to work behind the scenes: it reads the scenario, evaluates conditions, then takes the actions you specified.

When, If, Then at a glance

• WHEN: Set the scenario (the trigger)
• IF: Add conditions (the eligibility or context rules)
• THEN: Define actions (the exact steps and message outputs)

Below, you’ll build the structure yourself and then use it in real ecommerce support scenarios.

How To Write Guidance (Step-by-Step)

Let’s break the framework down into practical writing rules you can use immediately in AutoCallFlow.

1) WHEN: Set the scenario (your Guidance title)

Start by identifying the situation that should activate this Guidance. Use it as the title of your Guidance so it’s easy to find and manage later.

Good WHEN statements are:

• Specific to a customer request type
• Action-oriented
• Easy to scan

Examples:

• WHEN a shopper asks to return an order
• WHEN a customer wants to cancel their subscription
• WHEN a customer asks where their order is (WISMO)

Don’t overcomplicate the WHEN line—it’s just the scenario framing that tells your support workflow what this Guidance is for.

2) IF: Add conditions (the eligibility and context rules)

After the scenario, define the rules that determine what happens next. “If” statements help the system understand how outcomes change based on details like:

• Time since purchase
• Return window eligibility
• Whether an order is fulfilled vs unfulfilled
• Customer tags or plan type (VIP, subscription, etc.)
• Whether tracking information exists

Writing rules for IF conditions:

• Use only conditions that matter for the decision
• Include enough coverage so the system doesn’t get stuck
• Prefer clear thresholds (e.g., “less than or equal to 15 days”)

Examples:

• IF the order was placed ≤ 15 days ago
• IF the customer has a VIP tag
• IF tracking information is available

Important: If you leave gaps, your automated workflow may route to the wrong path or escalate.

3) THEN: Define actions (what to do, exactly)

The THEN section is where you specify the actual steps and outputs your support workflow should deliver. Be precise, and use bullet points or numbered steps to make actions easy to follow.

Examples (returns):

• Tell the shopper they’re eligible for a return
• Send them a link to the return portal
• Let them know they’ll receive a prepaid label via email after submitting the form

The more specific your THEN actions are, the more consistently your workflow will perform.

Pro tip: You’re not writing for yourself—you’re writing for a system that follows instructions literally. If a step is important, include it. If a message must be said a certain way, include the wording or structure.

Put It All Together: A Complete Guidance Example

Here’s what a full Guidance block looks like in “When, If, Then” format for an ecommerce returns question.

Example Guidance: Returns

WHEN a shopper asks to return an order:

• IF the order was placed ≤ 15 days ago, THEN
  • Tell the shopper they’re eligible for a return
  • Send them a link to the return portal
  • Let them know they’ll receive a prepaid label via email after they submit the form
• IF the order was placed > 15 days ago, THEN
  • Inform the customer that the return window has ended
  • Offer alternative solutions if available (exchange, store credit, or support review—only if your policies allow)

This structure prevents ambiguity and reduces the odds of unnecessary escalation.

What you gain:

• Fewer escalations because the system has a defined resolution path
• Faster resolutions because the correct steps are delivered immediately
• More consistent AI behavior because each scenario follows the same playbook

9 Ecommerce Support Scenarios Made Better with Guidance

These scenarios come up constantly in ecommerce customer support—and they follow predictable patterns. That makes them perfect candidates for Guidance in AutoCallFlow.

Each example below is written in the When, If, Then framework format. You can adapt them directly to your store policies, eligibility windows, and messaging.

1) Where’s my order? (WISMO)

WHEN a customer asks about their order status:

• IF tracking information is available, THEN
  • Provide the tracking number and link to the carrier’s tracking page
  • Inform the customer of the expected delivery date
• IF tracking information is unavailable, THEN
  • Inform the customer that the order is being prepared for shipment
  • Provide an estimated shipping date

2) What size should I order?

WHEN a customer inquires about product sizing for [item name]:

• IF the customer asks what size to get, or mentions they’re unsure about sizing, THEN
  • Share the sizing chart or guide
  • Offer recommendations based on common fit feedback (only if your data/policies support it)

3) Can I change my shipping address?

WHEN a customer requests to change their shipping address:

• IF the order has not been fulfilled, THEN
  • Confirm the new address with the customer
  • Update the shipping address in your ecommerce platform (Shopify or your chosen system)
• IF the order has already been fulfilled, THEN
  • Inform the customer that the address cannot be changed
  • Provide options for order interception or return (based on what you actually offer)

4) Can I cancel my order?

WHEN a customer asks to cancel their order:

• IF the order has not been fulfilled, THEN
  • Confirm that the order can be canceled
  • Tell them their refund timeline (example: “5–10 business days”)—use your real policy
• IF the order has already been fulfilled, THEN
  • Inform the customer that the order cannot be canceled
  • Help initiate a return once the item is delivered

5) How do I return an item?

WHEN a customer asks about returning an item:

• IF the return is within the allowed return window of [x] days after the order was received, THEN
  • Provide return instructions and a link to the return portal
  • Inform the customer about the refund process
• IF the return window has expired, THEN
  • Inform the customer that the return period has ended
  • Offer alternative solutions if available

6) Do you have any discount codes?

WHEN a customer inquires about discounts or promo codes:

• IF there is an active promotion for [item name], THEN
  • Share the current discount code and its terms
• IF there are no active promotions for [item name], THEN
  • Inform the customer that there are no current promotions
  • Suggest subscribing to the newsletter or following social media for future promos

7) I want to pause my subscription

WHEN a customer requests to pause their subscription:

• IF the customer has an active subscription, THEN
  • Provide instructions on how to pause the subscription through their account
  • Confirm the pause and inform them of the next billing date

8) When will this item be back in stock?

WHEN a customer asks about product restocking:

• IF a restock date is available, THEN
  • Inform the customer of the expected restock date
• IF the restock date is unknown, THEN
  • Offer to notify the customer when the product is back in stock
  • Suggest similar products

9) Do you ship internationally?

WHEN a customer inquires about international shipping:

• IF international shipping is available, THEN
  • Confirm that international shipping is offered
  • Provide estimated delivery times and any additional fees
• IF international shipping is not available, THEN
  • Inform the customer that shipping is limited to specific regions

Tip: Keep these “scenario playbooks” short and policy-accurate. If your store policies change, update the Guidance immediately.

Troubleshooting: Why Your Guidance Might Not Trigger

If your AutoCallFlow support workflow isn’t following your Guidance—or it’s escalating tickets you expected it to resolve—use this checklist to find the issue quickly.

• Descriptive, easy-to-understand Guidance name: Name your Guidance based on the scenario (e.g., “When a shopper asks about returns”). If names are vague, you’ll also struggle to manage and review them.
• Clear IF and THEN logic: Ensure the Guidance spells out what to do when a condition is met. If the “If” is missing or unclear, the “Then” may never be reached.
• Logic coverage (no gaps): Don’t leave your workflow hanging. Include fallback instructions for all possible variations you expect (eligible vs not eligible, shipped vs not shipped, fulfilled vs unfulfilled, etc.).
• No wall-of-text formatting: Break up Guidance with line breaks, spacing, and headings so the system can scan and follow it correctly.
• Use bullets or numbered steps: Lists reduce ambiguity and make actions easier to execute consistently.
• No unsupported tasks: Avoid instructions that your support workflow can’t perform. For example, don’t include steps that rely on internal actions you haven’t enabled or that don’t exist in your environment.

Quick diagnostic approach: Pick one failing ticket and map it to your Guidance. Then answer: Did it match the WHEN scenario? Did it satisfy the IF conditions? Did it include a complete THEN action list? That’s usually where the problem lives.

Bonus: Use AI to Help Draft Guidance (Without Losing Control)

Writing Guidance from scratch can be time-consuming—especially when you’re translating team knowledge into structured logic. The good news: AI can help draft Guidance that you then review for policy accuracy and completeness.

Here’s how to get practical value while staying in control:

• Start from your most frequent tickets: Choose the top 3–5 ecommerce questions that cause the most back-and-forth.
• Draft first, validate second: Use AI to propose WHEN/IF/THEN blocks, then validate every policy detail (return windows, refund timing, shipping limitations, promo eligibility).
• Adjust for your store specifics: Replace placeholders like [x] days or [item name] with your real values and rules.
• Iterate using real outcomes: If customers still escalate, update the missing conditions or add clearer THEN steps.

Why this works: Your team still owns the knowledge and the policies. AI helps convert them into structured Guidance faster, so you can scale consistency across your ecommerce support operations.