These chats arrive after the decision, not before
Most sales advice is about the top of the funnel — the visitor weighing options, comparing
features, working out whether you are credible. Procurement questions are the opposite. By the time
someone opens chat to ask whether you accept purchase orders, the evaluation is over and somebody
has decided to buy. What is left is a process problem, and processes stall for reasons that have
nothing to do with how good your product is.
That changes how you should treat the conversation. A vague answer to a feature question costs you
a little credibility. A vague answer to “can you invoice us annually against a PO?” costs
you a month, because the person asking has to go back to their finance team with nothing, and the
purchase drops to the bottom of somebody else's queue. The single most valuable thing you can do on
these chats is give a definite answer fast, even when the definite answer is no.
The questions that actually come up
The list is shorter than it feels, and it repeats. Writing the real answers down once means any
agent can handle them rather than routing everything to one overloaded person.
- Do you accept purchase orders, and above what value? Many companies accept POs
only over a threshold. Say the threshold.
- Can we pay by bank transfer or invoice rather than card? And on what payment
terms — on receipt, fourteen days, thirty days.
- Can you complete our vendor onboarding form? Usually a portal, sometimes a
spreadsheet, occasionally a phone call with a person who verifies bank details.
- Can you provide a tax form, a certificate of incorporation, or proof of insurance?
Whichever documents your jurisdiction and theirs require.
- Will you sign our terms instead of yours? The honest answer for most smaller
vendors is no, with a named exception list.
- How long is this quote valid, and can you hold the price? Budget cycles make
this question far more common at the end of a quarter.
- Can we get an annual invoice for a monthly plan? A billing question dressed up
as a procurement one, and usually the easiest yes on the list.
Answer definitely, including the noes
The instinct when a buyer asks for something unusual is to soften the answer while you find out.
In procurement that instinct backfires, because a hedge reads as a maybe and a maybe gets escalated
internally, which is how a two-day close becomes a three-week one.
Give the answer and the boundary in the same message. “Yes on purchase orders over
$2,000, net 30, and I can have the paperwork to you today. Below that we are card only.”
That is far more useful than a promise to check, and the buyer can immediately tell their finance
team what will happen. When the answer is genuinely no, say so and offer the nearest workable
route: “We cannot sign your MSA, but our terms are on the site and we can note any
specific clause your legal team flags.” Buyers deal with vendor constraints constantly.
What they cannot work with is uncertainty.
When you truly do not know, commit to a time rather than an outcome. “I do not want to
guess at that one — I will have a definite answer from finance by tomorrow morning.”
Then keep it, because a procurement chat is often the first time this buyer has seen how your
company behaves under a small obligation.
Capture what the paperwork will need
Procurement conversations generate their own follow-up work, and the details that make it painless
are the ones nobody thinks to ask for while the chat is open. Get them in the conversation rather
than in three emails afterwards: the legal entity name, the billing address and any billing email
that differs from the buyer's, the PO number if one exists, the tax identifier where relevant, and
the name of whoever actually signs. Ask them together, framed as speeding the process up, because
that is exactly what they do.
Then get the conversation out of chat and into whatever system will remember it. A procurement
thread that lives only in a transcript is fine until the buyer comes back in three weeks and reaches
a different agent who knows nothing about it. Attach the details to the account record or the deal,
and note what was promised — especially any price hold or payment term, which is the promise
most likely to be forgotten and most likely to matter.
Know when to leave chat
Chat is excellent at answering procurement questions and poor at executing procurement processes.
The line is worth being deliberate about: anything that involves a document being signed, bank
details being confirmed, or a form on someone's portal being completed should move to email or a
call, both because those channels leave the right paper trail and because bank-detail changes are a
standing fraud target. Confirming payment details over a public chat widget is exactly the workflow
attackers hope to find, and a chat widget is not an identity-verified channel.
Say why you are moving, so it does not read as a brush-off. “I will send this by email
so you have it in writing for your finance team.”
What to measure
Two numbers tell you whether this is working. Time from the first procurement question to
a definite answer — not to a resolution, to an answer, because that is the part you
control and the part that stalls deals. And the share of these chats that needed
escalation: if most of them leave the agent's hands, your answers are not written down yet,
and half a page of internal notes will fix it. Keep a tally of which questions arrive most often
too. A procurement question that recurs every week is usually a missing paragraph on your pricing
page, and answering it there converts buyers who would never have opened chat at all.