The 2 a.m. inquiry from Stuttgart (2026)

Bottom line:

2 a.m. in Germany is a working hour for a Stuttgart buyer. For a China factory that only staffs days, it is “marked read, drawing unseen.”
An auto-ack is not a substantive first response. Nights triage and confirm receipt. Price, tooling, and DDP leave through a named owner.
Accio may staff “extract + draft ack.” It may not staff “lock and send.” A person holds the send key.

The scene is ordinary: a Stuttgart buyer sends a German inquiry before a Monday meeting, with a 14 MB STEP. The China storefront shows read—someone left a tab open, or the auto-ack already fired. The process engineer who can open the model arrives at 09:30. The buyer refreshes before local lunch and sees “Dear customer, thanks for your inquiry.” They move to the next Verified shop.

The failure is not “Germans are impatient.” It is treating time zones as overtime virtue instead of a duty roster. How to write a four-factor reply is on how to answer an inquiry. When inquiries do not convert, use the stop-loss playbook. This page is only the night cut: who speaks, how long, and where they must stop.

1. Split “first response” into two grades

Platform response time and the buyer’s “someone saw my drawing” are not the same meter. Auto-acks, welcome macros, and unpriced Accio letters are grade one: received. Grade two is a substantive reply: seen fields, unseen fields, next time, named owner.

One SLA forces nights to invent prices and days to clean up. Two grades make the night pass mark obvious: confirm the file name within minutes and name a Beijing-time hour for process comment. DDP Hamburg is not due that night.

2. Night triage: which sentences are allowed

Pin the table at the top of the duty note. Veterans and new hires share one sheet.

Inbound	Night may do now	Night must stop	Day’s first hour
Drawing / STEP / PDF	Confirm file name, size, pages; list dimensions that need process	“Fully feasible,” “tolerance is fine”	Process reviews: make / change drawing / sample
Formal RFQ	Pull official detail fields; mark unseen	Fill target price or lead time the API did not return	Four-part draft via the RFQ pack
Catalogue price only	Return the published band and a validity date	Private discounts or MOQ edits to win the thread	Lock price after stock and tooling check
DDP / certificates / audit	“Day shift will check clause and certificate numbers”	Promise a DDP total or “we hold every certificate”	Match the wall and the contract

Plant rule, one sentence: without price authority, nights send received, not a full quote. Name three people. Do not write “the export department.”

3. Keep the master clock on Asia/Shanghai

The duty master column stays Asia/Shanghai. If a German colleague needs local time, add a second column. Do not edit the master. Edited masters drift the window, the weekly report, and any service review.

Buyer local	Typical send window	Beijing time	Minimum staffing
Germany / CET	Mon–Fri 08:00–11:00	15:00–18:00 (DST moves this by an hour)	Keep a drawing seat at the end of day shift; nights only confirm received
United Kingdom	08:00–10:30	16:00–18:30	Same; mark the DST switch week
US Eastern	09:00–12:00	21:00–24:00 next calendar day	Night received; quotes next morning
US Pacific	09:00–12:00	00:00–03:00 next calendar day	Heavier on auto-triage + first morning hour

Offsets move with DST. Use the official table for that year; do not treat the grid as a perpetual calendar. Put a red line on the duty note in switch weeks so no one recites “Germany is six hours behind” from memory.

4. What Accio may do that night—and must not

Accio is good at pulling material, tolerance, and quantity into a seen/unseen table, and at drafting an eight-line received note. It is not good at emitting “DDP Hamburg 28 days, $4.85” when lead-time master data is missing. Once sent, that sentence is your promise, not a model hallucination.

How to lock facts in a skill pack is on the RFQ quotation pack. If a veteran refuses to hand the send key to a robot, they are right. Handover is the shared inbox and the scripts, not the quote right—see don’t make the veteran fall in love with Accio.

5. Day shift’s first hour: queue by arrival, not by relationship

The morning process owner opens three columns the night left: arrival time, file name, unseen fields. Work arrival order. Familiar accounts may jump the queue only if the jump is written in the duty log; otherwise nights will mark everything urgent.

The first substantive day-shift reply must hit the window the night promised. If process comment was due 09:30 and the morning meeting overran, send “slipping to 10:00, line meeting” instead of letting the buyer refresh. Write lead time as working days / make-to-order per lead-time promises. Do not “make up” the night gap by writing in stock.

6. Three numbers in the weekly review

Did “received” land inside the promised window (indicative: 15 minutes on Central-European working mornings)?
How many full night quotes did day shift rewrite or retract?
How many drawing changes or withdrawals started from “fully feasible” written unread?

If the second number rises, nights are quoting beyond authority—take the send key back before you hire. If the third rises, the phrase is still in the macros. If nobody can open a drawing, return to move the shop floor first. Night software cannot hide a missing process seat.

Questions teams actually ask

Does an auto-acknowledgement count as meeting the response SLA?

Not as a commercial response. An auto-ack proves the system received a message. It does not prove a person saw the drawing, confirmed lead time, or named a next step. Writing ack time as first response misaligns both buyer feel and service metrics. Split “received” and “substantive reply.”

May a night assistant send a unit price?

Not without price authority. Night default is triage: confirm receipt, list unseen fields, give a day-shift window. Unit price, tooling, and DDP totals go out only after a named day-shift owner confirms. Accio may draft; a person sends.

The STEP file arrived in German. Must we send a long German letter the same night?

Send a short note in their language: file name received, page or model size, process opinion by a stated Beijing-time hour. Do not write “fully feasible” unread. Long letters and quotes wait for day shift so nights do not invent process.

Can Accio cover the night shift alone?

It can cover “confirm received + extract fields.” It cannot cover “lock and send price.” Skill packs help pull drawing fields and draft a native ack. They must not invent a DDP Hamburg price when the fact lock is empty. The send key stays human.

If weekend EU inquiries pile until Monday, will the platform score us poorly?

Buyer perception and some service indicators can suffer. Keep a weekend “received” duty rather than weekend misquotes. On Monday’s first hour, queue by arrival time, not by which salesperson likes the name.

We have inquiries but no orders. Is the night shift too slow?

Slow nights are one cause, not all of them. Conversion also depends on triage, sample stop-loss, and quote validity. Nights exist so you do not lose first response. Conversion stop-loss is a different page; do not pile every failure on the one person awake.

The 2 a.m. inquiry from Stuttgart