Skip to main content
Help Center

Set up the CRM: fields, rating models and activity types

Administration of the CRM: set ABC rating models for customers, prospects and suppliers, enable custom and standard fields, maintain activity types, configure service-note visibility and dynamic links.

Prerequisites

The CRM configuration controls how customers, prospects and suppliers are rated, which fields are available on the contact and on the organisation, and which activity types your team uses. You reach it via the System configuration button (at the bottom, next to the Administrator mode display) → category CRM → tab Settings. Within the configuration, administrator mode is always active in any case.

Info: Changes to rating models take effect immediately: teamspace recalculates the ABC classification in the background. You see the result directly in the Customers, Prospects, Suppliers lists.

Note on the paths (as of 2026-06-22, checked live): The rating models and fields are not under separate menu items Customer aspects/Sales aspects/Supplier/CRM templates, but bundled under Configuration → CRM → Settings. There you open the collapsible areas: Organisation - Customer → Customer aspects (customer rating model), Organisation - Prospect (prospects), Organisation - Supplier (suppliers), CRM activities → Available types (activity types) and Contacts (contact fields, dynamic link, field visibility). Separate menu items, by contrast, are Contacts and CRM activities (these are lists of the contacts and the CRM activities, not the field/type configuration) as well as Deletion deadlines. The following sections still name the old short paths in backticks; the real collapsible paths are given here.

1. Set rating models (ABC)

Each of the three relationships has its own rating model with a metric and a time horizon. The scheme is always 20% A / 60% B / 20% C – the logic behind it is described in Prospects, customers and suppliers.

Configuration CRM, Settings, collapsible area Organisation - Customer, Customer aspects with rating model Project times and time horizon 180 days
`Configuration → CRM → Settings → Organisation - Customer → Customer aspects`: rating model (here "Project times") and time horizon (here 180 days), plus customer/accounts-receivable number rules.
  • Customers (Configuration → CRM → Settings → Organisation - Customer → Customer aspects): choose the rating model. It is often preset to Project times (in the demo tenant with a time horizon of 180 days); for most organisations Invoices over the last 365 days is more meaningful – teamspace then sums all invoices per customer over the year, builds the ranking and assigns A/B/C. The time horizon (e.g. 365 days instead of 180) can also be set here.
  • Prospects (Configuration → CRM → Settings → Organisation - Prospect): choose the rating model – Revenue potential, Quotes (e.g. of the last 60 days), Revenue potential and quotes, Sales opportunities or Revenue potential and sales opportunities. Recommendation when using sales opportunities: Sales opportunities or Revenue potential and sales opportunities, because they carry a target value and probability and are not inflated by competing quotes.
  • Suppliers (Configuration → CRM → Settings → Organisation - Supplier): the rating model runs on Time, Quality and Cost; in addition you set the time horizon. You define the possible selection values and their weighting here.

Caution: The Revenue potential is a free, static field – if it is not maintained, a once-high value stays in place permanently and inflates the A-prospects. Either set an upkeep interval or switch to a dynamic model (Sales opportunities).

2. Custom fields and standard fields

teamspace comes with a large number of optional fields that you enable as needed:

Configuration CRM, Settings, collapsible area Contacts with the sub-areas General, Address, Dynamic link, Field visibility, Preset columns, Configurable preview card
`Configuration → CRM → Settings → Contacts` with the areas General, Address, Dynamic link, "Field visibility" (field activation), Preset columns and preview card.
  • Standard fields are enabled under Configuration → CRM → Settings → Contacts → Field visibility (for contacts) or the corresponding Organisation - … areas – such as social media profiles, additional address types and job title.
  • Custom fields are created there when a needed field is not included – separately for contact and organisation, since contact fields and organisation fields are stored differently.
  • Industries, size categories, customer categories: the selection values that appear in Statistics and classifications or Customer aspects are also maintained here.
  • Special contacts / roles: the assignable roles (managing director, data protection officer, etc.) are created in the CRM configuration (see Key account managers, VIPs and service notes).

3. Maintain activity types (CRM templates)

In the detail manager the user sees four to five standard activities directly at the plus button; you enable or disable all further (“passive” CRM activities) under Configuration → CRM → Settings → CRM activities → Available types (live, e.g. Acquisition, Enquiry, Follow-up, Note).

Configuration CRM, Settings, collapsible area CRM activities with Available types Acquisition, Enquiry, Follow-up, Note
`Configuration → CRM → Settings → CRM activities → Available types` (here Acquisition, Enquiry, Follow-up, Note) – via the plus you add further activity types.
  • If you take a type out of the list, it is no longer directly available to users.
  • The types fall into the three groups soft activities, hard factors and internal matters (see Activities and follow-ups).
  • This is also where the templates offered in campaigns are located (mail, form letter, address labels, CRM activity) as well as the associated form-letter and label layouts.

4. Service-note visibility

Via the configuration you define where service notes appear – only in the organisation, in the ticketing system, in documents, in projects. This way a note like “only pays after dunning level 2” automatically travels into the right context. Details on the service note itself are in Key account managers, VIPs and service notes.

Dynamic links connect each contact with an external system (e.g. their SharePoint folder). They are configured under Configuration → CRM → Settings → Contacts → Dynamic link: in the Name field you set the general part of the link, below it the individual link part with placeholders from the [x] symbol (e.g. {{contact.surname}} or {{contact.email}}). Adapt the placeholders to the target system – some expect an email address, others an ID, others the surname.

6. Telephony integration

Anyone who wants to dial directly from the follow-up list (handset symbol, call attempts are documented automatically) sets up the telephony connection in the configuration. You clarify the exact path and the supported phone systems with the consulting team – the dialling mechanism itself is described in Activities and follow-ups.

Common questions & needs

You want to …How to do it
Rate customers by annual revenue instead of project timesConfiguration → CRM → Settings → Organisation - Customer → Customer aspects: rating model to Invoices, time horizon to last 365 days.
Avoid inflated A-prospectsConfiguration → CRM → Settings → Organisation - Prospect: switch the rating model to Sales opportunities instead of Revenue potential.
Rate suppliers by time/quality/costConfiguration → CRM → Settings → Organisation - Supplier: set the rating model and time horizon, maintain the selection values.
A field that teamspace does not provideEnable a standard field under Configuration → CRM → Settings → Contacts → Field visibility or create a custom field.
Enable/disable an activity type for everyoneConfiguration → CRM → Settings → CRM activities → Available types: enable/remove the type.
Show a service note in tickets tooIn the configuration, enable the visibility of the service note for the ticketing system.
Jump from the contact into an external systemSet up dynamic links under Configuration → CRM → Settings → Contacts → Dynamic link with placeholders.