As a software company in the German healthcare market you sell to regulated healthcare providers, run a self-service SaaS product and operate with a small team across service, marketing and sales. e-health.CRM is built for exactly that – not retrofitted for it.
Born out of running our own healthcare product family – proven in real sales to midwives, nursing services and therapists.
Put your requirements catalogue next to this page. Every requirement a healthcare software company typically raises appears below as a row – with its concrete implementation in e-health.CRM alongside.
Most CRM platforms are built horizontally: broad, generic, for every industry and therefore for none in particular. e-health.CRM is vertical – for companies that sell regulated software to German healthcare providers. That closes exactly the integration and compliance gaps you would otherwise have to retrofit onto a generic tool.
e-health.CRM brings together the three teams that in many software companies work with separate tools and separate truths. Anyone picking up a conversation sees the full history – from the first mailing to last week's call.
e-health.CRM isn't just an internal tool; it connects directly to your website and channels. Inquiries, sign-ups and document requests become structured records without anyone retyping anything.
e-health.CRM provides the backend infrastructure for fully automated onboarding. The customer-facing app consumes the API; the CRM creates contract, communication room, license and billing – without anyone stepping in.
e-health.CRM bills software licenses and percentage-based professional services in one unified system — with cleanly separated invoice series and VAT treatments, no separate billing tool.
Support in e-health.CRM is a dialogue: customers reply straight from the app, resolve issues themselves and receive structured knowledge — while your team keeps the thread.
Every prospect moves through a defined funnel; every campaign interaction is tracked individually – for increasingly targeted follow-up.
A typical CRM requirements catalogue for a healthcare software company – row by row, with the implementation in e-health.CRM.
| Requirement | Implementation in e-health.CRM |
|---|---|
| groupsTeam- & contact-wide foundation | |
| Shared 360° view of every contact across service, marketing and sales | checkMet All three teams work on one record per contact – no silos between separate tools. |
| Ticketing with SLA tiers, team routing and escalation | checkMet Priority levels I–III plus Lead priorities, ownership routing, notes, escalation automation. |
| Sales pipeline with activity logging and conversion tracking | checkMet Pipeline with activity logging and end-to-end prospect-to-customer tracking. |
| Complete contact history – every touchpoint in one place | checkMet Campaigns, engagement events, inquiries, outbound calls and emails chronologically per contact. |
| publicWebsite & channel integration | |
| Inbound emails to functional addresses captured automatically as inquiries | checkMet Automatic inbound parsing turns mails (support@, anfragen@ …) into inquiries, classifies by origin and routes to the right team. |
| Contact form, newsletter & waitlist straight into the CRM | checkMet Sign-ups land as engagement events, link to known prospects and are confirmed via double opt-in. |
| Legal documents (T&Cs, DPA, SLA, EULA) delivered on request automatically | checkMet Delivered by email; requesters are automatically added to the prospect pipeline. |
| QR and tracking-link attribution in real time | checkMet Every campaign material carries a unique token that ties interactions to the individual prospect. |
| boltSelf-onboarding & billing | |
| Trial registration without any manual CRM step | checkMet Registration via the app creates a customer record, a contract and a dedicated communication room. |
| Verification, activation codes and payment mandate via API | checkMet API endpoints consumed directly by the customer-facing app. |
| License, slot and billing management automated | checkMet License management, usage slots and billing enforcement run automatically, incl. voucher and promo pricing. |
| SEPA direct debit & subscription management integrated | checkMet SEPA direct debit and subscription management are part of the platform – no separate billing system. |
| receipt_longBilling & invoicing | |
| Automatic invoice generation per billing cycle with line items | checkMet Invoices are generated automatically with full line-item breakdowns and collected by SEPA direct debit without staff involvement. |
| Two business lines with separate invoice series and VAT treatments | checkMet Software licenses and percentage-based services run in separate invoice series — cleanly delineated in one system. |
| Role-based accounting workflow (volume → draft → issue → SEPA) | checkMet A dedicated Accounting section guides accountant roles through the entire flow in one place. |
| Central price catalog with audit trail | checkMet Plan, add-on, bundle and congress action prices centrally managed; every change logged with VPI history. |
| campaignMarketing & campaigns | |
| Segmentation by provider type, region and software in use | checkMet IK classification codes, Bundesland filter and software tracking as multi-select criteria. |
| Automatic campaign rollout without list export/import | checkMet On confirmation, one rollout record with a unique tracking token is generated per matching prospect. |
| Per-prospect status & response tracking | checkMet Status per prospect: Planned, Dispatched, Responded, Converted, No response, Suppressed. |
| Campaign analytics with funnel and response rate | checkMet Funnel bar across all rollout statuses, response rate and a live activity feed linking back to the prospect. |
| Competitor-aware targeting (win-over campaigns) | checkMet "Current software" filter with include/exclude – targeted win-over campaigns at the right moment. |
| Suppression & over-contacting protection | checkMet Campaign-history filters and an automatic suppressed flag on objection. |
| forumCommunication | |
| Click-to-call directly from the contact record | checkMet VoIP phone system, every call logged with staff attribution; reason/note/outcome added afterwards. |
| Outbound email with role-based sender and signature | checkMet Personalised senders, HTML signature with logo and legal disclaimer, Markdown in the body. |
| SMS / WhatsApp status updates & callbacks | schedulePlanned SMS/WhatsApp gateway for status notifications and callbacks – on the roadmap. |
| Two-way support: customer replies straight from the app | checkMet Customers reply to open tickets from your app; the team sees them in real time, incl. self-resolution and auto-reopen. |
| Internal notes separate from customer-facing replies | checkMet Team-internal notes run alongside the customer thread — cleanly separated, context preserved. |
| Knowledge base with in-app articles and interactive checklists | checkMet Structured articles and tickable checklists right in the CRM room; completion status reflected back. |
| shield_lockCompliance & operations | |
| GDPR-compliant data handling with German data residency | checkMet Designed for the regulatory framework for healthcare providers in Germany. |
| Bidirectional API to the customer-facing app | checkMet Full API: trial, activation, license, billing and Matrix communication room. |
| Real-time notifications per customer and team | checkMet Matrix-based push notifications per customer and per team. |
A requirement in your catalogue that's missing here? Talk to us – we'll honestly classify it as "met", "planned" or "not intended".
The inbound and outbound channels e-health.CRM uses to connect your operations.
| Channel | Direction | Description |
|---|---|---|
| Email (inbound) | ← | Inbound parsing converts emails into CRM inquiries. |
| Email (outbound) | → | Transactional email delivery with personalised sender + signature. |
| SMS / WhatsApp | → | Planned: SMS/WhatsApp gateway for status updates and callbacks. |
| VoIP (click-to-call) | → | VoIP phone system, call logging. |
| Newsletter | ↔ | Double opt-in, sync with an email marketing service. |
| App (your software) | ↔ | Full API: trial, activation, license, billing, Matrix room. |
| Matrix | ↔ | Real-time push per customer and per team. |
What you'd have to retrofit onto a horizontal standard CRM – and find out of the box in e-health.CRM.
sell to regulated healthcare providers under German law.
run a large prospect base with structured campaign capabilities.
offer a self-service SaaS product with automated onboarding.
operate with a small team across service, marketing and sales.
require GDPR-compliant data handling with German data residency.
want their CRM tightly wired to website and customer-facing app.
e-health.CRM grew out of running our own healthcare product family and is in production use. For your context we set it up together and wire it to your website, app and channels – as a guided rollout, not a self-service download.
The prospect database is built on the German healthcare IK (institution identifier) codes. That lets you segment precisely by provider type – midwives, physiotherapists, outpatient nursing, therapists, health insurers – and combine it with Bundesland, funnel stage, software in use and engagement.
The customer-facing app consumes the e-health.CRM API. Trial registration creates a customer record, contract and communication room; verification, activation and payment mandate run through API endpoints; license, slots and billing are managed automatically. The path from trial to paying customer needs no manual CRM step.
Yes. The "current software" filter allows include/exclude by product in use. That lets you build targeted win-over campaigns – e.g. when a competitor raises prices or discontinues a feature – and prioritise warm leads within that segment via engagement history.
e-health.CRM is designed for the regulatory framework of healthcare providers in Germany: GDPR-compliant data handling with German data residency, double opt-in for newsletters and automatic suppression handling on objection.
Available: email inbound and outbound, click-to-call (VoIP), newsletter (double opt-in), app API and Matrix push. Planned: SMS/WhatsApp via a gateway for status updates and callbacks.
Send us your requirements catalogue – we'll walk through it row by row in a demo and honestly mark what's met, planned or not intended.