go~mus + crm

go~mus separates three levels cleanly: end customers with a login in the online shop and visible order history; contact persons with salutation, role and multiple phone numbers; and institutions (companies, travel agencies, schools) with VAT ID and collective invoicing setup. When you record a school class in the backend, you maintain the school as an institution, one or more teachers as contacts, and the booking person as a customer. The relationship stays intact even when the teacher changes.

Productively supported are Microsoft Dynamics 365, Salesforce, Brevo and Starmate.io. Contact and order data is synchronised in real time or batched, depending on the provider, with mapping configurable per tenant.

When a contact changes in go~mus, the change moves to your CRM. When it changes in the CRM, the update flows back to go~mus, without loops. Orders flow to Salesforce for marketing reports, transactional events trigger Brevo mailings. Custom integrations of further CRM systems are generally possible.

In the online shop, customers tick „subscribe to newsletter" at checkout and receive a double-opt-in email; the confirmation triggers the sync to the chosen provider. On the phone, your team actively offers a newsletter subscription when creating a new contact; the double-opt-in mail goes out directly.

Multiple newsletter lists per tenant are possible, e.g. „general", „family programme" or „press service" with their own API token per list. In the customer management view, your team sees which newsletters a person receives.

School, press or curator contacts can be grouped into contact lists. The list is exportable and also serves as a source for invitation management, e.g. for a vernissage or a school-course invitation.

For newsletter subscriptions, an email address is enough; all further fields are optional. Per-contact deletion and anonymisation workflows are built in; each CRM provider runs as a documented data-processing agreement.