Customers & communication
Plumbing Customer Communication Log: Record Decisions and Promises
A communication log should preserve decisions, customer expectations, and promised next actions. Link each entry to the right job and contact role instead of collecting messages that nobody can turn into an accountable task.
In this guide
Log the business meaning of the conversation
Record the date, channel, contact, relevant job or invoice, factual summary, decision, and next action. A note saying “called customer” tells the next person almost nothing.
Do not replace original approval evidence with an unsupported summary. When a decision affects scope, price, or timing, retain the relevant document or message reference and the approved version.
Copy the log columns
entry_id,contact_date,channel,customer_id,job_or_invoice_id,contact_role,factual_summary,decision_reference,next_action,next_action_due,owner
COMM-EXAMPLE,2026-09-29,email,CUST-EXAMPLE,JOB-EXAMPLE,billing_contact,requested_corrected_recipient,EMAIL-REFERENCE,verify_and_resend,2026-09-30,office_owner
The row is fictional. Keep only information the business needs and restrict access appropriately. Do not store full card numbers, bank credentials, or unrelated personal details in a general communication log.
Distinguish a request from a decision
A customer asking for a different appointment is not necessarily agreeing to the alternative you later suggest. A question about an estimate is not approval of its price.
Use precise summaries such as “customer requested Friday; office checking availability” rather than “moved to Friday” before confirmation. That small distinction prevents conflicting expectations between the schedule and the message history.
| Conversation | Better log entry |
|---|---|
| Customer asks about price | Question recorded; estimator to respond |
| Customer reports payment | Payment reference requested or under verification |
| Office offers a new time | Alternative proposed; acceptance pending |
| Customer approves a version | Exact version and evidence linked |
| Customer asks to stop messages | Preference recorded and workflow updated |
Assign ownership at the end of the entry
Every promise should have an owner and a due date or trigger. “Someone will call” is not an accountable next action.
For a one-person business, the owner can simply be you. The value comes from making the obligation visible when the day becomes busy, not from creating a complicated hierarchy.
Avoid duplicating entire conversations
Use a concise factual summary and link the source where appropriate. Copying a long thread into several customer, job, and invoice records can create conflicting versions and unnecessary exposure of personal information.
Choose one system or file as the main action record. Staff should know where to check before sending another reminder or making a new promise.
Review open promises, not just recent messages
A daily or weekly review should show actions due, overdue callbacks, pending customer decisions, and unresolved payment claims. A chronological list alone can hide an old promise beneath many new messages.
For a fictional example, an estimate follow-up from last week may still need an answer even though today's schedule has many recent updates. Filter by next action date and owner rather than assuming the newest entry is the most important.
Close entries with evidence
When the promised action happens, record the result and any new decision. Do not delete the original promise simply because it is complete.
A useful log lets another staff member answer: What did we tell the customer? What did they decide? What happens next? If those answers are clear, the log is doing its job without becoming an archive of every word ever exchanged.
Sources and editorial notes
Product and documentation references checked September 29, 2026. GoPlumber publishes this guide about its own product category. Examples and templates are original illustrative material, not customer case studies or market benchmarks. Confirm current vendor terms before acting.