The shared Inbox: who replies, what's waiting and nothing lost

The customer writes on Tuesday: “Still waiting to hear back.” On Thursday, she writes again. Several people have seen the first message in the store's shared mailbox. Each assumed someone else was answering it.

A shared Inbox needs an owner, a state, and the order context behind the message. OrderPilot connects conversations to quotes, orders, and purchase orders, then shows who is responsible and what needs a reply. The daily routine is to assign the work, answer it accurately, and leave the next action clear.

Start with the record the conversation belongs to

A question about the walnut legs belongs with the quoted sofa. A vendor's revised dispatch date belongs with the PO. When those messages become free-standing emails, staff have to find the sale, identify the version, and reconstruct what the previous person said before they can answer.

The Inbox brings those connected conversations into a shared working place. Portal messages and captured email replies can sit in the same order conversation. Staff can read the customer's question beside the record it concerns, rather than use a subject line as the only clue.

The customer portal guide explains the customer's side. The Inbox is where the team organizes its side of that relationship. It is available on Growth and Professional, with access limited by each staff member's role and record scope.

Know what appears in the Inbox

A conversation can belong to a quote, an order, or a purchase order. Customer messages from the portal and email replies can reach the relevant conversation; email reply capture needs the store's reply-domain setup. Vendor replies can also appear in the shared Inbox while remaining attached to their PO.

Automatic emails alone do not fill the Inbox with a separate piece of reply work for every status update. The working conversation appears when someone replies or staff write a message. That keeps the list focused on exchanges rather than making every routine notification look like an unanswered question.

The app's Inbox entry shows a count so the team can see that there is conversation work to inspect. Read that number in context. A count is a prompt to open the list, not a measure of the seriousness of each question. Before relying on captured email, test an ordinary reply with sample data. Confirm that it appears on the expected record and that an authorized colleague can open it. A shared Inbox cannot help with a vendor response that still reaches only a personal mailbox nobody else can access.

Give every live conversation an owner

The assignee is the person responsible for the next staff action. Order conversations can start with the order's assigned staff member, and PO conversations with the PO's creator. Treat those defaults as a starting point and reassign when the work belongs elsewhere.

Assignment should follow the task. An associate can handle a fabric clarification, while purchasing handles a vendor acknowledgment and the delivery coordinator handles a handover question. The customer should not have to identify the right department before the store takes responsibility.

Only staff who can reply and can reach the underlying record can be assigned. If the person you intend to use is unavailable as an assignee, review their actual access instead of treating the restriction as a problem with the customer's message.

Several conversations can be reassigned together. That is useful for shift cover and planned absences, provided the new owner knows which promises are waiting. Bulk assignment transfers the work; it does not summarize the history for the person receiving it. A conversation owner and a salesperson's sales credit are different responsibilities. Passing a question to someone able to answer it should not require pretending they made the original sale. Keep ownership of the reply clear while preserving the order's separate attribution.

Read views as different questions about the work

The built-in views make it possible to inspect the same work from different angles. Use the view that matches the question you are asking, then read the record before making a decision.

Filters such as Unread, Awaiting reply, Overdue, record type, and assignee narrow the list further. Conversations needing a reply receive priority in the working list. Before deciding a message has disappeared, inspect the active view and filters.

Unread and Needs reply are not the same thing. A message may have been read without receiving an answer. Waiting and Closed are different too: one expects further progress, while the other says the present exchange is resolved. Those distinctions keep “someone saw it” from becoming the end of the process.

Let replies change the state, then read what still needs doing

A staff reply moves a conversation to Waiting. A customer reply brings it back into active work. That gives the team a useful starting point without asking every employee to maintain a separate personal list.

The state still needs human interpretation. If staff say they will ask the vendor and return with an answer, the store has made a follow-up commitment even after sending that first reply. Record the promise and keep an owner for it. A waiting conversation should not disappear from your attention merely because the customer has nothing further to add.

Close an exchange when the current question is resolved. The furniture order can continue through production while its answered fabric question is closed. Equally, an order can be delivered while a conversation about a missing cushion remains open.

Use bulk close for a genuinely resolved set after checking the selection. Do not use it to make the count look smaller before a meeting. A clean Inbox is a useful result of completed work, not a substitute for it.

Set a reply goal the team can use

OrderPilot's default reply goal is four hours, and the setting accepts a goal from one to 168 hours. An unanswered recognized inbound message that passes the goal is flagged Overdue while the conversation remains unclosed. The clock is an attention signal for staff.

Choose a goal around actual coverage and the kinds of decisions customers need. A store with continuous desk coverage can work differently from a showroom where the owner handles messages between appointments. Do not announce a response promise the schedule cannot support.

The goal uses elapsed hours, so consider evenings and closed days when interpreting the flag. An overnight message can cross the goal before the store opens. Keep the public explanation of your response hours clear and use morning triage to address the waiting work.

A quick acknowledgment can be helpful if the final answer requires a vendor. Make it useful: identify what you are checking and when the customer will hear again. A friendly sentence without a next step can leave the same uncertainty under a new timestamp.

Staff alerts can draw attention to unread customer messages, and customer reminders can bring them back to an unseen store reply. These support the workflow; they do not replace the assigned person's responsibility to read the question and follow through.

Use quick replies as a starting point

The Inbox supports up to twenty quick replies. They can insert the customer's first name and the record number into text that staff can review and edit before sending. Keep the library small enough that each reply has a clear purpose. Good candidates are acknowledgments, requests for a needed measurement, an explanation of how to send a photo, or a link back to the order. Avoid saving a firm delivery date or a promise of compensation into reusable wording.

Write the quick reply so its next step is specific. “I've received your question about the finish and am checking the vendor's acknowledgment” is a useful beginning when that is the actual task. Add the real next contact date before sending.

Review inserted names and numbers as part of the message. A quick reply is still correspondence from the store, and the final text should make sense on this order. The button saves typing; it does not read the customer's question for you.

Keep internal notes different from customer replies

Internal notes are for staff-only context. Use them to explain a decision, record the question still waiting on the vendor, or hand the conversation to a colleague. Keep the customer-facing reply clear and complete on its own. A useful note contains the current fact and next action: “Vendor confirmed the chair finish; table dispatch date still outstanding; purchasing to follow up tomorrow.” Avoid commentary about the customer's personality. The person covering the desk needs the work, not an opinion.

Put enduring commercial decisions on the order as well as explaining them in the conversation. An accepted configuration change belongs in the actual order record. A note saying “customer wants oak” is not the same as an approved, applied change.

The conversation guide explains attachments and Seen indicators. Use those to support the exchange while keeping acceptance and payment decisions in their proper order workflows.

Use the details panel to act with context

The details panel keeps the quote or order beside the conversation. Depending on the record and the staff member's permissions, actions can include sending a payment request, resending a quote, or recording a payment. Read the current order before using those actions. A customer asking about a balance may have just paid through another route. A request for “the quote again” may refer to a version that has since changed. The nearby record helps staff respond to the current facts.

Payment actions follow the same plan, record, and permission rules as they do on the order page. The Inbox is another place to reach the action, not a separate payment policy. Confirm the amount and purpose in the message the customer receives.

For a requested change, the review drawer helps staff assess the exact item or detail concerned. Review, accept or decline, and apply the supported change through the record. Then use Send updated quote when the revised offer is ready for the customer.

The change-request guide covers that decision. A message saying “certainly” should not get ahead of vendor feasibility, the revised price, or any re-signing needed.

Handle a reply from a different address carefully

A message from an address not recognized on the record is flagged as not on file. Staff should not treat that flag as proof that the message is from the customer, or assume that a different address is automatically an authorized designer or family member.

The usual customer reply destination remains the address on file, and flagged message text is not carried into later email quotes as verified conversation content. Resolve the identity and contact question through the store's normal process before discussing private order details with a different person.

A common benign case is a customer replying from a work address after receiving the original message at home. Confirm that relationship and keep the contact information accurate. The practical aim is to help the real customer without letting an unexpected sender redirect the conversation.

Vendor correspondence has its own sender context, including recognized vendor-domain handling where supported. Purchasing should read the sender indication and the PO history rather than assuming every message bearing a familiar display name is the usual contact.

Give staff the right scope, not just the right view

Roles and record scope determine which conversations a person can reach. A salesperson can be limited to the records their role permits, while the operations team can have broader access for the locations it covers. The Inbox respects those boundaries.

Mine is a work view based on assignment; it is not the privacy control. All means all conversations the person is permitted to see, not every customer in the company. Use roles to establish access, then use assignment and views to distribute work within it.

Review scope before asking a backup to cover another location. They may be able to see the Inbox but not open a particular PO or reply on its behalf. Test the cover arrangement on representative records while there is time to correct access.

The order-desk coverage guide gives the handover checklist. When the usual person returns, transfer live work back deliberately and leave the history where both people can find it.

Follow a missed-date question through the Inbox

Consider an illustrative sofa order with a matching chair. On Tuesday morning, the customer asks whether both pieces will arrive together. The conversation enters reply work, and the order-desk colleague takes ownership rather than leaving it under a shared address.

The colleague reads the order and sees that the chair has arrived while the sofa's PO still has an expected dispatch window. They reply that they are confirming the sofa's timing, explain which piece is already at the store, and give the customer a specific next update.

Purchasing asks the vendor through the PO conversation. An internal note on the customer conversation records who is checking and when the promised response is due. The first reply can move the conversation to Waiting, but the note and assigned owner preserve the store's outstanding commitment.

When the vendor answers, the desk gives the customer the confirmed information and any practical choice about collection or delivery. If the customer chooses to wait for both pieces, staff record that arrangement. If the answer changes the original expectation, the message explains the change rather than hiding it in a status label.

Once the question and immediate arrangement are settled, close the exchange. The order remains active while the sofa is being made. A later customer reply can return the conversation to active work with its earlier context intact.

The difference from the opening example is visible: someone owned the next reply, the state described the exchange, and the order supplied the facts. The store did not need a more persuasive apology for Thursday. It needed a completed Tuesday handoff.

Run a short team routine around the views

At opening, assign Unassigned conversations, inspect Overdue, and deal with messages whose timing affects today's customer commitments. Review Waiting for follow-ups the store promised, especially vendor-dependent answers. Those checks should produce named actions rather than another group discussion about who might know.

During the day, the owner of each conversation sends the reply or hands it to a specific colleague with context. At shift change, review promises due before the next shift and transfer ownership where necessary. Before closing an exchange, confirm the current question has actually been resolved.

Use this practical division:

Aim for no unexplained overdue or unassigned work, rather than forcing every active conversation to Closed. A waiting vendor answer can be legitimate work in progress. What matters is that a colleague can identify who is following it and when the customer will next hear from the store.

How to do this in OrderPilot

Configure reply capture so supported email replies reach their order or PO. In Settings › Messages & notifications, review the reply goal and quick replies. Give the team the relevant record access and reply rights, then test a sample customer reply, a vendor reply, assignment, and a shift handover. Agree how the team will use Waiting, what earns a Closed state, and where promised follow-up dates are recorded. Show a backup how to open the order behind a message and read its current payment, configuration, and purchasing information.

For incoming website work, follow the online-request-to-priced-quote guide. Start the same ownership habit at the first question, before the request becomes a signed sale. A shared Inbox earns its name when the work is visible to the team and clearly owned by someone.