|
Lookup tables |
|
|
Under this window we have gathered a number of the tables that the ChannelCRM system is using for selection of data in drop downs. You have full control over the values and therefore you can use the to set up the right way for you company to segment the market in which you operate.
In each table there is a NULL value. This value is normally not to be removed. The meaning of the NULL value is to be used by the system when the user has not yet chosen a value. This way the user is not forced to make a selection.
Lets walk through the different tables and their purposes:
Company Primary Relation Is used to describe what you determine as your company's primary relation to the company in question. Is the company a prospect, a customer, ex-customer, partner , a competitor, a reseller?
There must be a NULL value.
Potential This lookup value is used to describe the sales potential that the Company in question represents to your organization. Often the term A, B and C customers are used, other use Platinum, Gold Silver. Remember that it is a good idea to have a "No sales Potential". In the exaple below it is the value X.
There must be a PotentialID = 0 which means unkown potential
Contact Type Some sales-models operates with ways of characterizing contacts. To support this way of dealing with and categorizing contacts the ChannelCRM system lets you attach a lookup value to contacts.
The ChannelCRM comes default with 5 types + unknown.
There must be a TyepID = 0 for unkown
Contact Function For marketing purposesI marketing sammenhæng vil man ofte have behov for at kontakte personer hos kunder/emner baseret på personernes jobmæssige funktion. Traditionelt håndteres dette ved at udvælge på f.eks. titel, men det giver ofte problemer. F.eks. kan en kontakt med ansvar for IT have titler som: IT-Leder, IT Direktør, CTO, EDB Chef, Afdelingsleder med ansv. for teknik, osv. I ChannelCRM kan du definere en række jobmæssige funktioner, som er relevante for det salgsarbejde i udfører. I eksemplet vil du således sætte CTO (Chief Technology Ofiicer) på alle de personer der har titler som ovenfor. Det gør det væsentligt lettere at lave effektive udtræk til f.eks. kampagner. Binding: Der skal som minimum være en funktion med FunctionId = 0 (svarende til ukendt).
Salgskonti Her angives simpelthen de salgskonti som forecast og ordrer skal kunne vurderes og rapporteres på. Opret ikke for mange. Det vil føre til uoverskuelige forecasts. For det tilfælde at der ønskes detailleret rapportering kan man i stedet dér vælge at rapportere helt ned på produkt og produktgrupper.
Page url: http://www.channelcrm.net/us/index.html?net_administrationlookups.htm |