Skip to main content
YourOrderBook

Lead to Order

Keep the customer story connected from enquiry to confirmed order.

Carry the customer, requirement and agreed details through follow-up and quotation so the order desk can see what sales agreed without rebuilding the story.

See the handoffsStart Business Audit

The record that movesOne sales opportunity

  1. OwnerSales

    1. EnquiryA person does thisIt arrives, and it needs an owner.
    2. Follow-upA person does thisSomebody owns the next action.
    3. QuotationA person does thisBuilt from the same enquiry.

  2. Handoff

    What moves
    Customer, requirement and agreed order details
    What must be true
    The customer has accepted the quotation
    What changes hands
    Responsibility passes from sales to the order desk
    What can stop it
    Something agreed in sales still needs clarification

  3. OwnerOrder desk

    1. Confirmed orderA person decidesChecked against what was agreed.

Different sources. The same sales process.

How an enquiry arrives changes who sees it first. It should not create four separate sales processes running beside each other.

  • Website
  • WhatsApp
  • Exhibition
  • Phone or salesperson

becomes

One enquiry, in one process

  • Customer
  • Requirement
  • Owner
  • Next action

The source is context. Once the enquiry exists, the journey is the same one — which is why there is no separate exhibition workflow here.

Keep the same customer and requirement attached.

Each stage adds something. None of it should replace what the stage before it knew.

ExampleThe same five fields, at every stage

Customer
The business that asked
Requirement
What they asked for
Owner
The person responsible now
Next action
What happens next, and when
Quotation
The document that came out of it

This is a thread, not a customer profile. What else is known about the account belongs on Customer 360.Customer 360

Every stage here already has a page that owns it.

This workflow connects them. It does not replace them, and it does not explain them again.

  • Enquiry

    Lead Management

    Organising an enquiry once it has arrived: ownership, next action, status.

  • Opportunity

    Sales Pipeline

    Active opportunities — stages, value and what is likely to close.

  • Follow-up

    Follow-up Automation

    Reminders and actions once a next action is known.

  • Quotation

    Quotation Automation

    Turning an enquiry into a quotation, with pricing and approval rules.

  • Order

    Order Management

    Taking the order, checking it, confirming it and tracking it.

The seam

Quotation accepted. Now the order desk takes over.

This is the one handoff on this journey that crosses from sales into order handling, and the one place where the story is most often retold from memory.

Sales

What sales knows

  • The customer, and who has been talking to them
  • The requirement, in the customer’s own terms
  • The commercial context, where it was recorded
  • The requested or promised date, where one was given
  • Anything still open or unclear

Changes hands

The handoff should carry what was agreed. Whether the order is created automatically or reviewed by a person depends on the process and software in use.

Order desk

What the order desk needs

  • Enough context to create or review the order
  • The accepted quotation it came from
  • Which details were agreed, and which were not
  • Who to ask when something does not match

What should the order desk inherit?

Not the whole conversation. The part somebody would otherwise have to go and find.

Example handoff

Customer
Who the order is for
Requirement
Items and quantities as agreed
Accepted quotation
The reference it came from
Commercial details
Where they were recorded
Requested date
Where one was given
Open exceptions
Anything still unresolved
Sales owner
Who to ask

The next team should not have to reconstruct the sale from messages and memory.

Exceptions belong at the handoff, not after it.

An exception that travels with the order is a question somebody can answer. One that does not becomes a phone call three days later.

  • Accepted, but the delivery date still needs confirming

    The commercial answer is agreed. The operational one is not.

  • A price exception is still unresolved

    Where the quotation needed an approval that has not come back.

    Quotation Automation

  • The customer changed the quantity after accepting

    The order and the quotation no longer say the same thing.

  • A credit review is needed before confirmation

    The order desk cannot confirm until the account position is clear.

    Order Approval Workflow

How each of those approvals works belongs to the page that owns it. What matters here is that the exception is visible at the moment the order changes hands.

One customer can cross two teams without losing the thread.

Here is the same customer as both teams already see them on this site — in the sales view, and in the order desk’s queue.

In the sales viewGrow Sales

Customer
Sri Lakshmi Stores
State
Follow-up overdue
Owner
AD

In the order desk’s queueOrder Management

Order
SO-2098
Customer
Sri Lakshmi Stores
Value
₹1,05,600
State
Credit approval needed
Owner
SK

Two teams, two views, two different people responsible — and nothing in either row tells you about the other. Connecting them is the whole job of this workflow.

Where the detail lives

This page is about the movement between these pages. Each one of them owns its own subject.

Where does your sales story get retold from memory?

Tell us how an enquiry becomes an order today, and we will help you find the handoff that loses the most.

Start Business AuditTalk to us