Platform / Projects
One customer site. One record of everything.
Each Project holds a customer site or deal: its operating conditions over time, the products in use and every work log. It is the context every case is reasoned from, so the answer fits that site, not a generic one.
What a Project holds
One customer site, its conditions over time, and the context every case is reasoned from.
-
Each product category suggests the operating conditions worth tracking, from a catalog covering over 100 product types. Add custom conditions for anything else.
-
Every value is kept with its date and unit, so you can see what changed before a problem started.
-
Record the products in use, their quantities and the dates they were applied.
-
Ask about a site and the agent reads its Project first, so the candidates and causes are weighed against that customer's real operating window.
-
Tell the assistant a new reading or product change, and it records the value with its date.
-
Agents weigh the site's readings over time, so a change that came before a problem is part of the analysis.
-
Customers can see the overview, conditions and products of their own sites in Field Care.
“We used to spend most of our time finding information and writing it up. Now Lubinpla works through the data and lays out the reasoning, so we read it and make the call.”
How teams use Projects
-
Answer a complaint
See the conditions and product changes that came before it, before the first call back.
-
Prepare a recommendation
Start product selection from the site's actual conditions, not a generic case.
-
Scope a supplier change
Find every site that uses an affected product when a supplier or regulation changes.
-
Hand over an account
Give a new rep the full history of every site in one place.
-
Follow a trial
Record the readings during a trial against the site they were taken at.
-
Review an account
Summarize one customer's technical activity and open risks, straight from its projects.
Turn technical reasoning into better results.