When an online request lands: from the Inbox to a priced quote

Friday evening: a request arrives for a pair of Madison sofas, matching lamps, and a question about the deeper seat clearing a narrow doorway. By opening time, several people have seen the notification. Nobody has yet made the reply their job.

A useful routine gives the request an owner, keeps the selected pieces intact, and moves it toward either a priced quote or a specific answer about what is still needed. Aim for a useful reply during the staffed day. Don't turn an unconfirmed vendor detail into a promise just to meet a reply target.

Who owns the new request?

Assign one person to lead the conversation, with a clear covering arrangement for absences. Seeing a request in the shared Inbox is not the same as owning its next action.

Begin with the Inbox's views for work needing a reply, assigned work, unassigned conversations, and waiting items. Assign the sample sofa request, then leave an internal note when another colleague needs to investigate a detail.

Before replying, read the existing conversation and assignment. That simple habit helps two associates avoid sending different answers. If ownership changes, make the handoff explicit and include the unanswered question. The shared-Inbox guide covers the team's daily organization. The online-selling guide explains the website route that brings the request here.

What should the associate check first?

Read the selected configuration and the customer's question before opening a price conversation. A request that includes the choices should not receive a reply asking the customer to select them again.

For the running example, check the named fabric, seat depth, arm, leg finish, and quantities. Identify whether the doorway question concerns the complete sofa, removable parts, or the access route beyond the door.

Treat the customer's measurement as information to review, not automatic proof of fit. Ask for the needed dimensions or a clearer explanation before promising delivery access. If a vendor needs to confirm how the piece travels, make that a named follow-up.

The complete-request guide helps improve what arrives. Here the associate's job is to use that information and identify the remaining decision.

How does the request become a priced quote?

Prepare the offer on the quote record, keeping the chosen products and the charges understandable. Add the agreed delivery service or named fee, and use any authorized discount according to the store's policy.

Say the illustrative sofas cost $3,000 each, the two lamps total $200, and the agreed delivery charge is $300. That gives a $6,500 subtotal before tax. The quote should show those parts clearly, with the selected fabric and depth on the sofa lines.

If design work is being sold, add the relevant service line instead of burying it in a furniture description. A design fee should be recognizable as a service the customer agreed to buy. Quote-only pricing remains private until staff send the priced quote. Review the full offer before releasing it so the customer receives a coherent amount rather than a collection of provisional entries.

How do questions and photographs stay in context?

Use the customer conversation to connect the question to the order and the piece. The portal supports photos and PDFs, and customers can raise questions or request changes against the relevant part of the quote.

For the doorway question, ask for the specific information that would help the review. A room photograph with the doorway out of frame will not settle the access issue, however lovely the room is.

Keep the question open until someone answers it. An internal note can explain that the vendor is checking removable components, while the customer-facing reply explains what the team is doing and when it will update them. This preserves the difference between a customer request, staff review, and an agreed change. No one should need to infer approval from an attachment arriving.

What if the customer changes the fabric?

Review the requested change, establish its consequences, and apply the agreed result to the quote. A portal request does not silently rewrite the sale.

If the customer changes the example oatmeal weave to another fabric, check the resulting price and availability. Explain the difference in the updated offer. Where a customer-facing edit affects an existing signature, OrderPilot asks for a new signature while keeping the earlier signed record.

Use a concise change summary so the customer can find what is different without comparing every line. The revised-quote guide shows how to make that message useful.

An unchanged product name is not proof of an unchanged order. The same Madison sofa can mean a different price, fabric, and lead time after the customer's revision.

How does the customer receive the quote?

Send the prepared quote by email with the supported branded PDF and link, then direct the customer to the review action. The portal gives them a place to examine the quote, continue the conversation, sign when ready, and use the available payment action. Where the store has SMS configured, status texts use the supplied templates; they are not a channel for a custom one-off explanation. Use the email or portal conversation for the specific discussion.

Review open information as a sign that the customer reached the material, not proof that they understood or approved it. The next action still depends on the customer's response.

What if the customer goes quiet?

Choose a follow-up that addresses the decision still open. If the customer was comparing fabrics, ask whether the sample resolved the choice. If the only remaining action is approval, point them back to the current quote.

OrderPilot's optional automatic reminder sends at most once per quote and only while it remains in Draft. A sent quote in another status should have an appropriate staff follow-up rather than being assumed to receive a reminder.

The quiet-quote reminder guide explains that distinction. Keep any manual message specific and useful instead of sending the same general nudge through several channels.

What if the vendor prevents a same-day price?

Send a useful holding reply with the exact outstanding question and the next update expectation. Do not call a request “waiting” without telling the customer what it is waiting for.

For the sample sofa, the vendor might need to confirm the fabric quantity or removable parts. Record who asked, what answer is needed, and who will follow up. Keep that work visible so a different colleague can cover it.

These example quick replies support the routine:

Received: “We have your selected pieces. I'm reviewing the configuration and delivery details and will update you by the next business day.” Access question: “To review the deeper sofa, could you send the clear doorway width and describe the turn immediately beyond it? I'll explain any further measurements we need.” Quote ready: “Your quote is ready to review. It includes the selected fabric and the delivery service we discussed. The link shows the full offer and the next step.”

Replace the example timing with a commitment the store can keep. If a vendor has not answered by that point, send the update anyway.

Who receives sales credit if the customer closes in the showroom?

Use the store's attribution policy and record the people who contributed. OrderPilot supports sharing sales credit among several salespeople; Inbox assignment is not a substitute for that decision.

For example, the web associate may prepare the quote and a showroom colleague may help settle the fabric. The store can recognize the agreed contributions without changing who owns the next customer reply.

Keep the distinction understandable to staff. A disagreement about credit should not leave the customer wondering which associate is answering the question.

What does a finished day look like?

A finished day means each request has an owner and a defined next action. Some will have a sent quote; others will have an answered question or a documented vendor wait with a customer update.

Before closing, review unassigned and Needs reply work, the promises made that day, and coverage for the next staffed period. Treat Saturday requests according to the hours the customer was told, with an acknowledgment followed by actual review.

Once the quote is approved, use the supported payment route and carry the agreed specification into purchasing. The website request to signed, paid order follows that continuation.