A new enquiry is good news for a business. Somebody still has to pick it up. At that point, a small ambiguity can make the result of good marketing much harder to use.
We have been building the ResaHost sales process inside Resappi. It exposed a very ordinary problem. The salesperson needed to see the right owner, and the lead's status needed to show whether someone had taken responsibility. Neither issue could be fixed simply by giving an instruction in a sales meeting.
During development in August, we corrected how leads were allocated to account representatives and made ownership visible in the sales views. We also fixed a situation where a lead with an owner could still appear as new. The system held information about responsibility, but the interface did not describe the state of the work clearly enough.
For a salesperson, that contradiction creates another task. Is this mine? Has someone already called? Should I check with a colleague before doing anything? If those questions come up every day, the system needs more work at exactly the point where it should be helping.
From a management perspective, I care about the distinction between responsibility and action. A name on a card tells us who is accountable for progress. It does not establish that the customer has been contacted. Both need to be visible. Otherwise, the reports start making work that has an owner look like work that has been completed.
Automatic allocation also needs sensible rules. We directed the work to the account representatives handling sales for that service. Having access to the system does not make every employee the right recipient for a new enquiry. An organisation chart and the actual division of work do not always match.
In ResaHost's case, a person can belong to the Resaco team while also selling ResaHost services. The software needs to understand that relationship well enough to display responsibility correctly. For the customer, the structure should stay in the background. They expect a response from the business they contacted.
Working on this can feel small compared with launching a campaign. Yet these details determine whether sales can use the opportunities the company has already generated. I want us to understand how current enquiries are handled before commissioning more of them. Otherwise, we increase the uncertainty alongside the volume.
A good way to examine your own process is to take one recent lead and follow its journey. Where did it come from? When was an owner assigned? What was the next agreed action? If you have to dig through message threads to find out, you have already found something worth improving.
That investigation does not require a major software project. A team can first agree on responsibility and records using its current tools. Automation is most useful when it supports a process the team can explain in its own words. That also makes exceptions easier to spot.
These small working situations have been valuable in developing Resappi. They force us to look at what a person needs for the very next decision. That is where useful sales software takes shape.
The same question of responsibility comes up later, when an offer becomes an agreement and delivery needs to start.
