MétaCan
Menu
Back to cohort
Record W4403994743 · doi:10.62477/jkmp.v24i4.462

Foundations, Design, and Integration of Customer Relationship Management (CRM) Systems Within Corporate Knowledge Management Strategies

2024· article· en· W4403994743 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Knowledge Management and Practice · 2024
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsnot available
Fundersnot available
KeywordsCustomer relationship managementBusinessKnowledge managementEnterprise relationship managementProcess managementCustomer advocacyComputer scienceMarketingService quality

Abstract

fetched live from OpenAlex

In highly competitive markets, companies need to secure their long-term viability by establishing and maintaining competitive advantages using Customer Relationship Management (CRM) systems. The way these systems are designed significantly impacts a corporation's future growth and profitability and should be recognized as a key factor in the success of corporate knowledge management. This paper aims to identify the design features and prerequisites of CRM systems that contribute to increased sales, the expansion of corporate knowledge, and overall organizational development. An empirical study conducted in 2019 within the Austrian packaging industry (Moser, 2021) highlights the importance of identifying CRM system requirements that enhance user acceptance. The design criteria identified can guide the implementation of future CRM projects, ensuring proper use and approval, and contribute to the development of a comprehensive CRM strategy that integrates corporate knowledge management.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.977
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0020.006
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.175
GPT teacher head0.355
Teacher spread0.180 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it