Place a voice-requested coffee order after confirming its total

Why use this

1. A spoken coffee request can leave important details implicit, including size, milk choice, pickup store and whether a remembered order still fits today's request. In a vehicle, extra clarification can also create distraction if it is handled at the wrong moment.

2. A concise order preview could turn those ambiguities into a clear confirmation of the merchant, items, total and pickup method. The owner could correct mistakes before a purchase rather than discovering them after the account has been charged.

Why an agent / simpler alternative

Useful judgment

Interpret a spoken request and identify missing modifiers without silently substituting remembered preferences.

Simpler alternative

Use the merchant's saved-order button when the drink and pickup location are already correct.

Unsuitable when

Interaction would distract a driver or the user cannot review the exact purchase details.

Proposed inputs

1. Name

   Order request

   Owner

   Customer

   Minimum scope

   Drink, size, modifiers and intended pickup method

   Quality check

   Flag ambiguous speech and unavailable-item assumptions.

2. Name

   Checkout preview

   Owner

   Customer

   Minimum scope

   Merchant location, itemization, total and currency

   Quality check

   Verify the selected store and distinguish estimate from final total.

Access and setup — proposed or unknown

Proposed minimum

1. Fictional order transcript and mock checkout summary; no vehicle or merchant access.

Compatibility unknowns

1. Unknown: current runtime, vehicle interface, merchant access and ordering eligibility.

External actions requiring approval

1. Account access and the exact purchase, including merchant, location, items, total and pickup method.

Expected deliverable and review checks

Proposed artifact

Order confirmation prompt with unresolved fields and a conditional order-status record.

Critical checks

1. Confirmation refers to the exact checkout version.

2. No order is labelled placed without a definitive merchant response.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   The selected pickup store differs from the named location.

   Why it matters

   A correct drink could be purchased at the wrong place.

   Proposed response

   Hold the preview and ask the customer to confirm the intended store.

2. Signal

   A modifier changes the total after confirmation.

   Why it matters

   The approved amount no longer matches the purchase.

   Proposed response

   Rebuild the itemized preview and obtain approval for the changed total.

Effort and cost — unknown

Setup work

1. Define required order fields and a safe interaction setting.

Ongoing review

1. Check store, modifiers and final purchase details.

Unknowns

1. Unknown: current menu prices, availability, fees and order-status reliability.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional voice request names one store while a mock cart selects another and adds a priced modifier.

Acceptance checks

1. Flag both location and total changes.

2. Produce a fresh confirmation prompt without placing an order.

Stop conditions

1. Live checkout, vehicle interaction or a moving-driver conversation is required.

Limits

1. The proposed confirmation checklist is not verified merchant or vehicle interface behavior.