The latest from Lubinpla
More stories
-
A customer stopped ordering: how to tell if it was technical
Customers who stop ordering over a technical issue usually show signs first: repeat questions, a complaint, off-target readings or a new contact.
-
Annual water treatment service review: what it should cover
An annual water treatment service review fixes the period and systems, compares each result with its control limit, lists open risks and sets next checks.
-
KPIs to agree in a water treatment service contract
Agree outcome KPIs such as control-range compliance and corrosion rate when the supplier controls dosing, and visit and reporting KPIs when the plant does.
-
Coating Warranty Claim: The Evidence the Maker Needs
A coating warranty claim needs the defect definition, application records, dated photos, test results and a suspected cause stated as a hypothesis.
-
How to get operators to log coolant concentration correctly
Operators log coolant concentration correctly when the time and point are fixed, the refractometer factor is applied, fields are few and results go back.
-
The people a technical supplier should know at a customer plant
Map five roles at each customer plant: purchasing, maintenance, production, quality and EHS. Note what each asks, name a backup and review the map yearly.
-
How to keep technical records for a multi-plant customer
Split company-level and plant-level records, keep shared documents once, log each plant's own conditions and compare plants on the same product.
-
Open issues list template for a customer review: what goes in
An open technical issues list for customers shows issue, date found, impact, owner, status and next date; margins and opportunity notes stay internal.
-
Same chemical, different trade names: matching TDS, SDS and CoA
Match one chemical across regional trade names with four checks: same manufacturing site, same SDS Section 3 composition, same TDS values, supplier letter.
-
CoA retention period: how long a distributor should keep CoAs
Keep each CoA until lot expiry or the claim period's end, whichever is later, and longer where a quality agreement, 21 CFR 211.180 or REACH requires it.
Talk to us about your sales team.
Custom plans, custom terms, security reviews and onboarding across teams or branches. Tell us a little about your organization and we will reply with a starting plan.
Contact Sales- 01Start from site data and your documents
Bring in the TDSs, test reports and site records your team already has. Where a case has too little to go on, the agent searches the web for public sources such as manufacturer data and standards.
- 02State the case
Describe the customer's situation in plain words. The agent reads the site's conditions and history, proposes the task that fits, and starts when you say go.
- 03Review the reasoning, step by step
Each step shows what was considered, what the evidence supports and what was ruled out, with the source behind each point. You can carry on, ask for changes or stop.
- 04One document for this customer
The case ends in a document built for that customer: the conclusion, the reasoning, the conditions it depends on and what to do next. Share it through Field Care when you choose.