Purpose
The Contact Reason Code feature enables organizations to categorize the reasons for contact interactions, decisions, or outcomes within the sales process.
These codes help track why a contact was won, lost, or remains in a specific stage — supporting performance analysis, identifying trends, and improving decision-making.
By configuring standardized reason codes, companies can ensure consistent reporting and gain valuable insights into customer behavior, sales challenges, and engagement effectiveness.
Access Path
Control Center → Sales Management → Contact → Contact Reason Code
Accessing the Configuration
-
Navigate to Sales Management → Contact → Contact Reason Code.
-
Click Add Contact Reason Code to create a new record.
-
Use the Edit icon to modify an existing code’s details or description.
-
Click Delete to remove a code no longer relevant.
Configuration Fields

| Field | Description |
|---|---|
| Code | The name or title of the reason (e.g., Clear Value Proposition, Competition, Lack of Interest). |
| Company | Defines the company or business unit where this code applies. |
| Description | Provides additional context or explanation about the reason, helping users choose the appropriate one during contact updates. |
💡Tip Each company can maintain its own set of reason codes, ensuring they are aligned with its specific sales processes and terminology.
Example Configuration
| Field | Example Value |
|---|---|
| Code | Clear Value Proposition |
| Company | Architecture Company |
| Description | The company has communicated a clear value proposition, highlighting the unique benefits of its products or services. |
Interpretation:
This configuration helps sales teams classify contacts or opportunities where a clear value proposition led to successful engagement. Similar codes (e.g., Competition, Budget Constraints) can be used to record reasons for lost or stalled opportunities.
Usage
-
Contact Reason Codes are used when updating a contact’s status, closing a sales opportunity, or logging interaction outcomes.
-
They allow for:
-
Identifying patterns in customer decisions (e.g., frequent “budget” issues).
-
Generating reports and KPIs that show reasons for wins, losses, or inactivity.
-
Enhancing strategic decisions (e.g., adjusting pricing or improving communication).
-
-
These codes can also feed into Sales Analytics dashboards for visual insights.
Best Practices
- Define reason codes collaboratively — involve sales, marketing, and management to ensure codes reflect real-world scenarios.
- Keep them standardized — avoid duplicates or overlapping meanings.
- Use descriptive names — short but meaningful, helping users pick the right option quickly.
- Review periodically — remove outdated codes and add new ones based on changing business trends.
- Leverage for analytics — integrate reason codes into reporting tools for data-driven improvements.
Summary
| Item | Description |
|---|---|
| Feature | Contact Reason Code |
| Location | Sales Management → Contact |
| Objective | Track and categorize reasons for contact actions or outcomes |
| Key Fields | Code, Company, Description |
| Example | Clear Value Proposition – “Company clearly communicated unique benefits.” |
| Use Cases | Sales analysis, opportunity tracking, customer behavior insights |
Related Articles
System Configuration – Companies Setup
System – User Profiles and Access Rules
Sales Management – Contact Segmentation
General Parameters – Types / Global Lists
Help Center