A request arrives in three messages, two photos and a voice note, then quantities change in another chat. Drafting while scrolling from memory can reuse old facts or miss a service. Prepare a summary first.
You need not impose a complex form. Continue the conversation while organising recipient, outcome, products or tasks, quantities, constraints and missing information. This makes notes usable.
Separate confirmed decisions from suggestions
Chats mix requests, alternatives and assumptions. “Maybe four devices” is not a final quantity. “I'd also like installation” is service scope rather than a minor note. Identify the latest decision and remaining question.
Photos and messages are not complete technical checks. Record unverified measurements, access or compatibility. Collection should reveal uncertainty rather than remove it for convenience.
Send a summary for confirmation
“For the proposal, I am allowing for four devices, delivery to the stated site and initial configuration. Model and network availability remain to be confirmed. Is that correct?” lets the client fix the basis before calculations.
For consulting, summarise objectives, deliverables and meetings. For on-site work, areas, tasks and checks. For cleaning, frequencies and spaces. Do not paste the entire chat into the commercial document.
Turn the summary into items
Each line should describe a saleable product, accessory, transport, installation or service. Personal preferences and internal notes are not priced items. Separate selectable alternatives from the main proposal.
Four products at €150, configuration at €180 and transport at €40 produce an illustrative €820 subtotal before taxes. Three products reduce this to €670 only if service and conditions stay unchanged. Check before editing.
Terms must not remain only in voice notes
Record required access, infrastructure and client materials in notes. Match validity and timing to what you can confirm. A message promise may be remembered even if absent from the PDF, so check relevant communication.
Update the summary if scope changes. A description based on the first chat and total based on the latest quantity makes an inconsistent offer.
PDF and sending message
Review the generated document without the chat. If it cannot stand alone, information is missing. Check recipient, subject, lines, terms and total. Give the file a recognisable reference and version.
Explain which request is being summarised and open choices. Ask when the client expects to review it. Sending or a chat reaction does not necessarily confirm every condition.
What to reuse and what to check
Reusing items and data reduces copying but cannot make ambiguous facts certain. PreventivOk is not presented here as an automatic WhatsApp importer or voice-note transcriber. Summarising and checking remain your steps.
Poki assists within available product functions and permissions but is not required for an organised proposal. Avoid entering unnecessary information into your tools. Record facts useful to the job.
Keep the right evidence
Retain the sent PDF and relevant decisions. For changes, request one list and create a new version. Chat then remains a communication channel rather than the only archive for reconstructing price and service.
A quantity changes in the latest message
Check the latest choice and ask for confirmation if it contradicts the summary. Do not add quantities across messages without knowing whether they replace or supplement each other. “Two more” differs from “two in total”.
Reply with a short final configuration list. With several chat participants, check who confirms operating decisions. Summarise the calculation basis rather than transcribing everything. This reduces unnecessary revisions and prevents old preferences or internal notes reaching the client PDF.
Enter verified information in PreventivOk and generate the PDF. Collecting from WhatsApp is manual; automatic chat integration is not promised. Create your next quote with PreventivOk.