Sending Quotes, Invoices and Documents in Chat

There is a reflex that survives from the era before business chat: important documents go by email. So a conversation that has run entirely in WhatsApp — the enquiry, the questions, the photos, the price discussion — reaches its most important moment and is moved to a channel where the customer is not paying attention. Our guide to the half of chat that is not text treats this as a straightforward conversion problem.

The channel switch is where deals go quiet

Every change of channel loses people. The email goes to a filtered address, arrives among invoices and newsletters, or lands in spam because it has an attachment from a sender they have never emailed before. Two days later you follow up in chat asking whether they saw it, which tells you the answer.

Sending the same PDF in the thread you were already using gets opened within the hour, usually within minutes. Nothing about the document changed; only the friction did.

Send a message, not just a file

A PDF arriving alone is an obligation. The document should come with two or three lines that make it readable without opening anything: what it covers, the total, what happens next.

"Here's the quote for the bathroom — 3,400 including materials, about four days' work, valid until the 30th. Happy to walk through any of it. If it looks right, I can hold the week of the 12th." That message can be answered from a lock screen, and a customer who can answer without opening a file answers faster.

“

Send the number in the message and the detail in the file. People decide from the message and confirm with the file.

— be digital ai team

Practicalities that matter

• Name the file properly. "Quote-Marconi-Bathroom-March.pdf" is findable later; "document(3).pdf" is not.
• Keep it small, within the limits described in where chat media goes and what it costs to keep. A twelve-megabyte file with photographs at full resolution may not send at all and will not be opened on mobile data.
• One document per message, so it is obvious what has been received.
• Put the essentials — price, validity, what is included — in the first half page, because most people read a PDF on a phone and stop after one screen.

The last point is the one businesses resist and should not. A quote whose price appears on page three is a quote that gets skimmed and misunderstood.

Signatures and approvals

For most small transactions, an explicit "yes, go ahead" in the chat thread is sufficient agreement and is far easier to obtain than a signature. It is timestamped, attributable to a phone number, and preserved in the conversation record.

Where a formal signature genuinely is required — larger contracts, regulated work — send the signing link in the chat rather than moving to email. The customer signs on their phone and the confirmation returns to the same thread. And if money is involved at that point, collecting it in the same place removes another channel switch, which is what taking Stripe payments from inside a chat is for.

Keep the record

Where the quote was built from images the customer sent, keep those on the record too — the reasoning is in when a photo answers the question faster. Six months later, someone will ask what was agreed. The thread should answer that: the quote sent, the version number, the customer's acceptance, and any variation discussed afterwards. This is the practical value of documents living in a CRM rather than in an individual's chat history — the record survives the person who created it.

Version control matters more than it seems. When you revise a quote, send the new one with a clear label and say what changed, rather than sending an updated file with the same name. A conversation containing three identically named quotes is one where you will eventually be arguing about which one applies.

Follow up on the document, not the file

Two days of silence after a quote is normal and does not mean no. What it does mean is that the follow-up should give them something to react to rather than asking whether they got it — "Did you see it?" invites a one-word answer and ends the exchange.

Better is to ask about the decision: whether the timing works, whether they want the alternative specification, whether anything in it needs explaining. That is a question a busy person can answer in one line, and it is the sequence described in automations that fire when a deal moves.

What does not belong in chat

Some documents should not travel this way. Anything containing another customer's data, identity documents you have no reason to keep, and medical or financial records beyond what the conversation genuinely requires. The test is whether you would be comfortable with that file sitting in the phone gallery of whoever receives it, because that is often where it ends up.