A contractor calls while two customers are at the counter. One employee is checking stock. Another is helping with will-call. The caller asks for a price, wants to know whether material can be delivered Friday, and says the usual salesperson already knows the job.

Picking up the phone is only the first step. The real operating question is whether the yard can preserve the request without guessing, making a promise from stale information, or leaving the next person to reconstruct the conversation later.

This guide presents a candidate workflow for reviewing that problem. It is based on public trade context, general governance guidance, and Second Counter’s discovery framework. It is not an industry standard, and it does not claim that every yard handles calls the same way.

Separate reception from resolution

A person can answer a call without resolving it. A voicemail can capture words without creating ownership. A transferred call can move the interruption without moving the work forward.

A useful process should establish what the customer is asking for, what information arrived, who owns the next step, and what may safely be said or done before that owner reviews it.

Capture the minimum useful record

The intake record does not need to solve the whole request. It needs to keep the next person from starting over.

  • caller name and callback number;
  • company or account, when known;
  • job or project reference;
  • the caller’s own description of the request;
  • item, quantity, unit, and relevant specifications that were actually stated;
  • whether the request concerns stock, an order, a quote, a takeoff, delivery, credit, a technical question, or a named employee;
  • requested timing, recorded as a request rather than a commitment;
  • original timestamp and channel;
  • who received or captured the call;
  • assigned owner and next step.

Keep the original message or transcript beside any summary when policy and consent allow it. A clean summary can hide an uncertain unit, an unfamiliar product name, or a condition the caller considered important.

Triage before answering the hard part

The same phone number can receive very different kinds of work: a routine stock question, a price request, a quote needing takeoff or specialist input, an order change, a delivery-status question, a credit matter, a substitution question, a request for a specific salesperson, a complaint, or an urgent message.

Those requests do not share one safe response. A useful triage step identifies the request class, shows what is missing, and routes it to the role that can act. If classification is uncertain, expose that uncertainty instead of placing the request into a confident but wrong queue.

Put a name and a next step on the request

“Someone will call you back” is not an operating state.

A captured request should move to a named person or yard-defined role with:

  • the source message and collected facts;
  • any missing information;
  • the reason it was routed there;
  • the customer-facing acknowledgment, if one was sent;
  • the expected internal review point;
  • a visible state such as received, assigned, waiting for customer, waiting for specialist, resolved, or closed.

The acknowledgment should remain neutral. It can confirm receipt and repeat what will happen next. It should not create a price, stock, delivery, credit, technical, or fulfillment commitment that has not been checked through the yard’s current records and authority rules.

Protect named relationships

Some callers expect a particular salesperson. Some accounts have contact preferences, special pricing rules, private notes, active disputes, credit restrictions, or instructions not to contact them through a certain channel.

A safe process can identify the account owner, prepare a summary, and route the request with context. It should not bypass named ownership, disclose private notes, start duplicate outreach, or put a protected account into a generic follow-up sequence.

The yard needs a backup rule for times when the named employee is unavailable: who may see the request, who may respond, and which decisions still wait for the account owner or manager.

Treat after-hours calls as a separate workflow

Before opening, after closing, and weekend calls may mix routine requests with messages the caller considers urgent. The yard should define which requests wait, which role receives an urgent notification, what information must be collected, which words may be used in an acknowledgment, and what never counts as authorization to dispatch, deliver, release material, or make a safety decision.

A caller’s description of an emergency is important context. It is not, by itself, authority for the yard to promise an operational response.

Stop before the call becomes an unsupported promise

The receiving person or system should stop and escalate when the answer depends on:

  • current price, margin, freight, tax, or quote validity;
  • physical stock or a conflict between system stock and yard reality;
  • credit, terms, past-due status, deposit, refund, or private account information;
  • a substitute, engineered product, technical selection, or code question;
  • delivery capacity, routing, timing, site conditions, loading, or unloading;
  • a named-account rule or relationship decision;
  • stale, missing, conflicting, or inaccessible source data;
  • anything outside the receiver’s defined role.

The safe response is not to sound more certain. It is to state what needs checking, preserve the request, and send it to the person who owns the decision.

A 20-minute call-handling review

Take the last five calls that arrived while the counter was busy. For each one, record when it arrived, who or what received it, what the caller wanted, what information was captured, who owned the next step, what was communicated back, which records or people had to be checked, where it waited or changed hands, and its final state if known.

Patterns across five real calls are more useful than a generic claim about the industry. They show which part of the local process needs attention: reception, qualification, routing, authority, follow-through, or recordkeeping.

Where assistance can begin

The lowest-authority work comes first: capture the caller’s words, structure the fields, identify missing information, route the request, prepare a neutral acknowledgment, and make the owner and state visible.

More consequential work should remain behind explicit controls. A draft price is not an approved price. A system stock value is not physical confirmation. A requested delivery date is not a delivery promise. A fluent answer is not authority.

The request-to-fulfillment map shows the broader operating context. The software guide separates source records from the workflow around them, and the AI control guide explains where assistance can grow and where it must stop. You can find all three in the Second Counter resource center.

Second Counter is researching these workflows with independent lumberyards before finalizing its service. We do not claim production call-handling results or a universal process today.

Questions for an owner or counter lead

  • What happened to the last five calls received while the counter was busy?
  • Which request types come through the main number, and who owns each one?
  • Which callers require named-person handling?
  • What may be acknowledged without checking another system or person?
  • Which conditions force a stop rather than a best guess?
  • How do after-hours messages become owned work?
  • Where is the final outcome recorded?

Sources and limitations

  1. LBM Journal, The Employee Balancing Act, March 14, 2025. This article provides attributable dealer responses about staffing and operating tradeoffs. It is a non-random panel and does not establish a universal call-handling pattern.
  2. National Institute of Standards and Technology, Artificial Intelligence Risk Management Framework (AI RMF 1.0), January 26, 2023. This is voluntary, general guidance, not an LBM standard or product certification.
  3. NIST AI Resource Center, Appendix C: AI Risk Management and Human-AI Interaction. This resource supports defining human and system roles; workflow-level controls still require local validation.
  4. Second Counter, How Lumberyard Operations Work. This candidate operating map provides the broader request-to-fulfillment context and carries its own evidence limitations.