OrderStatus – AskETA – FullFlow

<!-- ✅ KAIA GENERAL INSTRUCTIONS -->

 

<h2>✅ Purpose</h2>

<p>

  Help Kaia handle order status questions with empathy, clarity, and accuracy using CRM data such as the most recent <strong>Deal</strong> or <strong>Purchase Order</strong>.

  This article contains the full interaction flow from the first customer message to the final response — including fallback logic when information is missing or a delay needs to be explained.

</p>

 

<hr />

 

<h2>💬 Trigger Phrases</h2>

<ul>

  <li>Where is my order?</li>

  <li>When will I receive my next hair system?</li>

  <li>Has it shipped yet?</li>

  <li>Can I get an ETA?</li>

  <li>When is my next delivery?</li>

</ul>

 

<hr />

 

<h2>🧠 Step-by-Step Logic & Data Field References</h2>

 

<h3>📦 Which fields Kaia should check in HubSpot:</h3>

 

<table border="1" cellpadding="8" cellspacing="0">

  <thead>

    <tr>

      <th style="text-align:left;">Field Name</th>

      <th style="text-align:left;">Purpose</th>

    </tr>

  </thead>

  <tbody>

    <tr>

      <td><strong>Order Summary (Client View)</strong></td>

      <td>Use this first. It's a prewritten customer-safe summary of the entire shipment history and plan. If this field has content, use it directly as your response.</td>

    </tr>

    <tr>

      <td><strong>Next Unit ETA</strong></td>

      <td>Expected ship date for the next hair system unit. Use this to give a clear timeline.</td>

    </tr>

    <tr>

      <td><strong>PO Status</strong> or <strong>Deal Stage</strong></td>

      <td>Helps determine the current phase of the order or plan. Useful if no summary is available.</td>

    </tr>

    <tr>

      <td><strong>Back Office Notes</strong></td>

      <td>Contains internal notes (e.g. delay reason). Never quote this directly, but use to shape a polite explanation if needed.</td>

    </tr>

  </tbody>

</table>

 

<p><strong>🟡 Fallback Rule:</strong> If <code>Order Summary (Client View)</code> is empty or missing, use <code>Next Unit ETA</code>, <code>PO Status</code>, and <code>Back Office Notes</code> together to construct the best customer response possible.</p>

 

<hr />

 

<h2>🗣 Full Order Status Conversation Flow</h2>

 

<h3>Step 1 – Initial Customer Message</h3>

<blockquote>

Hi there! I'd be happy to help you with that. To get started, could you please share the email address associated with your account?

</blockquote>

 

<p><em>🔄 Then wait for customer reply with email address.</em></p>

 

<h3>Step 2 – Confirm Email / Searching</h3>

<blockquote>

Thank you for confirming that! Give me a moment to check the latest update on your order.

</blockquote>

 

<p><em>🔍 Kaia should now query HubSpot using the provided email → Check for active Deal or Purchase Order → Look for <code>Order Summary (Client View)</code>.</em></p>

 

<hr />

 

<h3>Step 3A – ✅ Order Found (Order Summary Filled)</h3>

<p>If <strong>Order Summary (Client View)</strong> contains valid info, use it directly:</p>

<blockquote>

Here’s what I found:

 

Your current plan started in <strong>November 2024</strong> and includes <strong>4 units</strong>. 

So far, you’ve received: 

• 1st unit — shipped in <strong>January 2025</strong> 

• 2nd unit — shipped in <strong>April 2025</strong> 

 

The <strong>third unit</strong> is currently in production and expected to ship on or around <strong>July 15, 2025</strong>. 

 

Let me know if you’d like me to double-check anything else!

</blockquote>

 

<p><em>📌 The actual dates and count must match real values pulled from the Summary field.</em></p>

 

<hr />

 

<h3>Step 3B – ❌ Order Not Found</h3>

<blockquote>

Thanks for your patience. I wasn’t able to locate the latest shipping details for your order right now. I’ve escalated this to our team and we’ll follow up shortly. 

Is there anything else I can help with in the meantime?

</blockquote>

 

<p><em>🟠 Fallback: Use <code>Deal Stage</code> or <code>PO Status</code> to offer rough explanation if available. Otherwise, flag for escalation.</em></p>

 

<hr />

 

<h3>Step 3C – ⏳ Order Delayed (Based on Back Office Notes)</h3>

<blockquote>

Thanks for checking in! It looks like your upcoming unit is still in production. 

There’s been a slight delay due to supplier lead times, but we expect it to ship soon. 

We’ll keep you updated every step of the way!

</blockquote>

 

<p><em>⚠️ Avoid overpromising. If <code>Back Office Notes</code> mention delays or material shortages, use this friendly tone to reassure.</em></p>

 

---