Keep customers informed while their furniture is being made

Week six of a twelve-week build can be quiet in the store and rather busy in the customer's head. The deposit is paid, the old sofa has gone, and nothing has arrived since the confirmation email. In this example, production may be on schedule. The customer has no way to tell.

Plan updates around meaningful milestones, with a personal check-in when the wait between them becomes long. Tell the customer what happened, what it means for their pieces, and when they will hear from you again. OrderPilot's status emails, order conversation, and portal give that plan a shared home.

Answer the questions behind the wait

A production update should answer whether the order is on track, what timing is known, what happens next, whether the customer needs to act, and who can answer a question. Not every message needs a long paragraph, but it should reduce a real uncertainty.

Start with a clear confirmation. Recap the actual fabric, finish, size, and delivery arrangement, together with the agreed expected window. If the customer later wonders which legs they chose, the record should answer before a salesperson has to remember the swatch session.

Choose milestones that describe real progress

Build the plan around events your team can verify. A PO sent is a purchasing milestone. A vendor-confirmed production stage is a different milestone. Arrival at your warehouse is not yet delivery to the customer.

The order-update templates provide wording to adapt. Use them after deciding what each stage means in your store. Good prose cannot rescue an inaccurate milestone.

Add a check-in when a stage runs long

Milestone updates should be the foundation, with a planned human review between them. As a suggested routine, check an order that has had no meaningful news for three weeks. Adjust that interval to the vendor program and the expectation you gave the customer.

The check-in should contain an actual review of the order. Read the vendor commitment, confirm whether anything has changed, and set the next contact. If the facts remain the same, say so plainly. “The vendor has confirmed the production window remains unchanged; we'll update you after the next review” is useful when the confirmation exists.

Avoid empty updates sent merely because a calendar reminder fired. The customer does not need a weekly announcement that the sofa continues to be a sofa. They need confidence that someone is paying attention to the particular order.

A promised date should not pass in silence. When the plan changes, send the delay message before the customer has to discover the problem. If a new date is not known, say what you are checking and when you will report back.

Make the portal the reference point

The customer portal gives customers a place to return through the store's email link without creating a storefront account. They can see the public order stage, the progress of individual pieces, documents, the balance and available payment action, and the conversation. For a multi-piece order, name each affected piece in the message and let the item progress support it. “Your chair has arrived; the sofa is still being made” is a clearer answer than one broad readiness label. Explain whether the customer can collect the chair or whether the store is planning a combined delivery.

Introduce the link while the customer is still engaged with the sale. Show where questions belong and explain that the page remains useful after signing. For trade work, the designer-status guide considers the communication around the same customer record.

Decide what to automate and what to say personally

Automate routine messages when the recorded event reliably supports the wording. Send a personal update when the customer has a particular deadline, a requested change, a delay, or a question the standard message does not answer.

The salesperson can remain involved without personally composing every receipt update. A tailored note at a meaningful point can connect the showroom relationship to the production wait. The order desk can own vendor follow-up while keeping the conversation visible to the person who made the sale.

There is no universal point at which updates become too frequent. Look at whether messages add information, repeat the same stage, or ask the customer to act unnecessarily. If several internal steps happen close together, choose the public milestone worth communicating rather than sending each technical change.

If a customer prefers phone calls, record that preference and assign the calls. Follow a material conversation with a concise written recap where appropriate so the agreed details remain available. Offering a portal should make information easier to reach, not make a phone-preferring customer feel unwelcome.

Run the plan in OrderPilot

Choose the statuses that should email the customer in Settings › Messages & notifications. Keep detailed staff steps inside plain customer-facing groups, so the customer reads an understandable stage rather than an internal shorthand. Use the store's email theme and editor to keep the message recognizable. The opening line should explain the event; the next line should explain the customer's next step or the store's next contact. A branded header is useful, but the paragraph underneath does the work. Email updates are available across plans; the portal and SMS are on Growth or Professional, and workflow automation is on Professional. Where SMS is enabled for the store, status texts use fixed templates, so tailored production explanations belong in email.

With reply capture configured, customer email replies join the order conversation. Staff can also answer portal questions through the order or shared Inbox. Keep one owner for the next response so a message that several people can see does not become one nobody answers.

Put useful answers in production emails

Explain what In production means for the program: the vendor has confirmed the relevant production stage, rather than the store merely sending a PO. Use the vendor's actual timing for stage lengths; a general estimate should not overwrite the customer's particular fabric lead time.

Explain how handover is arranged. If the coordinator calls after receiving and inspection, say that. State when the balance is due under the agreement and how the customer will receive the request. If they want to change something, direct them to the order conversation or change-request process before suggesting the maker can still accommodate it.

These answers can sit in a short reusable section. Keep them consistent with the terms the customer accepted. A production email is a useful reference, not a place to introduce a new payment or delivery policy.

Leave the order desk a one-page update plan

For each milestone, record the evidence, message owner, channel, and next expected contact. Use this compact planning sheet:

Use the status-call diagnostic to see which questions your plan still leaves unanswered. Then improve the message at that point in the journey, while keeping the customer connected to the same order.