Make search results comparable, reportable, and actionable.
Result codes should differentiate between what the search technically was and what it commercially resulted in. "Unanswered" and "customer not interested" are not the same thing.
Excessively long code lists make delegate use difficult, while overly general codes reduce management knowledge. A hierarchical and campaign-appropriate code structure should be established.
Technical results
Unanswered
Busy
Unreachable
Incorrect or invalid number.
voice message
The call was dropped.
Technical error
Customer and sales results
The meeting has concluded.
Offer submitted
Order created
Appointment or callback
He/She is not interested.
The decision-maker could not be reached.
Using a competitor's product.
Rejected due to price, product, or timing.
Request not to be contacted
Hierarchy of reasons
For example, under the main result of sales loss, sub-reasons such as high price, unsuitable product, late delivery, lack of budget, or competitor preference can be identified. Sub-reasons may vary depending on the campaign and product type.
Code governance
Definition and usage explanation
Mandatory monitoring areas
Automatic next action
Campaign and validity period
Codes that have been merged or deprecated
Matching for report comparison
Manage the result codes not as fields selected to end the call, but as enterprise data describing the sales process and customer response.