Customer conversations with photos, PDFs and Seen indicators

The stairwell photo went to the salesperson's personal email. Weeks later, the delivery crew needs to see the landing, the salesperson is on vacation, and the office is searching for an attachment described as “the narrow bit.” The customer already supplied the answer. The store simply can't find it.

Keep customer conversations with the order. OrderPilot brings portal messages, captured email replies, photos, and PDFs into the record your team uses to sell and fulfill the furniture. The next person can pick up the conversation without asking the customer to start again.

Give the conversation an order to belong to

A conversation attached to the order carries context that a personal inbox cannot reliably supply. The quoted sofa, chosen fabric, delivery arrangement, and previous answers are close at hand. Staff don't need to infer the order from a subject line or a customer's first name.

Order emails use threading information so the customer's mail app can group the exchange, although the mail app controls its own display. With reply capture turned on and its domain setup completed, customer email replies join the record. Customers can simply reply to the email; they don't have to learn another habit to ask a question.

Without reply capture, direct the customer to the portal conversation. A configured reply address and a working portal are distinct routes into the exchange. Test the route you tell customers to use before making it part of the showroom script.

The Conversation action opens the thread from the quote or order. Vendor correspondence has its own conversation on the PO. Keep those audiences distinct: a vendor's production question and a customer's living-room photo can concern the same sofa without belonging in the same outward message.

Send the file with the explanation

A photo is most useful when the message says what the reader should notice. “This is the turn above the entrance; the radiator stays in place” gives the delivery reviewer a question to assess. A photograph without context can show a lovely hallway while hiding the obstacle that matters.

Customers and staff can attach JPEG, PNG, and WebP images and PDFs in the conversation. The customer conversation allows up to five files per message, each up to 10 MB. Those are its own upload limits, not the separate rules for PO attachments.

A phone photo saved in another format needs conversion to a supported image before sending if the picker doesn't provide it. A revised drawing can travel as a PDF, with a short message identifying the revision. Don't rely on a filename such as final-final to explain which dimensions are now agreed. Keep the explanation close to the attachment:

• A doorway photo: identify the doorway and the measurement it supports.
• A swatch photo: name the fabric and explain the lighting or comparison.
• A drawing: identify the piece and revision being discussed.
• A specification sheet: say whether it is a reference or the proposed order specification.

A file is evidence for a conversation, not automatic approval. If a drawing changes a customer-facing specification, use the proper quote revision and agreement process. If a photograph raises a fit question, get the needed measurements or delivery assessment rather than promising access from the image alone.

Read Seen as a signal, not a decision

Seen tells staff that a portal message has been seen in the conversation. Viewing now indicates that the customer is on their portal page. Email delivery and open activity describe another part of the exchange. Each signal helps the team choose a sensible next action. None of those signals means the customer agreed to a change, accepted a delay, or understood a drawing. Ask for the decision the job requires. “Please confirm the left-hand chaise shown in the revised quote” gives the customer something definite to answer; “I can see you opened it” doesn't.

Email opens are especially easy to overread. They are activity signals, not proof of comprehension or a substitute for a signature. Use the send-log guide to distinguish sending, delivery, and opening before describing the record to a colleague or customer. When a store reply remains unseen, an email alert can bring the customer back to the conversation. An unread customer message can also trigger a staff alert. Those alerts support the handoff, but the team still needs a person responsible for answering.

Give unread messages a responsible person

Staff alerts follow the assigned salesperson where there is one, then the people credited on the order, then the store's default copy addresses, with access checks on who can answer. The practical setup question is whether those destinations reach someone who is working.

Before a salesperson goes away, review their waiting conversations and hand off responsibility. The colleague covering should be able to open the record, see unresolved questions, and understand what was promised. A vacation auto-reply doesn't hand over the sofa.

Use the shared Inbox for ownership and follow-up. Staff should distinguish work that needs their answer from work waiting on a customer or vendor. The inbox status is useful only when the next move is understood.

The customer can close the chat panel, but that doesn't settle the store's open work. Staff answer and close questions through the Inbox. Tell customers to reply when the issue is resolved rather than suggesting that dismissing a panel cancels a request or approves the quote.

Choose chat, formal email, or an internal note

Use the conversation for a quick explanation, a file, or a written recap. Use the order's formal email tools for the quote, revised quote, payment request, and signature request, where the message has a specific document or action to carry.

Internal notes are for staff-only context. A delivery reviewer might note that the customer has sent the stairwell photograph and that a measurement is still needed. The outward reply should tell the customer which measurement to provide and who will review it. Keep card numbers out of the conversation. Send the appropriate payment link instead. Keep private staff discussion out of customer replies too; read the audience and the message before sending, especially when switching between internal notes and outward communication.

For a question about a specific finish or fee, use the pinned review tools. They attach the question to its target and preserve the context more precisely than a general “about the chair” message.

Keep the right conversation with the right customer

Reply capture checks the sender before adding an email to the customer conversation. Replies from unrecognized addresses are flagged rather than automatically treated as the customer's authorized exchange. That protects a forwarded message from quietly becoming a new participant.

Changing the order's customer also changes what that customer can see. The new customer doesn't inherit the earlier customer's conversation. Staff should still treat reassignment as a real change of audience and review any outward documents before sending them.

Say an illustrative sofa order includes the customer's stairwell photo and a later PDF drawing. The covering associate opens the order, reads the photo's explanation, sees the drawing discussion, and asks for the missing measurement. The customer supplies only the missing detail, not the whole history again.

End each phone call with a short record while the conversation is fresh. “Customer will send the landing width; delivery review remains open” is enough to preserve the next step. Then send the customer the promised recap or request.

The order becomes useful to the colleague who didn't hear the call. Set up that handoff with the shared Inbox working guide.