Text or email? Choosing the channel for each order update

“Your sofa delivery is Thursday morning. Please use your order conversation if the arrangement needs to change.” That is useful information at a useful moment. “Your order status has been updated,” arriving late at night, gives the customer a small mystery to solve.

Choose text or email according to the customer's next action. Email is the lasting record for detail and documents. A text should draw attention to something that matters now. The sample wording here illustrates a communication standard; OrderPilot's own status texts use fixed templates.

Put the agreement and detail in email

Email is the natural home for the quote, revised quote, signed copy, invoice, and payment request. The customer can return to the specification, compare the proposed change, or forward the document to the person helping with the room.

A detailed production update belongs there too. If the maker has changed the fabric availability, explain the affected piece, timing, alternatives, and response needed in a message that can carry the whole answer. A text can point the customer toward that explanation when the decision is time-sensitive.

Name the event in the subject and the first sentence. “Your dining chairs have arrived; the table is still in production” helps more than “Order update.” Keep the piece and its state explicit so the customer doesn't mistake a partial arrival for a complete delivery.

The order-stage message guide gives the messages a consistent purpose. The customer should be able to identify what changed and whether they need to do anything without translating your internal workflow.

Reserve text for a useful interruption

Text suits an update that changes the customer's immediate plans or asks for a clear action. A pickup-ready notice, a supported payment reminder, or attention to a delay affecting an imminent delivery can deserve the shorter channel.

The message should identify the store and make the next step obvious. Use a clear link when the customer needs to review, sign, pay, or answer in the order conversation. Keep the explanation in the linked record or email when the detail is too long for the text.

Don't invite a text reply unless the store's sending service and team actually receive and handle those replies. In OrderPilot, use the portal or the configured email conversation for a reliable discussion route; a status text shouldn't promise an SMS chat workflow that hasn't been established.

Good timing is part of good writing. Send during the customer's reasonable waking and business hours, and make sure someone can answer the next question. A beautifully worded pickup notice is less useful when the showroom has just closed for the weekend.

Build a channel map around customer decisions

Use this table as a starting point for the store's communication plan. It recommends channels for the job; it isn't a list of custom text templates available in OrderPilot.

An internal step deserves a message only when it changes the customer's understanding. Moving a file from one desk to another is office news. The sofa has not become more delivered because someone changed its tag.

Where the delivery company owns the appointment, agree who sends the window and who handles changes. OrderPilot's order record can carry the communication and progress; the delivery partner must supply an actual arrival update.

Choose the status messages in OrderPilot

OrderPilot lets the store choose whether a status sends email, SMS, or both, subject to enabled channels and setup. Branded email uses the store's configured sender domain. The status should represent something the customer understands before its message goes out. SMS uses the ready-made templates exposed by the app, including quote, invoice, and quote follow-up messages. Staff cannot edit those texts or compose one-off SMS from an order. Review the available template against the event before enabling it; the personal explanation can be written in the order email. Avoid assigning an unrelated message simply because a status has an SMS switch. If the available text doesn't express a pickup-ready event accurately, send the clear pickup email and use the store's established customer contact process. The aim is an accurate message, not an occupied checkbox.

Test the configured notification with sample data. Read what the customer receives, including the store identity and destination link. Then review a partial-arrival example as well as a complete order, since the customer's next action differs.

Keep reminders distinct from status updates

A reminder follows a quiet quote; a status update reports an event. OrderPilot's optional automatic quote reminder sends at most one email for a quote still in Draft, using the chosen template and sending window. Use the reminder to reopen a decision, not to manufacture urgency. The customer may still be comparing a fabric with their curtains. A helpful reply route does more work than repeatedly announcing that the quote exists.

The first follow-up after a showroom visit covers the personal sales conversation. Keep that separate from automatic order notifications so the customer doesn't receive overlapping messages about the same unfinished choice.

Ask about preferences and permission separately

A customer can prefer email for documents and text for practical notices. Ask which updates they want and record the answer in a custom customer field where profiles are enabled. That field is a staff note; it doesn't automatically filter which notifications OrderPilot sends. Staff must use the actual sending controls and consent process. A phone number supplied for delivery isn't a reason to add the customer to every promotional message.

Use the texting consent guide for the rules and records behind permission. Keep sale announcements out of transactional updates. A channel preference describes how the customer would like to hear from the store; consent describes what the store is permitted to send.

Set expectations about cost and replies

OrderPilot's SMS delivery uses a Twilio-based setup. Messaging charges depend on the sending arrangement, destination, message segments, and carrier or registration charges. Twilio's pricing information explains the provider components; obtain the store's actual billing terms during setup rather than assuming texts are included or unlimited.

Before enabling customer texts, establish who owns replies, failed sends, and opt-outs. A delivery notification with nowhere to answer can create a second phone call instead of avoiding one. Direct customers to the route the team monitors.

At signing, ask how the customer prefers to receive updates and show where the ongoing conversation lives. Then keep the detailed record in the customer portal, where the next message has somewhere useful to lead.

Sources

1. SMS pricing in the United States — Twilio; provider pricing structure, with no rate quoted.