Skip to content

Dietitian CRM

The client's first measurement, the change in the third week and the revision made to the programme sit in separate notebooks; at the follow-up, the question "where did we start from?" is answered all over again every time.

Weight and circumference measurements are dated records on the client card, never overwritten; each revision of the nutrition programme is kept with its date; last session date is a field.

Dietitian CRM
  • Record each client's measurement history session by session and follow the change on a chart
  • Keep the nutrition programme and its revisions version by version on the client card
  • Track session packages, remaining consultation entitlement and payments from one place
  • Send appointment reminders and keep the client who did not turn up on a list
  • List the clients who have taken a two-week break and get in touch with them
Measurement RecordsEvery measurement is a dated record tied to the client card; the weight, circumference and body analysis fields are not overwritten, and because they accumulate, the change is read from the same card.
Programme and RevisionThe nutrition programme is a separate record tied to the client; every revision is kept with its own date, and what changed in which programme can be seen afterwards.
Package and Remaining SessionsThe package is a record; the total and used sessions sit in fields, the remaining entitlement is calculated from that record, and a reminder task opens before it runs out.
Meal DiaryThe meal form the client fills in turns into a dated record tied to the client card; at the follow-up session these records are read side by side with the measurement rows, and the programme revision rests on both.
List of Clients on a BreakThe last session date is a field; clients who pass the threshold are gathered with a filter. You set the threshold during setup.

In dietetics the result shows not in a single session but in the difference between sessions. When the measurements are written in one notebook, the programme in a file and the payment somewhere else, the question "where did we start from?" has to be answered again at every follow-up, and it becomes harder for the client to see their own progress.

Rapitek CRM keeps the measurement, the programme and the package under the same client record; because measurements are not overwritten, the change accumulates on the card. Since the last session date is a field, clients who have taken a break appear in a list before they are lost.

The scope of the plans and the separately priced items are written on the pricing page.

Frequently asked questions

How do I follow a client's measurement history?
Every measurement sits under the client card as a dated record. Because weight and circumference measurements are not overwritten, the change between the first session and today appears side by side on the same card.
Can I go back to earlier versions of the nutrition programme?
Yes. Every revision is kept as a separate record with its own date; which programme was given on which date and what changed stays in the history.
How much does a dietitian CRM system cost?
We keep the current plan prices in a single place and publish them openly on our pricing page; we do not put figures on this page, so that you do not read a different price in two places. The price is determined by the number of users and the plan chosen. The scope of setup, data migration and training is not the same in every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items.
How are CRM integrations done on the dietitian side?
If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection ourselves. There is no out-of-the-box module: because the access and field structure on the other side differs from installation to installation, a single button does not work the same way everywhere. The connection is set up specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and cost at the discovery meeting and share them in writing.
How does the move to a CRM system work on the dietitian side?
We start with a discovery meeting: we work out your client follow-up process, which fields and which stages are needed, together. After the meeting we give you a date, not a range. We migrate your data ourselves and we train your team in Turkish ourselves. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is not a matter of capacity, it is a choice.
Can a dietitian use a mobile CRM?
Yes. The field and branch team can update the customer card, the note and the follow-up task from a phone. The app is live on both the App Store and Google Play. The web interface also works on tablet and phone. The app does not work offline; if the connection drops while you are filling in a form, what you have written is kept on the device for 24 hours.
Made with RapitekGO

We would like to use optional cookies to measure your visit. The site works exactly the same if you decline. Cookie policy