# Rapitek > Rapitek CRM is a cloud CRM built in Istanbul. We do the setup; scope and any fee are agreed in writing. A separate database per customer, hosted in the EU. - Site: https://rapitek.com/en - Sitemap: https://rapitek.com/sitemap.xml - Index: https://rapitek.com/en/llms.txt - Format: grup=`## ` · bölüm=`### []()` · gövde başlığı=`#### ` ve derini · madde=`- ` · alan ayracı=` | ` ## Languages - tr: https://rapitek.com/llms-full.txt - ar: https://rapitek.com/ar/llms-full.txt ## Pages ### [Rapitek CRM | Cloud CRM Set Up Around Your Process](https://rapitek.com/en) Rapitek CRM is a cloud CRM built in Istanbul. We do the setup; scope and any fee are agreed in writing. A separate database per customer, hosted in the EU. For B2B sales and field teams of 5+ users #### Reps change. The customer history stays. Leads in a spreadsheet, chats in WhatsApp, quotes lost in email — that's where deals go missing. Rapitek CRM ties the three to one record: quote, correspondence and order in the same place, and they stay with the company when a rep leaves. We set it up around your process; migration, integrations and training are part of the rollout, and the scope is agreed in writing before we start. Book a demo See pricing Rapitek in numbers - 200+ | Enterprise CRM projects completed for other companies during our Salesforce era - 183 | Ready-made business objects: accounts, deals, quotes, invoices; all via API - 1:1 | A separate database per customer From our CRM projects ##### Organizations whose CRM projects we delivered. A selection from our CRM implementation and consulting projects. Logos belong to their respective owners. - Yıldız Holding - Akkök Holding - NETAŞ - MAPFRE Sigorta - Eureko Sigorta - Petroyağ - Sağlık ve Eğitim Vakfı - Iyzico - Aktif Filo - Eğitim Gönüllüleri - Hürriyet Projeland - V-Count Mobile app · iOS and Android #### The same CRM, in the field team's pocket. The mobile app is not a separate product: open opportunities, today's tasks and overdue work are read from the same records you see on the desktop. The WhatsApp inbox, the customer card, quotes and visit tracking all run inside the app, and Rapi writes records from speech. Published on the App Store and Google Play. See the mobile app ##### Powerful features, a clean interface. - Sales pipeline | Every lead and every stage on one screen. Drag-and-drop pipeline, your own stages, win probability, and team-level views. - WhatsApp shared inbox | Your team replies from a single number inside the CRM; every conversation is linked to the related contact, lead, or opportunity. - Built-in AI assistant | In the mobile app, Rapi creates and updates records by voice and turns a photo of a business card into a lead; it can be set to ask for your confirmation before saving. Rapi is off by default: unless you turn it on, your CRM data is not sent to any AI provider. - Reports and dashboards | Tabular and summary report types; a drag-and-drop dashboard designer, PDF and Excel export. - ERP and email connectivity | Connects to systems like Logo, Netsis, Mikro or SAP through REST API, OAuth2, webhooks and import/export, delivered by the team that builds the product. You connect your own Gmail account over OAuth for sending email and calendar sync; your inbox is not read. Outlook and Microsoft 365 are not available yet. - Separate database and access control | A separate database per customer, two-factor authentication (email code or authenticator), role-based access, and a field-level audit trail. Delivery ##### How we get you started. - Discovery | Together we map your sales process, your team structure, and the systems you use today. A 30-minute call is enough. - Setup and data migration | Fields, stages, roles, and reports are configured around your process; your existing data is migrated, and integrations are built in this step. The scope of setup — and any fee for it — is agreed in writing beforehand. - Training and go-live | We train your team ourselves. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range — data migration and training are part of that date. ##### Let's see how it would be set up for you. We listen to your process and map out which fields, stages and reports would be configured. Request a demo 30 minutes · No obligation · The call is held in Turkish From our Salesforce-era projects ##### What teams who worked with us say. - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Read the customer story - With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. | Ögetay Can | Sales Director | Petroyağ | Read the customer story - As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient. | Utku Aydın | Business Development Director | Iyzico The references above relate to CRM implementation and integration projects carried out by Rapitek; they do not mean that those organizations use the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### Who Rapitek CRM is not for. - Teams smaller than 5 users | Rapitek CRM starts at 5 users. The setup effort does not shrink as the team shrinks: fields, stages, roles and reports have to be built once, however many people will use them. Below that scale we do not think the model is right. If you only want to gather demand from a single channel, Inbox is a separate product; we can talk about that. - Anyone expecting self-service setup | There is no path where you sign up and set it up yourself the same day. We configure the fields, stages, roles and reports around your process, we migrate the data, and we do the training. - Anyone looking for a free plan | There is no free tier, and no trial you start yourself either. First a 30-minute demo, then discovery, then scope and price in writing. If you are looking for a path that moves forward without opening a budget line, this is not it. - Companies tied to app-marketplace add-ons | If your processes depend on add-ins installed from an app marketplace, or on your existing licence architecture, moving may not be right for you: we have no marketplace of our own and no trained partner network. We do not offer our own ecosystem; we offer an open REST API and integration built for the project. ##### Frequently asked questions. - What is Rapitek CRM? | Rapitek CRM is a cloud-based customer relationship management (CRM) application built in Istanbul by Rapitek Bilişim. Sales, marketing, and customer service teams manage leads, contacts, accounts, opportunities, quotes, invoices, and customer communication on a single platform. Each customer runs in its own separate database. - Who is Rapitek CRM for? | It is built for B2B companies with at least 5 users and a sales or field team — from SMB to enterprise. Especially sales and field teams that have outgrown Excel and WhatsApp groups. It is not a good fit for solo users, teams smaller than 5 users, or anyone expecting an instant, setup-free self-service product; we say that upfront. - How long does implementation take? | It depends on scope. What sets the timeline is not your team size; it is how ready your existing data is, the customization you need, and the scope of integrations. Because those vary from project to project, we do not commit to a timeline before discovery. We work out the scope together; after the discovery call, we give you a date, not a range. That date covers data migration, customization, integrations, and user training. - Can we explore the product ourselves? | There is no trial you start yourself by signing up. We begin with a 30-minute live demo on your own scenario: we walk through your sales process, your fields, and the reports you want to see, together on screen. Afterwards, if you would like to explore the product at your own pace, we open a time-limited demo account for you. The call carries no obligation. - How much does Rapitek CRM cost? | There are three tiers, all priced per user per month: Sales at 39 USD, Platform at 69 USD, and Enterprise from 119 USD. Each tier includes the one before it. Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 that mainly want to gather demand coming from a single channel, there is a separate starting point: Inbox, at 149 USD per company per month (up to 5 users). Prices are based on annual billing. The scope of setup — and any fee for it — is worked out in the discovery call and put in writing before the work starts. - Does it integrate with our existing ERP? | Rapitek CRM connects to Turkish ERPs such as Logo, Netsis, Mikro, and Paraşüt, and to global platforms like SAP, Oracle, and Odoo through REST API, OAuth2, webhooks and import/export, delivered by the team that builds and develops the product — it is not an out-of-the-box connector, and we define the scope together during the project. For your own systems, there is a REST API that covers the 183 business objects that ship in a standard install, OAuth2/JWT, and signed webhooks. - Where is my data stored? | Each customer gets its own separate database — separation at the database level, not a row filter in a shared table. Databases are hosted in the European Union (Helsinki, Finland) and media files in Frankfurt. A few sub-processors operate outside the EU; we name each one, and where it processes data, in our privacy policy. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK, Turkey's data protection law (No. 6698); we establish the basis for that transfer together during the contracting process. The product includes consent-evidence fields, a history of the field changes made to existing records, and data export; your KVKK and GDPR processes use them, but these tools do not meet your obligations by themselves. - How does support work? | There is no call centre on our support line. Your question is answered by the team that builds and develops the product — that is a choice, not a matter of capacity. Because the same team did your setup, you do not have to explain your case from scratch. We do not commit to a written response time (SLA); we do not put a time on the site that we cannot keep. - Can you support our teams in other countries? | Support is provided during Turkish business hours. If you have teams in other time zones, let's go through the scope together in the call. - The product is new. Why should we trust you? | The product is new; the team is not. Rapitek was founded in 2018 and has delivered more than 200 enterprise CRM projects. We ran those enterprise implementation projects in the Salesforce ecosystem, and that era has ended. The same team that builds the product does the setup, the data migration, and the training; support comes from that same team. If it doesn't work out, you can export your data and leave. ##### See the product on your own scenario. In a 30-minute live demo we show Rapitek CRM on your own sales process — a real screen, not a slide deck. Afterwards, if you want to explore at your own pace, we open a time-limited demo account for you. Book a demo A 30-minute call · No obligation · The call is held in Turkish ### [About Rapitek — 200+ Enterprise CRM Projects | Rapitek CRM](https://rapitek.com/en/about) Founded in 2018, we delivered 200+ enterprise CRM projects before building our own CRM. Based in Maslak, Istanbul; customer data hosted in the EU. About us #### We learned in the field, and built it for you. Across more than 200 enterprise CRM projects we saw the same problems over and over: expensive licenses, implementations that drag on for months, support lost in ticket queues, and a separate invoice for every customization. We built our own CRM to solve them. Request a demo Explore the product By the numbers - 2018 | Founded - 200+ | Enterprise CRM projects completed for other companies during our Salesforce era - Same team | The team that builds the product does the setup and answers support questions ##### We built other people's CRMs first Rapitek was founded in 2018. In our early years we did software development and IT consulting; after that we focused on enterprise CRM implementations and worked in the Salesforce ecosystem. We delivered more than 200 enterprise projects across manufacturing, retail, textiles, logistics, construction and healthcare: process analysis, data migration, custom development, integration and team training. That chapter has ended, and we hold no official Salesforce partnership today. We still provide independent Salesforce consulting — performance tuning, data migration, integration and security reviews. For official partner benefits, you would need to talk to Salesforce directly. ##### A small team. We say so on purpose. The scope of the platform sets an expectation: 183 business objects, iOS and Android apps, a messaging inbox, an open REST API. In our own discovery calls we have met companies who came expecting a large software company on the other side of the table; we have not counted how many calls those were, so we are not putting a figure on it. Let us state the truth up front — the team is small, the experience is large-scale. Our core team has never been a crowd. We ran holding-scale enterprise projects at this size, and we repaired other people's broken implementations at this size too. Today the same core does the product's architecture, its implementation, its integrations and its support. This is not an excuse; it is the source of our promise. If we can write the sentence “There is no call center on our support line. Your question is answered by the team that builds and installs the product,” we can write it because we are small. A company of hundreds cannot make that sentence work structurally: there, the person who greets you is not the person who wrote the product, and cannot be. The same applies to the implementation promise — the team that sets up your fields, stages and reports around your process is the team that writes the code behind those fields. What you get: a short decision chain, a counterpart who knows the work, and a party that can change the product itself. What you do not get: a support desk running in shifts, a roster of regional account managers, a headcount that would look impressive on a vendor evaluation form. Which of those is right for you is something we can work out together in the discovery call. ##### Why we built our own CRM Across 200 projects we learned this: there is a gap between what a growing business needs from a CRM and what the global platforms package for it. - Implementation takes months. A company decides to adopt a CRM and six months later it is still in configuration meetings. Meanwhile the team drifts back to Excel. - Customization is always a separate line item. Adding a field, adjusting a screen or building a report means either employing a certified administrator in-house or buying hourly consulting outside. - Support is far away. The team hits a problem, opens a ticket, and gets an answer days later from another continent — and not from someone who knows the product. - Pricing is unpredictable. The license is one number; implementation is another, integration another, training another. We wrote Rapitek CRM to fix these four things: customization done by us rather than billed to you by the hour, and support that comes directly from the team building the product. On timing we make no commitment before discovery; after the discovery call we give you a date, not a range. On price we leave no surprises either: whatever sits outside the plan price — including the scope of setup — is worked out in the discovery call and put in writing before the work starts. ##### What we are not When we describe ourselves, we prefer to state the limits too. - The product is new, the team is not. It is not a ten-year-old product — it is a new product written by the team that delivered more than 200 enterprise CRM projects. We don't hide that difference. - We are not a large software company. We are a small and senior team. We have no regional account manager roster and no call center running in shifts; the person you deal with is the person doing the work. - We are not self-service SaaS. If you are not looking for a tool you set up yourself in five minutes with a credit card, you are in the right place; if you are, you are not. - We are not a fit for teams smaller than 5 users. Implementation and training take the same effort on every project, and below that size the effort does not pay off. - We don't promise everything to every industry. In the discovery call we tell you plainly which of your needs the product covers in a standard install and which are project work. ##### How we work There is no call center on our support line. Your question is answered by the team that builds and installs the product — this is a choice, not a matter of capacity. There is no ticket system either, and because the team that did your implementation is the same team, you do not have to explain your situation from scratch; you reach them directly over WhatsApp. In practice we reply the same working day. We deliberately put no number on that and make no written response-time (SLA) commitment: we have no system measuring ticket times yet, and we do not publish a duration we have not measured. The day we measure it, we will write it here. Support is provided during Turkish business hours; if you have teams in other time zones, let's work through the scope together on the call. Built for teams operating in Turkey. The mobile app ships with a Turkish interface and the voice assistant Rapi understands and writes Turkish; training, documentation and support are in Turkish too. Rapi is off by default; unless you turn it on, your CRM data is not sent to any AI provider. The database is hosted in Helsinki, Finland, media files in Frankfurt and database backups in Falkenstein, both in Germany; a few sub-processors operate outside the EU, and we name each one, with where it processes data, in our privacy policy. The technical measures are listed one by one on our security page. We do the setup. Fields, stages, roles, reports and integrations are configured to your process — by us. You don't need to hire a CRM administrator, and when changes are needed after go-live, we make them too. Founder #### Kerim Yıldırım Founded Rapitek in 2018. During our Salesforce era he worked on more than 200 enterprise CRM implementations, and that field experience is what shaped the product's architecture. He writes the posts on the blog, and he is the person you meet in the demo call. From our CRM implementation projects ##### The teams behind those projects, in their own words. - With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. | Ögetay Can | Sales Director | Petroyağ | Case study - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Case study - As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient. | Utku Aydın | Business Development Director | Iyzico | Case study - Our foundation needed a cloud-based software system for data management. Rapitek is a company that is careful and attentive in understanding our wishes and needs; they also translated our requirements into the system very well. When we have new requirements, they support us with extremely fast and thorough solutions. As SEV, we are highly satisfied with working with Rapitek. | Meryem Boğa | Project and Resource Development Manager | Sağlık ve Eğitim Vakfı | Case study - The most important element of bringing new business ideas to life is your IT infrastructure and applications. Rapitek offered much more than just providing an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during the development process, we reached our first product quickly and ensured healthy project continuity. | Denizhan Edeer | CEO | Aktif Filo | Case study - As a newly established company aiming to make rapid progress, we realized we needed an overall infrastructure for sales management, team tracking, and inventory management. With that need, we started the project with Rapitek, and we are still continuing our work together today. Rapitek is truly a solution partner. | Ceren Karaman | Operations Manager | Hürriyet Projeland | Case study From 200+ CRM implementation and consulting projects ##### Some of the organizations we have worked with. We delivered CRM implementation and consulting projects for these organizations; the list does not indicate that they use Rapitek CRM. Logos belong to their respective owners. - Yıldız Holding - Akkök Holding - NETAŞ - MAPFRE Sigorta - Eureko Sigorta - Petroyağ - Sağlık ve Eğitim Vakfı - Iyzico - Aktif Filo - Eğitim Gönüllüleri - Hürriyet Projeland - V-Count - Genç Hayat Vakfı - Alapros - Elab - Klassis - Anadolu Flygt Xylem - Life Fitness - Akcoat - Trucas - Tazi.ai - ELS - QTerminals - Anatolia Tile ##### See the proof behind the story Anatolia Tile, the SEV Foundation and Petroyağ — CRM implementation projects we ran during our Salesforce years, told in our customers' own words. Read the customer stories Three case studies, with their sectors and scope. Frequently asked ##### Frequently asked questions about Rapitek - Is Rapitek a Salesforce partner? | No. We worked as an official partner in the Salesforce ecosystem and completed more than 200 enterprise projects in that era; that partnership has ended. We have no current Salesforce partnership. We still provide independent consulting on Salesforce implementations — performance tuning, data migration, integration and security review — but for official partner benefits you need to talk to Salesforce directly. - What does "more than 200 CRM projects" actually mean? | That number refers to enterprise CRM implementation projects we delivered for other companies during our consulting era: process analysis, data migration, custom development, integration and team training. It is not the number of Rapitek CRM installations. The product is new and is building its own user base. We keep those two things deliberately separate. - When was Rapitek CRM released? How mature is the product? | Rapitek CRM is a new product. Not a ten-year-old product — a new product written by the team that delivered more than 200 enterprise CRM projects. The product being young and the team being experienced are two different things, and we would rather you did not conflate them. - Where is my data stored? | In the European Union. The database runs in Helsinki, Finland and media files are stored in Frankfurt, Germany, with a separate database for each customer. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. Data is not stored in Turkey, and we say so plainly. - Do you hold ISO 27001 or SOC 2 certification? | No. As of today we hold no such certification and we do not claim otherwise. The concrete measures we do apply: a separate database per customer, current TLS in transit, two-factor authentication and a field-level audit trail. - Who is Rapitek not a good fit for? | Teams smaller than 5 users. Setup and training take the same effort on every project, and below that size the effort does not pay off. We are also not self-service SaaS: if you want a product you can configure yourself in five minutes with a credit card, this is not it. There is no trial you start yourself; after the call we can open one depending on what you need — we begin with a demo built around your own scenarios. ##### Company details Rapitek Bilişim Teknolojileri Anonim Şirketi (Rapitek Information Technologies Inc.) Maslak Mah. Büyükdere Cad. Nurol Plaza Sit. No: 255/B02 34485 Sarıyer / Istanbul, Turkey MERSIS (Turkey's central trade registry) no: 0734159061600001 WhatsApp: +90 212 963 22 84 Email: info@rapitek.com ##### Tell us about your process. A 30-minute discovery call is enough to find out whether we are the right solution for you. And if we are not, we say so. Request a demo Free, with no obligation ### [Anatolia Tile Customer Story | Rapitek CRM Projects](https://rapitek.com/en/anatolia-tile-customer-story) How a global ceramics and natural-stone manufacturer brought customer relationships, sales and logistics onto one platform. Customer story · Manufacturing #### Anatolia Tile: sales and logistics met on the same screen. A global player in ceramics, porcelain and natural stone since 1995. Growing export volume made it necessary to manage customer relationships and logistics in a single system. Let's talk about a similar rollout Other customer stories The company - 1995 | Founded - Istanbul | Headquarters - Global | Ceramics, porcelain and natural stone market - Enterprise | Project scale The project ##### What was there, what we built, what changed. - The challenge | Leadership in a global market, a distinctive logistics service and a customer-first approach — all three were only sustainable if every process was managed on one platform. Sales, customer relationships and logistics each sat somewhere else. - What we built | The platform was customised around the company's process: customer relationship management, sales processes and logistics operations were brought into one system. Custom modules and reporting were built to support their customer-satisfaction-first approach. - The result | Customer data came together on a single platform; sales rates and growth volumes can now be read from a report. Customer requests are answered faster and decisions are made more quickly. In the customer's own words ##### What the Anatolia Tile team said - The active role we play in the global market and our strategies created the need to work with a solution partner who could accelerate our adaptation to a changing world and lighten our workload. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile - We can store all of our customers' information and active data securely. We gained momentum in our work-tracking process and in our customer relationships, and we work in a more organised way. In areas such as sales rates and growth volumes in particular, we can carry out detailed research and interpret the statistics more accurately. | Meryem Koç | Assistant Marketing Specialist | Anatolia Tile Scope ##### What was built in the project? Scope is project-specific; in every rollout it is defined together in the discovery call. Area | What was done - Interface design | The screens the team uses daily were simplified around the company's process - Customer tracking | Customer information and history were brought together on a single record - Opportunity management | Pipeline stages and win probability were defined - Activity and team tracking | Who is doing what with which customer was made visible - Logistics operations | Shipping and delivery processes were connected to the same system - Reporting | Custom reports were built for sales rates and growth volume ##### This project belongs to our Salesforce era This implementation belongs to Rapitek's Salesforce implementation era; afterwards we built our own product, Rapitek CRM. The method described here — listen to the process, migrate the data, train the team — comes from the same team; we simply apply it on our own platform now. ##### How would your sales and logistics process be set up? In a 30-minute discovery call we listen to your process and work out together which fields, stages and reports would be configured. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Auto Parts CRM: Dealer and Wholesale Sales | Rapitek CRM](https://rapitek.com/en/auto-parts-crm) OEM and cross-reference codes and vehicle fitment are fields on the product record; enquiry-to-quote pipeline, dealer price lists, lost-sale reports. Industry solution · Auto Parts #### CRM for auto parts dealers, wholesalers and retailers Vehicle details, stock enquiries, quotes and dealer price lists in one system. Run your wholesale, retail and B2B dealer channels as separate processes — it is configured around your own processes, and we do the setup. Request a demo Talk to an industry consultant ##### In auto parts, when an enquiry is never recorded, its outcome cannot be measured Stock and invoicing are already handled by a separate program in your business. The place that bleeds is the space between the enquiry and the sale: who asked for what, which vehicle they were looking at, whether a quote went out, and why it was not taken. Here is the picture we have seen again and again in our own CRM projects: - The day goes by on the phone; “do you have this part for that vehicle?” enquiries stay on the phone and in the salesperson's personal WhatsApp. When an enquiry is never recorded, its outcome cannot be measured: whether it was bought, or bought somewhere else, nobody knows. - When the same garage calls for the third time, the vehicle details are asked all over again; which customer works on which vehicles lives in the salesperson's memory. - The quote is in Excel or in a chat bubble; nobody keeps track of which quote never got a reply. - Dealer discounts are in the salesperson's head; because the discount table is not recorded anywhere, there is no check that catches it when a price is given from the wrong list. - The account balance sits in the accounting program; when the salesperson quotes, they do not see the customer's payment terms or credit risk. None of this is solved by a new stock program. It takes record-keeping discipline and properly configured fields — which is exactly what a CRM is for. A concrete scenario ##### Tuesday 09:40 — a garage calls: “Front pads and discs for a 2016 diesel Focus, needed today.” - The enquiry becomes a record while the call is still on | The calling garage is matched to its account record; the enquiry is opened as an opportunity tagged with its source (phone, WhatsApp). It is written into the sales pipeline, not into a notebook. - Vehicle details are stored as fields | Make, model, year and engine type are held as separate fields, not as free-text notes. When the same garage calls again, the vehicle is not asked for a second time; past enquiries stay on the record. - The part is found from the OEM or the cross-reference code | Because the product record holds the OEM number, cross-reference codes and vehicle fitment details as fields, search and filters work on those fields. If your ERP is the master source for stock quantities, it can feed the CRM through the flow defined during setup. - The quote goes out as a PDF from the price list | The price comes from the price list the customer is attached to; the discount is visible on the record. The PDF quote is sent over WhatsApp from the office's single business number, and the conversation is logged on the customer record. - An unanswered quote waits in the pipeline instead of being forgotten | Every quoted enquiry stays in the pipeline as an open opportunity; a follow-up task and a reminder are set. The answer to “who did we quote yesterday, and who never came back?” is on screen as a list. - The outcome is closed with a reason | If the sale happens, the quote turns into an order; if not, a closing reason such as “it was out of stock” or “the price was too high” is selected. At month end, a report shows how many enquiries were lost in which part group, and why. ##### The building blocks we set up for auto parts teams - Customer and account records | Garages, dealers, fleets and retail customers are held as separate records. Account details such as payment terms, due dates and credit limits are modelled as fields on the record; the salesperson sees them while quoting. The official source of the account statement stays in your accounting program. - Vehicle and part fitment data | The product record holds the OEM number, aftermarket (cross-reference) codes and vehicle fitment details as fields; search and filters work on those fields. There is no magic here: properly configured fields and correct data imported from your own catalogue. - Quotes and orders | Price list, discount, PDF generation and conversion into an order in a single flow. Multiple currencies are supported; exchange rates are pulled automatically from the Central Bank of Türkiye (TCMB) every day — no manual rate arithmetic when you price imported parts. - B2B price lists | Separate price lists are set up by dealer group, customer segment or channel. Which customer is priced from which list is configured — the discount table that lived in the salesperson's head moves into the system. - WhatsApp from a single number | All salespeople write from the company's single business number; messages land in a team inbox and are logged on the customer record. The connection we recommend and set up is Meta's official WhatsApp Cloud API. We do not present QR-code pairing as a product promise: it is not Meta's official API and risks the number being restricted by Meta; if that happens, your business number is shut down. - Demand and lost-sale reports | Which part group is in demand, which enquiries were lost and why, how many quotes and how many closes per salesperson — with tabular and summary reports and a drag-and-drop dashboard designer, without writing code. Matrix and joined report types are supported as well. ##### At the counter, in the warehouse, and with the software you already run ###### Mobile at the counter and in the field Both our iOS and Android apps are live and ship with a Turkish interface; while checking a part in the warehouse, the salesperson can update the customer record, the quote and the follow-up task from their phone. Rapi, the voice assistant in the mobile app, creates and updates records in the CRM through spoken Turkish. WhatsApp messages are handled in a single inbox inside the app — an incoming enquiry can be answered while the salesperson is at the counter or on the road. Instagram direct messages land in the same inbox. Details are on the mobile app page. ###### Connecting to your accounting and ERP software Rapitek CRM does not replace your stock and accounting program; it adds a customer relationship layer on top of it. The connection to your accounting or ERP program is built as follows: over REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data flows in which direction, and how often, we define together during the setup stage. The details of the approach are on the integrations page. There is no out-of-the-box module — it would not be right to say there is. Because access differs from one installation to the next, there is no single button that works the same way in every installation; the connection is a scoped integration job and is planned as part of the setup. If you also sell tyres, or if you have a sales team out on the road, similar flows apply to those channels as well. Division of labour ##### Stock program or CRM? Both. Rapitek CRM does not replace your accounting and stock software; it adds the customer relationship layer on top. The data flow between them is built with APIs and import/export. Layer | What it does - Accounting / ERP / stock program | Stock quantities, purchase and sales invoices, account statements and official records - Rapitek CRM | Customer and vehicle details, the pipeline from enquiry to quote, dealer price lists, WhatsApp conversation history, lost-sale reports - The connection between them | REST API, OAuth2, webhooks and import/export; the scope is defined during setup with the team that builds and develops the product Verifiable numbers ##### Measured data, not a marketing line - 200+ | Enterprise CRM projects delivered during our Salesforce era (before Rapitek CRM) - 277 | Custom fields added by 19 tenants without writing code - Every 6 hours | Automatic backup frequency; backups are copied to a separate country - 183 | Business objects in the REST API — each with a data and a schema endpoint - EU | Data location: Helsinki (Finland), media in Frankfurt, backups in Falkenstein Implementation ##### How is a CRM rolled out in an auto parts business? - Discovery and analysis | We map out your part groups, your sales channels (wholesale, retail, B2B dealer), your price list structure and your account flow. This is where we decide which fields you actually need. - Configuration | Customer and vehicle fields, the product catalogue, pipeline stages, price lists, the permission matrix and reports are set up around your process. No code is required; setting it up well takes expertise, and that part we do ourselves. - Data migration | Customer, vehicle and product records from your Excel files or from your current system are imported, and duplicate records are cleaned out. - Training and go-live | Training for salespeople and managers, close follow-up in the first week, and continuous support after that. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. From our CRM implementation projects ##### What do the teams we work with say? - The most important element in bringing new business ideas to life is your IT infrastructure and your applications. Rapitek offered far more than simply supplying an application - they became our solution partner. Thanks to their fast responses in unexpected situations and their flexibility during development, we reached our first product quickly and kept the project running soundly. | Denizhan Edeer | CEO | Aktif Filo - With Rapitek's solution-focused approach, we began the work needed to complete the improvements to the Salesforce customisations and integrations we were using quickly. With those improvements, duplication of data was prevented and we increased the efficiency of the system. | Ögetay Can | Sales Director | Petroyağ | Case study - As a newly founded company that wanted to make fast progress, we realised we needed a general infrastructure for sales management, team tracking and inventory management. With that need, we started the project with Rapitek, and we are still working together today. Rapitek really is a solution partner. | Ceren Karaman | Operations Manager | Hürriyet Projeland The references above relate to CRM implementation and integration projects carried out by Rapitek; they do not mean that those organisations use the Rapitek CRM product today. Brand names, logos and titles belong to their respective owners. ##### Data location, KVKK and security — as it is In the auto parts business, customer data is a trade secret: your customer list, your discount rates, your account terms. That is why we speak plainly here. - Your data is held in the European Union. The database is in Helsinki (Finland), media files in Frankfurt, and backups in Falkenstein (Germany). We do not say that the data is held in Türkiye, because it is not. - Under Article 9 of the KVKK, this counts as a transfer abroad. That is why a privacy notice is presented on our forms; the basis for the transfers in your own processes is something we establish together during the contract stage. - TLS is used in transit. Passwords are hashed one-way; two-step verification secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. A separate database is used for each customer. - Role-based permissions are in place; which salesperson sees which customer group and which price list is defined. We do not hold an information security certificate, and we do not claim to. Every technical detail we state has its counterpart in the system; we answer your security questions in writing before setup. ##### We put the number on the pricing page, not on this one The scope of setup, data migration and training is not the same in every project; it is shared in writing after discovery. Plan prices we keep in one single place — so that you never read two different numbers in two places. See pricing Three plans, the scope table and the separately priced items, all on one page. FAQ ##### Frequently asked questions about CRM in the auto parts industry - What is an auto parts CRM? | An auto parts CRM is customer relationship software that brings customer and vehicle details, incoming stock enquiries, quotes, orders and dealer price lists together in one place. It does not replace your stock and accounting program; it builds the follow-up layer between the enquiry and the sale. Rapitek CRM configures that layer around your process and takes it live. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. - How is vehicle-to-part fitment tracked? | We do not offer an out-of-the-box vehicle-to-part fitment database; it would not be right to say we do. The source of the fitment data is your own catalogue: the product record holds the OEM number, cross-reference codes and vehicle fitment details as fields, and that data is imported during setup. After that, search and filters work on those fields; the salesperson lists the suitable parts for a given vehicle. - Can OEM and aftermarket (cross-reference) codes be tracked? | Yes. On every product record, the OEM number and the cross-reference codes are held as separate fields; search and list filters work on those fields. Whichever code the customer quotes, you reach the same part. Which code fields are created, and how your catalogue is migrated, we decide together during the setup stage. - Does it do stock tracking? | Two set-ups are possible. If your accounting or ERP program is the master source for stock quantities, that source does not change; the data is fed into the CRM over REST API, webhooks and import/export, through the flow defined during setup. If you have no separate stock source, the inventory and stock movement objects come with the standard installation and you can build the tracking directly in the CRM — but today we cannot point to a live installation to describe stock execution. Which set-up fits you, we decide together in the discovery call. - Does it connect to our accounting or ERP program? | On the ERP or accounting side, there is no out-of-the-box module. The connection is built as follows: over REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data flows in which direction, and how often, we define within the scope of the setup. - Can account balances and payment terms be tracked in the CRM? | The CRM does not replace accounting; the official source of the account statement stays in your accounting program. On the CRM side, details such as payment terms, due dates and credit limits are modelled as fields on the customer record, and the salesperson sees them while quoting. If you want it, summary balance information can be fed from the accounting side through an API flow defined during setup. - Can we define prices and discounts specific to our dealers? | Yes. Separate price lists are set up by dealer group, customer segment or channel; which customer is priced from which list is configured. On a quote, the price comes from the right list and the discount applied is visible on the record. We build the list structure together during setup, around your own discount model. - Can we run wholesale and retail sales as separate processes? | Yes. Rapitek CRM supports more than one sales process; you can run the wholesale, retail and B2B dealer channels with separate stages, separate fields and separate reports. Which channel moves through which process, and the permissions, we decide together during setup. - Can several salespeople use the same WhatsApp number? | Yes. With the WhatsApp integration, salespeople can write from the company's single business number. Messages land in a team inbox and are logged on the relevant customer record; managers can see the conversations. Even if a salesperson leaves, the history stays with the company. The connection we recommend and set up is Meta's official WhatsApp Cloud API. Pairing a phone by QR code is also possible, but we do not present it as a product promise: that method is not Meta's official API and carries the risk of the number being restricted by Meta; if that risk materialises, your business number is shut down. - Is there a mobile app for use in the field and at the counter? | Yes. Both our iOS and Android apps are live and ship with a Turkish interface; the salesperson can update the customer record, the quote and the follow-up task from their phone while in the warehouse or on a customer visit. Rapi, the voice assistant in the mobile app, creates and updates records in the CRM through spoken Turkish. WhatsApp and Instagram messages are handled in the same single inbox in that app; replying to Instagram from the mobile app has not yet been measured in a customer deployment. - Can we see the product before we buy it? | There is no trial you can start on your own. First we run a live 30-minute demo; then, if you want to explore the product at your own pace, we open a time-limited demo account for you. In the demo we show the product live on your own scenario and answer your questions there. Configuration specific to your industry and your process is done after purchase, during the setup stage. - How long does setup take and what is included? | We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. Setup consists of these steps: discovery and analysis, configuration, data migration from Excel or from your current system, team training and go-live. The duration depends on the number of branches, the size of the catalogue and the scope of the integration. The scope of the setup, and its cost if any, is worked out in the discovery call and shared in writing before work starts; for the plan structure you can look at the pricing page. - Where is our data held? | The database is held inside the European Union, in Helsinki (Finland); media files are stored in Frankfurt and backups in Falkenstein (Germany). Under Article 9 of the KVKK this counts as a transfer abroad; the basis is established according to the tiers in Article 9 — first an adequacy decision, failing that appropriate safeguards, and exceptionally the incidental cases. TLS is used in transit and a separate database is kept for each customer. ##### Related solutions - Tyre CRM | For tyre dealers: stock, seasonal swings in demand and customer follow-up. - Field Sales Software | Dealer visits, route plans and performance reports for the field team. - Luca Integration | The accounting side: the data flow between Luca and the CRM. ##### See your parts sales flow live In a 30-minute demo, let us show you enquiry capture, the vehicle and part fields, quote generation and dealer price lists on your own scenario. Request a demo The scope of the setup, and its cost if any, is worked out in the discovery call and shared in writing. ### [Blog — CRM, sales process and customer management | Rapitek](https://rapitek.com/en/blog) Field notes from enterprise CRM implementations: process setup, pipeline tracking, integration decisions and the questions worth asking before you choose a CRM. Rapitek Blog #### Written for the teams who actually use the CRM What we see inside enterprise CRM projects: process setup, pipeline tracking, team habits, and the questions worth asking before you choose a system. ##### What you'll find here The Rapitek blog is written for teams moving their customer relationships into software for the first time, or rebuilding a setup that stopped working. Most of our readers are sales managers, operations leads and owners of companies that are growing faster than their processes. These are not product brochures; they are notes on how a specific problem got solved. Most posts start from a concrete question: why quotes fall out of sight, where inbound WhatsApp requests disappear, why reporting breaks once you open a second branch, which clauses matter in a CRM contract. We describe what we ran into across more than 200 enterprise CRM implementations delivered during our Salesforce era, without translating it into marketing language. Recurring topics: CRM rollout and data migration, sales process design, quoting and pricing, customer communication over WhatsApp, reporting, and getting a team to actually adopt the tool. Posts are written by our founder, Kerim Yıldırım. ##### Latest posts ##### Want to see your own process on screen? In a short demo we'll map your sales flow together and talk through how any of this applies to your business. Request a demo Your question is answered by the team that builds and develops the product. ### [ChatGPT Integration: CRM and REST API | Rapitek CRM](https://rapitek.com/en/chatgpt-integration) Connecting ChatGPT to a CRM runs through an open REST API and OAuth2; that surface is live today. The product's assistant Rapi runs on Anthropic Claude. Integration · ChatGPT #### If yours is a team that uses ChatGPT, you can connect it to your CRM. The surface the connection will rest on is live today: a REST API authorized with OAuth2, describe that returns the object schema, composite that carries 25 sub-requests in a single request, and bulk endpoints that handle up to 200 records per call. We build it as an integration project whose scope is defined in the discovery call. Request a demo Schedule a discovery call ##### The team works in ChatGPT, the record sits in another window If your team no longer uses ChatGPT as an experiment — the subscription has been bought, the team has settled in, most of the work runs in that window — then the CRM is sitting somewhere else during the same day. The mechanism is this: with no defined link between the two windows, a human does the transfer, and the moment it flows across, the origin of the record is lost. Three outcomes we have seen in our own projects and in our buying conversations: - Data is moved by copy-paste. The summary is produced in ChatGPT, then pasted into the CRM by hand; where the record came from and who produced it are lost. - In the procurement meeting someone asks, “Is your CRM AI-powered?” Saying “yes” is easy; once they ask with which model, under what authorization and where the data goes, the answers get blurry. - IT asks something else: which data goes to which provider, who turned it on, can it be revoked? The answer to that question can be left to the contract stage — that is, to the worst possible moment. This page answers all three openly — and on one of them it answers against our own interest. First what there is, then what has been measured, then what has not been measured. A page that does not write the third one teaches it to the buyer on installation day. ##### First the sentence against our own interest: this product's assistant runs on Claude There is no out-of-the-box module for ChatGPT, and we are not going to say there is. The connection is built as an integration project — with REST API, OAuth2, webhooks and import/export — whose scope is defined in the discovery call. Now the thing that really needs saying. Rapi, the assistant inside the product, runs on Anthropic Claude — not on GPT. That is why you will not read the sentence "GPT-powered CRM" on this page; writing it would help us in search results, but it would not be true. With the same care: our 18-tool MCP package, downloaded from the Setup screen, is defined today as a Claude connector. We cannot say it has been tested with any other AI client; and because we have not tested it, we do not say it. Setting out these two sentences up front ends the "but the website said so" conversation before it can start after purchase. So what is actually there? The way to connect ChatGPT to the CRM runs through the product's open surface, and that surface is live today: the product ships with 183 business objects and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there is authorization with OAuth2, composite carrying 25 sub-requests in a single request, and bulk endpoints that handle up to 200 records per call. That is exactly what an AI client needs in order to be able to look at the CRM. Which connection route is used on the ChatGPT side — depending on the client's capabilities at the time and on your subscription type — is chosen together during discovery. We can say that this surface really is usable from outside on the strength of a measured fact: in one live customer installation, a third-party ERP integrator reads and writes records over this same REST API. We do not give a name because we do not have permission to publish it; what we are saying is a measured fact, and this is a single installation, not a list of cases. We have described the product's own assistant and the MCP package on the Claude integration page, the same framework inside an ERP on the Netsis integration page, and our general approach on the integrations page. A concrete scenario ##### Thursday 14:25 — a rep is preparing for a meeting. Once the connection is in place, this is what changes: - Data is not copied, it is called | Once the connection is in place, the client reads customer, contact and opportunity records from the API. The copy-paste step in between disappears; which record an answer rests on becomes clear. - Authorization comes from OAuth2, not from a person | Access is granted with OAuth2; no user password is shared. You define the scope, and you can take it back the way you granted it — from a single screen. - The schema is not tracked by hand | The object schema is read from the describe endpoint. When you add a new field to the CRM, the connection code does not have to chase after it; what it reads changes along with it. - Write access is a separate and deliberate decision | Reading and writing are not the same thing. Which objects get write access is written out one by one in the scope; we do not grant access that is open to everything by default. - Changes to existing records leave a trace | Changes made over the API to existing records land in the field-level change history: when which field moved to which value (for protected fields, only a marker). A newly created record's initial values are not recorded there. An assistant coming from outside does not skip the audit trail. - The relationship with the provider stays in your name | You use your own ChatGPT subscription; the contract on that side is between you and your provider. We do not sell tokens, credits or models in between. ##### The surface the connection rests on — the part that is live today - 183 business objects, each with its own endpoint | The product ships with 183 business objects and each one is published in the REST API with its own data and schema endpoint — from lead to quote, from invoice to task. You can read the field structure from outside with describe. - Authorization with OAuth2 | Access is granted with OAuth2. No integration is built by sharing a user's password; authorization is taken back the way it was granted. - Schema reading with describe | The object schema is read from the API. Custom fields the tenant adds without writing code also appear in that schema; the connection stays current. - composite and bulk endpoints | Several operations are sent in a single request — composite carries 25 sub-requests; bulk endpoints handle up to 200 records per call. - Change history covers changes made over the API as well | Changes made over the API to existing records land in the field-level change history. A newly created record's initial values are not recorded there; the creator (the user the API client is bound to) and creation time are set by the system and cannot be changed from the user screens, data import or the API. The fields the AI changed on existing records can be seen one by one afterwards. - A separate database per tenant | Your CRM data is held in a separate database that belongs to you; access arriving over the API also stays inside that boundary. Measured and not measured ##### What was measured, what was not? There are two separate things on this page: the REST API surface that is live today, and the ChatGPT side, which we have not measured. We deliberately do not put the two in the same sentence. Topic | Where it stands today | What that means - The assistant inside the product | Rapi runs on Anthropic Claude; it reads and writes CRM records | We make no claim of a “GPT-powered CRM”; we write down which model we run on, by name - MCP package — 18 tools | It is defined today as a Claude connector and is downloaded from the Setup screen | We have not tested the package with ChatGPT; and because we have not tested it, we do not say it - REST API + OAuth2 | Live; each of the 183 business objects that ship out of the box is published with its own data and schema endpoint, and describe and composite are supported | This is the surface a ChatGPT connection will rest on, and it works today - The connection route on the ChatGPT side | It depends on the client's capabilities at the time; we have no measured record of it | The route is chosen together during discovery; we do not ship an out-of-the-box GPT or plugin - Where the data goes | You use your own ChatGPT subscription | The contract on that side is between you and your provider; we do not sell tokens or credits in between What we can say ##### What we have verified - 183 | business objects in the REST API; each with its own data and schema endpoint - 25 sub-requests | operations the composite endpoint carries in a single request - 200 records | records the bulk endpoints can process in a single call - Claude | The model family that Rapi, the assistant inside the product, runs on - Not tested | Whether the MCP package works with ChatGPT has not been measured to date Implementation ##### How is the connection brought live? - Discovery | We work out how you use ChatGPT today, which subscription type you are on, and which records you want to look at in the CRM. We recommend that your counterpart on the IT and compliance side is in this call. - Scope and authorization table | Which object gets read access and which gets write access is written out one by one. Which provider the data will go to, and what that means in terms of transfer abroad, sits in the same document. - Configuration and a limited start | OAuth2 access is defined and the connection is opened with a narrow scope. We recommend limiting the initial scope to reading only; write access is widened after the team's flow has been seen, and at your decision. - Training, auditing and go-live | The team is shown how to follow the assistant's work through the change history. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. ##### Our limits: what we do not promise on this page AI is an easy headline to overstate, and an expensive one. We write down what we do not promise, by name. - We do not say “GPT-powered CRM”. Rapi, the assistant inside the product, runs on Anthropic Claude. That sentence would help us in search results; we do not write it because it is not true. - We do not say that our MCP package works with ChatGPT. The package is defined today as a Claude connector and we have not tested it with another client. If you want to connect another assistant, the route is REST API and OAuth2; that is a separate piece of work whose scope is defined in discovery. - We do not ship an out-of-the-box GPT or plugin. There is no listing from us in the store. - We do not sell an autonomous agent. The number of steps that can be taken in a single request in the product's own assistant is limited — at most eight. We do not offer a system that runs on its own through the night. - We do not promise that your stock will stay in sync, that the order → invoice → collection chain will flow by itself, or production/MRP automation. Connecting an assistant does not change those three. We have written the reason for all three, and what can be done instead, in one place: the three things we do not promise. AI and consent: the product's own assistant is off by default; unless you turn it on, your CRM data is not sent to any AI provider. When you connect your own ChatGPT client, that decision is yours, and we define its scope in writing at setup: which object, which permission, which user. Seen from Turkey this is a transfer abroad and falls under Article 9 of Law No. 6698; we establish its basis together during the contract process. Our sub-processor list is on our security page. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Turkey and we have no region-selection feature. The detail is on the security page and in the KVKK privacy notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### Plan prices are published; scope comes out of discovery The scope of a ChatGPT connection — and any fee for it — comes out of the discovery call. We publish plan prices, and separately priced items such as Rapi AI credits, on a single page. See pricing Three plans, a scope table and separately priced items, on one page. FAQ ##### Frequently asked questions about the ChatGPT integration - Can we connect ChatGPT to Rapitek CRM? | You can, but not with a provider-specific module of ours. The route runs through the product's open surface: a REST API authorized with OAuth2, schema reading with describe, composite and bulk endpoints. That surface is live today. Which connection route is used on the ChatGPT side is chosen together during discovery, according to the client's capabilities at the time, and the scope is shared in writing. - Is Rapitek CRM a “GPT-powered” CRM? | No, and we prefer to write that plainly: Rapi, the assistant inside the product, runs on Anthropic Claude. The sentence “GPT-powered CRM” does not appear on this page because it is not true. Asking which model an AI feature runs on is the right question; we write the answer down before it is asked. - Do you provide a ready-made Custom GPT or plugin? | No. We do not ship an out-of-the-box GPT or plugin; there is no listing from us in the store. What we give instead is a documented REST API and OAuth2 access; the connection is built on top of that, as a project whose scope is defined in discovery. If such a package is critical for you, say so in discovery and let us assess the scope together. - Does your MCP package work with ChatGPT as well? | Because we have not tested this, we cannot say it works. The 18-tool package downloaded from the Setup screen is defined today as a Claude connector. If you want to connect another AI client, the route we trust is REST API and OAuth2; that is a separate piece of work whose scope is defined in discovery, and it is priced that way. - Which model does the product's own assistant run on? | Anthropic Claude. Rapi does not only read the CRM, it writes records too: it fetches, creates and updates core records such as leads, contacts, companies and opportunities. The number of steps that can be taken in a single request is limited — at most eight — so it is not an agent running on its own in the background. The detail is on the Claude integration page. - Will we be using our own ChatGPT subscription? | Yes. You use your own ChatGPT subscription; we do not sell tokens, credits or models in between. The practical consequence is this: the contract, the terms of use and the invoice on that side are between you and your provider. We apply the same approach on the WhatsApp and SMS side, which is why we can give a consistent answer. - If the connection is set up, can ChatGPT write records to the CRM? | As much as the authorization you grant. The REST API supports both reading and writing records; which objects get write access is written out one by one in the scope. The start we recommend is a narrow scope: reading only first, writing after the team's flow has been seen. We do not grant access that is open to everything by default. - How do we audit the changes the assistant makes? | From the field-level change history. Changes made over the API to existing records land in that trail as well: you can see when which field moved to which value (for protected fields, only a marker). A newly created record's initial values are not recorded in it; the creator (the user the API client is bound to) and creation time are set by the system and cannot be changed from the user screens, data import or the API. An assistant coming from outside does not use a separate route that skips the audit trail. - Does our CRM data go to OpenAI? | It does not go there unless you set up the connection; there is no flow inside the product that goes to OpenAI. Once you set the connection up, the records within the scope you granted your client go to the provider through your own ChatGPT account. Seen from Turkey this is a transfer abroad and falls under Article 9 of Law No. 6698; we establish its basis together during the contract process. - Is the AI assistant on by default? | No, it is off. The assistant inside the product is off by default and is switched on per tenant; unless you turn it on, your CRM data is not sent to any AI provider. We built it this way not as a marketing choice, but to leave the transfer decision to you. The detail is on our security page. - Why is the product's assistant not ChatGPT? | Because that was our choice when we built the product, and this is the model family whose results we have measured. It would have been easy to write a sentence like “it works the same way whatever the model”, but we have no measurement for that. If what is critical for you is the team using ChatGPT from its own window, the connection route is built over the REST API, as we have written on this page. - How long does setup take, is it included in the plan price? | The scope of the connection is determined by how many objects, which permissions and which users are involved, and it is planned together with the CRM rollout. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. Project-specific development is scoped separately and priced separately. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Turkey and we do not offer region selection. Your CRM data is held in a separate database that belongs to you. When you open an AI connection, the provider side is added to this. - Can we see it before buying? | There is no trial you start on your own. First we run a 30-minute live demo; in that call we show the API surface, OAuth2 authorization and how the change history records writes, on your own scenario. After that we open a time-limited demo account. ##### Related pages - Claude integration | Ready today. Rapi, the assistant inside the product, and the 18-tool MCP package downloaded from the Setup screen. - Integrations | Which connection works in the product today, which ones we build on request, and the reason for the three things we do not promise. - Security | Which country the data sits in, the sub-processor list, authorization, the audit trail and what we do not offer yet. ##### Let us spend 30 minutes on which record we open with which permission In the demo, let us show the API surface, OAuth2 authorization and how write operations land in the change history, on your own scenario; and let us narrow the scope together. Request a demo The authorization table is drawn up in discovery: which object, which permission, which user. ### [Claude Integration: MCP Package and Rapi | Rapitek CRM](https://rapitek.com/en/claude-integration) The Rapi assistant runs on Anthropic Claude and writes records to the CRM. Connect your own Claude with the 18-tool MCP package from the Setup screen. Integration · Anthropic Claude #### If you use Claude, your CRM talks to Claude. This connection runs in production today; setting it up does not require a provider-specific project. Rapi, the assistant inside the product, runs on Anthropic Claude and does not only read the CRM — it writes records too. And with the MCP package you download from the Setup screen, you connect your own Claude to the same CRM with 18 tools. Request a demo Let's talk about setup ##### Why does AI end up bolted on in a CRM? When AI comes up, two separate expectations get sold with the same sentence on the CRM side. The first is an assistant embedded in the product: one that finds what you ask for, summarises, writes. The second is the assistant the team already uses — a team that works with Claude all day wants to reach the CRM from that same window. In both cases the mechanism jams at the same point — as we have seen it in our own projects: - If the assistant only reads, the work is not finished: you read the summary and still open the record yourself, still fill the field in by hand. - If the assistant is outside the CRM, copy-paste creeps in between; where the record came from is lost, and no trace is left behind. - When AI is positioned as an add-on, the tool the team actually uses and the tool inside the CRM stay two separate worlds. - And this question goes unanswered: where does this assistant take the data, who turned it on, can I turn it off when I want to? This page's job is to answer those four questions one by one: first what it is, then where it stands, then where it does not. ##### This connection is live today — and it is really two separate things 1. The assistant inside the product: Rapi. Rapi runs on Anthropic Claude and does not only read the CRM — it writes records too. Today it has ten tools; it fetches, creates and updates core records such as leads, contacts, companies and opportunities. Every field it changes on existing records lands in the product's field-level change history; the initial values of a record it creates are not recorded there. 2. Your own Claude: the MCP package. The package you download from the Setup screen — the version live today is v1.11.0 — contains 18 tools and connects your own Claude client to the CRM. The surface this connection rests on is the same one integrators use: a REST API authorised with OAuth2, describe for reading the object schema, composite for multiple operations in a single request, and bulk endpoints. What we can say about usage, and what we cannot. Rapi runs in production today; the weight of that use, however, is still our own team. That is why on this page you will not find a figure for how many runs it has done, or a sentence saying “our customers connect their own Claude”. What we can state is what the product does; what we cannot measure is who uses it and how much. We wrote up our general approach to integrations with the same openness on the integrations page. A concrete scenario ##### Wednesday 11:15 — a quote is being prepared. With Rapi turned on, this is what changes: - You ask for the customer by name, and Rapi brings up the record | Company, contact and open opportunity records arrive without searching the list screen. Rapi produces the answer not from the internet, but from the records in your own CRM database. - The meeting note stays as a record, not as a summary | When you have the note written, Rapi posts it to the relevant record. The assistant's job does not end with producing a summary; the record itself changes, and you do not need to open the screen a second time. - Missing fields are not opened and filled one by one | You ask for fields such as tax number, industry or owner to be updated; Rapi updates the record. You are the one who says what is wanted — Rapi does not start a job on its own. - The quote → order step is already built into the product | The record action that turns a quote into an order is built into the product. The chain is not a flow the assistant invented; it is the product's own action. - Changes to existing records leave a trace | Every field Rapi changes on existing records lands in the field-level change history: when which field moved to which value (for protected fields, only a marker). The initial values of a record Rapi creates are not recorded there. The changes the AI makes stay auditable. - If the job runs long the assistant stops; it does not carry on by itself | The number of steps that can be taken in a single request is limited — at most eight. Rapi is not an agent running in the background; every job starts with a request you initiate and ends with that request. ##### The surface you rest on when you connect your own Claude - An MCP package with 18 tools | The package is downloaded from the Setup screen and registered with your own Claude client. The version live today is v1.11.0; the package contains 18 tools. - Authorisation with OAuth2 | Access is granted with OAuth2; no connection is made by sharing a user password. You can withdraw the authorisation just as you granted it. - 183 business objects, each with its own endpoint | The product ships out of the box with 183 business objects, and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. - Reading the schema with describe | The object schema is read from the API; the connecting code does not have to track the field list by hand. When the schema changes, what is read changes with it. - composite and bulk endpoints | More than one operation can be sent in a single request — composite carries 25 sub-requests; bulk endpoints work on up to 200 records in a single call. - The change history covers the assistant too | Changes made through the assistant to existing records also land in the field-level change history; when which field moved to which value is visible (for protected fields, only a marker). The initial values of a record created through the assistant are not recorded there; the creator and creation time are set by the system and cannot be changed from the user screens, data import or the API. Two separate routes ##### Rapi, or your own Claude? These are two different things and they are enabled separately: we enable Rapi per tenant, and you download the MCP package and install it in your own client. You can also use both together. Topic | Rapi — the assistant inside the product | The MCP package — your own Claude - Where it runs | Inside the CRM: in the mobile app, alongside the record screens | In your own Claude client; it connects to the CRM without disturbing the way you already work - Number of tools | 10 tools | 18 tools - How it is enabled | Enabled per tenant, and off by default | Downloaded from the Setup screen; access is authorised with OAuth2 - Does it write records | Yes — it reads and writes; it creates and updates core records such as leads, contacts, companies and opportunities | The authorisation you grant determines the scope of access; you decide how much of it to open - What its limit is | At most eight steps in a single request; it does not run by itself in the background | The package is a Claude connector; we do not say it has been tested with any other client - Where the request goes | While the assistant is on, to Anthropic's service in the United States | To Anthropic through your own Claude account; the contract on that side is between you and Anthropic What we can say ##### What we have verified - 18 tools | The scope of the MCP package downloaded from the Setup screen; version v1.11.0 - Reads and writes | Rapi does not stop at fetching records; it creates and updates core CRM records - At most 8 steps | Steps allowed in one request; not autonomous — you start the request - Off by default | The AI assistant is enabled per tenant; the decision is yours - EU | Database Helsinki, files Frankfurt, backups Falkenstein; Anthropic US Implementation ##### How is the Claude side switched on? - The decision is yours | The AI assistant is off by default and is enabled per tenant. As long as it is not enabled, no AI request involving your CRM data is made. - We set the framework for the transfer in writing | When the assistant is enabled, requests go to Anthropic's service in the US. This is a second cross-border transfer on top of the hosting in the EU. Anthropic is named in the sub-processor list on our security page. We establish the basis for the transfer together during the contract process. - Installing the package for your own Claude | The MCP package is downloaded from the Setup screen, registered with your Claude client, and access is authorised with OAuth2. You decide who connects and with what scope. - Auditing and turning it back off | Updates made through the assistant to existing records are tracked in the change history; the initial values of newly created records are not recorded there. If you change your mind, the assistant is turned off from the same place; the rest of the CRM carries on working exactly as it did. ##### Our limits: what we do not promise on this page AI is the subject where overstating is easiest. We name the things we do not promise. - We do not say “autonomous agent”. Rapi does not run by itself in the background: every job starts with a request you initiate, and the number of steps that can be taken in a single request is limited — at most eight. We are not selling a system that works through the night and puts finished work in front of you in the morning. - We do not publish a usage figure. Rapi runs in production today, but the weight of that use is still our own team. We have no measurement that would let us say “our customers connect their own Claude to the CRM”; and because we do not have it, we do not say it. - The MCP package is a Claude connector. We cannot say we have tested the package with any other AI client. If you want to connect another assistant, the route is the REST API and OAuth2; that is a separate piece of work whose scope is set in discovery. - The assistant does not change the product's general limits. We do not promise stock synchronisation, an order-invoice-collection chain that flows on its own, or production automation; turning the assistant on does not change that. How we scope connections to ERP and accounting systems is on the integrations page. Data location — and the second transfer here. Your data sits in the European Union: the database in Helsinki (Finland), the files and media you upload in Frankfurt (Germany), the database backups in Falkenstein (Germany). We have no component in Türkiye, and we have no such feature as region selection. The AI assistant adds a second cross-border transfer on top of this: while the assistant is on, requests go to Anthropic's service in the United States. That is precisely why the assistant is off by default and is enabled per tenant. Seen from Türkiye, both transfers fall within the scope of Article 9 of Law No. 6698; we establish the basis for them together during the contract process and state in writing which component sits in which country. We named Anthropic, together with the country it is in and the condition under which it comes into play, in the sub-processor list on our security page. Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### Plan prices are out in the open; scope comes out in discovery The Claude connection runs in the product today; Rapi AI credit, on the other hand, is a separately priced item. We publish plan prices and the separately priced items on a single page, with the figures. See the pricing Three plans, a scope table and the separately priced items on a single page. FAQ ##### Frequently asked questions about the Claude integration - Does AI really work in Rapitek CRM? | Yes, in two separate forms. Rapi, the assistant inside the product, runs on Anthropic Claude; it reads and writes CRM records. The second route is the MCP package: with the 18-tool package you download from the Setup screen, you connect your own Claude client to the CRM. Both work in the product today; no provider-specific development project is needed. - Which AI provider does Rapi run on? | Anthropic Claude. This is an optional feature enabled per tenant inside the product, and it is off by default. Once you enable it, the assistant's requests go to Anthropic's service in the United States; we wrote up what that means in KVKK terms in the limits section. - Does Rapi only read, or does it write records too? | It reads and writes. It fetches, creates and updates core records such as leads, contacts, companies and opportunities; today it has ten tools. The changes it makes to existing records land in the product's field-level change history, which means those changes can be audited one by one afterwards; the initial values of a record it creates are not recorded there. - Can I connect my own Claude account to the CRM? | Yes. You download the MCP package from the Setup screen and register it with your own Claude client; access is authorised with OAuth2, and no user password is shared. The package version live today is v1.11.0 and it contains 18 tools. - What is the MCP package? | It is a connector that introduces the CRM to an AI client. The package rests on the same surface integrators use: a REST API authorised with OAuth2, describe for reading the object schema, composite for multiple operations in a single request, and bulk endpoints. In other words, the assistant does not look into the CRM from outside the scope the API permits. - Does the package work with ChatGPT or Gemini as well? | Today we define the package as a Claude connector; we cannot say we have tested it with any other client, and so we do not say it. If you want to connect another AI tool, the route runs through the REST API and OAuth2, and it becomes a separate piece of work whose scope is set in the discovery meeting. - Is the AI assistant on by default? | No, it is off. The assistant is enabled per tenant; as long as it is not enabled, no AI request involving your CRM data is made. We built it this way not as a marketing choice, but to leave the decision about the data transfer to you. - Does our data go to Anthropic? | While the assistant is on, the content the request requires goes to Anthropic's service in the United States. Where your CRM data sits does not change — database in Helsinki, files in Frankfurt, backups in Falkenstein — but the assistant adds a second cross-border transfer on top of the hosting in the EU. Seen from Türkiye, this too falls within the scope of Article 9 of Law No. 6698; we establish the basis for it together during the contract process. - How do we audit the changes the assistant makes? | From the field-level change history. Changes made through the assistant to existing records also land in this audit trail: when which field moved to which value is visible (for protected fields, only a marker). The initial values of a record created through the assistant are not recorded in it. The AI does not use a separate route that skips the product's audit trail. - Does Rapi work autonomously — does it do work by itself overnight? | No. Every job starts with a request you initiate, and the number of steps that can be taken in a single request is limited — at most eight. We do not offer an agent that runs indefinitely in the background and sets its own goals; and we say so plainly to any enterprise buyer who expects one. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. Your CRM data is held in a separate database that belongs to you. If the AI assistant is on, the Anthropic (US) side is added to this. - Can we see it before we buy? | There is no trial you can start on your own. First we run a 30-minute live demo; in that meeting we show the assistant writing records and where the MCP package is downloaded from, using your own scenario. Afterwards, if you want to explore the product at your own pace, we open a time-limited demo account. ##### Related pages - Integrations | The connections that run in the product today, the ones we build per project over the REST API, and how an integration is scoped. - Security | Which country the data sits in, the sub-processor list, backups, the audit trail, and what we do not offer yet. - Product | Modules, API scope and the full set of platform controls — the ground the assistant runs on. ##### Let's look at the Claude side with your own data, in 30 minutes In the demo, let us show you Rapi writing records and how the MCP package connects to your own Claude, using your scenario; and let's talk through the decision on whether to enable the assistant together. Request a demo The assistant is off by default; the decision to enable it and the written framework for the transfer are handled as part of setup. ### [Contact Rapitek | CRM Demo, Quotes and Support](https://rapitek.com/en/contact) Reach Rapitek on WhatsApp, by email or via the form; the number we publish is a WhatsApp line, not a call centre. Office: Nurol Plaza, Maslak, Istanbul. Contact #### Get in touch. A demo, a quote or a question about your existing setup — the same team answers all of it. Message us on WhatsApp Fill in the form ##### Direct contact WhatsApp: +90 212 963 22 84 — the conversation stays in one window, and screenshots and files stay in the same place. Email: info@rapitek.com Address: Maslak Mah. Büyükdere Cad. Nurol Plaza Sit. No: 255/B02, 34485 Sarıyer / Istanbul, Turkey Business hours: Monday-Friday 09:00-18:00 (GMT+3). We are closed on weekends. There is no call centre on our support line. Your question is answered by the team that builds and maintains the product — that is a choice, not a capacity limit. We aim to come back to messages that arrive during business hours the same working day. We do not write that as a commitment: we have no system that measures ticket times, and we do not promise a duration we do not measure. Our registered trade name, MERSIS number (Turkey's central trade registry ID) and tax details are listed in the legal notice at the bottom of the page. For details on how we process personal data — including our obligations under KVKK, Turkey's data protection law (No. 6698), and the GDPR — see our Privacy Policy; for data deletion requests, see our Data Deletion Instructions. Frequently asked ##### Frequently asked questions about contacting us - What is the fastest way to reach Rapitek? | Message our WhatsApp line. All three — WhatsApp, the form on this page and email — reach the same team; there is no ticket queue. We put WhatsApp first because of the channel itself: the conversation stays in one window, and screenshots and files stay in the same place. We have not measured a difference in response time between the channels, so we do not claim that one of them is faster. - Can I call that number? | No — the number we publish is a WhatsApp line, not a call centre or switchboard. Please write to us on WhatsApp instead of calling. Writing keeps your request on record and gets it to the right person; a phone call loses part of what you explain. If a live conversation is needed, we schedule it as a call. - How quickly do you reply? | We do not commit to a written response time (SLA) — we do not put a figure we have not measured on this page. What we can say is this: there is no call centre on our support line. Your question is answered by the team that builds and maintains the product. That is a choice, not a capacity limit. We do not offer 24/7 support either: support is provided during Turkish business hours. If your teams work across other time zones, let's discuss the scope together on the call. - What are your working hours? | Monday to Friday, 09:00-18:00 (GMT+3). We are closed at weekends. You can still write on WhatsApp outside those hours; your message is recorded and answered the next business day. - What happens to my data when I submit the form? | Your contact details are processed only to evaluate your request and get back to you. Your form record is kept in the European Union, on our website server in Germany (Falkenstein), and a copy is passed to our CRM system in Finland (Helsinki) so that we can respond. For organisations in Turkey this counts as an international transfer under Article 9 of KVKK, and no adequacy decision has been issued by the Board for the countries concerned. Details are in our KVKK disclosure text, and deletion requests are covered on our Data Deletion page. ##### Send us a message Briefly tell us what you need and we'll connect you directly with the right person. Company and team size are optional — they just help us find that person faster. Send message ##### Our office Nurol Plaza, Maslak Mah. Büyükdere Cad. No: 255/B02, Sarıyer / Istanbul ### [Cookie Policy | Rapitek CRM](https://rapitek.com/en/cookies) Our six cookies: names, purposes and durations. We use no third-party analytics or ad cookies, and our measurement cookie is set only with your explicit consent. Legal #### Cookie Policy How we use cookies to improve your experience ##### On this page Last updated: 23 September 2026 ##### What Are Cookies? Cookies are small text files that are placed on your device when you visit our website. They help us provide you with a better experience by remembering your preferences and understanding how you use our site. This Cookie Policy explains what cookies are, how we use them, and how you can manage your cookie preferences. ##### Types of Cookies We Use ###### Essential cookies These cookies are required for the site to work and do not require consent. All of them are first-party; they are not shared with any third party. Cookie name | Purpose | When it is set | Duration - csrftoken | Prevents cross-site request forgery (CSRF) on form submissions | On every page of the site | 364 days - sessionid | Keeps you signed in | Only when you sign in | 12 hours - rgo_cerez_onay | Remembers your cookie choice (accept or decline) | When you make a choice in the cookie banner | 180 days ###### Functional cookies Used to remember your preferences. These are first-party as well, and they are set only when you perform the related action. Cookie name | Purpose | When it is set | Duration - django_language | Remembers the language you selected | Only when you change the language | Session - rgo_onizleme | Opens a signed preview of unpublished pages | Only when you arrive through a preview link | 1 day ###### Measurement cookie — only with your explicit consent If you select Accept in the cookie banner, we set a cookie named rgo_oturum that links together the order of the pages you view within a single visit. We use it to understand which content is useful and, when we speak with you, to see more clearly what you need. This cookie is a random string: it is not derived from your name, e-mail address, IP address or any device fingerprint, and on its own it does not identify you. If you decline, it is not set and the site works exactly as before — no feature is switched off. If you delete the cookie, the record stops there and a new visit starts as a new record. The browsing information we record is deleted after 90 days. If you submit a form on our site while your consent to the measurement cookie is in effect, a short summary of your browsing (at most 50 steps) is saved with your enquiry and used to understand your request. That summary is not deleted after 90 days: on our site it is kept with your enquiry for 24 months from the date the form was submitted, and its copy in our customer relationship management (CRM) system is kept there together with your enquiry record for as long as that record exists. ###### Analytics and marketing cookies We use no third-party analytics or advertising cookies. There are no external trackers, advertising cookies or remarketing cookies on the site, including Google Analytics, and no cookie follows you across other websites. For our own measurement we use a first-party cookie named rgo_oturum, which is set only if you give consent and covers only your browsing on this site. If you decline, this cookie is never set. Cookie name | Purpose | When it is set | Duration - rgo_oturum | Links together the order of the pages you view within a single visit | ONLY if you have given consent in the cookie banner | 30 days ##### How to Manage Cookies You can control and manage cookies in various ways. Please note that removing or blocking cookies can impact your user experience and parts of our website may no longer be fully accessible. ###### Changing your decision about the measurement cookie The cookie banner is shown only if you have not yet made a choice; once you select accept or decline, your decision is remembered for 180 days and the banner does not appear again. You can change that decision whenever you like: select Cookie preferences at the very bottom of any page. Your saved choice is cleared, the rgo_oturum measurement cookie is deleted, and the banner asks you again on the next page — it makes no difference whether you accepted or declined. Alternatively you can still delete this site's cookies from your browser, which has the same effect on your next visit. ###### Browser Settings Most browsers allow you to control cookies through their settings. You can set your browser to refuse cookies or delete certain cookies. For more information, check your browser's help section. ###### Browser Cookie Settings - Chrome: Settings > Privacy and security > Cookies and other site data - Firefox: Settings > Privacy & Security > Cookies and Site Data - Safari: Preferences > Privacy > Cookies and website data - Edge: Settings > Privacy, search, and services > Cookies and site permissions ##### Third-Party Cookies We do not use any third-party cookies on our site. All six cookies listed above are first-party, meaning they are set directly by us and are not shared with any other company. Where we embed a map, we use OpenStreetMap; we chose it because it does not track visitors and requires no API key. ##### Updates to This Policy We may update this Cookie Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. When we make changes, we will update the 'Last updated' date at the top of this policy. We encourage you to review this policy periodically to stay informed about our use of cookies. FAQ ##### Frequently asked questions about cookies - Which cookies does this site use? | Six in total. The essential ones are csrftoken (prevents cross-site request forgery on form submissions), sessionid (keeps you signed in) and rgo_cerez_onay (remembers your cookie choice). The functional ones are django_language (remembers the language you selected) and rgo_onizleme (opens a signed preview of unpublished pages). The measurement cookie is rgo_oturum, which is set only if you accept in the cookie banner. - What is the difference between essential, functional and measurement cookies? | Essential cookies are required for the site to work and do not require consent. rgo_cerez_onay belongs to that group: the cookie that records your choice is needed so that a decline can be remembered, otherwise you would be asked again on every page. Functional cookies remember your preferences and are set only when you perform the related action. The measurement cookie (rgo_oturum) is not needed to deliver the service, so it is set only with your explicit consent. All six are first-party cookies. - Do you use analytics or advertising cookies such as Google Analytics? | We use no third-party analytics or advertising cookies. There are no external trackers, advertising cookies or remarketing cookies on the site, including Google Analytics, and no cookie follows you across other websites. For our own measurement we use a first-party cookie named rgo_oturum, which is set only if you give consent and covers only your browsing on this site. Where we embed a map we use OpenStreetMap, chosen because it does not track visitors and requires no API key. - What happens if I decline the measurement cookie? | Nothing is switched off. The site, with all of its pages and forms, works exactly as before; rgo_oturum is not set and no record of your browsing is created for measurement. The technical access logs that our website's server keeps for every request, regardless of consent, for security and troubleshooting are separate; they are described in our Privacy Policy. Your decision to decline is stored in the rgo_cerez_onay cookie so that you are not asked again on every page. - Can I change my decision later? | Yes, at any time. Select Cookie preferences at the very bottom of any page: your saved choice is cleared, the rgo_oturum measurement cookie is deleted, and the cookie banner asks you again on the next page, where you can make a different choice. This works whether you accepted or declined originally. The banner itself does not reappear on its own, because once you accept or decline your decision is remembered for 180 days. You can also delete this site's cookies from your browser, which has the same effect on your next visit. - How can I refuse or delete cookies? | If you have not yet made a choice, you can decline the measurement cookie in the cookie banner on the site. If you have already made a choice, select Cookie preferences at the very bottom of any page to change it — your saved choice is cleared and the banner asks you again on the next page. For all cookies you can use your browser settings. Chrome: Settings > Privacy and security > Cookies and other site data. Firefox: Settings > Privacy & Security > Cookies and Site Data. Safari: Preferences > Privacy > Cookies and website data. Edge: Settings > Privacy, search, and services > Cookies and site permissions. Please note that deleting the essential cookies can affect parts of the site. - How long do these cookies stay on my device? | The duration depends on the cookie: csrftoken 364 days, sessionid 12 hours, rgo_cerez_onay 180 days, django_language for the session, rgo_onizleme 1 day and rgo_oturum 30 days. In addition, the browsing records themselves are deleted after 90 days; however, if you had accepted the measurement cookie when you submitted a form, the short summary of your browsing saved with your enquiry is not subject to that deletion: it is kept on our site for 24 months from the date the form was submitted, and its copy in our CRM system is kept together with the enquiry record in that system for as long as that record exists. ##### Contact Us If you have any questions about our Cookie Policy or how we use cookies, please contact us: Contact form Rapitek Bilişim Teknolojileri A.Ş. Maslak Mah. Büyükdere Cad. Nurol Plaza 255, B02 34485 Sarıyer / Istanbul, Turkey ### [Is Rapitek CRM a Fit? A 5-Question Check | Rapitek CRM](https://rapitek.com/en/crm-chooser) Five questions — team size, budget, region, must-have features and speed — score whether Rapitek CRM fits your team. The weights and scoring are out in the open. Free tool · 60 seconds · 5 questions #### Is Rapitek CRM a fit for you? Answer five questions and see your fit score. The result may be “waiting is the better call for now” — and when it is, we tell you so. The scoring is out in the open. Talk through your situation Rapitek pricing ##### Rapitek CRM fit check Five questions. Answering them on its own sends nothing. If the result is “wait for now”, we say that too. - Rapitek CRM looks like a fit | For Turkey-based B2B sales and field teams with at least 5 users: a separate database, a built-in WhatsApp inbox, Turkish-language support, and a model where we do the setup ourselves. After the discovery call, we give you a date, not a range. Plans start at 39 USD per user per month. | Request a demo - Waiting is the better call for now | Record-keeping discipline comes before a software decision. In a one- or two-person team running a single process, the cost-benefit balance doesn't work out; establishing the follow-up habit comes first. If you got this result, there is no reason to come to us — look again when the team grows. | Read the guide - How many people will use the CRM? | 1-5 users (small team) · 6-25 users (growing team) · 26-100 users (mid-market) · 100+ users (enterprise) - What is your budget per user per month (USD)? | Free / under $20 · $20-50 · $50-150 · $150+ (enterprise budget) - Where do you operate? | Turkey only / mostly TR — KVKK and Turkish matter · UAE / Saudi / GCC — Arabic-language support needed · EU / GDPR markets — EU data residency · Global / multi-region — local partner network needed - Which of these are non-negotiable for you? | Built-in WhatsApp Business API · MRP / inventory / manufacturing execution · ERP integration (Logo, Netsis, SAP, Mikro) · AI features (voice assistant, business-card scanning) · A separate database per customer · Inbound marketing and content tools · Field sales and visit tracking · A written SLA commitment - How quickly do you need to go live? | Today / this week · 2-4 weeks · 1-3 months · 6+ months (no rush) This score is a weighted sum of your answers: team size, budget and region 20% each, non-negotiable features 25%, go-live speed 15%. We assigned the weights and scores ourselves; this is not an independent measurement. We do not score other products — only our own fit. The scores against us are here too, and we do not soften the reason: we do NOT provide Arabic-language support — the web interface is in Arabic, but support and training are in Turkish and no one on our team speaks Arabic. We have no written SLA either. Show the result ###### Your fit ##### Why did we build a tool that can argue against us? Because a rollout that doesn't work wastes both our time. For a three-person, sales-only team, saying “not yet” is more honest than selling ourselves — that team doesn't meet our minimum user requirement anyway. Let's be plain: Rapitek built this tool and Rapitek assigned the scores. It is not an independent measurement. We do not score other products, and we say nothing about other products on this page — because we have no measurement that confirms what another product does or does not offer today, and that is the sentence that goes stale fastest. The only thing we measure here is our own fit. What we do put in the open is the method and the weights, and we write down the scores that go against us. You can judge how much to trust a result by how much the tool is willing to say against itself. Even if the result says “a fit”, we'd suggest seeing a few demos. In our own demo, if we think we're not the right fit, we say so. ##### If Rapitek came out on top, let's test that in 30 minutes. We listen to your sales process and work out together which fields and reports would be configured. If we're not a fit, we'll say that too. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [How to Choose a CRM: A Field-Tested Guide | Rapitek](https://rapitek.com/en/crm-guide) A CRM selection guide distilled from 200+ enterprise projects: needs analysis, evaluation criteria, hidden costs, questions to ask vendors, and a rollout plan. Guide · CRM selection #### How to choose a CRM: a buyer's guide written in the field We delivered more than 200 enterprise CRM projects during our Salesforce era, and we watched right and wrong choices play out up close. This page is not a PDF to download — it is the guide itself: what to look at, what to ask, where each cost hides, and why implementation decides more than the license. ##### Why this guide exists — and why it is honest Let's be upfront: we sell a CRM too. The reason we try to stay fair on this page is not virtue but experience: we delivered more than 200 enterprise CRM projects in the Salesforce ecosystem, and we saw up close, again and again, how badly chosen systems end. We won't dress up the cost of a wrong choice with an inflated statistic. The cost we saw in the field is this: a system nobody enters data into after six months, a quiet retreat to Excel, and a second migration paid for within two years. None of it shows up on the license invoice; all of it costs more. This page is not a document you trade your email address for; it is the guide itself. Read it in order, or jump straight to what you need: the selection process, evaluation criteria, the hidden-cost map, questions to ask vendors, and how to measure adoption. You can put every question in this guide to every vendor you talk to — including us. Process ##### CRM selection in six steps - Write the need down | "Let's get a CRM" is not a need. Write down the three to five concrete problems you want solved: follow-ups get forgotten, quotes go out late, the management report is compiled by hand. How many users, which teams, which processes — this list defines the scope. - Cut the shortlist to three | There are hundreds of CRMs on the market; you cannot look at them all. Filter with your hard criteria (language, data location, budget range, industry experience) and continue with at most three candidates. Spend your energy testing three candidates deeply, not making the list longer. - Ask for a demo with your own scenario | The vendor's canned scenario looks flawless in every product. Have them walk your flow: a lead comes in, a quote goes out, a follow-up task drops in, the report reflects it. Run the same scenario with every candidate so the comparison is real. - Calculate cost over three years | The monthly license is the visible tip of the iceberg. Add implementation, data migration, training, integration, the support package, renewal increases and the exit cost. The hidden-cost map below exists exactly for this calculation. - Ask for proof | Ask for a reference at a similar scale with a similar process. If a trial environment is offered, test it with your own real records; if not, demand the same depth in the demo. You want to see it done, not hear that "it can be done." - Sign the rollout plan along with the decision | Selection doesn't end with the contract. Who configures the system, when data moves, when the team is trained, which date you go live — tie it all to a written plan. Define adoption metrics from day one; we suggest some below. ##### Nine evaluation criteria - Data model and customization | Can fields, objects and sales stages be adapted to your process? Don't settle for "anything is possible"; watch an example from your own process being configured in the demo, and ask who does the configuration. - Ease of use | How many clicks does the most frequent job take — opening a record, adding a note, closing a task? If the sales team can't create records on their own from day one, the system stays empty no matter how powerful it is. - Integration approach | Look past shiny logo walls to the method: which system, in which direction, and who will build it should be pinned down in writing. An open REST API with webhook support outlives any list of prebuilt connectors. - Reporting | Canned reports impress in demos; the real question is whether you can build a report for your own question. Ask who keeps the management dashboard current and whether building a report requires code. - Mobile use | If your team is in the field, the real test of a CRM is on a phone. If updating a record after a visit means going back to a desk, the data doesn't get entered that day — and usually never does. - Security and data location | Ask plainly which country the data is kept in. For companies in Turkey, data hosted abroad is a cross-border transfer under KVKK, Turkey's data protection law (No. 6698, Art. 9), which sets out tiered bases for transfer: adequacy, then appropriate safeguards, and only exceptionally incidental cases. Find out whether permissions reach record level and how customers' data is kept separate. - Artificial intelligence | Look at the scenario, not the show: which task does it cut from how many steps to how many? Whether an assistant with write access asks for confirmation on risky operations matters more than an impressive demo. - Support model | Who answers your question: an agent in a ticket pool, or a team that knows the product? Get the language, channel and response-time commitment in writing before you buy. - Data ownership and exit | Plan the exit before the entry: in what format, and at what cost, can you export all of your data? If the answer is vague, you are leaving your negotiating power at the door. Total cost of ownership ##### The hidden-cost map Run this table on every vendor you talk to — including us. Our own pricing page states plainly which items are included in each plan. Cost item | Where it hides | The question to ask the vendor - Implementation and configuration | The "not included in the license" line usually surfaces in a contract annex | Are implementation, configuration and training included in the price? If not, how many days of work, and at what cost? - Data migration | Moving data from the old system is billed separately as "professional services" | Is migrating our existing records, including de-duplication, part of the scope? - Training | Charged per session or per user | How many training sessions are included? How is training for people who join later charged? - Integration | "There is an API" does not mean the integration will be built | Who builds this connection? Are the scope and cost given in writing before the quote? - Forced plan upgrades | The one feature you need sits in a higher tier | Which plan is this feature in? What else would we be paying for in that plan? - API access | In some products the API is a separately priced add-on | Are API access and request limits included in the plan? - Support | Standard support is email-only; phone and priority handling cost extra | Who answers support requests, through which channel, and within what time? - Renewal increases | The first-year discount reverts to list price in year two | How is the second-year renewal price set? Can we have it in writing? - Exit cost | Exporting your data is restricted or charged | If we leave, in what format and at what cost do we get all of our data? ##### 20 questions to ask before you buy Send these questions to the vendor in writing before the meeting. Written answers are far more binding than verbal "yes"es during a demo — and every question that goes unanswered is an answer in itself. ###### Data and security - Which country is our data hosted in? If it is outside Turkey, how do you handle the cross-border transfer requirements of KVKK Art. 9? - Is our data kept in a separate database, or in tables shared with other customers? - Do permissions go down to record level? When an employee leaves, what happens to their access and record history? - How often are backups taken? Can we recover a record that was deleted by mistake? ###### Customization and implementation - Who configures the fields, stages and flows specific to our process — you or us? Is it included in the price? - Do you commit to an implementation date? What is your typical timeline? - After go-live, who do we reach when changes are needed, and at what cost? - Is migrating our existing records, including de-duplication, part of the scope? ###### Integration - Who builds the connection to the ERP or accounting software we use? Are the scope and cost given in writing before the quote? - Is API access included in the plan? What are the request limits? - Do you support webhooks for pushing data to our systems? ###### Usage and adoption - How many training sessions are included in the price? How does repeat training for people who join later work? - What languages are the interface and support available in? - Which platforms is your mobile app available on? - Who works alongside us in the first months after go-live? ###### Contract and exit - How is the second-year renewal price set? Can we have it in writing? - What are the minimum commitment period and the early exit terms? - If we leave, in what format and at what cost do we get all of our data? - When and how is our data deleted after the contract ends? - Can you share the full list of items not included in the price? You can ask us every one of these questions too; we answer all of them in writing at the demo. Where our answer is "we don't have that", we prefer to say so plainly — that is why this guide exists. Behind this guide ##### Written in the field, not at a desk - 200+ | Enterprise CRM projects completed for other companies during our Salesforce era - A date, not a range | We give you a go-live date after the discovery call - EU | Data location: database in Finland, media in Frankfurt ##### Implementation decides more than the license What we saw again and again across 200+ projects is this: CRM projects fail not because of the product but because of implementation and adoption. Badly designed stages, twenty required fields nobody fills in, a team dropped into the system without training — that turns even the best product into an empty database within six months. So when choosing, weigh "who implements it, and how" as heavily as "which product". A product whose license looks cheap can turn out to be the most expensive option once implementation and training are billed separately — and the reverse is just as true. ###### How do you measure adoption? Login counts are a misleading metric; looking at the system and using the system are not the same thing. In the first 90 days, watch these four: - Record discipline: How much of the team's contact with customers actually lands in the CRM? If people still write in phone notes and notebooks, the system is only alive on paper. - Field completion: Are required fields genuinely filled in, or waved through? A field that keeps getting skipped is a badly designed field. - Meeting source: Is the weekly sales meeting run from the CRM screen, or has it drifted back to Excel? A manager compiling the report by hand is the first crack. - Direction of questions: If the team asks "how do I do this in the system", adoption has begun; if they ask "do I really have to enter this into the system", revisit the setup. ###### How do you calculate the return? We won't promise a template with multipliers; we suggest three measurable items. Measure the current state before implementation so you have something to compare against: - Share of leads left without follow-up — how many inbound inquiries go unanswered? - Time to quote — how many days pass between the request and the quote going out? - Hours spent on reporting — how many people spend how many hours on the management report each week? We have seen this picture so often that we built our own model around it: we do the setup ourselves, and after the discovery call we give you a date, not a range. We also apply our own advice to ourselves — whatever sits outside the plan price, including the scope of setup, is worked out in the discovery call and put in writing before the work starts. You can find the current plans on our pricing page. From our CRM implementation projects ##### From our CRM projects - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Case study - As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient. | Utku Aydın | Business Development Director | Iyzico | Case study - The most important element of bringing new business ideas to life is your IT infrastructure and applications. Rapitek offered much more than just providing an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during the development process, we reached our first product quickly and ensured healthy project continuity. | Denizhan Edeer | CEO | Aktif Filo | Case study ##### Check the fit in 60 seconds You do not have to read this guide end to end. The fit check asks five questions and tells you whether Rapitek CRM fits. The answer may be that waiting is the better call for now. Open the fit check No signup, no email required. FAQ ##### Frequently asked questions about choosing a CRM - What should you look for when choosing a CRM? | Look at nine areas: data model and customization, ease of use, integration approach, reporting, mobile use, security and data location, artificial intelligence, the support model, and data ownership and exit terms. The one-sentence summary: choose the system your team will actually use and whose total cost is predictable — not the one with the most features. - How should CRM pricing be calculated? | The monthly license alone is misleading. Calculate the three-year total cost of ownership: license, implementation and configuration, data migration, training, integration, the support package, renewal increases and exit cost. Ask the vendor for a written list of everything not included in the price. We do the same: the items priced outside the plan — including the scope of setup — are listed one by one on our pricing page, and the cost is worked out in the discovery call and put in writing. - Does a small team need a CRM? | Below 5 users, simple self-service tools are usually sufficient and usually the smarter choice; we say that openly. A CRM investment starts to make sense when the team grows and knowledge can no longer live in one person's phone. Rapitek CRM, where we do the setup ourselves, focuses on growing teams of 5 users or more. - What is the advantage of a CRM over Excel? | Excel is tied to a person: whoever has the file has the knowledge; there is no record history, no reminders, two people can't comfortably work in it at once, and when an employee leaves, the relationships leave with the file. A CRM turns the same data into the team's shared property, with permissions, record history, tasks and reminders, and reporting. If your spreadsheet is now managed with color codes and "final_v3_FINAL" file names, it is time to move. - How long does a CRM implementation take? | It depends on scope: user count, data volume, integration needs and the number of processes set the timeline. Implementations that drag on for months usually trace back to scope never being pinned down at the start. In Rapitek CRM, the rollout covers discovery, configuration, data migration and training; after the discovery call we give you a date, not a range, and the scope of the rollout — along with any fee for it — is put in writing before the work starts. - Should you choose a free CRM? | For a small team it can work at the start; honesty requires saying so. You pay the price elsewhere: user and record limits, limited support, often unclear data location, and an unavoidable migration cost when you grow. When choosing your permanent system, put the very same questions from this guide to the free product; every question you can't get answered marks a limit. - Does it matter whether the vendor is local or international? | The label alone measures nothing; the criteria stay the same. The practical differences are these: support language and working hours, interface language, the currency the price is set in, familiarity with KVKK and local business practices, and data location. A local vendor or an international one can both be the right choice if they answer these five points well; if they answer badly, the label is irrelevant. - Where should CRM data be stored, and what matters legally? | What matters is not the place but transparency: the vendor must be able to say plainly which country your data lives in. For companies in Turkey, data hosted abroad is a cross-border transfer under KVKK Art. 9, so a lawful transfer ground and disclosure processes must be in place. Rapitek CRM hosts the database in the European Union, in Finland, with media files in Frankfurt — and we state this openly. TLS protects data in transit and every customer gets a separate database. Passwords are hashed one-way; two-factor secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. - Are AI features in a CRM actually useful? | The right question is not "does it have AI" but "which task does it cut, from how many steps to how many". An assistant that can create records genuinely saves time — but an AI with write access must ask for confirmation on risky operations. In Rapitek CRM, the voice assistant Rapi works only in the mobile app; it takes spoken Turkish commands to create and update records across 11 objects, and asks for confirmation before saving risky changes. The scanner that turns a business-card photo into a lead works on both web and mobile. - What happens to our old data when we switch CRMs? | Data migration is the topic discussed last in selection meetings and the most critical job of implementation. Customer, company and opportunity records from spreadsheets or your current system are imported, and duplicates are cleaned up at that stage. Always ask the vendor whether migration is in scope and who handles de-duplication. In Rapitek CRM, data migration is part of implementation; the scope of setup, and any fee for it, is worked out in discovery and put in writing. From guide to product #### We applied these criteria to ourselves first We built Rapitek CRM to give clean answers to the questions in this guide: a separate database for every customer, hosting in the European Union, an open REST API, and a transparent model where anything outside the plan price — including the scope of setup — is put in writing before the work starts. Explore the product See pricing ##### Put us on your shortlist too In a 30-minute demo, ask us every question in this guide; we will walk the product through your own scenario, live. Where the answer is "we don't have that", we say so plainly. Request a demo The scope of setup — and any fee for it — is agreed in writing before the work starts. ### [Are You Ready for a CRM? | 8-Question Check | Rapitek](https://rapitek.com/en/crm-readiness-quiz) Eight questions, an honest answer. Sometimes the answer is "not yet" — and we say so. No email required. Free tool · 2 minutes · 8 questions #### Is your company ready for a CRM? Answer eight questions and see your readiness score along with the steps that fit your situation. No sign-up, no email — the result appears straight on the screen. ##### CRM Readiness Quiz Pick the option closest to you on each question. There are no right or wrong answers — the point is to read where you stand today. - How do you track your sales opportunities today? | Excel / Spreadsheet · Pen and paper / Whiteboard · Email · Another CRM · We don't track them - How large is your sales team? | 1-5 people · 5-20 people · 20-50 people · 50+ people - How many new leads do you get in an average month? | 1-10 · 10-50 · 50-200 · 200+ - How long is your average sales cycle? | Days · Weeks · 1-3 months · 3+ months - What is your biggest sales problem? | Losing leads · No visibility into the pipeline · Manual reporting · Slow follow-up · All of the above - Which tools are you using right now? | Excel · Email · WhatsApp · An ERP system · Another CRM · None of these - What is your CRM budget per user per month? | Under $20 · $20-50 · $50-100 · $100+ · Not sure yet - When are you planning to move to a CRM? | Right away · Within 1-3 months · Within 3-6 months · Just researching - Early stage | Your business is still early for a CRM rollout — and we would rather tell you that honestly. If your team is under 5 people and you mainly want to gather demand from a single channel, Inbox (149 USD per company per month, up to 5 users) may be the right starting point. For a full CRM rollout, waiting — and keeping your customer data tidy in the meantime — is the better call. | Look at Inbox - Ready for a CRM | Your team is at the right point to make the move. Bringing your pipeline, activity tracking and reporting into one place is the right step in this band; we have not measured how quickly that pays back, so we do not put a timeframe here. The Sales plan (39 USD per user per month) is the starting point we recommend for this band; we define the scope together in the discovery call. | Book a demo - High readiness | Your need is clear, and waiting has a cost. In this band, marketing, communications and operations usually come into play as well — the Platform plan (69 USD per user per month) covers that. We do not commit to a timeline before discovery; after the discovery call, we give you a date, not a range. | Let's scope it together - Urgent need | At this score, continuing without a CRM is costing you something: lost leads, an invisible pipeline and reports assembled by hand. The Enterprise plan (119 USD per user per month, minimum 10 users) is the tier where scope, the rollout plan and integrations are worked out specifically for your project. There is no call center on our support line — the team that builds and develops the product answers your question. We would not put the discovery call off. | Let's talk now - Moving your existing data is part of the job | Your customer list — in a spreadsheet or buried in email — is imported during setup and duplicates are cleaned out. Data migration is not a separate project; it is part of the rollout. - At this size, visibility is the real issue | Past 20 people the problem is no longer keeping records — it is whether a manager can see the pipeline by looking rather than by asking; that is the need we have seen in our own enterprise projects. Role hierarchy, sharing rules and team-level reports support that, and we define them around your organization during setup. - Catch inbound demand whatever channel it arrives on | Requests from WhatsApp, Instagram, email and SMS land in the same shared inbox and attach to the customer record — nothing stays on one person's phone. The web form object ships with the standard setup; routing form submissions into the CRM is something we configure during your rollout. - A drag-and-drop pipeline | Every opportunity on one screen, with your own stages and a win probability. Whatever is stalled shows up in a report instead of in someone's memory. - Keep the WhatsApp history with the business | The team writes from a single work number and every message is logged on the customer record. Even when a rep leaves, years of conversation history stay with you. - Let's talk budget and scope together | Our plans start at 39 USD per user per month, and Sales and Platform both require at least 5 users. For smaller teams, Inbox (149 USD per company per month) is a separate starting point. ###### Your readiness score Show my result Start over ##### How is this score calculated? Every option carries a score and the eight questions are added up. What raises your score is what raises the cost of carrying on without a CRM: a growing team, more inbound demand, a longer sales cycle, and follow-up that isn't happening at all. This is an estimate, not a measurement. It is an approximation made without knowing your business model — the real answer comes out of a 30-minute discovery call. Your answers never leave your browser. The scoring runs on your device; no data is sent to us, we don't ask for an email address, and you don't have to fill in a form to see the result. ##### Whatever your score, let's make it concrete in 30 minutes. We listen to your sales process and work out together which fields, stages and reports would be configured. If it isn't a fit, we say that too. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Customer Stories | CRM Projects We Delivered | Rapitek](https://rapitek.com/en/customer-stories) Real projects from 200+ enterprise CRM implementations — what was built, and what the customers said in their own words. Customer stories #### Let our customers describe what we did in the field. Three enterprise CRM projects: a manufacturer, a foundation, and a chemicals company. What the problem was in each, what we built, and how the customer describes the result — as it is. Let's talk about your process About us The team behind them - 200+ | Enterprise CRM projects completed during our Salesforce era - 2018 | The year Rapitek was founded ##### Three projects, three different industries. - Anatolia Tile — Manufacturing | A global player in ceramics, porcelain and natural stone since 1995. Customer relationships, sales and logistics operations were brought onto a single platform. - SEV Foundation — Non-profit | A foundation running ten schools, a hospital and a publishing house. Alumni data, donations and scholarship tracking moved into one cloud-based system. - Petroyağ — Chemicals and lubricants | More than 800 customers, 8 dealers, exports to over 40 countries. B2B sales, order management and production planning were integrated. In their own words ##### The managers we worked with on these three projects. - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Read the customer story - Our foundation needed a cloud-based software system for data management. Rapitek is a company that is careful and attentive in understanding our wishes and needs; they also translated our requirements into the system very well. When we have new requirements, they support us with extremely fast and thorough solutions. As SEV, we are highly satisfied with working with Rapitek. | Meryem Boğa | Project and Resource Development Manager | Sağlık ve Eğitim Vakfı | Read the customer story - With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. | Ögetay Can | Sales Director | Petroyağ | Read the customer story ##### These projects belong to our Salesforce era — and we don't hide it The three stories below come from Rapitek's Salesforce implementation era. In that era we delivered enterprise projects in the Salesforce ecosystem; afterwards we built our own product, Rapitek CRM. We leave the stories as they are, because what they actually describe is not a product but a method: listen to the process, model it correctly in the system, migrate the data, train the team, and stay reachable afterwards. The same team does the setup today — only now on our own platform. We do not commit to an implementation time before discovery; after the discovery call, we give you a date, not a range. Customer stories built on the new product are being prepared for publication. ##### Let's work out how your process would be set up. In a 30-minute discovery call we listen to your sales process and decide together which fields, stages and reports would be configured. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Data Deletion Instructions | Rapitek](https://rapitek.com/en/data-deletion) How to request deletion of your personal data from Rapitek, including data received via Instagram and WhatsApp. Request address, scope and response time. Legal #### Data Deletion Instructions Last updated: September 24, 2026 ##### On this page This page explains how to request deletion of the personal data Rapitek processes about you. It covers data you send us through our website as well as data that reaches us through messaging channels such as Instagram and WhatsApp. Requests are handled under Turkish Personal Data Protection Law No. 6698 (KVKK). ##### What data we process When you message us via Instagram, WhatsApp or similar channels: - message content (the text and media you send) - sender username and platform ID - the time the message was sent - the CRM record the message is linked to, if any (e.g. a lead record) When you submit a form on our website, we process your name, email address, phone number, company details and message, together with technical data about your visit (IP address, traffic source). ##### How to request deletion To request deletion of your data, send an email to: info@rapitek.com To help us process your request, please include: - “Data Deletion Request” in the subject line - which channel you contacted us through (Instagram, WhatsApp, website form) - your username on that channel, or the email/phone you gave us ##### Response time and scope of deletion We resolve your request as soon as possible and in any case within 30 days, as required by Article 13 of Law No. 6698, and confirm the outcome to you in writing. Deletion covers your message content, channel identifiers and the linked CRM record. Once approved, these records are deleted from our systems or irreversibly anonymized; copies in backups drop out automatically from the local backups on our CRM server after 30 days and from our website's backups within about 6 months at most under our backup cycle; our CRM's encrypted off-server backups are deleted automatically after 90 days; the unencrypted backups there are not covered by this automatic deletion. Records we are legally required to keep — such as invoices, accounting records and proof of consents you gave — are retained for the statutory period and destroyed afterwards. Where this applies, we tell you which record is retained and why. ##### Your rights under KVKK Under Article 11 of Law No. 6698 you have the right to learn whether your personal data is processed, to request information about it, to learn the purpose of processing, to know the third parties to whom it has been transferred in Turkey or abroad, to request correction if it is incomplete or inaccurate, to request erasure or destruction, to request that such correction and erasure be notified to those third parties, to object to a result produced solely by automated analysis that works against you, and to claim compensation for damage arising from unlawful processing. For details on how we process your personal data, see our Privacy Policy and Cookie Policy. FAQ ##### Frequently asked questions about data deletion - How do I request deletion of my data? | Send an email to info@rapitek.com. To help us process it, put "Data Deletion Request" in the subject line and tell us which channel you contacted us through (Instagram, WhatsApp or the website form) along with your username on that channel or the email/phone you gave us. - How long does my request take? | We resolve your request as soon as possible and in any case within 30 days, as required by Article 13 of Law No. 6698, and we confirm the outcome to you in writing. - What exactly does deletion cover? | It covers your message content, your channel identifiers and the CRM record linked to them. Once your request is approved, these records are deleted from our systems or irreversibly anonymized, and copies held in backups drop out automatically from the local backups on our CRM server after 30 days and from our website's backups within about 6 months at most under our backup cycle; our CRM's encrypted off-server backups are deleted automatically after 90 days; the unencrypted backups there are not covered by this automatic deletion. - Is everything deleted, or are there exceptions? | Records we are legally required to keep — such as invoices, accounting records and proof of the consents you gave — are retained for the statutory period and destroyed afterwards. Where this applies, we tell you which record is being kept and why. - If I messaged you on Instagram or WhatsApp, what data is processed? | We process the message content (the text and media you send), the sender username and platform ID, the time the message was sent, and the CRM record the message is linked to, if any. - I am a customer of a company that uses Rapitek CRM. What should I do? | This page concerns data that Rapitek processes as data controller. If you are a customer of a company that uses Rapitek CRM and want that company's records about you deleted, send your request directly to that company — it is the controller of its own data. If such a request reaches us, we will point you to the right contact. ##### If you are a Rapitek CRM customer This page concerns data that Rapitek processes as data controller. If you are a customer of a company that uses Rapitek CRM and want that company's records about you deleted, you should send your request directly to that company — it is the controller of its own data. If such a request reaches us, we will point you to the right contact. ### [Book a Rapitek CRM Demo | 30-Minute Live Session](https://rapitek.com/en/demo) See Rapitek CRM live with your own sales scenarios. A free 30-minute demo with the team that builds the product, held in Turkish. No self-service trial. Demo #### See Rapitek CRM live. A 30-minute walkthrough shaped around your business, held in Turkish. We set up your own sales scenarios on screen and show them; no sales pressure. There is no self-service trial you sign up for with a credit card; after the call we can open a trial or a demo account for you, depending on what you need. Go to the demo form See pricing ##### What you'll see in the demo - Sales pipeline management | The full flow from lead to quote to order: Kanban view, stages and reports. - AI that enters the data for you | In the mobile app, tell Rapi in Turkish what happened and it creates the record. We also show business-card scanning and meeting notes live. - Integrations and API | A shared WhatsApp inbox, Google Calendar sync and a REST API covering the 183 business objects that ship in a standard install, to connect your existing systems. Process ##### How it works. - Demo | 30 minutes, held in Turkish. We ask about your process beforehand and build the demo around it. It's free and creates no obligation. - Scope and quote | After the demo we pin down your user count, the modules you need and your process scope, and share a written quote. If you would like to explore the product at your own pace, we open a time-limited demo account for you at this stage. - Setup — where the customization begins | Once we agree, we configure fields, stages, roles and reports around your process — data migration, integrations and team training. After the discovery call we give you a date, not a range; the scope of setup, and any fee for it, is agreed in writing before the work starts. ##### Request a demo Fill in the form and your request goes straight to the team that builds the product, not to a call centre. Your team size and a brief note on what you need is enough. Request a demo ##### About the demo. - How long does the demo take? | A demo session runs 30 minutes. If you need more depth we can schedule a second session. - What language is the demo held in? | The demo call is held in Turkish. Rapitek CRM's web interface is available in Turkish, English and Arabic, but the mobile app interface is Turkish only, and our support and training are given in Turkish — we do not offer Arabic-language support. We say this before the demo so neither side is surprised afterwards. - Is the demo paid? | No, the demo is completely free and carries no obligation. The team that builds the product runs it; there is no sales pressure. - Can we explore the product ourselves? | There is no trial you start yourself by signing up. We begin with a 30-minute live demo built around your own scenario; afterwards, if you would like to explore the product at your own pace, we open a time-limited demo account for you. That account lives in our demo environment and comes with sample data — please do not enter your real customer data there. Setup with your own data happens after we agree, during the setup phase. - Is the system customized for us in the demo? | In the demo you see the standard product, walked through your scenario. Customization — your own fields, sales stages, role structure, reports and integrations — is configured by us during setup after we agree. The scope of setup, and any fee for it, is worked out in the discovery call and put in writing before the work starts; we want to show you what you are actually getting, unembellished. - Can the demo be tailored to our industry? | Yes. We have delivered more than 200 enterprise CRM implementations across manufacturing, retail, B2B services, textiles and many other fields. We ask about your process before the call and shape the demo around it. - Who do you work with? | With businesses that have 5 or more users and a sales team — from SMB to enterprise. We are not the right fit for teams smaller than 5 users, or for anyone expecting a setup-free self-service product; we say so before the demo so neither side wastes time. ##### Still have a question? Let's cover it in the demo. Fill in the form and we'll ask about your process beforehand, then build the demo around it. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Moving from Dynamics 365 | Rapitek CRM](https://rapitek.com/en/dynamics-365-alternative) Migrating from Dynamics 365 to Rapitek CRM: the team that builds the product runs the rollout, a separate database per customer, and our limits in writing. For teams coming from Dynamics 365 #### The team that builds the product runs the rollout — and puts the date in writing. We handle migrations for teams coming from Dynamics 365. This page sets out how we deliver, what we can measure and where our limits are. We have no formal partnership with Microsoft. Request a demo See pricing ##### The short answer We do not compare ourselves with another product on this page. We write what we do and what we don't do. This is how we deliver. Discovery, configuration, data migration and training are run by the team that builds the product; there is no separate consulting project in between. We don't commit to a timeline before discovery; after the discovery call we give you a date, not a range. When you evaluate any proposal, put setup, customisation and training next to the licence line. Without those lines two proposals aren't being compared on the same scale. What we do ##### How Rapitek CRM works Area Rapitek CRM - Time to go live | No timeline committed before discovery; after discovery a date in writing, not a range - Who does the rollout | The team that builds the product - Microsoft ecosystem | We connect over standard APIs. Outlook and Microsoft 365 connections are not available today; we have no built-in integration with Teams or Power BI - WhatsApp | Inside the product - Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery - Support and training language | Turkish - Licensing structure | Three tiers, per user, prices published - Data location | European Union: database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany) - Data separation | A separate database per customer - Ecosystem breadth | Narrow. We have no app marketplace and no trained partner network — we say so plainly - Multi-region enterprise operations | Not our focus; we are not positioned for multi-region, multi-entity enterprise operations ##### Where the difference shows at mid-market scale - A date, not a range | After the discovery call we give you a date, not a range, for the move from discovery to go-live. You don't have to manage a long consulting project. - Shared WhatsApp inbox | The team writes from a single work number; every message is logged on the customer record and the history stays with the business. - Turkish ERPs | Per-project connections to Logo, Netsis, Mikro and Paraşüt — and the same method for SAP and Oracle. - A separate database | A separate database per customer — not a row filter in a shared table. - Connect your own AI | Your CRM is open over MCP; you connect your own Claude account and access stays capped by that user's permissions. - Predictable licensing | Three tiers, per user per month, prices written on the page. No module matrix to decode. ##### When we are not the right product - If you are deeply invested in the Microsoft ecosystem. If you work through Teams, report in Power BI and manage identity with Azure AD: Outlook and Microsoft 365 connections are not available today, and we have no built-in integration with Teams or Power BI. - If you run a multi-region, multi-entity structure. Enterprise requirements at that scale are not our focus. - If you want ERP and CRM under one roof. We don't have an ERP side; we connect to your existing ERP instead. - If you are looking for an app marketplace and a broad partner network. We have no app marketplace and no trained partner network. - If your procurement runs through an existing enterprise agreement. We are not a party to such an agreement. FAQ ##### About migrating from Dynamics 365 - Can our Dynamics data be migrated? | Yes. Leads, contacts, accounts, opportunities, activities and your custom fields are migrated and duplicates cleaned out. The scope is decided in discovery and put in writing. - Do you work with Teams and Outlook? | Outlook and Microsoft 365 connections are not available today; we do not connect to Outlook for email or calendar sync, and we say so plainly. Email sending from your own Google Workspace account and two-way calendar sync are available. We have no built-in integration with Teams or Power BI. - How much does Rapitek CRM cost? | Our plans start at 39 USD per user per month, and the setup scope and any fee are put in writing during discovery. When you evaluate any proposal, put setup, customisation and training next to the licence line. - How long does the migration take? | We don't commit to a timeline before discovery. A rollout covers discovery, configuration, data migration and training. After the discovery call, we give you a date, not a range. What drives that date is how ready your data is and the scope of integrations. ##### Let's map the scope and the timeline together. In a 30-minute call we listen to your current setup and talk through whether a migration is realistic. If it isn't, we'll say so. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Email Integration: Sending from Gmail | Rapitek CRM](https://rapitek.com/en/email-integration) Connect your Gmail account with OAuth; the connection covers sending and calendar sync, and the inbox is not read. Outlook and Microsoft 365 are not live. Integration · Gmail and Google Workspace #### If you use Gmail, the email you send goes out from your own account and lands on the customer record. You connect your own Gmail account with OAuth; the connection covers email sending and calendar sync. The email you send lands on the relevant customer record. Inbox reading is switched off, so this is not two-way inbox sync. Outlook and Microsoft 365 connections are not live. Setting up the Gmail connection does not require a development project; it is configured during setup. Request a demo Discuss your setup scope ##### The correspondence sits in a person's mailbox, not on the customer record The quote goes out by email, the objection is written by email, the decision is given by email. That is where the mechanism starts: as long as the correspondence sits in a personal mailbox, whoever is looking at the customer record cannot see it. This is the picture we have seen in our own CRM projects: - Whether the quote was sent and who wrote what stays in a personal mailbox; whoever is looking at the customer record cannot see it. - When a rep leaves or the customer is handed over to someone else, the correspondence history does not transfer; the new owner starts from scratch. - The answer you can give a customer who says "we wrote to you yesterday" depends on whether the person who can find that email is available. - Three people correspond separately on the same subject; the customer gets two different answers to the same question. - The "last contact" field on the customer card is updated by hand; keeping it current depends on nobody forgetting. - An unanswered thread may go unnoticed until the customer follows up. The fix is not to move the team onto a new mail client; it is to send from the mailbox they already use, from inside the CRM, so that what goes out is written to the customer record. This covers the outgoing half of the picture above: inbox reading is switched off, so what arrives in the mailbox stays in the mailbox. ##### The Gmail connection: what it covers and what it does not In Rapitek CRM the email connection is built into the product for one provider: Google (Gmail / Google Workspace). Outlook and Microsoft 365 connections are not live. - Authorisation is via OAuth. You grant access from Google's own consent screen; your email password is not given to us. - The connection covers sending, not inbox reading. An email you write from inside the CRM goes out from the Gmail account you connected. Inbox reading is switched off: correspondence arriving in your mailbox is not pulled into the CRM, so this is not two-way inbox sync. - What you send is attached to the record. The message you send lands under the relevant customer or lead record; even when the owner changes, that history stays on the record. Why only Google? The whole connection is built on OAuth. We do not support connecting a mailbox over generic IMAP/SMTP — that is, connecting a mailbox on your own server or at your hosting provider by supplying a username and password is not possible in this product. Rather than bury this in a footnote, we write it on the page: if your corporate mail infrastructure is not Google, we talk through what can be done on the email side up front, in the discovery call. Do you use Gmail and Google Calendar together? This page is the canonical page for email. For teams that use both we also have a Google Workspace integration page; it narrows to Workspace and spells out one by one why Drive, Docs, Sheets and Meet are out of scope. We have written our general approach to integrations, and what we do not promise, with the same clarity on the integrations page. A concrete scenario ##### Wednesday, 11:15 — the customer says "I think you sent the quote." Here is what changes once the connection is in place: - The quote email sits under the customer record | The email that was sent from the CRM is attached to the relevant customer record, together with its attachment and date. Whoever picks up the phone does not go hunting through a mailbox for "was it sent" — they read it off the record. - The reply that comes back stays in your mailbox | When the customer's reply lands in your mailbox, it is not pulled into the CRM: inbox reading is switched off. This is not two-way inbox sync — the incoming side is read in your own mail client. - An email written from the CRM goes out from your own account | You write the reply from inside the CRM; the message goes out from the Gmail account you connected. Nothing changes on the customer's side. - When the owner changes, the history transfers with it | When the customer is assigned to another rep, the email sent from the CRM stays on the record and therefore transfers along with it. The new owner does not have to ask anyone "what have we written to this customer". - The appointment runs alongside the calendar — on the Google side | Once a meeting is agreed, the event syncs with Google Calendar in both directions: fetching, creating, updating and deleting. Outlook and Microsoft 365 connections are not live, so there is no Microsoft calendar sync either; we have written that out separately below. - The last-contact field is not updated by hand | When you last wrote to the customer and what you wrote is read off the email on the record. Nobody has to open a separate note saying "I wrote, waiting for a reply". ##### What happens in the product once the email connection is in place? - Gmail and Google Workspace accounts | A Google account is connected with OAuth; the permission is granted from Google's own consent screen. The connection covers email sending and calendar sync; the email you send is attached to the relevant record. - Outlook and Microsoft 365 accounts | Outlook and Microsoft 365 connections are not live. Only a Google account can be connected today, and we do not commit to a date for a Microsoft connection. - Sending, not inbox sync | Email goes out from the CRM through your own Gmail account and is written to the record. Inbox reading is switched off, so incoming mail is not pulled in; the team carries on using the mailbox they are used to. - What you send is attached to the customer record | The messages you send collect under customer, lead and opportunity records. What was written to the customer sits on the company's record, not only in an individual's sent folder. - Use alongside Google Calendar | On the Google side the calendar sync is two-way: fetching, creating, updating and deleting events runs on a schedule. Appointment and correspondence meet on the same record. - One customer, one record | The email you send, WhatsApp messages and activities come together on the same customer record. When the channel changes, the customer's history is not split. Scope ##### What syncs and what does not? The table shows where things stand today. For the rows marked "None" we do not commit to a date; build your setup plan on what works today. Topic | Status | Detail - Gmail / Google Workspace email sending | Working | The account is connected with OAuth; email sent from the CRM goes out from your own account and is attached to the relevant customer record - Inbox reading (mailbox to CRM) | None | Inbox reading is switched off; correspondence arriving in your mailbox is not pulled into the CRM. This is not two-way inbox sync - Microsoft 365 (Outlook) email sync | None | Outlook and Microsoft 365 connections are not live; only a Google account can be connected today - Google Calendar sync | Working | Two-way: fetching, creating, updating and deleting events. Runs on a schedule - Outlook / Microsoft calendar sync | None | Outlook and Microsoft 365 connections are not live. Calendar sync exists only on the Google side - Connecting a mailbox over generic IMAP/SMTP | None | A mailbox on your own server or at your hosting provider cannot be connected with a password; only Google OAuth is supported - Scheduled report emails | None | Reports and dashboards exist in the product, but sending a report by email at set intervals is not a feature that works today - The CRM's own notification emails | Separate infrastructure | System notifications go out not from your mailbox but through a separate delivery service (AWS SES) What we can say ##### What we have verified - Sending only | Email goes out from your own Gmail account; inbox reading is switched off - One provider | Gmail / Google Workspace only; Outlook and Microsoft 365 are not live - OAuth | Permission via Google's own consent screen; your password is not given to us - Google only | Calendar sync is specific to Google and runs in both directions - Three EU locations | Database in Helsinki, files in Frankfurt, backups in Falkenstein Implementation ##### How is the email connection put into service? - Discovery | We work out whether your mail infrastructure is Google Workspace — the only one that can be connected today — which mailboxes will be connected and which correspondence should land on which record. We recommend that whoever runs your IT is in this meeting. - Authorisation | The account is connected from the Setup screen; the permission is granted from Google's own consent screen. In Google Workspace tenants an administrator's approval may be required — we walk through this step together; we do not describe it as a one-button job. - Scope and matching | You decide which accounts get connected; no data flows into the CRM from a mailbox you have not connected. Which customer and lead records the email you send matches to is verified with sample data. - Training and go-live | Team training and close follow-up in the first week. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. Configuring the email connection is done within that plan. ##### Our limits: what we do not promise on this page There are four things in email integration that are easy to confuse. We name all four — because learning them on setup day costs more than reading them on this page. - Inbox reading is switched off. The Gmail connection covers email sending and calendar sync. Correspondence arriving in your mailbox is not pulled into the CRM; what is written to the record is the mail you send from the CRM. This is not two-way inbox sync. - Outlook and Microsoft 365 connections are not live. There is no Outlook email sync and no Outlook calendar sync. We do not promise a Microsoft 365 integration, and we do not commit to a date for one. - We do not support generic IMAP/SMTP. Only Google accounts are connected, via OAuth. Connecting a mailbox on your own server or at your hosting provider by supplying its password is not possible; if your corporate mail infrastructure is not Google, email sync cannot be set up. - We do not send scheduled report emails. Reports and dashboards exist in the product; but having a report land in your inbox every morning is not a feature that works today. Reports are viewed in the CRM. Nor do we promise that setup will be easy. Connecting the account goes through Google's own consent screen; in Google Workspace tenants an administrator's approval may be required. We walk through these steps together during setup. Data location: your data is held in the European Union — the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We do not have a single component in Türkiye, and we do not have a region-selection feature. This is a transfer abroad within the meaning of KVKK art. 9; we establish your legal basis for the transfer together during the contract process. Your CRM data is held in a separate database that belongs to you. The details are on the security page and in the KVKK privacy notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your corporate security assessment forms and describe the architecture in writing. We have gathered what we do not promise on the ERP, stock and invoicing side in one place; we do not repeat it here: the three things we do not promise. ##### We keep plan prices in one place, out in the open The Gmail connection is configured during setup. We have written out line by line on the pricing page what each plan covers and which items are priced separately. See pricing We do not write the figure in two places, so that you do not read two different numbers. FAQ ##### Frequently asked questions about email integration - Does Rapitek CRM integrate with Gmail? | Yes. You connect your Google account with OAuth; the connection covers email sending and calendar sync. An email you write from inside the CRM goes out from your own account and is attached to the relevant customer or lead record. Inbox reading is switched off, so incoming mail is not pulled into the CRM — this is not two-way inbox sync. No separate development project is needed; the connection is configured during setup. - Can Microsoft 365 and Outlook email be connected? | No. Outlook and Microsoft 365 connections are not live; a Microsoft account cannot be connected today. Only Google (Gmail / Google Workspace) accounts are connected, via OAuth. We do not commit to a date for a Microsoft connection. - Can we connect the mailbox on our own server over IMAP/SMTP? | No. Generic IMAP/SMTP is not supported; only Google accounts are connected, via OAuth. Connecting a mailbox on your own server or at your hosting provider by supplying a username and password is not possible in this product. If your mail infrastructure is not Google, email sync cannot be set up — we say this up front, in discovery. - Will our Outlook calendar sync with the CRM? | No. Outlook and Microsoft 365 connections are not live, so we do not sync your Outlook calendar. Calendar sync exists only on the Google side, and there it runs in both directions: fetching, creating, updating and deleting events. - Is the sync two-way? | No. An email you write from inside the CRM goes out from the Gmail account you connected and is written to the record — that is the outgoing direction. Inbox reading is switched off, so correspondence arriving in your mailbox is not pulled into the CRM. The team does not move to a new mail client; they carry on using the mailbox they are used to. - Do we have to give you our email password? | No. The connection is made with OAuth: you grant access from Google's own consent screen, and your password is not given to us. You can revoke the permission at any time from your own account management screen. - Will our personal correspondence end up in the CRM too? | No mailbox is read. Inbox reading is switched off, so no incoming correspondence is pulled into the CRM; what is written to the record is the mail you send from the CRM through the account you connected. Which accounts get connected is your decision. If there are mailboxes your company policy requires to be kept separate, we do not connect them. - Can reports arrive by email every morning? | Not today. Reports and dashboards exist in the product, but sending a report by email at set intervals is not something we can offer as a working feature; reports are viewed in the CRM. We put this line on the page so that it is not a surprise on setup day. - Do the notification emails the CRM sends go out from our account? | No. System notifications go out not from your mailbox but through a separate delivery service. The email you write to your customer, on the other hand, goes out from the Gmail account you connected — the two are different paths. - Is the email connection included in the plan price? | Configuring the built-in connections — Gmail email, Google Calendar, WhatsApp, İYS, SMS and import/export — is within the scope of setup. The scope of the setup and its cost, if any, are worked out in the discovery call and shared in writing before work begins. For what each plan covers, see our pricing page. - How long does setup take? | We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. Setup consists of these steps: discovery, configuration, data migration, training and go-live. Configuring the email connection is done within that plan. Connecting the account goes through Google's consent screen; in Google Workspace tenants an administrator's approval may be required. - Do WhatsApp conversations show up on the same record? | Yes. When you connect your own Meta WhatsApp Business account, the messages are also written to the customer record; the email you send and the WhatsApp history come together on the same record. For scope and setup details, see our WhatsApp CRM page. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We do not have a single component in Türkiye and we do not offer region selection. This is a transfer abroad within the meaning of KVKK art. 9; we establish the legal basis for it together during the contract process. Your CRM data is held in a separate database that belongs to you. ##### Related pages - Google Workspace integration | A narrow scope for teams that use Google only: Gmail and Google Calendar together; Drive, Docs, Sheets and Meet are out of scope. - Integrations | Which connection works in the product today, which ones we build on request — and the three things we do not promise, with the reasons. - WhatsApp CRM | Shared inbox and team messaging order: the other channel that meets email on the same customer record. - Security | Which country the data sits in, the sub-processor list, backups, the audit trail, and what we do not offer yet. ##### Reading before you connect a channel - What does “we have email integration” cover? | Which provider, which direction, which permission scope — a six-step procedure for putting a vendor to the test. - WhatsApp Business API guide | The difference between the official Cloud API and QR pairing, and the risk of the number being restricted. - What happens if a connected message is deleted? | The trash, backup frequency, and the measured result of a restore test. ##### Let's get your email flow clear in 30 minutes In the demo call, let's go through which mail infrastructure you use, which mailboxes will be connected and how the mail you send will land on the customer record — using your own scenario. Request a demo The scope of the setup and its cost, if any, are worked out in the discovery call and shared in writing. ### [ERP CRM Integration: Scope and Method | Rapitek CRM](https://rapitek.com/en/erp-crm-integration) Your ERP stays put; the CRM talks to it: account, balance and document data on the sales screen. We build the connection with REST API and OAuth2. ERP and CRM · category guide #### Your ERP stays where it is; the CRM talks to it. Account, balance, order and invoice data stays in the ERP; your sales team sees the same data in the CRM. We build the connection ourselves, using REST API, OAuth2, webhooks and import/export. This page describes the framework that stays the same whatever your ERP is called. Request a demo Schedule a discovery call ##### ERP and CRM do not do the same job — where exactly is the line? The debate between ERP and CRM comes from the fact that both systems use the same words. Both have a “customer”, both have a “product” and a “price” — but they do not mean the same thing. - The ERP records work that has already happened. The order was entered, the goods shipped, the invoice issued, the payment collected. The accuracy of the record carries financial and legal consequences; that is why an ERP is conservative, and it should be. - The CRM records work that has not happened yet. Who called, what was discussed, which quote was given, why it was lost. A record here is not a document but a possibility; it is normal for it to change often. - The gap sits between the two. One question sums it up: when does the person writing the quote find out that the company across the table has an overdue balance? The ERP knows this; the person writing the quote does not. Integration work means closing that gap, and it is finished when four questions are answered: which field, in which direction, how often, on which key. The fourth is less visible than the other three, because its answer only emerges once you put the records side by side: which field matches the same company across the two systems? In our own installations that field is the tax identification number, not the trade name — because a name can be written “A.Ş.” in one system and “AŞ” in the other, and a match built on the trade name disappears silently. We draw up this four-line table in the discovery call and hand it over in writing; if a line stays empty, we write it down as empty. When an empty line gets filled in halfway through the project, the field mapping and testing done up to that point have to be revisited — we have seen this in our own projects. That is why the table is filled in before the work starts. ##### Why the connection is not an out-of-the-box module There is no out-of-the-box module for any ERP, and we will not claim there is. The connection is built as an integration project whose scope is determined in the discovery call, using the REST API, OAuth2, webhooks and import/export. The proof that this is not a bluff is in how the product is actually used: in a live customer installation today, a third-party ERP integrator reads and writes records over that same REST API. We do not name them, because we do not have permission to publish the customer's or the integrator's name. And let us not overstate it: this is a single installation, not a list of case studies. These are the tools we have: - REST API — the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint; you can read the field structure from outside with describe. Authentication is via OAuth2; composite sends 25 sub-requests in a single call, and bulk endpoints carry 200 records per call. - Outbound webhooks — a signed notification is sent to your system on record creation and change events; the receiving side verifies the signature to filter out forged notifications, and failed calls are retried. - Import — a four-step wizard: upload, map fields, preview, run. More than 75 objects are supported; there is a limit of 25 MB per file and 100,000 rows per job, and you confirm the mapping on screen. Export is done in the same module; we have not measured its limits, so we are not putting a figure here. So why do we not write a plug-in that works the same way for every customer? Because access on the other side changes from installation to installation: the ERP's version, the licence scope, which modules were bought and where the system runs — on-premise server or hosted — determine the method. Handing everyone the same button and saying “it works the same in every installation” would be a promise that fails as soon as the access conditions change. For the general framework, see the integrations page. We also cover how the same framework looks for a single ERP on our Netsis integration page, and — for readers who want the two paths side by side with a decision criterion — on a separate page comparing a built-in connection with a project-specific integration. A concrete scenario ##### Wednesday, 10:40 — IT, sales and finance around the same table in the discovery meeting. Six decisions come out of it: - Each field's authority is assigned to one side | Trade name and tax number stay in the ERP; conversation history and quotes stay in the CRM. No field is left with two owners: if the same field is updated independently in two places, nothing decides which value is valid when the two diverge. - The matching key is chosen, the exceptions listed | The tax identification number is taken as the key; the trade name is used only for verification. A list of records with no key is drawn up, and the meeting decides whether they should be merged or left to be handled manually. - The direction of flow is written down field by field | Balance flows from the ERP to the CRM; the order details of a won opportunity flow from the CRM to the ERP. If a field is to work in both directions, the conflict rule — which side wins in a contradiction — goes on the same line. - Frequency is a business decision, not a technology preference | Balance visibility can be achieved with a daily transfer; if it needs to be closer to the event, the method shifts to the REST API and webhooks. As frequency goes up, scope and cost change, which is why the business side makes this call. - Whether the ERP can be reached from outside is answered | If there is access, we talk about the REST API; if not, the flow is built on periodic import/export. Both work; the difference is latency and maintenance load. If the access conditions change later, the same scope moves onto an API-based flow. - Who will write the connection is decided | Both paths are open: we write the connection, or your partner who knows the ERP side writes it themselves over that same REST API. In the second case we provide the schema, the OAuth2 access and the field mapping table. ##### Flows that can be built between the ERP and the CRM - Account matching and duplicate clean-up | Accounts in the ERP are linked to company records in the CRM using the tax identification number as the key. Records whose key does not match are filtered out during setup; the matching rule lives in the written scope, not in someone's memory. - Visibility of balance, due dates and credit limit | Fields such as open balance, overdue amount and credit limit are transferred onto the company record. The transfer frequency — daily, weekly or periodic — is set in the scope, and the values are visible on the quote screen. - Tracking document data | Order and invoice headers are tracked as a list on the company record. Authority over the document stays in the ERP; the CRM does not produce documents, it adds a visibility layer for the sales team. - Product and price list transfer | When product records and the price list are transferred from the ERP to the CRM, quotes are written at the current price. The transfer can be periodic or set up over the REST API; authority stays in the ERP. - Passing a won opportunity to the ERP side | A signed webhook that passes the order details to the external system when an opportunity is won can be set up. Entering the same data a second time by hand on the accounting side is reduced; which fields are sent is written into the scope. - Defining the CRM equivalent of ERP fields without writing code | An administrator defines the CRM-side equivalent of fields such as credit limit, payment terms, dealer code or region without writing code. Adding custom fields and custom objects is standard in the product. Choosing a method ##### Four methods — which one, when? The method is chosen during discovery according to the access available on the ERP side; the chosen method and scope are shared in writing. Method | What it does | When it is preferred - REST API (183 business objects, each with its own data and schema endpoint) | An external system reads and writes records in the CRM; it is authorised with OAuth2, the schema is read with describe, and composite sends 25 sub-requests in a single call | When suitable access exists on the ERP side and the flow is expected to run close to the event - Outbound webhook | Events in the CRM are delivered to the external system with a signature; the receiver verifies the signature and failed calls are retried | For flows that need notification from the CRM towards the ERP, if there is an endpoint on the ERP side to listen - Import (Data Hub) | Excel/CSV extracts are transferred with a four-step wizard: upload, map fields, preview, run. 75+ objects, 25 MB per file, 100,000 rows per job. Export is done in the same module; we have not measured its limits | It requires no API access on the other side, so it can be started before the access question is answered; when a periodic sync is enough, or when the ERP cannot be reached from outside - Third-party integrator | Your partner who knows the ERP side can write the connection themselves using that same REST API; we provide the schema, the OAuth2 access and the field mapping table | When you want to keep working with the firm that implemented your ERP What we can say ##### What we have verified - 183 | Business objects in the REST API, each with a data and schema endpoint, OAuth2 - 1 live installation | A third-party ERP integrator reads and writes records over this API - 25 sub-requests | In a single composite call; bulk endpoints carry 200 records per call - 100,000 rows | Upper limit per import job; 25 MB per file, 75+ objects supported Implementation ##### How an ERP connection is put live - Discovery and access assessment | We establish your ERP's version, licence scope, which modules you use and where the system runs. We recommend that the partner who implemented your ERP, or your IT lead, joins this call; they hold the answer to the access question. - Field mapping table and written scope | Which field flows in which direction, how often, and the conflict rule are written line by line. The method is chosen here; the scope and any cost are shared in writing before work starts. The table is filled in first and the work starts after, so no surprise item appears. - Configuration and a test transfer with sample data | Fields, lists and permissions on the CRM side are set up; a test transfer is run with a sample of a real extract. Matches are verified on the key field, duplicate records are filtered out and faulty rows are reported. - Training, go-live and maintenance responsibility | Team training and close follow-up in the first week. Who updates the mapping table when a field or version changes in your ERP is written into the scope; when a flow stops, you know who to contact. Limits ##### Three things we do not promise — and the long reasons why - We do not promise real-time stock synchronisation | Authority over the stock record stays in your ERP or warehouse system. We do not offer a live two-way stock mirror as a measured capability; if we did, it would produce two stock figures that do not agree. Instead we build a visibility layer with a defined scope. - We do not say orders, invoices and payments flow on their own | The chain is built into the product and can be switched on or off per installation; turning a quote into an order runs through a built-in action. But we do not think it is right to sell this as an automated accounting flow — producing official documents is not our job. - We do not promise production and MRP automation | Bill of materials, production line and work order screens exist in the product, and the BOM side has been set up with real data. But we cannot today point to a customer using work order execution; we do not sell what we cannot demonstrate. ##### What the three have in common — and how this page relates to the short version This page is the long reasoning; the short verdict sits elsewhere. The one-sentence verdict on the three things we do not promise, and what we do instead, is in the limits section of the integrations page: a three-line table, for a quick look. The reasons are written out at length here. We split the work this way so that we do not end up with two different sentences in two places — the verdict there, the reasoning here. What the three have in common is this: all three promises would require taking authority over the data away from the ERP and moving it to the CRM. A CRM that does this starts to replace the ERP; and replacing the ERP is not an integration project but an ERP replacement project, and that is not our line of work. A sync and a mirror are not the same thing. Copying a field between two systems does not on its own count as a sync; a sync also requires defining which side wins in a contradiction. How often that rule comes into play is determined by how fast the field changes: a balance may change a few times a day, stock within minutes. When the rule fires, the losing side shows the wrong number; seeing the wrong stock figure on the sales screen has a different consequence from seeing no stock figure at all — because a promise is made to the customer on the strength of the number that was seen. What do we do instead? We leave authority where it is and move visibility. For stock, a visibility layer with a defined scope and frequency; on the document side, carrying the number, date and amount across as fields; in production, setting up the bill of materials and the line definition, but not claiming that planning is run from the CRM. The same criterion applies to all three: we sell what we can demonstrate with a customer using it. e-Fatura and e-Arşiv: Rapitek CRM does not issue official documents and is not a GİB-accredited special integrator; the product has no fields such as ETTN or GİB status. Your invoices continue to be issued by your current provider; the invoice number, date and amount can be carried onto the company record over the REST API or by periodic import. Data location: your data is held in the European Union — the database in Helsinki (Finland), the files you upload in Frankfurt, and database backups in Falkenstein (Germany). We have no component in Türkiye and we do not have a region selection feature. This is a transfer abroad under KVKK art. 9; we establish the basis for that transfer together during the contract process. The details are on the security page and in the KVKK privacy notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### Scope comes out of discovery; plan prices are in the open The cost of an ERP connection depends on data volume, the direction of the flow and the access available on the other side; it is shared in writing after discovery. We publish plan prices and separately priced items on a single page. See pricing Three plans, a scope table and separately priced items on one page. FAQ ##### Frequently asked questions about ERP–CRM integration - We already have an ERP. Why would we need a CRM? | Because an ERP records work that has happened and a CRM records work that has not happened yet. Orders, invoices and collections are the ERP's job and should stay there. Leads, conversation history, the quoting process and the reason a deal was lost are not in the ERP's data model; in our own CRM projects we have seen this information sitting in personal Excel files and WhatsApp threads. The job of integration is not to change the ERP but to connect the two sides with a defined flow. - What does ERP CRM integration mean in practice, what actually gets done? | It means answering four questions: which field, in which direction, how often, on which key. The answers are written into a field mapping table; that table is then implemented with the REST API, outbound webhooks or import/export. The starting flow we recommend is making the account balance and document data from the ERP visible on the company record in the CRM. Work does not start before the table exists — when an empty line gets filled in halfway through the project, the mapping and testing done up to that point have to be revisited. - Is there a ready-made ERP module in Rapitek CRM? | No; it would not be right to say there is. There is no out-of-the-box module for any ERP. What there is instead: the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside that there is OAuth2, signed outbound webhooks and a four-step import wizard; we build the connection on top of these tools, as a project whose scope is set during discovery. - Has anyone actually used this API so far? | Yes. In a live customer installation, a third-party ERP integrator reads and writes records over Rapitek CRM's REST API — this is a measured fact. We do not give names, because we do not have permission to publish the customer's or the integrator's name. Let us also state that this is a single installation: one verified example, not a list of case studies. - Which ERPs do you work with? | The framework does not change with the name of the ERP; in every case the connection is built with the REST API, OAuth2, webhooks and import/export. We have pages where we have written up the scope separately: Netsis, Nebim, Logo, Mikro, SAP, Paraşüt and Luca. The same path applies to other systems such as Dia, ETA, Odoo, Oracle, IFS, Set, Uyumsoft and Workcube. If you use an ERP that is not on the list, our answer does not change: we look at what access is possible on the other side, work out the scope and give it to you in writing. - Which field is used to match companies across the two systems? | In practice, the tax identification number. The trade name is not used as the key, only checked for verification: when the same company is written “A.Ş.” in one system and “AŞ” in the other, the trade name match disappears without anyone noticing. A separate list of records with no key is drawn up during setup, and we decide together with you whether they should be merged. - Our ERP server cannot be reached from outside. Is integration still possible? | Yes, only the method changes. Without access, the flow runs on periodic import/export: extracts taken from the ERP are transferred into the CRM with the same template, on a defined schedule. This path requires no API access on the other side; it can be started before the access question is answered. If access conditions change later, the same field mapping table moves onto an API-based flow — the scope is not rewritten, only the carrier changes. - Can our own ERP partner write the integration? | Yes, this is a path we support. Your partner who knows the ERP side can write the connection themselves using Rapitek CRM's REST API; we provide the API documentation, the OAuth2 access, the object definitions and the field mapping table. Who updates the mapping table when a field or version changes is also set out in the written scope. - Why is stock synchronisation not promised? | Because stock is a field that can change within minutes; when it is copied between two systems, the values on the two sides can diverge. A sync requires defining which side wins in a contradiction; when that rule fires, the losing side shows the wrong number. Seeing the wrong stock figure on the sales screen has a different consequence from seeing no stock figure at all: a promise is made to the customer on the strength of the number that was seen. We leave authority in the ERP and build a visibility layer with a defined scope. The short verdict is in the limits section of the integrations page; the long reasoning is on this page. - Can we issue e-Fatura from the CRM? | No. Rapitek CRM does not issue e-Fatura or e-Arşiv documents and is not a GİB-accredited special integrator; fields such as ETTN or GİB status do not exist in the product. Your invoices continue to be issued by your current provider. Information such as the invoice number, date and amount can be carried onto the company record as fields over the REST API or by periodic import. - Is synchronisation real-time? | It depends on the method, and we do not promise “real-time” up front. REST API and webhook-based flows can run close to the event; import/export is periodic. For balance visibility a daily transfer may be enough; if it needs to be more frequent, we define that in the scope and commit to the frequency in writing. - How is the cost of the integration determined? | By scope: the number of fields to be carried, the direction of the flow, the frequency, whether there is a conflict rule, and what access is possible on the ERP side. That is why we do not put a figure on this page. After the discovery call we share the scope and the cost in writing; integration is a separate line item from the CRM implementation and is priced separately. Plan scopes are on the pricing page. - How long does implementation take? | We do not commit to a duration before discovery; after the discovery call we give you a date, not a range, and the day you go live is set out in the written scope. Implementation consists of these steps: discovery, configuration, data migration, training and go-live. An import/export-based ERP flow can be built within that plan; the duration of API-based flows becomes clear during discovery, according to scope. - Will we lose data when we move our ERP data into the CRM? | We do not give a zero-data-loss guarantee — it would not be right to guarantee something we cannot measure. What we do: you confirm the mapping at the preview step of the import wizard, the transfer is first tried with sample data, faulty rows are reported, corrected and run again. Your source file stays with you; and you can export the data in the CRM at any time. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, and database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. This is a transfer abroad under KVKK art. 9; we establish the basis for it together during the contract process. Your CRM data is held in a separate database of your own. ##### Is your ERP on this list? - Netsis integration | Which direction account, balance, order and invoice data flows in; choosing a method for an installation running on an on-premise server. - Nebim integration | How the retail and wholesale channels are kept apart in the same CRM; the flow of dealer balances and the seasonal price list. - Logo integration | Scope for installations using Tiger, Go and j-Platform; the effect of a version upgrade on the field mapping table. - Mikro integration | Connecting to the commercial and accounting software: account records, balance and invoice data visible on the sales screen. - SAP integration | Scope, choice of method, and written answers to the security questions IT will ask. - Paraşüt integration | The pre-accounting side: account and collection visibility; what we do and do not do about e-Fatura. - Luca integration | How the flow is built when your accounting sits with your financial adviser, and the scope of periodic transfers. - Built-in connection or project? | The decision criterion: when a connection configured during setup is enough, and when a project-specific integration is required. - Integrations | The connections working in the product today and the ones we build on request; the short verdict on the three things we do not promise. - Security | Which country the data sits in, the list of sub-processors, backups, audit trail and what we do not offer yet. ##### Let's answer the four questions together in 30 minutes Which field, in which direction, how often, on which key — in the demo call let us start filling in this table against your own ERP, and choose the method and the scope together. Request a demo The scope of the implementation, and any cost, are worked out in the discovery call and shared in writing. ### [From Excel to a CRM | How the Move Works | Rapitek](https://rapitek.com/en/excel-to-crm) When a spreadsheet stops being enough, and how the move actually runs: what gets migrated, what gets cleaned, and what your team has to change. Migration guide #### From Excel to a CRM: the hard part isn't the data, it's the habit. Excel isn't a bad tool — it's the wrong tool for tracking sales. This page covers when to make the move, how to prepare your data, and where migrations got stuck in our own projects. Let's plan the move together CRM Readiness Quiz ##### When does Excel stop being enough? A spreadsheet is fine for holding a customer list for a long time. The moment it stops being enough usually announces itself like this: - Three versions of the same file are in circulation. Whose copy is current has become a matter of debate. - Follow-up is nobody's job. “Who is going to call this customer?” has no answer in the file. - The history is gone. What was discussed and what price was quoted lives on somebody's phone or in their email. - Reports are assembled by hand. At month end, someone loses two days to pivot tables. - When an employee leaves, the customer leaves too. The relationship belongs to the person, not the company. If a few of those sound familiar, the problem is no longer the file — it's the process. Preparation ##### How to prepare your spreadsheet before the move - 1. Consolidate into one file | Pull the scattered files into a single sheet. Decide now which version is authoritative — deciding during the migration is far more expensive. - 2. Fix the header row | Give every column one clear heading: company, contact, phone, email, city, last contact, status. Merged cells and stacked header rows make migration harder. - 3. Deduplicate on phone and email | We match duplicates on the phone number: if the same number shows up on two records, that is where the match is made. Unify the format — a mixed country code makes one number look like two records. We clean duplicates during the import too; we saw this in our own migration work. - 4. Flag the dead records | Don't delete companies that closed or haven't been touched in years — flag them in a separate column. They move across as archive and stay out of the daily list. - 5. Decide what won't move | Not every column needs an equivalent in the CRM. Fields nobody uses stay empty in the new system too and fill the screen with columns nobody completes — we saw this in our own migration work. ##### Where did migrations get stuck in our own projects? There are three places where we have seen a migration get stuck in our own projects; all three were about the setup, not the software. This is our own observation, not a measured industry rate: 1. The system went in and nobody used it. The team stayed on Excel because the new system didn't make their work easier — it produced reports for the manager. The fix: configure it around the salesperson's daily flow. 2. Too many fields. “While we're at it, let's record everything” turns into a long list of mandatory fields. In the first week everyone started leaving them blank. The fix: start with few fields and add as the need appears. 3. The migration landed in the busiest month of the year. The team had no time to learn. The fix: pick an off-season date. How it runs here ##### An Excel migration at Rapitek - Discovery | We open your file together. Which column goes where, and which piece of information becomes a field rather than a note — we work that out in 30 minutes. - Import | Records are imported, duplicates cleaned out and phone formats unified. You keep the original file; after the import we compare record counts, and anything missing is corrected and re-run. - Configuration | Your pipeline stages, fields and reports are set up around your process. Modules you won't use don't get switched on. - Training and the first week | We train the team and stay close through the first week. If the team doesn't move into the new system in that first week, sliding back to the old file gets easier — we saw this in our own projects. FAQ ##### About the Excel migration - My spreadsheet is a mess — can it still be migrated? | Yes. A messy file is expected and it doesn't block the migration. We look at it together in the discovery call and decide there how much of the cleanup is yours and how much is ours. - Will we lose data? | You keep the original file and we never write over it. After the import we compare record counts; if anything is missing, it is corrected and re-run. - What if the team goes back to Excel? | It is a real risk and we'll say so plainly. A CRM that doesn't make a salesperson's day easier won't be used — we saw this in our own projects; what decides the outcome is not the software itself but the setup decisions. That is why we do the setup ourselves and stay close through the first week. - How many records can be migrated? | The import wizard has measured limits: 25 MB per file and 100,000 rows per job. Larger files are imported in parts, and after each part record counts are compared; if anything is missing, that part is corrected and re-run. We measure your file's size and structure together during discovery and build the import plan around it. - How long does the move take? | We don't commit to a timeline before discovery. After the discovery call we give you a date, not a range: once the file's structure, the columns to be migrated and the training plan are settled, you get the schedule in writing. ##### Let's look at your file together. In a 30-minute call we'll open your spreadsheet and work out which column goes where. If it's still too early to move, we'll say that too. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Gemini Integration: CRM and REST API | Rapitek CRM](https://rapitek.com/en/gemini-integration) The way to connect Gemini to the CRM is the open REST API and OAuth2. On the Google side, the connections live today are Gmail and Google Calendar sync. Integration · Google Gemini #### If you are on Google Workspace, your CRM already talks to the Google side. Gmail connects over OAuth; the connection covers email sending and calendar sync, not two-way inbox sync. Google Calendar works in both directions — pulling, creating, updating and deleting. The surface you will rely on in order to connect Gemini is the REST API authorised with OAuth2; we build it as a project whose scope is defined during discovery. Request a demo Schedule a discovery call ##### "We're on Google, so it reads the CRM too" — it does not In a company that uses Google Workspace, Gemini is not a choice but an encounter: you open Gmail, it is there; you write a document, it is there. That habit produces a very reasonable assumption — “we're on Google, so it reads the CRM too.” It does not. The CRM is a separate system and the door between them has to be opened. This is the picture we see in our own implementation meetings: - Correspondence with the customer sits in Gmail, the appointment in the calendar, the quote and the record somewhere else. All three belong to the same customer but they are not attached to the same record. - In a purchasing meeting, “do you have a Google integration?” is asked as though it were a single question. In fact it contains five separate products: Gmail, Calendar, Drive, Docs, Meet. Saying “yes” to all five is easy; telling apart which of them is actually in place is hard. - The AI question is asked with the same blur. The phrase “AI-powered” does not say which model looks at which data with which permission. - IT asks something else: which data goes where, who turned it on, can it be revoked? This page separates all four. On the Google side there are two connections that are measured and live today, there are four products that are out of scope, and for Gemini there is a path that has to be built. We do not put the three in the same sentence. ##### There are two things live on the Google side — and neither of them is Gemini We have no out-of-the-box module for Gemini and we are not going to say that we do. The connection is built as an integration project using the REST API, OAuth2, webhooks and import/export, with its scope defined in the discovery call. We also have no partnership with Google, no joint programme and no approved AI pairing; because we do not have one, we do not imply one either. Rapi, the assistant inside the product, runs on Anthropic Claude — not on Gemini. Our 18-tool MCP package, downloaded from the Setup screen, is today defined as a Claude connector; we cannot say that it has been tested with any other AI client, and because we have not tested it we do not say so. You will not find the sentence "Gemini-powered CRM" on this page. By contrast, there are two connections that really are live on the Google side — and they are the most concrete part of this page: you connect your Gmail account over OAuth, and the connection covers email sending and calendar sync — mail you send lands on the relevant customer record, but this is not two-way inbox sync and inbox reading is switched off; Google Calendar works both ways — events are pulled, and are also created, updated and deleted from the CRM; the sync runs on a schedule. In the product, calendar sync is specific to the Google side only. The details of both are on the Google Workspace integration and email integration pages; we do not repeat them here. We write what is out of scope with the same clarity: the product has no connection for Drive, Docs, Sheets or Meet. It would have been easy to say "with all Workspace apps"; that is not the measured situation. When you want to connect Gemini to the CRM, the surface you will rely on is the product's open API: the product ships out of the box with 183 business objects and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there are OAuth2, a composite endpoint that carries 25 sub-requests in a single request, and bulk endpoints that work on up to 200 records per call. We can say that this surface really is usable from outside on the strength of a measured fact: in one live customer installation, a third-party ERP integrator reads and writes records over this same REST API. We do not give a name because we do not have permission to publish it; this is a single installation, not a list of case studies. The same framework as it applies to an ERP is on the Netsis integration page, and our general approach is on the integrations page. A concrete scenario ##### Wednesday 09:35 — the day starts in Gmail. Once the connections are in place, this is what changes: - Email you send to the customer is attached to the record | Once your Gmail account is connected over OAuth, the connection covers email sending and calendar sync: mail you send lands on the relevant customer record. This is not two-way inbox sync — inbox reading is switched off. When the rep changes, that history stays with the company. - Appointments work in both directions | Events are pulled from Google Calendar; events are also created, updated and deleted from the CRM. The sync runs on a schedule, so nobody has to copy anything by hand. - "When did we last speak?" is answered from the record | The meeting history is read from the customer record rather than by searching the calendar. Correspondence, appointment and opportunity sit side by side on the same card. - The Gemini side is opened by a separate permission decision | When the connection is built, which object gets read permission and which gets write permission is written out one by one in the scope. We do not grant access that is open to everything by default. - Changes to existing records leave a trace | Changes made over the API to existing records land in the field-level change history: when which field moved to which value (for protected fields, only a marker). A newly created record's initial values are not recorded there. The audit trail also covers an assistant coming from outside. - The relationship with the provider stays in your name | You use your own Google account and your own AI subscription. The contract on that side is between you and your provider; we do not sell tokens or credits in between. Once the connection is built — one example ##### A scenario that works if you connect Gemini over the REST API: the pre-meeting briefing - Permission starts narrow: read only | The connection is built through your own Google account; which connection route is used on the Gemini side is chosen during discovery, according to what the client supports at that time. As a starting scope we recommend read-only permission on the customer, opportunity and activity objects. - The client reads the field structure itself | Which object has which fields is read from outside with the describe endpoint. You do not have to hand over a field list; a custom field added during implementation shows up at the same endpoint. - One question before the meeting, one summary back | When you ask “where do things stand with the company I'm seeing tomorrow?”, the client reads that customer record, its open opportunities and its latest activities; the composite endpoint, which carries several objects in a single request, exists for exactly this. - If write permission is granted, changes leave a trace | If you want Gemini to write the meeting note, write permission is opened within the same scope. Every API change to an existing record lands in the field-level history: which field, when, to which value (for protected fields, only a marker); a new note's initial values are not recorded there. ##### The surface you rely on on the Google side - Gmail — live today | Your account connects over OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant record. This is not two-way inbox sync — inbox reading is switched off. Generic IMAP/SMTP is not supported, and Outlook and Microsoft 365 connections are not live. - Google Calendar — two-way | Events are pulled; they are created, updated and deleted from the CRM. The sync runs on a schedule and, in the product, is specific to the Google side only. - 183 business objects, each with its own endpoint | The product ships out of the box with 183 business objects and each one is published in the REST API with its own data and schema endpoint. This is the surface an AI client will rely on; the field structure is read from outside with describe. - Authorisation with OAuth2 | Access is granted with OAuth2; no user password is shared. You define the scope, and you can withdraw it just as you granted it. - describe, composite and bulk endpoints | The schema is read from the API; composite carries 25 sub-requests in a single request, and bulk endpoints work on up to 200 records per call. - The change history covers changes made over the API | Changes made over the API to existing records land in the field-level change history; the field an AI changed on an existing record can be seen afterwards. A newly created record's initial values are not recorded in that history; the creator (the user the API client is bound to) and creation time are set by the system and cannot be changed from the user screens, data import or the API. What is measured and what is not ##### What exists on the Google side, and what does not? The two connections live on the Google side today are Gmail and Google Calendar; neither of them is Gemini. A Gemini connection is scoped separately, over the REST API. Topic | Status today | How it is built - Gmail | Live today: connects over OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant record — not two-way inbox sync, inbox reading is switched off | You connect your account over OAuth; the details are on the email integration page - Google Calendar | Live today and two-way: pull, create, update and delete; runs on a schedule | Set up with the Google account connection; in the product, calendar sync is specific to Google - Gemini | We do not have a Gemini connection built into the product | Built over the REST API and OAuth2, as a separate piece of work whose scope is defined during discovery - MCP package — 18 tools | Today it is defined as a Claude connector | We cannot say that it has been tested with Gemini; and because we have not tested it, we do not say so - Drive, Docs, Sheets and Meet | Out of scope; we have no code that connects to these products | We do not offer it. Attachments and files are kept in the CRM's own file storage - App verification on the Google side | We share its status in writing before implementation | That is why there is no sentence such as "it connects without a hitch" on this page What we can say ##### What we have verified - Two-way | Google Calendar sync: pull, create, update and delete - Live | Gmail OAuth: email sending and calendar sync; not two-way inbox sync - Out of scope | We have no connection for Drive, Docs, Sheets or Meet - Claude | The model family that Rapi, the assistant inside the product, runs on - Not tested | Whether the MCP package works with Gemini has not been measured to date Implementation ##### How is the Google side brought into service? - Discovery | We work out who administers your Workspace tenant, who the Gmail and Calendar sync will cover, and how you use Gemini today. We recommend that your IT lead is in this meeting. - Scope and permission table | Which user's account will be connected, and which object gets read permission and which gets write permission, are written down. The Workspace products that stay out of scope are also listed explicitly in the same document. - Configuration and a limited start | The Gmail and Calendar connection is set up over OAuth and verified with sample records. The AI side is opened with a narrow scope; we recommend limiting the initial scope to read only, with write permission extended later and by your decision. - Training and go-live | The team is shown what the sync does and how the change history is read. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The scope of the project-specific connection is also settled in that same discovery. ##### Our limits: what we do not promise on this page Under the Google heading, the thing that is easily overstated is scope; under the AI heading, it is the implication of a partnership. We write down what we do not promise, by name. - We do not say “Gemini-powered CRM”. Rapi, the assistant inside the product, runs on Anthropic Claude. - We have no partnership with Google and no approved AI pairing and we do not imply such a relationship. - We do not say that our MCP package works with Gemini. The package is today defined as a Claude connector and we have not tested it with any other client. If you want to connect another assistant, the path is the REST API and OAuth2; that is a separate piece of work whose scope is defined during discovery. - We do not say “it works with all Workspace apps”. Drive, Docs, Sheets and Meet are out of scope; we have no code that connects to these products. - We do not say “it connects without a hitch”. We share our app verification status on the Google side in writing before implementation; we do not leave what you will see on the connection screen as a surprise. - We do not sell autonomous agents. In the product's own assistant, the number of steps that can be taken in a single request is limited — eight at most. - We do not promise that your stock will be in sync, that the order → invoice → collection chain will flow by itself, or production/MRP automation. We have written the reason for all three, and what can be done instead, in one place: the three things we do not promise. AI and consent: the product's own assistant is off by default; unless you turn it on, your CRM data is not sent to any AI provider. When you connect your own Gemini client, you are the one who has made that decision, and we define its scope in writing during implementation: which object, which permission, which user. Seen from Türkiye this is a transfer abroad and falls within the scope of Article 9 of Law No. 6698; we establish its legal basis together during the contract process. Our sub-processor list is on our security page. Data location: your data is kept in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no such feature as region selection. With the Gmail and Calendar connection, your mailbox and your calendar continue to stay on the Google side. The details are on the security page and in the KVKK privacy notice. Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment questionnaires and describe the architecture in writing. ##### We keep plan prices in one place, out in the open The scope of the connection on the Google side, and its cost if there is one, are worked out in the discovery call and shared in writing. Plan prices and separately priced items we publish on a single page, with the figures. See pricing Three plans, the scope table and separately priced items, all on one page. FAQ ##### Frequently asked questions about the Gemini integration - Can we connect Gemini to Rapitek CRM? | It can be connected, but not through a provider-specific module of ours. The path runs through the product's open surface: the REST API authorised with OAuth2, schema reading with describe, composite and bulk endpoints. That surface is live today. Which connection route will be used on the Gemini side is chosen together during discovery, according to what the client supports at that time; the scope, and the cost if there is one, are shared in writing. - Is Rapitek CRM a "Gemini-powered" CRM? | No. Rapi, the assistant inside the product, runs on Anthropic Claude, and we write that by name. The sentence "Gemini-powered CRM" does not appear on this page because it is not true. When you evaluate an AI feature, asking which model it works with is a fair question; we write the answer without being asked. - Do you have a partnership with Google? | No. We have no partnership with Google, no joint programme and no approved AI pairing. The Gmail and Google Calendar connections are set up with the standard OAuth method; that is not a business partnership but an authorisation route that anyone can use. We care about the difference because tenders and security questionnaires ask about this distinction. - Does your MCP package work with Gemini as well? | Because we have not tested this, we cannot say that it works. The 18-tool package downloaded from the Setup screen is today defined as a Claude connector. If you want to connect Gemini or another client, the route we trust is the REST API and OAuth2; that is a separate piece of work whose scope is defined during discovery, and it is priced as such. - What is live on the Google Workspace side today? | Two connections: Gmail and Google Calendar. You connect your Gmail account over OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant customer record — this is not two-way inbox sync, inbox reading is switched off. Google Calendar also works both ways: events are pulled, and are also created, updated and deleted from the CRM; the sync is scheduled. Both of them have their own detailed page. - Is the Google Calendar sync really two-way? | Yes, two-way. It does not only pull from the calendar; it also creates, updates and deletes events through the CRM. The sync runs on a schedule. Let us add this too: in the product, calendar sync is specific to the Google side only — Outlook and Microsoft 365 connections are not live. - Do Drive, Docs, Sheets and Meet connect? | No, all four are out of scope. We have no code that connects to these products and we do not make a statement such as "it works with all Workspace apps". Document and image attachments are kept in the CRM's own file storage. If one of these products is critical for you, say so during discovery; we will assess the scope separately. - If our Gmail correspondence lands in the CRM, can Gemini read it too? | No, these are two separate things. The Gmail connection makes the mail you send land on the CRM record — it is not two-way inbox sync, and inbox reading is switched off; that does not mean that Gemini can read the CRM. For Gemini to be able to look at CRM records, a separate connection is required, and that connection is built over the REST API, as a piece of work with a defined scope. - Will we run into a verification screen when we connect our Google account? | We share our app verification status on the Google side in writing before implementation — so that what you will see on the connection screen is not a surprise. That is why there is no sentence such as "it connects without a hitch" on this page. We make the connection together during implementation; you do not go through the steps on your own by trial and error. - If the connection is built, can Gemini write records to the CRM? | As far as the permission you grant. The REST API supports both reading and writing records; which object write permission will be opened on is written out one by one in the scope. The start we recommend is a narrow scope: read only first, then writing once the team has seen the flow. Every field changed over the API on an existing record lands in the change history. A newly created record's initial values are not recorded there; the creator (the user the API client is bound to) and creation time are set by the system and cannot be changed from the user screens, data import or the API. - Does our CRM data go to Google? | With the Gmail and Calendar connection your mailbox and your calendar are already on the Google side; the copy that lands in the CRM stays in your database in the EU. Unless you build a Gemini connection, your CRM records do not go to an AI service. When you do build the connection, the records within the scope you granted go to the provider through your own account; that is a transfer abroad within the scope of Article 9 of the KVKK. - Is the AI assistant on by default? | No, it is off. The assistant inside the product is off by default and is enabled per tenant; unless you turn it on, your CRM data is not sent to any AI provider. We built it this way not as a marketing choice but in order to leave the transfer decision to you. - How long does implementation take, and is it included in the plan price? | Configuring the Gmail and Calendar connection is within the scope of implementation. A project-specific AI connection such as Gemini is scoped separately and charged separately. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. - Where is our data kept? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. Your CRM data is kept in a separate database that belongs to you. When you enable an AI connection, the provider side is added to that. - Can we see it before buying? | There is no trial that you start on your own. First we run a 30-minute live demo; we show how the Gmail sync lands on the record and how Google Calendar works in both directions, over your own scenario. After that, if you want to explore the product at your own pace, we open a time-limited demo account. ##### Related pages - Google Workspace integration | Ready today. The Gmail and Google Calendar connections together; why Drive, Docs, Sheets and Meet are out of scope is written there too. - Claude integration | Rapi, the assistant inside the product, and the 18-tool MCP package downloaded from the Setup screen — the AI side that works today. - Integrations | Which connection works in the product today, which ones we build on request, and the reason for the three things we do not promise. ##### Let's make the Google side clear in 30 minutes In the demo, let us show how the Gmail sync lands on the record and how Google Calendar works in both directions; and let us talk through together what has and has not been measured on the AI side. Request a demo The Workspace products that stay out of scope are also listed explicitly in the written scope. ### [Google Workspace Integration: Gmail & Calendar | Rapitek CRM](https://rapitek.com/en/google-workspace-integration) Gmail connects with OAuth, correspondence lands on the customer record; Google Calendar syncs both ways. Scope is these two apps — and it is live today. Integration · Google Workspace #### Gmail and Google Calendar work inside your CRM with Google Workspace. You connect your Gmail account with OAuth; the connection covers email sending and calendar sync — the inbox is not read. Google Calendar works both ways: events are pulled into the CRM, and an appointment you open in the CRM is created, updated and deleted in your calendar. This connection is live today — setting it up does not require a provider-specific project. Request a demo Talk through the setup scope ##### The team works in Google, customer history stays in a personal inbox In a team that has moved to Google Workspace, the working day is spent on two screens: Gmail and Google Calendar. Each works well on its own; the mechanism jams here: both work tied to an individual — correspondence and appointments sit in one person's account, not on the company's record. This is the picture we have seen in our own CRM projects: - All correspondence with the customer sits in the rep's own inbox. When the rep goes on leave or leaves the company, the history goes with them. - The answer to "what did we last write to this customer?" depends on finding that person and asking. - The appointment is in Google Calendar and the meeting note is somewhere else; the two never meet on the same customer record. - The meeting time changes in Calendar while the record in the CRM or the spreadsheet stays as it was — nobody knows which one is right. - When a new rep takes over, they have to rebuild the customer history from scratch; the handover is done by forwarding emails. - A manager cannot answer "how many meetings were held this month" without going through the calendars one by one. The right setup is not to replace Gmail or Calendar; it is to connect these two surfaces the team already uses to the customer record. ##### This connection is live today — how does it work? On the Google Workspace side, two connections are built into the product and are configured during setup: - Gmail — connected with OAuth. Email is sent from inside the CRM and linked to the relevant record; the connection covers sending and calendar sync, not two-way inbox sync — inbox reading is switched off. No user password is shared; access is authorised with OAuth. We covered the whole email side on our email integration page; we do not repeat it here. - Google Calendar — two-way sync. Events in the calendar are pulled into the CRM; an appointment created, updated or deleted in the CRM finds its counterpart on the Google side. The sync runs on a schedule in the background; it does not depend on manual triggering. There is a counterpart to this inside the product: activity, task and event records are among the CRM's core modules; they come with the standard installation and are not an add-on that has to be installed separately. The calendar sync connects not to a void but to the product's own record structure. The calendar sync is specific to the Google side. Outlook and Microsoft 365 connections are not live, so a Microsoft 365 account cannot be connected at all — neither for email nor for the calendar. We write this not as a superiority claim but as a fact worth knowing — if you use Workspace, this is the side that works in your favour. The scope is narrow and we say so up front: not every application that comes to mind when you say Google Workspace, but Gmail and Google Calendar. We have no connection for Drive, Docs, Sheets or Meet; we have written out the status of each one in the table below. A concrete scenario ##### Wednesday, 11:15 — the customer says "the quote we discussed last week". Once the connection is in place, this is what changes: - Correspondence history on the customer card, not in one person's inbox | Correspondence sent through Gmail is linked to the relevant customer record. Whoever answers the phone can see what was last discussed with that customer without searching their own inbox. - The appointment is opened in the CRM and appears in Google Calendar | You schedule the meeting from the customer record in the CRM; the event is created in your Google Calendar. There is no need to enter it a second time somewhere else. - A change made in the calendar comes back to the CRM | When a meeting changes time or is cancelled in Google Calendar, the record on the CRM side is updated too. The sync works in the pull direction as well. - The outcome of the meeting goes onto the record, not into memory | The post-meeting note, the next step and the owner all sit on the same customer record. Activity and task records are a core module of the product; they are not something that has to be installed separately. - Handover is not done by forwarding emails | When the rep changes, the customer history stays on the record. The new owner takes over the correspondence and the appointment history as they are. - At month end, meeting counts are not gathered from calendars | Who held how many meetings, and when each customer was visited, is read from a report. The manager does not have to go through the calendars one by one. ##### Flows that work on the Google Workspace side today - Connecting Gmail with OAuth | You authorise your Google account with OAuth; this is not a connection set up by sharing a user password. The authorisation is done together during the setup session. - Email sending, not inbox sync | Email can be written and sent from inside the CRM, and what you send is visible on the CRM side. Inbox reading is switched off — this is not two-way inbox sync; the detail is on our email integration page. - Linking correspondence to the customer record | Correspondence lands under the relevant customer or contact record. History accumulates on the company's record rather than in a personal inbox. - Pulling from Google Calendar into the CRM | Events in your calendar are taken into the CRM. A rep who keeps their appointments in Google Calendar does not have to change that habit. - Create, update and delete from the CRM to the calendar | An appointment opened in the CRM is created in Google Calendar; if it is updated it is updated, if it is deleted it is deleted. The sync runs on a schedule in the background. - Activity and task records kept in the same place | The appointment, the meeting note and the follow-up task accumulate under the same customer record. Activity and task are among the product's core modules; they come with the standard installation and do not need to be installed separately. Scope ##### What syncs and what does not? The scope is limited to Gmail and Google Calendar. We do not make the claim "integrates with all Workspace apps", because it is not true. Google Workspace app | Status | What happens - Gmail | Connected — sending and calendar | The account is connected with OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant customer record. Inbox reading is switched off — this is not two-way inbox sync. The full scope is written out on the email integration page - Google Calendar | Connected — two-way | Events are pulled into the CRM; an appointment created, updated or deleted in the CRM finds its counterpart on the Google side. The sync runs on a schedule in the background - Google Drive | No connection | We have no Drive-specific connection and we will not say that we do. Files are uploaded directly to the CRM and attached to the relevant record; the folder structure in Drive is not reflected in the CRM - Google Docs and Sheets | No connection | There is no live Docs or Sheets connection. You can export the list in Sheets as CSV or Excel and import it into the CRM with Data Hub's four-step wizard: upload, map fields, preview, run - Google Meet | No connection | Meet meetings do not land in the CRM on their own; we have no connection for the meeting link, its participants or its recording What we can say ##### What we have verified - Live | Gmail OAuth works today — sending and calendar sync, not inbox reading - Two-way | Google Calendar: pull, create, update and delete — on a schedule - Google only | Calendar sync is Google-only; Outlook and Microsoft 365 are not live - OAuth | Access is granted on Google's own consent screen; we never get your password Rollout ##### How is the Google Workspace connection brought live? - Discovery | We work out how many users will be connected, which calendars will sync, and which record you expect correspondence to be linked to. We recommend having your Workspace administrator in this meeting. - Authorising the Google accounts | We do not expect you to do the Gmail and Calendar authorisation on your own; we do it together in the setup session. We walk through Google's permission screens step by step. - Configuration and testing | We set up which user syncs which calendar, which record correspondence is linked to, and the permissions. We verify both directions with a sample appointment and a sample email. - Training and go-live | Team training and close follow-up in the first week. We do not commit to a duration before discovery; after the discovery meeting we give you a date, not a range. The Gmail and Calendar connection goes live within that plan. ##### Our limits: what we do not promise on this page We do not promise everything that comes to mind when you hear "Google Workspace integration". We name what we do not promise: - We do not say "integrates with all Workspace apps". The scope is limited to Gmail and Google Calendar. We have no connection for Drive, Docs, Sheets or Meet; nor do we open these up during setup. - We do not say "it connects without a hitch". Google's app verification process is not in our hands, and we cannot turn its current state into a commitment on this page. That is why we do not leave the authorisation to you, but do it together in the setup session. - No mail server other than Gmail can be connected. Generic IMAP/SMTP is not supported, and Outlook and Microsoft 365 connections are not live; on the email side there is only the Gmail OAuth connection. The detail is on our email integration page. - We have no feature that automatically emails your reports to Gmail. Reports and dashboards run inside the CRM; scheduled email delivery is not something we can offer today. - We do not replace Google Calendar. The calendar stays in Google; the CRM links the same appointment to the customer record. Which of the two sides is the source of truth is set as a rule during setup. We have written the three things we do not promise on the ERP, marketplace and accounting side — real-time stock synchronisation, the order-invoice-collection chain flowing on its own, and production/MRP automation — together with the reasons, in one place: the integrations page. We do not repeat it here. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no region selection feature. Under KVKK art. 9 this is a transfer abroad; we establish your transfer basis together during the contract process. With the Gmail and Calendar connection, one side of the data is additionally with Google. The detail is on the security page and in the KVKK privacy notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### We put the number on the pricing page, not on this page The Gmail and Google Calendar connection is configured during setup. We have written what each plan covers and which items are priced separately on a single page. See pricing We do not write the number in two places, so you never read two different ones. FAQ ##### Frequently asked questions about the Google Workspace integration - Does Rapitek CRM work with Google Workspace? | Yes, it is live today — but let us state the scope up front: Gmail and Google Calendar. You connect your Gmail account with OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant customer record. Inbox reading is switched off, so this is not two-way inbox sync. Google Calendar works both ways. We have no connection for Drive, Docs, Sheets or Meet. - Is the Google Calendar sync really two-way? | Yes. Events in the calendar are pulled into the CRM; an appointment created, updated or deleted in the CRM also finds its counterpart on the Google side. The sync runs on a schedule in the background; it does not depend on manual triggering. Which user syncs which calendar is defined during setup. - Does our Gmail correspondence land on the customer record? | Mail you send does. Once your Google account is connected with OAuth, email can be written and sent from inside the CRM and is linked to the relevant record. Inbox reading is switched off — incoming mail is not pulled in, so this is not two-way inbox sync. We have covered the whole email side separately — which providers are supported and how the connection is set up — on our email integration page. - Our company-domain email comes through Workspace. Does it still work? | Yes; the connection is established with the OAuth authorisation of your Google account, and having your domain on Workspace does not change that. One point to watch: generic IMAP/SMTP is not supported. If your mail sits on a server outside Workspace, the email sync cannot be set up. - Do our files in Google Drive connect to the CRM? | No. We have no Drive-specific connection and we will not say that we do; the folder structure in Drive is not reflected in the CRM. You can upload files directly to the CRM and attach them to the relevant record. The files you upload are held in the storage in Frankfurt, in the separate area allocated to each customer. - Can we import our customer list from Google Sheets into the CRM? | Yes, but not through a live Sheets connection. You export the list as CSV or Excel and bring it into the CRM with Data Hub's four-step wizard: upload, map fields, preview, run. You confirm the mapping on screen. We do the first data import as part of the setup. - Do our Google Meet meetings land in the CRM? | No. We have no connection with Meet; the meeting link, the participant list or the recording does not come into the CRM on its own. You can record the meeting itself as an activity in the CRM and write its note and next step onto the customer record — but we do not take that from Meet automatically. - We also have a team on Microsoft 365. Is it the same for them? | Not the same. Outlook and Microsoft 365 connections are not live, so a Microsoft 365 account cannot be connected — neither for email nor for the calendar. We write this up front, because learning it during setup would be an unpleasant surprise. In a mixed team, those on Workspace get the Gmail and Calendar connection; the Microsoft side gets neither. - Do we set the connection up, or do you? | We do. We do not expect you to do the Gmail and Calendar authorisation on your own; in the setup session we go through Google's permission screens together. We do not make the claim "it connects without a hitch" — Google's app verification process is not in our hands, which is why we do not leave you alone at this step. - Is each user's own Google account connected separately? | Who will be connected and which calendar will sync is defined during setup; we decide this together, based on your user list and your internal arrangement. The authorisation is done with OAuth and no user password is shared. - Is this integration included in the plan price? | Gmail and Google Calendar are built-in connections; configuring them is part of the setup. The scope of the setup and its cost, if any, are worked out in the discovery meeting and shared in writing before work starts. Project-specific development such as the ERP or marketplace side is scoped separately; plan details are on the pricing page. - How long does the setup take? | We do not commit to a duration before discovery; after the discovery meeting we give you a date, not a range. The setup consists of these steps: discovery, configuration, data import, training and go-live. The Gmail and Calendar connection goes live within that plan; it is not added to the schedule as a separate integration project. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. Under KVKK art. 9 this is a transfer abroad; we establish the basis for it together during the contract process. With the Gmail and Calendar connection, one side of the data is additionally with Google. - Can we see it before buying? | There is no self-service trial you can start on your own. First we run a 30-minute live demo; then, if you want to explore the product at your own pace, we open a time-limited demo account for you. The demo shows the standard version of the product; the Gmail and Calendar connection is configured as part of the setup. ##### Related pages - Email integration | The canonical page for the email side: which providers connect, how the sync works, and what is not supported, written out one by one. - Integrations | The connections working in the product today, the ones we build on request, and the three things we do not promise — all on one page. - Security | Which country the data sits in, the sub-processor list, backups, the audit trail, and what we do not offer yet. ##### Let us clarify your Gmail and Calendar flow in 30 minutes In the demo meeting, let us talk through which record correspondence will be linked to and how the calendar sync would be set up in your own team, using your own scenario. Request a demo The scope of the setup and its cost, if any, are worked out in discovery and shared in writing. ### [Moving from HubSpot to Rapitek CRM | Rapitek CRM](https://rapitek.com/en/hubspot-alternative) Rapitek CRM is built for the sales team's daily work: WhatsApp inbox in the product, ERP connections built per project, a separate database per customer. For teams coming from HubSpot #### A CRM built for the sales team's daily work. Demand arriving over WhatsApp, a field sales team, and an order process that has to reach your ERP — that is what we built Rapitek CRM for. We do the setup ourselves. Request a demo Read the migration guide ##### The short answer We do not compare ourselves with another product on this page. We write down what we do and what we do not do. Rapitek CRM was built to run sales: demand arriving over WhatsApp attached to the customer record, a field team working from their phones, quotes and orders that talk to your ERP, a web interface available in Turkish, English and Arabic, and support and training in Turkish. We also do the setup ourselves. What we do not do is written out below just as plainly. When you weigh up any quote you receive, put implementation, customisation and training alongside the licence fee, and price your usage two years from now rather than the size of your team today. What's in, what's out ##### What Rapitek CRM does and does not do Area Rapitek CRM - What it was designed for | The sales team's daily work and field operations - WhatsApp | Inside the product: shared inbox, logged on the customer record - Setup | The team that builds the product; we commit to no timeline before discovery, and after discovery we give a written date rather than a range - Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery - Support and training language | Turkish - ERP connection (Logo, Netsis, Mikro) | Built per project by the team that builds the product; there is no off-the-shelf module - Manufacturing, inventory, work orders | Work order and quality control objects ship in the standard installation; we cannot yet point to a live installation running production execution - Data separation | A separate database per customer - Depth of marketing automation | Limited. Campaign sending with consent management (İYS sync when you connect your own İYS account through Verimor); beyond that it is not an area we have gone deep in - Content and landing-page tools | None. We do not offer blog, landing-page or form tools - Ecosystem breadth | Narrow. We have no app marketplace and no trained partner network — we say so plainly - How cost scales | A flat per-user tier; plan prices are public ##### What stands out on the sales and operations side - Shared WhatsApp inbox | In Turkey a large share of business conversation happens on WhatsApp. The team writes from a single work number and every message is logged on the customer record. - Connections to Turkish ERPs | Systems like Logo, Netsis, Mikro and Paraşüt are connected per project over REST API, OAuth2 and webhooks. Not an off-the-shelf connector — we say that plainly too. - Manufacturing, inventory and work orders | Visit tracking, voice-created records and business-card scanning in the mobile app. iOS and Android are both live. Route plans and field visit records are a separately priced module — 25 USD per user per month. - Field sales teams | Visit tracking, voice-created records and business-card scanning in the mobile app. iOS and Android are both live. - Connect your own AI | Your CRM is open over MCP. You connect your own Claude account; access can never exceed the permissions of the user who connected it. - We do the setup | Fields, stages, roles and reports are configured around your process, your data is migrated and your team is trained by us. ##### When we are not the right product Rapitek CRM is not the right tool for every team. We will say the same thing in the discovery call: - Your growth comes from content and inbound. We do not offer blog, landing page, form or email workflow tools; that is not where we are strong. - The tool will mainly be used by your marketing team. We built Rapitek CRM for the sales team's daily work, and the tool should be chosen for whoever's daily work it serves. - You depend on a large number of ready-made add-ons. We have no app marketplace and no trained partner network; the connections you need are built per project by us. - Your team is under 5 people. Our Sales and Platform tiers require at least 5 users; for small single-channel teams, Inbox (149 USD per company per month) is a separate starting point. FAQ ##### About moving from HubSpot - Can our HubSpot data be migrated? | Yes. Your contacts, companies, deals and activity records, along with your custom fields, are migrated and duplicates cleaned out. What moves is decided in the discovery call and put in writing. The step-by-step process is set out on our HubSpot Migration Guide page. - What marketing needs does Rapitek CRM cover? | The Platform plan includes the Marketing, Communications and Operations hubs, and campaign sending runs with consent management. For customers who connect their own İYS account (Turkey's commercial-message consent registry) through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM. Beyond that we do not offer content production, blog or landing page tools; marketing automation is not an area we have gone deep in. - How much does Rapitek CRM cost? | Our plans are public: Sales 39 USD, Platform 69 USD, Enterprise from 119 USD (per user per month, billed annually). Our advice is to price your usage two years out rather than your team today. When you weigh up any quote you receive, put implementation, customisation and training alongside the licence fee. Our setup scope, and any fee, is put in writing during discovery. - How long does the migration take? | We commit to no timeline before discovery. A rollout covers discovery, configuration, data migration and training; after the discovery call we give you a date, not a range. ##### Let us listen to your team's daily work. In a 30-minute call we listen to your sales process and talk through whether Rapitek CRM fits. If it does not, we will say so. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [HubSpot Migration Guide | What Moves, What Doesn't | Rapitek](https://rapitek.com/en/hubspot-migration-guide) What transfers from HubSpot, what has to be rebuilt, and the cases where staying put is the better decision. Migration guide #### Leaving HubSpot: the real question is what happens to marketing. The hard part of a HubSpot migration isn't the CRM data — that moves easily. The hard part is deciding where your content, forms and email workflows are going to live. Book a migration call What Rapitek CRM offers ##### An honest warning first: what we don't have Our depth on the content and inbound marketing side is limited, and we won't claim otherwise. Blogs, landing pages, a content calendar and multi-step marketing automation are not in the product; what it is built around is the daily work of a sales team and field operations. So a migration from HubSpot takes one of two shapes: - A full exit: if you aren't really using the marketing side, or you have another tool for it. The cleanest scenario. - A split: move the CRM and sales side to us and leave marketing where it is today. That route is open: contact sync between the two systems can be built over the REST API, with the scope defined at discovery. We are not claiming we have done this on a live setup to date — we have no provider-specific code written for it. We decide together in the discovery call which one applies. If the second is right for you, we'll say so. Steps ##### How do you plan a HubSpot migration? - 1. Separate the record types | Contacts, companies, deals and activities are exported separately. Pull the list of custom properties too — and check which of them are genuinely filled in. - 2. Review your deal stages | You don't have to carry your current pipeline stages across as they are. In most teams stages multiply over time and lose their meaning; a migration is a good moment to simplify. - 3. Inventory the workflows | Which workflow does what, and which ones still fire? Workflows don't migrate — the need gets rebuilt. We have equivalents for the sales-side workflows; we can't say the same for all of marketing automation. - 4. Plan the forms and inbound channels | If your HubSpot forms come down, what replaces them? The web form object ships in a standard install, but we can't demonstrate a form request reaching the CRM on a live setup today; scope is set at discovery. WhatsApp, email and SMS land in the shared inbox; Meta Lead Ads can't be set up today. - 5. Migrate the consent records | Commercial-message consent matters legally. Consent status and consent date must move; adding a record with no consent history to a mailing list creates real risk. FAQ ##### About the HubSpot migration - Can HubSpot data be exported? | Yes. Contacts, companies, deals and activity records, along with custom properties, are exported and imported; duplicates are cleaned out. - Does the history of our marketing emails move? | We don't recommend migrating the full send history — in practice it goes unused and becomes a large burden. What matters is consent status and the last-interaction information per contact; those move. - What does your marketing automation offer? | The Platform plan includes the Marketing, Communications and Operations hubs; the plan is a billing template, and module scope is settled at setup. Campaign sending runs with consent management. For customers who connect their own İYS account (Turkey's commercial-message consent registry) through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM. Meta Lead Ads can't be set up today. Our depth on the content and inbound side is limited: blogs, landing pages and multi-step marketing automation are not in the product. - Can we move only the CRM side? | Yes, and this is a common choice. Sales and customer management come to us while marketing stays where it is today. Contact sync between the two systems can be built over the API; the scope is defined in discovery. - How long does it take? | We do not commit to a duration before discovery. After the discovery call, we give you a date, not a range. The scope covers discovery, configuration, data migration and training. ##### Let's separate the marketing and sales sides together. In a 30-minute call we'll work out what you actually use in HubSpot and decide together whether a full exit or a split is right. Book a migration call 30 minutes · No obligation · The call is held in Turkish ### [Instagram CRM: Comment Management, Lead Source | Rapitek](https://rapitek.com/en/instagram-crm) Instagram DMs land in the same shared inbox as WhatsApp and are answered from the CRM. Comments are managed there too, attached to the customer record. Instagram + CRM #### Instagram grew your business. Now it's limiting it. The ads are on Instagram, the DMs are on Instagram, the comments are on Instagram. Who the customer is, where they came from, what was said — all of it lives inside one app you can't look into from outside. An Instagram CRM integration breaks that dependency. Request a demo Explore the product ##### Being stuck on one channel A great many businesses live off Instagram today: the ads run there, the customer writes in the DMs, the sale closes there. It works — until someone asks: - How many enquiries came in this month, and how many turned into sales? - Who was the person who asked about pricing three months ago, and what did we discuss? - What happens if the colleague who runs social media leaves? - If we advertised somewhere other than Instagram, how would we follow up the people who came in? All four have the same answer: Instagram is a shop window, not a system of record. It keeps no customer history, produces no reports, and you cannot search who said what and when. Businesses aren't stuck on Instagram by choice — they're stuck for lack of a tool. They don't consider selling anywhere else because they have nowhere to follow up the people who would arrive. The moment the customer relationship lands in the company's records, that dependency ends. ##### What you gain by putting Instagram on the record - Choosing a channel becomes a choice | The moment someone from Instagram lands in a lead record with their source logged, you can compare that against an ad you ran somewhere else. Until you can measure it, Instagram isn't a choice — it's the only option. - The month-end question is answered in a report | “How many enquiries came in this month, and how many turned into sales” is no longer answered by scrolling the app; the record is in the CRM, so it is read off the pipeline report. - Setup is done by the team that builds the product | The Instagram connection, the comment flow and how the lead source is logged are defined together during setup. No separate consulting project sits in between, and you don't need to hire a CRM administrator. How it works ##### You published a post. Here's what happens next. - Posts and comments land in the system | Your posts and the comments underneath them are logged in the CRM. Who wrote what is on one screen — nobody has to open the app and scroll. We have verified this flow end to end in our own environment; it has not yet been measured in a customer deployment. - A comment can be answered publicly | Reply publicly and close the matter there — comment management is verified end to end in our own environment, not yet measured in a customer deployment. A private reply moves the person into a DM; Meta's limit applies: one private reply per comment, within 7 days of the comment. - The person attaches to a customer record | The person who engaged in the comments is attached to their existing record by Instagram username; if they have none, a setting switched on during setup creates a new lead with Instagram logged as its source. At month end, “how many customers did Instagram bring” becomes a report. - The history stays with the company | Comment and customer history lives in the CRM. Even when the person running social media changes, the record stays with the business and the next person picks it up by reading it. ##### What can you actually do? - Instagram DMs — answered from the CRM | Instagram direct messages land in the CRM and are answered from there. Verified in a customer deployment with real customer messages. - Comment management | Public reply, hide and delete on post comments — from inside the CRM. Comment management is in place and verified end to end in our own environment; it has not yet been measured in a customer deployment. A private reply moves the person into a DM; Meta's limit applies: one private reply per comment, within 7 days of the comment. - Attached to the customer record | The person who comments is attached to their existing record by Instagram username; if they have none, a setting switched on during setup creates a lead with Instagram logged as its source. Pipeline, quotes and tasks all run on that same record. - The record stays intact | Comment history is kept as the company's record and survives a change in whoever manages the social account. - One inbox for two channels | Instagram direct messages land in the same shared inbox as WhatsApp; a conversation is assigned and handed over the same way. - Run it with your own AI | Your CRM is open over MCP: connect your own Claude account to summarise conversations or draft replies. Access is capped by that user's permissions. ##### What Instagram can't do — know this before you buy Where things stand today: Instagram direct messages land in the CRM and are answered from there, within the limits below. Instagram is not WhatsApp. The limits Meta places on Instagram are not our product decisions, but they bind you. The most important one: The 24-hour window. After a customer writes to you, you can reply within 24 hours. Meta defines an extension that takes this to 7 days, but it requires separate approval; our application was not approved, so your window is 24 hours. Once the window closes there is nothing you can do — you have to wait for the customer to write again. There are no approved template messages. On WhatsApp you can re-open contact with an approved template when the window closes; on Instagram no such concept exists. There is no escape hatch. Beyond that, Instagram does not support: message reactions, button and list menus, sending a location, sending a contact card, forwarding a message, editing or deleting a sent message, group conversations, or voice notes. These are recorded in the product and are never offered to you in the interface — you won't click something and get an error. Meta's limit on private replies: a comment can receive a private reply only once, and only within 7 days of the comment. A private reply moves the person into a DM; it has not yet been used in a customer deployment. The two channels are not the same ##### The real differences between WhatsApp and Instagram Area WhatsApp | Instagram - Reply window | 24 hours; contact can be re-opened with an approved template | 24 hours — the 7-day extension requires separate approval and we do not have it today - When the window closes | You can send an approved template message | You can only wait for the customer to write — there is no other way - Bulk campaigns | On the Cloud API, with approved templates to consented lists | Not available - Post comments | Not applicable | Reply, hide and delete are supported — verified end to end in our own environment, not yet measured in a customer deployment; private reply moves the person into a DM, once per comment and within 7 days of the comment - Connection method | Meta Cloud API or QR pairing (QR is not the official API) | The official Instagram Graph API — the only route - Account requirement | A business number | A professional account + a connected Facebook Page + Page admin rights - Voice notes | Supported | Not supported - Button and list menus | Available on the Cloud API | Not supported Before connecting ##### Three conditions — and what we do behind them - Your Instagram account must be professional | A Business or Creator account. A personal account cannot be connected — that is Meta's rule. Converting takes a few taps in the Instagram app. - It must be connected to a Facebook Page | Your Instagram account has to be linked to a Facebook Page. The Page doesn't have to be actively used, but the link must exist. - Whoever connects it must be a Page admin | The account granting permission must be an administrator of that Facebook Page. If you manage several Pages, you choose which one to connect — the system doesn't guess and take “the first one”. - We handle the rest during setup | Permissions and webhook subscriptions are established automatically in the connection flow; the administrator doesn't need to know anything technical. ##### Plan prices are published; scope comes out of discovery The scope of the Instagram connection, and any cost for it, are worked out in the discovery call and shared in writing. Plan prices and separately priced items are published on one page. See pricing Three plans, a scope table and separately priced items. FAQ ##### About Instagram CRM - Which Instagram API do you use? | The official Instagram Graph API, via Facebook Login. We use no unofficial method on the Instagram side — the QR pairing option that exists for WhatsApp has no Instagram equivalent; the official API is the only route. - Can we connect a personal Instagram account? | No. The account must be professional (Business or Creator), it must be connected to a Facebook Page, and the person connecting it must be an admin of that Page. All three are Meta's requirements, not restrictions we invented. - Can we message a customer whenever we want? | No. After a customer writes to you, you have a 24-hour reply window; the extension that would take this to 7 days requires separate approval and we do not have it today. Once the window closes there is no way to re-open contact on Instagram — the approved-template concept from WhatsApp has no equivalent. We say this upfront so the process can be built around it. - Can we send bulk messages from Instagram? | No. Instagram has no campaign or bulk-notification sending. If you need bulk communication, the right channel is the WhatsApp Cloud API, where sending runs through approved templates to consented lists. - Can we reply to comments from inside the CRM? | Yes. You can reply publicly to post comments, hide a comment or delete it. To be precise about the level: comment management is in place and we have verified it end to end in our own environment; it has not yet been measured in a customer deployment. A private reply, which moves the person into a DM, is also available; Meta's limit applies: one per comment, within 7 days of the comment. It has not yet been used in a customer deployment either. - Does the AI answer customers on its own? | Not today: in no deployment does AI reply to customers on Instagram on its own. Your CRM is open to AI over MCP; you can connect your own account to summarise conversations or draft replies. You decide what it does, and access can never exceed the permissions of the user who connected it. Note: we never set the tag that extends the reply window to 7 days — that extension requires separate approval and we do not have it today; the window is 24 hours. - Can we manage it from mobile? | Yes. Our iOS and Android apps are live and the inbox works inside the app; WhatsApp and Instagram messages are handled there. Replying to Instagram messages from the app has not yet been measured in a customer deployment. - How long does setup take? | The Instagram connection itself is made during setup: if the conditions are met, the authorisation flow completes in one pass. For the full CRM rollout, after the discovery call we give you a date, not a range. ##### Connect your Instagram traffic to the company's memory In a 30-minute demo we'll show comment management and how a person who engaged attaches to a customer record — on your own account's scenario. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [CRM Integrations: REST API, WhatsApp, ERP | Rapitek](https://rapitek.com/en/integrations) Rapitek CRM integrations: REST API for every standard-install object, OAuth2, signed webhooks, WhatsApp, Google Calendar. ERP/accounting links scoped per project. Integrations #### An integration is not a logo list — it's a piece of work with a defined scope. Rapitek CRM connects to your existing software through REST API, OAuth2, signed webhooks and import/export; our professional services team builds the connection. This page lays out what is ready today, what gets built per project, and how the process works — as it is. Request a demo Discuss your integration scope ##### Why is there no logo wall on this page? You won't find a wall of logos here. Instead, we spell out which connections are built in today, which are built per project, and how an integration job gets scoped. You may be running Logo, Netsis, Mikro, Paraşüt, SAP or Odoo — ERP and accounting systems widely used in Turkey — and we have no out-of-the-box connector for any of them. We connect to all of them the same way: through REST API, OAuth2, webhooks and import/export, delivered by our professional services team. That is not a gap; it is how the job actually works: two systems cannot talk reliably until the field mapping, flow direction, sync frequency and error scenarios are pinned down — and those differ at every company. Across more than 200 enterprise projects in the Salesforce ecosystem, this was the work we did most: getting two systems to talk. What that experience taught us is that an integration cannot truly be planned until the field mapping table exists. We produce that table ourselves during discovery and hand it to you in writing. Process ##### How does an integration project proceed? - Discovery | Which systems are in place, who owns the data, which data should flow which way? We look at your current Excel files and the other system's API documentation together. By the end of this call, the need is clear on both sides. - Scope and written quote | The field mapping table, flow direction, sync frequency, and error and duplicate scenarios are put in writing. Custom integration is a separate line item; you get its price and timeline in writing at this stage. - Development | The connection is built with REST API, OAuth2 and signed webhooks. Our professional services team does the development; from your side, system access and a point of contact are enough. - Testing and validation | Sample records are verified in both directions: does the account visible in the ERP match the CRM, and does a record created in the CRM appear correctly on the other side? Duplicate and error scenarios are exercised here. - Go-live and monitoring | The flow goes live and is watched through API usage analytics. When a field changes or a flow stops, you know exactly who to call: us. ##### What the REST API actually offers - Every object in a standard install | From leads to quotes, invoices to tasks, records are read and written through REST endpoints. Almost everything you see in the CRM is reachable from the API. - OAuth2 authentication | API access is authorized with OAuth2; JWT is supported. No integration is ever built by sharing a user's password. - Signed webhooks | Your system gets notified when a record is created or changed. Calls are signed, so the receiving side can verify the signature and reject forged notifications. - describe and composite endpoints | Read object schemas from the API (describe) and send multiple operations in a single request (composite). Integration code doesn't have to track the schema by hand. - Import and export | Bulk data transfer works both ways via Excel/CSV. You can export your data and take it with you at any time — the data is yours. - Rate limiting and usage analytics | API traffic is protected by rate limits; usage analytics show how many requests each integration is making. Ready today ##### Built-in connections ERP and accounting links are not in this table because they are not ready-made connectors; they are built per project over the REST API — details below. Connection | What it gives you | How it is set up - WhatsApp — Cloud API | Shared inbox: the team writes from a single business number and messages are logged on the customer record | Via Meta's official WhatsApp Business Cloud API; we connect your own WhatsApp Business account - Email sending | Send from your own Gmail or Google Workspace account inside the CRM; each email is attached to the related record | By connecting your Google account; the connection covers sending — your inbox is not read - Google Calendar | Two-way sync for appointments and events | Through a Google account connection, configured during setup - Import/export | Bulk transfer via Excel/CSV for the initial migration and for reporting | Built in; we handle the initial data migration during setup ##### Index · ERP, email and messaging - ERP CRM integration | The frame that does not change whichever ERP you run: what stays where, how the connection is built, how scope is drawn. - SAP integration | We build it. Scope, method selection, and written answers to the security questions your IT team will ask. - Oracle integration | We build it — but only after clarifying which Oracle. “Oracle” is not one product, and we do not promise scope before that is settled. - Odoo integration | We build it. Because Odoo is open source and modular, the access question starts differently than with other ERPs; the page opens there. - Email integration | The canonical page for email: Gmail connects over OAuth, and the connection covers sending — the inbox is not read. Outlook and Microsoft 365 are not open today. - Google Workspace integration | Gmail and Google Calendar in one connection. Drive, Docs, Sheets and Meet are out of scope. - WhatsApp integration | The connection itself: Meta Cloud API, your own WhatsApp Business account — the number and the Meta invoice stay in your name. ##### Index · sales channels, team tools and AI - Shopify integration | We build it. Product, cart and payment run in Shopify; the buyer, repeat sales and wholesale requests are recorded in the CRM. - WooCommerce integration | We build it. Orders, payment and delivery run in WooCommerce; the buyer, quote requests and wholesale customers are recorded in the CRM. - Stripe and CRM | Amount, date and currency of the payment record move to the customer card over the REST API. The payment adapters defined in the product are iyzico and PayNkolay; there is no built-in Stripe adapter. - Slack integration | We build it. Signed outbound webhooks, retry on failure and a notification node in the workflow engine already exist; we set up the subscription. - Microsoft Teams integration | The same notification infrastructure, aimed at a Teams channel. Outlook and Microsoft 365 email is not open today. - Zoom integration | You upload the call recording to the record; it is transcribed, and a summary and action items come out. Pulling the recording from Zoom automatically is separate work. - LinkedIn and CRM | Lead lists are loaded with Data Hub's four-step wizard and the profile URL becomes a field on the contact. We do not offer automatic pulling from LinkedIn. - Claude integration | Rapi, the assistant inside the product, and connecting your own Claude with the MCP package downloaded from the Setup screen. - ChatGPT integration | The foundation is live today: a REST API authorised with OAuth2, plus describe, composite and bulk endpoints. The product's MCP package is for Claude; it has not been tested with a ChatGPT client. - Gemini integration | Gmail and Google Calendar work today. Connecting Gemini rests on the same REST API; scope is set in discovery and built as a project. ##### Two connections where we write today's status separately Instagram DMs and comments. Instagram direct messages land in the same shared inbox as WhatsApp; the conversation is assigned and handed over the same way. Comment management is in place and verified end to end in our own environment; it has not yet been measured in a customer deployment. Because DMs and comment management stand at different points, we describe Instagram here rather than in the table above. For the scope and the current status, see our Instagram CRM page. WhatsApp QR pairing. The same shared inbox can also be connected by pairing a phone via QR. This method is not Meta's official API and it carries the risk of the number being restricted by Meta; for that reason we do not offer it as a product promise — we recommend the official Cloud API instead. If you still prefer this route, we share the risk with you in writing and make the decision together. Source attribution #### Every record that comes from outside arrives with its source. A form on your website or a portal you've connected through the API — whichever channel a record comes from, it lands in the lead list tagged with its source. You don't guess which channel actually brings business; you read it in a report. Verifiable numbers ##### A team that does this work, not just sells it - 200+ | Enterprise CRM projects completed for other companies during our Salesforce era - 183 | Business objects reachable through the REST API in a standard install - A date, not a range | We give you a go-live date after the discovery call - EU | Data location: database in Finland, media in Frankfurt ##### ERP and accounting: typical flows, timeline and cost ###### Typical flows Across enterprise projects, four flows come up most often: - Accounts and invoices from the ERP flow into the CRM, so the sales team sees the customer's commercial history on the customer record. - Balances and collection status from accounting appear on the sales screen, so open balances are visible while a quote is being prepared. - Leads from forms and portals land in the CRM tagged with their source. - Calendars and appointments sync two-way with Google Calendar. The first two are custom development per project; the last two use built-in connections. ###### Timeline and cost The CRM rollout itself covers configuration, data migration and training; after the discovery call we give you a date, not a range, and its scope — along with any fee for it — is put in writing before the work starts. Custom work such as ERP and accounting integration is a separate line item: the scope is defined during discovery, and the price and timeline arrive as a written quote. Duration depends on the number of fields and on what the other system's API allows; we don't promise a timeline before discovery — we put one in writing after it. Plan details, and the items priced outside the plan, are on our pricing page. Limits ##### Three things we do not promise — and why This is the only place we spell these limits out. Also: Rapitek CRM does not issue e-Invoice or e-Archive documents and is not an accredited special integrator with Turkey's revenue administration. We do not promise | Why | What we do instead - Real-time stock synchronization | The authority over stock records stays in your ERP or warehouse system. We cannot present a two-way live stock engine as a measured capability; if we did, it would produce two stock figures that disagree with each other in two systems | Which stock fields are carried into the CRM, and how often, is defined during discovery. What we recommend is a periodic visibility layer - Order, invoice and collection flowing on their own | The chain is built into the product and can be switched on or off per tenant; but we do not think it is right for it to be sold as an automatic accounting flow. Producing official documents is not our job | The quote → order conversion runs as a built-in action; the invoice and collection steps are switched on optionally. The document is issued in your accounting or e-invoicing system, and its data is carried into the CRM - Production and MRP automation | Bill of materials, production line and work order screens exist in the product; but we cannot point to a live reference for work order execution today. We do not sell what we cannot demonstrate | Bill of materials and line definitions are set up, and the sales and quoting side runs in the CRM. We do not say that production planning is run by the CRM References ##### From our CRM implementation projects - As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient. | Utku Aydın | Business Development Director | Iyzico - With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. | Ögetay Can | Sales Director | Petroyağ | Read the customer story ##### Plan prices are published; project scope comes out of discovery Connections that work on setup day are covered by your plan; the ones we build as a project are priced after the discovery call, in writing. We keep the numbers on one page. See pricing Three plans, a scope table and separately priced items. FAQ ##### Frequently asked questions about integrations - Does Rapitek CRM integrate with Logo? | We have no out-of-the-box connector for Logo, a widely used Turkish ERP — and claiming one wouldn't be honest. The connection is built through REST API, OAuth2, webhooks and import/export, delivered by our professional services team. Which account, invoice and stock data flows which way is decided in the discovery call; scope and price are fixed in a written quote. - How does a connection to SAP, Netsis or Mikro work? | The same honest answer applies to all of them: no ready-made connector; the link is built through REST API, OAuth2, webhooks and import/export by our professional services team. We review the other system's API capabilities during discovery and produce the field mapping table; development and testing are done by us. - Can it connect to accounting tools like Paraşüt or Luca? | Within the same framework: connected through REST API, OAuth2, webhooks and import/export by our professional services team — we don't offer a ready-made connector for these widely used Turkish accounting platforms. The most requested flow is showing account and collection status on the sales screen. - What do you offer for CRM API integration? | The REST API reaches the 183 business objects that ship in a standard install; beyond reading and writing records, it supports schema reading with describe and batched operations with composite. Authentication is OAuth2, with JWT supported. Signed webhooks fire on record events; traffic is protected by rate limits and monitored through usage analytics. - Do you support webhooks? | Yes. Your system is notified on events such as record creation and updates. Calls are signed; the receiving side verifies the signature to reject forged notifications. Which events go to which endpoint is configured as part of the integration scope. - How does the WhatsApp connection work? | The route we recommend and build is Meta's official WhatsApp Business Cloud API: we connect your own Meta WhatsApp Business account, and Meta invoices you directly. The team writes from a single business number in a shared inbox, and messages are logged on the customer record. We do not offer pairing a phone via QR as a product promise; that method is not Meta's official API and it carries the risk of the number being restricted by Meta. If you still prefer that route, we share the risk with you in writing and decide together. The detail of the connection is on our WhatsApp integration page. - Is there two-way email sync with Gmail or Outlook? | What we offer today is this: you connect your own Gmail or Google Workspace account and send from inside the CRM; each sent email is attached to the related record. The connection covers sending; your inbox is not read. Outlook and Microsoft 365 connections are not live. We don't promise full two-way sync. - Will forms on my website feed the CRM? | Yes. Your website form connects through the REST API or a webhook; each submission arrives as a lead tagged with its source. The Meta Lead Ads connection is not live today, so submissions to your ad form do not flow into the CRM. Form connections are planned during discovery and set up by us. - How long does an integration take? | The honest answer: it depends on scope. Single connections such as a form or a webhook are quick; ERP flows that need field mapping take longer. We don't promise a timeline before discovery; at the end of discovery you get the scope and a written schedule. After the discovery call we give you a date for the CRM rollout, not a range, and the integration is planned alongside it. - Are integrations included in the plan price? | Configuring the built-in connections — WhatsApp, sending from your own Gmail, Google Calendar, import/export — is part of setup. The scope of setup, and any fee for it, is worked out in the discovery call and put in writing before the work starts. Custom work such as ERP and accounting integration is scoped and priced separately; you get the price in a written quote at the end of discovery. - Can e-commerce platforms like Trendyol, Hepsiburada or Shopify connect? | We have no ready-made connector for these platforms (Trendyol and Hepsiburada are Turkey's largest online marketplaces). Getting order and customer data into the CRM is built per project with the REST API and webhooks, as professional services work. What the platform's own API allows is decisive; we define the scope together in the discovery call. - Where is our data processed in integration traffic? | The database is hosted in the EU, in Finland; media files are in Frankfurt. A few sub-processors operate outside the EU, and we name each one, with where it processes data, in our privacy policy. For companies subject to KVKK (Turkey's data protection law No. 6698), EU hosting is an international transfer under Article 9, and consent and disclosure processes are set up accordingly. TLS protects data in transit, and each customer gets a separate database. Our security page has the detail. ##### Related pages - Product | Modules, API coverage and the full set of platform controls. - Pricing | Plan scopes and the items priced outside the plan. The scope of setup — and any fee for it — is agreed in writing before the work starts. - Security | Data location, permissions and our approach to data protection — as it is. - CRM guide | A practical, plain-language guide to choosing and rolling out a CRM. - Contact | Reach the team directly — no ticket queues. - Demo | See it live on your own scenario in 30 minutes. ##### Let's scope your integration together In a 30-minute demo we show the API, the WhatsApp connection and the typical flows for your systems — on your own scenario. At the end of discovery you get the scope and timeline in writing. Request a demo The scope of setup — and any fee for it — is agreed in writing; custom integration is scoped separately. ### [KVKK Privacy Notice | Rapitek CRM](https://rapitek.com/en/kvkk-notice) Which personal data Rapitek CRM processes and why. Storage in the EU, transfer abroad under KVKK art. 9, and your rights under KVKK art. 11. Legal #### KVKK Privacy Notice How we process your personal data and what your rights are under Turkish Personal Data Protection Law No. 6698 (KVKK). ##### On this page ##### Data controller Rapitek Bilişim Teknolojileri Anonim Şirketi Maslak Mah. Büyükdere Cad. Nurol Plaza Sit. No: 255/B02, Sarıyer, İstanbul, Türkiye MERSIS: 0734159061600001 Trade registry no: 157552-5 Tax no: 7341590616 WhatsApp: +90 212 963 22 84 E-mail: info@rapitek.com ##### What personal data do we process? When you submit the contact or demo form on our site, we record the fields we ask for (e.g. name, e-mail, phone, company, team size, your message) together with the submission time, the address of the page you submitted the form from, the page address you came from, browser information and a digest of your IP address generated with a secret key; the form record on our site does not hold your raw IP address. The copy passed to our CRM system, however, may also contain your raw IP address. If you consented on the cookie banner, the sequence of pages you visited in the same session is also recorded; without that consent no such record is created at all. If you gave consent, the full text shown to you at that moment and the time of consent are also stored as proof of consent. When you submit the form on the fit-check page, in addition to the fields above we also record the answers you gave in the check (team size, monthly budget per user, your region of operation, the features you treat as non-negotiable, and your go-live speed) together with the fit score calculated from them. Taking the check on its own sends nothing — your answers do not leave your browser; this record is created only if you choose to submit the form, and what will be sent is shown to you before you send it. For both forms, a copy of your form record is passed from our site to our company's own CRM system (Rapitek CRM) so that we can respond to your enquiry; that system is hosted in the European Union locations listed below. ##### Why do we process it? To respond to your enquiry and carry out pre-contractual discussions; to keep the service secure by preventing form abuse (bots/spam); and to meet our legal obligations. ##### What is our legal ground? Your personal data is collected through the forms on our site, by automated means and in an electronic environment. The legal ground for each processing activity is as follows: - Responding to your request — our legitimate interest in reviewing your request and getting back to you (Law No. 6698, Art. 5/2-f). If a contract is formed, processing continues on the ground of the establishment and performance of that contract (Art. 5/2-c). - Preventing form abuse (bots/spam) — our legitimate interest in keeping the service secure (Art. 5/2-f). - Meeting our legal obligations — Art. 5/2-ç. - If you consented on the cookie banner, the sequence of pages you visited in the same session — your explicit consent (Art. 5/1). Without that consent no such record is created at all, and you may withdraw your consent at any time. - Keeping the consent text and the time of consent as proof of the consent you gave — the establishment, exercise or protection of a right (Art. 5/2-e). ##### Measurement in our e-mails If we e-mail you in response to your enquiry, we measure whether those messages are opened and whether the links inside them are clicked. To do this, a small invisible image is placed in the message and links are routed through our measurement address. In the process we record the time of opening, your IP address and information about the e-mail program you use. The purpose is to see whether the message reached you and to avoid sending you unnecessary follow-ups. This processing rests on our legitimate interest under article 5(2)(f) of Law No. 6698. For any request about this measurement you can write to us using the contact details above; if you prefer, we will stop sending you e-mail altogether. ##### How long do we keep it? Form records on our site are kept for 24 months from the date the form was submitted and are deleted automatically at the end of that period. The copy passed to our CRM system is not covered by this automatic deletion, and no separate automatic retention period applies to it; you may ask us to delete it at any time. Deleted records do not leave backups at once: they remain in our site's backups for up to about 6 months under our backup cycle and in the local backups on our CRM server for 30 days; our CRM's encrypted off-server backups are deleted automatically after 90 days; the unencrypted backups there are not covered by this automatic deletion. ##### Where is your data stored? (transfer abroad) Your form records and CRM data are hosted within the European Union: our site's forms and form records are kept on our website server in Germany (Falkenstein), and their backups are also kept in Germany. Our CRM system's database is in Finland (Helsinki), uploaded files and images are in Germany (Frankfurt), and CRM database backups are in Germany (Falkenstein). Each customer's data sits in a separate database, and connections from your browser are encrypted with TLS; the TLS connection terminates at an edge server in Cloudflare's global network (a US-headquartered provider), whose location varies by request. There is one exception to this separation and we state it plainly: the application's technical error logs are kept in a table shared by all customers. These records may contain personal data relating to the request at the moment the error occurred. They are kept solely for troubleshooting purposes and are not the content of your CRM itself. This hosting constitutes a transfer abroad within the meaning of article 9 of Law No. 6698. The Board has issued no adequacy decision for the countries involved; below we name every component, the country it sits in and the provider that holds it. You may ask us to delete your data at any time — follow the steps on the Data Deletion Instructions page or write to us using the contact details above. ##### Who is your data transferred to? (our service providers) To provide the service we use the following providers. Each of them processes data only for the task written next to it, and only to the extent that task requires: - Cloudflare, Inc. — content delivery network, TLS termination (traffic, including form contents, passes through this point decrypted and is re-encrypted on its way to our servers), web application firewall and bot protection · edge server nearest the visitor / United States - Hetzner Online GmbH — website server and form records · Falkenstein, Germany - Hetzner Online GmbH — backups of the website and form records · Germany - Hetzner Online GmbH — CRM application server and database · Helsinki, Finland - Hetzner Online GmbH — CRM database backups · Falkenstein, Germany - DigitalOcean — storage of uploaded files, images and voice recordings · Frankfurt, Germany - Amazon Web Services (AWS SES) — outgoing e-mail delivery · Frankfurt, Germany - Functional Software, Inc. (Sentry) — application error monitoring · Germany - Anthropic PBC — AI assistant (Rapi), the AI tools our team uses on our own CRM records, and our WhatsApp pre-qualification assistant · United States - Meta Platforms Ireland Ltd. — WhatsApp Business and Instagram messaging · Ireland / United States In our customers' CRM accounts the AI assistant is off by default. Unless you turn it on, the data in those accounts is not sent to any AI provider. Your form records from our site, however, may be processed with AI in our own CRM: our team uses Anthropic's AI tools (Claude and the in-app assistant Rapi) on our CRM records. If you write to our WhatsApp line, your messages are passed to Anthropic PBC so that our pre-qualification assistant can reply to you. Messaging on the Meta side only comes into play when you connect your own WhatsApp Business account to the CRM. When something on this list changes, we update this page. ##### Your rights (KVKK art. 11) You have the right to learn whether your personal data is processed, to request information about it, to learn the purpose of processing, to know the third parties it is transferred to, to request correction if it is incomplete or inaccurate, to request erasure where the conditions are met, to object to a result reached against you solely through automated analysis, and to claim compensation for damage. You can send your requests using the contact details above; we respond within 30 days at the latest. ### [How LinkedIn Leads Enter the CRM | Rapitek CRM](https://rapitek.com/en/linkedin-integration) Lead lists from LinkedIn and fairs are uploaded with Data Hub's 4-step wizard; the profile address is a field on the contact card, the source is tagged. Integration · LinkedIn #### The lead list you come back with from a trade fair or LinkedIn enters the CRM without loss. You upload the list that comes back from a trade fair, an event or LinkedIn with Data Hub's four-step wizard: upload, map fields, preview, run. The profile address sits on the contact card as a field, the record's source is tagged, and the follow-up lands on the owner as a task. Importing works in the product today. Request a demo Let's talk through your list-upload scenario ##### The fair is over, the business cards are in a drawer; the LinkedIn connections are on a phone In B2B the door a lead comes through is a familiar one: a trade fair, an industry event, a webinar and then the connection requests that follow on LinkedIn. The mechanism is this: as long as the list does not enter a system, follow-up stays tied to personal memory. These are the points of loss we have seen in our own projects: - You come back from the fair with a box of business cards. Some are called in the first week, the rest stay in the drawer — because a record that has not been called appears on no list, follow-up stops of its own accord. - The LinkedIn connections are in the rep's personal account. When the rep leaves, the network goes with them; the company is left with no record at all. - The event list circulates in Excel. Two people call the same company, a third is never called; who called whom is on nobody's screen. - “Where did this lead come from?” goes unanswered. The fair, LinkedIn, an ad — because the source is not held as a field, the budget meeting runs on guesswork. - The same person sits on three different lists with three different spellings; if the duplicate is not caught at entry it multiplies with every new import, and it only surfaces when someone happens to notice. - Commercial-message consent has never been discussed. The list goes into a bulk email, and that is where the real risk arises. Not one item on this list is solved by an “automatic LinkedIn integration”. All of them are solved by the list you already have entering the CRM in a disciplined way. ##### The honest picture first: we do not have an automatic LinkedIn connection We do not have an automatic connection to LinkedIn; you upload leads coming from LinkedIn as CSV/Excel with Data Hub's 4-step wizard, and you keep the LinkedIn profile address as a field on the contact card. We do not say that your Lead Gen forms land in the CRM by themselves. We have no Sales Navigator integration. You cannot manage your LinkedIn messages from the CRM — the product's messaging channel list is closed and contains only email, WhatsApp Business, WhatsApp QR and SMS. We do not offer QR pairing as a product promise: the method is not Meta's official API and it carries the risk of the number being restricted; the route we recommend is the official Cloud API. The details are on the WhatsApp integration page. But there is something real to tell on this page, because the part that does the actual work runs in the product today: the four-step import wizard — upload, map fields, preview, run. Imports run into more than 75 objects, up to 100,000 rows per job and 25 MB per file; .csv, .xls and .xlsx are accepted. We measured 1,681 company records imported in a single import job, and the records are still there. Nor do we overstate automatic field mapping. We measured it: 19 of the 19 headers in a Salesforce lead export mapped correctly; in a HubSpot contact export 13 of 17 headers mapped, two mapped incorrectly and the city field did not map at all. Among Turkish headers, the spelling “E-posta” does not map either. This is exactly why the preview step exists: you confirm the mapping on screen, and we do the first setup. So the answer is this: there is no automation on the LinkedIn side, and there is a working import discipline on the CRM side. We set out the general framework on the integrations page. A concrete scenario ##### Monday 08:40 — you are back from the fair, there is a box of business cards on the desk and dozens of new connections on a phone. It goes in this order: - The list is consolidated into a single file | The fair list, the connections you exported from LinkedIn and personal notes are gathered into a single CSV or Excel file. This step is human work, and we say that it is. - It is uploaded with the four-step wizard | Upload, map fields, preview, run. On the preview screen you confirm which column goes to which field; automatic mapping is not flawless, which is why this step cannot be skipped. - Its source is tagged | Each record is marked as “fair — which fair” or “LinkedIn”. Three months later, which channel brought in business is read from a report; the budget meeting does not run on guesswork. - Duplicates are caught at entry | If the same person has a record left over from last year's fair, it is seen in the preview and merged. Duplicates are weeded out at entry, rather than becoming a pile to be cleaned up later. - The LinkedIn profile becomes a field on the contact card | The profile address is kept as a custom field; the rep finds the person in the CRM and goes straight to their profile. The connection now sits in the company's record, not in a personal account. - Follow-up becomes a task, and WhatsApp or email is written to the record | Every record is linked to an owner and a follow-up task. When the correspondence runs through the company WhatsApp number or the connected email account, it is written to that same record. ##### There is no automatic connection — what do we do instead? - The four-step import wizard | Upload, map fields, preview, run. Imports into more than 75 objects, 100,000 rows per job, 25 MB per file; .csv, .xls and .xlsx. We do the first import as part of the setup. - Keeping the LinkedIn profile address as a field | An administrator adds fields such as the profile address, the connection date or which group you met through, without writing code. Adding custom fields is standard in the product: today there are 277 custom fields defined across 19 tenants. - Source attribution and channel comparison | Which fair, which event or LinkedIn a record came from is tagged in the source field. Which channel actually brings in business is not guessed at, it is read from a report. - Weeding out duplicates at entry | Earlier records for the same person are seen at the preview step and merged. Which field will be the match key — email, phone or company name — is decided during setup. - Tying follow-up to a task and an owner | Every uploaded record is linked to an owner and a follow-up task; the ones that have not been called sit in a view. Instead of a pile of business cards in a drawer, you get a list you can track. - Business card scanner | The business card scanner that turns a photo into a lead exists in the product and can be used. Let us write this down too: 74 of the 74 scans measured were made in our own installation; we do not build a claim on customer usage. What exists and what does not ##### What exists and what does not on the LinkedIn side The left column states what is actually being asked for when LinkedIn comes up. The right column shows where that request is met today. What is being asked | In Rapitek CRM | Where it is done - Lead Gen forms landing in the CRM automatically | No. There is no built-in, automatic connection to LinkedIn in the product | Export on the LinkedIn side + import with Data Hub - Sales Navigator integration | No. There is no connector written for Sales Navigator in the product | On the LinkedIn side; moving it into the CRM by export and import - LinkedIn messages appearing in the CRM inbox | No. The messaging channel list is closed: email, WhatsApp Business, WhatsApp QR and SMS. QR is not the official API, and we do not offer it as a product promise | In the LinkedIn app - Generating leads automatically by scraping profiles | No, and we do not do it. Scraping is risky in terms of platform rules and personal data | Nowhere — this is not a shortcoming, it is a choice - Uploading the lead list to the CRM as CSV/Excel | Yes. Four-step wizard: upload, map fields, preview, run. 75+ objects, 100,000 rows per job | Rapitek CRM — the first import is within the setup scope - Keeping the LinkedIn profile address on the contact card | Yes. Added as a custom field without writing code | Rapitek CRM - Tagging a record's source, and channel reporting | Yes. The source field and reporting are standard in the product | Rapitek CRM - Sending an automatic email sequence to the uploaded list | We do not promise it. The sales sequence screens are in place in the product, but today we cannot point to a reference for it | Discussed during setup; the start we recommend is task-based follow-up - Sending commercial messages to the collected list | Conditional. Consent status is kept on record in the CRM and, when you connect your own İYS account through Verimor, synchronised with İYS both ways; sending runs together with that record | Rapitek CRM + İYS; the legal assessment rests with you and your adviser What we can say ##### What we measured on the import side — the good and the bad - 1,681 companies | Company records imported in a single import job; the records are still there - 100,000 rows | The upper limit per import job; 25 MB per file, 75+ objects supported - 19/19 | Salesforce lead export headers that mapped correctly, automatically - 13/17 | Headers matched in a HubSpot contact export; two wrong, city not matched at all - 277 custom fields | Custom fields added across 19 tenants without writing code Implementation ##### How is the list-upload routine set up? - Discovery | We work out which doors leads come through — fair, event, webinar, LinkedIn, referral — and which file is kept at each door today. We recommend that your sales manager is in this meeting. - Template and match key | A single upload template is settled on, and it is decided which field will catch duplicates: email, phone or company name. If the template is not fixed, a different file format arrives after every fair. - Fields, source list and task rule | Custom fields such as the LinkedIn profile, the source options and who the task falls to after an upload are set up. We do the first import together with a sample file, and we read the preview together with your team. - Training and handover | Your team does the subsequent uploads itself; the wizard is four steps and requires no code. We do not commit to a duration before discovery; after the discovery meeting we give you a date, not a range. ##### Our limits: what we do not promise on this page Precisely because there is something real to tell on this page, the boundary needs to be drawn even more clearly. - We do not say “your Lead Gen forms land in the CRM automatically”. There is no built-in automatic connection to LinkedIn in the product. - We have no Sales Navigator integration. - We do not say “manage your LinkedIn messages from the CRM”. The product's messaging channel list is closed and contains only email, WhatsApp Business, WhatsApp QR and SMS; LinkedIn is not on that list. - We do not offer pairing the phone by QR code as a product promise. The same inbox can be connected this way too, but the method is not Meta's official API and it carries the risk of the number being restricted by Meta. The route we recommend is the official Cloud API; if you still prefer this route, we share the risk in writing and we take the decision together. The details are on the WhatsApp integration page. - We do not scrape data. We have no tool that automatically collects data from profiles, and we do not want one. Scraping is risky both under the platform's own rules and in terms of personal data, and we do not pass that risk on to our customer. - We do not promise an automatic email sequence to the uploaded list. The sales sequence screens are in place in the product, but in eight of the eight installations we measured this table is empty. The start we recommend is task-based follow-up. - We do not build a customer-usage claim for the business card scanner. The feature exists in the product; 74 of the 74 scans measured were made in our own installation. Consent and commercial messages: having taken someone's business card at a fair does not mean you have permission to send that person commercial electronic messages. For customers who connect their own İYS account through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM; sending runs together with the consent record. Preparing your privacy notices and consent texts is your job and your legal adviser's; we build the mechanism. Data location: your data is held in the European Union — the database in Helsinki (Finland), the files you upload in Frankfurt, the backups in Falkenstein (Germany). We have no component in Türkiye, and we have no region selection feature. This is a transfer abroad within the scope of KVKK art. 9; we establish your legal basis together during the contract process. The details are on the security page and in the KVKK privacy notice. Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. The canonical limits that apply to every integration — stock synchronisation, the order–invoice–collection chain and production automation — sit in one place: the three things we do not promise. ##### Plan prices are in the open; scope comes out at discovery The scope of the list-upload and follow-up routine is worked out in the discovery meeting and shared in writing. Plan prices and separately priced items we publish on a single page, with the figures. See the pricing Three plans, a scope table and separately priced items on a single page. FAQ ##### Frequently asked questions about LinkedIn and Rapitek CRM - Does Rapitek CRM have a LinkedIn integration? | Not in the sense of an automatic connection. You upload leads coming from LinkedIn as CSV or Excel with Data Hub's four-step wizard, and you keep the LinkedIn profile address as a field on the contact card. The import side runs in the product today: more than 75 objects, 100,000 rows per job, 25 MB per file. - Do our LinkedIn Lead Gen forms land in the CRM automatically? | No, they do not, and we will not say that they do. You export the form responses on the LinkedIn side and upload them to the CRM; your team can do the upload itself, and we do the first import as part of the setup. If you want a regular flow, it is possible to build the bridge between them over the REST API within a project scope; we discuss this not as a promise but as work whose scope will be determined at discovery. - Does it work with Sales Navigator? | We have no connector written for Sales Navigator. You move the lists you take from Sales Navigator into the CRM the same way as any other list — by export and the import wizard. The record's source is tagged, so the return from this channel can be reported separately. - Can we manage our LinkedIn messages from the CRM? | No. The product's messaging channel list is closed and contains only email, WhatsApp Business, WhatsApp QR and SMS; LinkedIn is not on that list. We do not offer QR pairing as a product promise: the method is not Meta's official API and it carries the risk of the number being restricted; the route we recommend is the official Cloud API. In the shared inbox you see your WhatsApp correspondence and the correspondence going out from your connected email account; a LinkedIn conversation stays in LinkedIn. - How do we get the business cards from a fair into the CRM? | There are two routes. The first, and the one we recommend: writing the business cards into a single Excel file and uploading it with the four-step wizard — upload, map fields, preview, run. The second: producing leads from a photo with the business card scanner in the product. For the second route, let us write this down too: the feature exists, but 74 of the 74 scans measured were made in our own installation. - Do the fields map automatically when we upload? | Partly, and we measured it. 19 of the 19 headers in a Salesforce lead export mapped correctly; in a HubSpot contact export 13 of 17 headers mapped, two mapped incorrectly and the city field did not map at all. Among Turkish headers, the spelling “E-posta” does not map either. This is exactly why the preview step exists: you confirm the mapping on screen. - The same person is on several lists; will duplicate records be created? | They are caught at the preview step. Which field will determine a duplicate — email, phone or company name — we decide during setup; the choice stands in the written scope. Existing records can be merged. Weeding duplicates out at entry is far cheaper than cleaning them up afterwards. - Can you collect data from LinkedIn profiles? | No, we have no such tool, and we do not want one. Profile scraping carries risk both under the platform's own rules and in terms of the processing of personal data; we do not pass that risk on to our customer. The data that enters the CRM is data you have collected by legitimate means. - Can we send bulk email to the list we uploaded? | Technically the sending channels are there; the real question is consent. Sending commercial electronic messages runs together with the consent record in the CRM. For customers who connect their own İYS account through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM. Having taken a business card at a fair does not on its own amount to consent. The legal assessment rests with you and your adviser; we build the mechanism. - If our rep leaves, do the LinkedIn connections stay with the company? | A LinkedIn account belongs to the person and that account goes with the rep — we cannot change that. What we can change is this: the contact record, the meeting history, the profile address and the follow-up notes stay in the CRM as the company's record. When the correspondence runs through the company WhatsApp number or the connected email account, that is written to the record too. - Can we see how many leads came from which channel? | Yes. Every record's source is tagged as a field — fair name, event, LinkedIn, referral, web form. Channel comparison is done with the table and summary report types and with the drag-and-drop dashboard designer. What matters is that the tag is applied at the moment of upload; applying it afterwards turns into a laborious clean-up job. - Can we do the import ourselves? | Yes, the wizard is four steps and requires no code: upload, map fields, preview, run. We do the first import as part of the setup and fix the template and the match key together with you; your team does the subsequent uploads itself. If the template is not fixed, a different file format arrives after every fair and the routine breaks down. - How long does setup take? | We do not commit to a duration before discovery; after the discovery meeting we give you a date, not a range, and the day you go live stands in the written scope. Setup consists of these steps: discovery, configuration, data migration, training and go-live. The list-upload routine is set up within this plan. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. This is a transfer abroad within the scope of KVKK art. 9; we establish the legal basis for it together during the contract process. Your CRM data is held in a separate database belonging to you. - Where does support come from? | There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. Support is provided during Türkiye business hours; if you have teams in different time zones, let us discuss the scope together in the meeting. - Can we see this before we buy? | There is no trial you can start on your own. First we do a 30-minute live demo — if you like, let us walk through the import wizard step by step with your own sample list; we particularly recommend showing the preview step, because that is where you see where the mapping needs a human hand. Afterwards, if you want to explore the product at your own pace, we open a time-limited demo account. ##### Related pages - Integrations | Which connection works in the product today, which ones we build on request — and the reason for the three things we do not promise. - KVKK and consent | When you upload a lead list the real question is consent: what KVKK says, what it does not say and how the İYS side works. - Netsis integration | What comes after a lead becomes a customer: bringing account, balance and invoice information onto the sales screen. ##### Let's set up your list routine before the next fair In a 30-minute demo, let us walk through the import wizard step by step with your own sample list; let us settle the template, the match key and the follow-up tasks together. Request a demo The first import is done as part of the setup; your team does the subsequent uploads itself. ### [CRM Mobile App for iOS and Android | Rapitek CRM](https://rapitek.com/en/mobile-app) Both apps are live and ship with a Turkish interface. WhatsApp messages in an in-app inbox, voice-written records with Rapi, visit tracking on the phone. Mobile app · iOS and Android #### Selling doesn't happen at a desk. Your CRM shouldn't stay there either. The Rapitek CRM mobile app is live on both iOS and Android, and it ships with a Turkish interface. The shared inbox, the customer record, quotes and visit tracking — all of it works from the field. See it live in a demo Explore the product ##### If the inbox stays on the desktop, it never reaches the field team's day — we saw this in our own projects For a rep who is out in the field, mobile access isn't a comfort but a condition of use: the rep is on the phone all day, so an inbox that sits in a desktop browser doesn't get opened in practice. We saw this with our own teams on enterprise CRM projects; we haven't measured how many installations it happens in, so we're not putting a figure on it. What follows is this: the customer writes on WhatsApp and the reply waits until the rep is back at the office — or the rep answers from their own phone and the conversation leaves the company. Here, the inbox is inside the app. WhatsApp messages are handled from the app, and every conversation stays attached to the customer record. Instagram direct messages land in the same shared inbox. Inbox · inside the app #### Every conversation stays attached to the customer record. WhatsApp messages are managed in the app's own inbox: each thread is opened under the customer it belongs to, assigned to a rep, and filtered by status — open, active, waiting, resolved. The history stays with the company, not on someone's personal phone. Instagram direct messages land in the same inbox. How the WhatsApp connection works ##### What's in the app? - One inbox, inside the app | WhatsApp messages are handled in the inbox inside the app; the conversation attaches to the customer record, gets assigned to a rep, and its history stays with the business. Instagram direct messages land in the same inbox. - Rapi — an assistant that writes records by voice | It creates and updates your CRM records from speech in Turkish. It can be configured to ask for your confirmation before it writes; set up that way, control stays with you. - Business-card scanning | Photograph a card and the fields are extracted into a lead record. One photo can hold several cards — each becomes its own record. No manual data entry on the way back from a trade show. - Visits and field tracking | Visit check-in, follow-up tasks and performance reports. The field team's whole day runs from the phone. Route plans and field visit records are a separately priced module — 25 USD per user per month. - The customer record in your pocket | Before you walk into a meeting you have the customer's history, open opportunities and most recent messages in hand. - Turkish interface | The app ships with a Turkish interface. We don't offer an English interface today, so this is worth checking if your field team doesn't read Turkish. A typical day ##### A field rep's day - Morning — route and history | The day's visits are on the phone. Each customer's last message, open quote and pending task show up on the card. - On the visit — record by voice | The moment the meeting ends, the rep talks into the phone in the car: Rapi saves the note and opens the follow-up task. No pile of data entry waiting at the office that evening. - Afternoon — an incoming message | The customer writes on WhatsApp. It lands on the company's work number, the rep replies from the app, and the conversation stays on the customer record. - Evening — the manager's view | Which visits were logged, where each meeting stands and which conversations are waiting for a reply are all in a report. Nobody has to ask. Note: the app does not track location in the background; location is recorded only at the moment of a visit check-in. FAQ ##### About the mobile app - Which platforms is it on? | Both our iOS and Android apps are live, and both ship with a Turkish interface. - Does the mobile app cost extra? | No. The mobile app is standard in every installation. Items priced outside the plan are listed one by one on our pricing page. - What do we need to use Rapi? | Rapi is on every plan; usage draws from your AI credit and it has to be enabled on your account. It can be configured to ask for your confirmation before it writes a record — running autonomously, independently of that approval, is not what it is meant for. - Are Instagram messages in the app too? | WhatsApp and Instagram messages are handled in the single inbox inside the app. Replying to Instagram from the mobile app has not yet been measured in a customer deployment. Channel connections are configured during setup. - Does it work without an internet connection? | The app works online. How your field team should work in areas with weak coverage is something we talk through in the discovery call. ##### Let's look at it with your field team. If you like, we'll run the demo with someone from your sales team — the person who will actually use the app is the best test. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Odoo Integration: Open Source ERP and CRM | Rapitek CRM](https://rapitek.com/en/odoo-integration) Account, product and order data from Odoo appears on the sales screen. Because it is open source, we do not guess the scope — we look at your installation. Integration · Odoo #### If you use Odoo, your CRM talks to Odoo. Account, product, order and invoice data stays in Odoo; your sales team sees the same data in the CRM. Because Odoo is open source and modular, the access question starts differently than it does with other ERPs — and that is where this page begins. Request a demo Schedule a discovery call ##### Odoo's modules are open, yet the pre-sales process is still adrift At companies using Odoo, the product may have been customised either by an in-house developer or by an Odoo partner. This page was not written to disparage Odoo; it was written to describe a real pattern that recurs at the companies who call us. - Orders and invoices move along properly in Odoo; but everything before the order — the lead, the discovery, the quote revision, the reason for losing — accumulates nowhere. - The customer request arrives over WhatsApp, the quote goes out by email; both are outside the ERP and both get lost. - The field team does not use the ERP screen on a phone; the visit note stays a note that never gets written up in the evening. - As customisation accumulates, new requests join the developer queue; the sales manager cannot add their own field themselves. - The person who prepares the reports sits in the technical team; the question “what is in the pipeline this week” turns into a ticket. - And there is the possibility nobody likes: two customer lists form in two places, and which one is correct becomes a matter of debate. That last item is the real subject of this page. The job of an integration is not to produce a second list, but to set a rule for which system is the authority for which data. ##### How is the connection built? There is no out-of-the-box module for Odoo on our side, and we will not claim there is. The connection is built as an integration project whose scope is determined in the discovery call, using the REST API, OAuth2, webhooks and import/export. Which external interface will be used on the Odoo side — which endpoint, with which permissions — we determine together during discovery. Odoo differs from other ERPs in one way, and that makes our work easier: because the source code is open, what is possible on the other side is not guessed at, it is looked at. With a closed ERP, the answer to the access question is sought at the licence and version desk; with Odoo, we look at your own installation during the discovery call. This lets us determine the scope earlier and more precisely; but it is not the same thing as an out-of-the-box module — there is still a connection that has to be written. Three tools are used on the Rapitek CRM side: - REST API — the product ships out of the box with 183 business objects, and each one is exposed in the REST API with its own data and schema endpoint; access is authorised with OAuth2. An object's schema can be read from the describe endpoint, several operations can be sent in a single composite request, and bulk transfer is done through the batch endpoints. - Outbound webhook — CRM events are delivered to the external system signed; a failed call is retried and the target address is verified. - Import/export — a four-step wizard; we do the initial data migration ourselves during setup. The limits of these three tools are measured, not estimated: the REST API gives object and field definitions from the describe endpoint, processes up to 200 records in a single batch request, and carries 25 sub-requests at once in a composite call. The import wizard works on more than 75 objects, up to 100,000 rows per job and 25 MB per file. Our general approach is on the integrations page, and the same framework applied to a closed ERP is on the Netsis integration page. A concrete scenario ##### Thursday, 15:10 — the customer asks for a revision over WhatsApp, and the quote had been written in Odoo. Once the connection is in place, here is what changes: - The request lands as a record, not as a message | If your WhatsApp Business account is connected to the CRM, the message is written into the shared inbox and onto the relevant customer record. The revision request does not stay on one person's phone. - The quote revision is tracked on the opportunity record | Which revision number it is, what changed and who approved it stay in the CRM. The version that turns into an order is passed to Odoo through defined fields. - The price stays the same as the list in the ERP | Because the product catalogue and the price list are transferred from Odoo, the quote is written at the current price. The authority for the price stays in Odoo; the copy in the CRM is there for the sales screen. - The authority for the customer record is set by a rule | Which system the customer record is created in, and how it flows to the other, is written down during setup. The two lists do not drift apart, because one becomes the source and the other the mirror. - The sales manager adds their own field themselves | Adding custom objects and fields on the CRM side is done without writing code. There is no joining the developer queue for a new sales field; the customisation queue on the ERP side gets some relief. - A reporting screen, not a report request | The pipeline, the source breakdown and the reasons for losing are prepared with the drag-and-drop dashboard designer. No appointment with the technical team is needed for a sales report. ##### Flows that can be built between Odoo and Rapitek CRM - Customer record matching and the authority rule | Which system is the authority for the customer record, and how it flows to the other, is defined in the written scope. Matching is set up on the tax number or on the identity key on the Odoo side. - Product catalogue and price list transfer | Product cards and the price list are transferred into the CRM; quotes are written at the current price. The transfer can be periodic, or it can be set up over the API. - Passing a won opportunity to Odoo | A signed webhook that passes the order data to the external system when an opportunity is won can be set up. Entering the same data by hand a second time is reduced. - Account balance and invoice visibility | Balance, due date and invoice header data are transferred onto the customer card. The authority for the document stays in Odoo; the CRM adds a visibility layer for the sales team. - Connecting messaging channels to records | Your own Meta WhatsApp Business account is connected to the CRM and the correspondence lands on the relevant record. You connect your own Gmail account with OAuth; that connection covers email sending and calendar synchronisation — inbox reading is switched off. Outlook and Microsoft 365 connections are not live. - Adding fields and objects without writing code | The administrator defines the fields the sales side needs themselves. The customisation queue on the ERP side is not tied up for a new sales field. Choosing a method ##### Which method, and when? We choose the method together with your Odoo partner. All four use the same REST API surface; the difference is who moves the data, and how often. Method | What it is for | When it is preferred - REST API (183 business objects out of the box, each with its own data and schema endpoint) | The external system reads and writes the records in the CRM; it is authorised with OAuth2, the schema is read from the API, and 25 sub-operations are sent in a composite request | When an external interface can be used on the Odoo side and the flow is meant to run automatically - Outbound webhook | Events in the CRM (e.g. opportunity won) are delivered to the external system signed; a failed call is retried | In flows that need event notification in the CRM-to-Odoo direction - Import (Data Hub) | Excel/CSV extracts are transferred with a four-step wizard: upload, map fields, preview, run. Export is done in the same module; we have not measured its limits | For the initial data migration and one-off transitions; as a bridge until the API flow is in place - Your own developer or your Odoo partner | The team that already knows the Odoo side can write the connection themselves using the same REST API; we give them the schema, the OAuth2 access and the field mapping table | If customisation has accumulated in your Odoo and you will keep working with that team What we can say ##### What we have verified - 183 | Business objects in the REST API - 25 sub-requests | Operations that can be sent in a single composite request - 200 records | Records processed in a single call on the batch endpoints - every 6 hours | A database backup is taken; local copies kept 30 days, compression checked Implementation ##### How is the Odoo connection put into service? - Discovery | We work out where you run Odoo, which modules you use and which customisations have been made. We recommend that the partner or developer who set up your Odoo joins this call. - The authority rule and field mapping | Which system is the authority for which data is decided here — this is the critical step in Odoo flows. The field mapping table, the direction of flow, the frequency and the cost, if any, are shared in writing. - Configuration and test migration | The objects, fields and permissions on the CRM side are set up; two-way verification is done with sample records. Duplicate record scenarios are tried out here. - Training and go-live | Training for the sales and field teams, then close follow-up during the first week. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The duration of the API-based Odoo flow becomes clear according to the scope. ##### Our limits: what we do not promise on this page There are four things people ask about when ERP integration comes up. We do not promise any of the four, and we write down why. - We do not say “your stock will be in sync”. The authority for the stock record stays in Odoo. - We do not say that the order → invoice → collection chain will flow on its own. That chain is built into the product, but we do not think it is right for it to be sold as an automated accounting flow. - We do not promise manufacturing and MRP automation. The bill of materials and the production line definition exist in the product; we cannot describe work order execution with a reference case today. - We do not issue e-Invoice or e-Archive documents. Rapitek CRM is not a GİB private integrator; it does not produce official documents and does not track ETTN or GİB status. Your invoices continue to be issued under your current arrangement. We wrote the reason for the first three, and “what can be done instead”, in one place, line by line: the three things we do not promise. We are not repeating it here, so that we do not end up writing two different sentences in two places. One more thing: if a module has to be installed or an endpoint has to be written on the Odoo side, that work sits with your developer or your Odoo partner. We provide the CRM side, the schema, the OAuth2 access and the field mapping table. We do not offer Odoo installation, upgrade or maintenance services. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We do not have a single component in Türkiye, and we do not have a region selection feature. This is a transfer abroad within the scope of KVKK art. 9. The details are on the security page and in the KVKK disclosure notice. Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. ##### Plan prices are out in the open; scope comes out of discovery The scope of the Odoo connection, and its cost if there is one, are worked out in the discovery call and shared in writing. Plan prices and separately priced items, on the other hand, we publish on a single page, with the figures. See the pricing Three plans, a scope table and separately priced items on a single page. FAQ ##### Frequently asked questions about Odoo integration - Is CRM integration with Odoo possible? | Yes — but not with an out-of-the-box module; as an integration project with a defined scope. The connection is built with the REST API, OAuth2, a signed outbound webhook and import/export. Which external interface will be used on the Odoo side, and with which permissions, is determined during discovery and shared as a written scope. - Is there a ready-made Odoo module in Rapitek CRM? | There is not; it would not be right to say there is. We have no out-of-the-box module specific to Odoo: a code scan looked for provider-specific code under the Odoo name and did not find any. As for what exists in a third-party app marketplace, we have not measured that, so we do not write about it. What we do have is a documented interface: the product ships out of the box with 183 business objects, and each one is exposed in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe; alongside it, OAuth2, a signed webhook and a four-step import wizard. - Odoo has its own CRM module. Why a separate CRM? | That is a legitimate question, and our answer is this: if Odoo's sales side does the job for you, do not change it. The reason we hear at the companies who call us tends to be a different one: the sales and field teams not using the ERP screen in their daily work, WhatsApp and email traffic staying off the record, and the setup being left to them. What sets us apart is not a feature list: we do the setup, the data migration and the training in Turkish ourselves. - We run Odoo on our own server. Will access be a problem? | It does not have to be, because in an installation on your own server you define the permissions. What is decisive is this: can an endpoint with limited permissions be defined that lets the CRM and Odoo reach each other? We check that during discovery together with your IT lead. If it cannot be defined, the flow is built with periodic import/export. - We have a partner who has done customisation in Odoo. Can they write the connection? | Yes, this is a path we support. Your partner can write the connection themselves using Rapitek CRM's REST API; we give them the API documentation, the OAuth2 access, the object definitions and the field mapping table. Who writes what, how the testing will be done and which field flows in which direction we set out separately, in writing, during discovery. We do not have a figure for how many Odoo installations have taken this path; since we have not measured it, we do not write a number either. - Does it matter which Odoo version we use? | It affects the scope, it does not change the answer. During discovery we work out your version, the modules you use and the customisations that have been made; what is decisive is whether an externally accessible interface can be defined. The Rapitek CRM side is the same in every case: 183 business objects out of the box, each with its own data and schema endpoint in the REST API, authorised with OAuth2. - Won't we end up with two customer lists in two systems? | This is a step that is expensive to skip in integrations, and it is where we start. During setup, an authority is determined for each data type: where the customer record is created, which field flows in which direction, and which one wins in a conflict. That rule sits in the written scope. In an integration built without the rule being written down, the two lists can drift apart over time; talking about it beforehand is the cheapest part of the job. - Does it replace Odoo? | No, and we do not recommend that it should. Odoo stays on the accounting, stock, order and official document side; Rapitek CRM takes the pre-sales process: the lead, the meeting history, quote revisions, messaging and sales reporting. The job of the integration is to connect these two sides with a defined flow. - Will our stock stay in sync with the CRM? | We do not promise real-time stock synchronisation. The authority for the stock record stays in Odoo; the scope of the stock data to be carried over to the CRM side, its frequency and which fields it will include are defined during discovery. We wrote the reason, and what can be done instead, in the limits section of the integrations page. - Can we issue an e-invoice from the CRM? | No. Rapitek CRM does not issue e-Invoice or e-Archive documents and is not a GİB private integrator; fields such as ETTN or GİB status do not exist in the product. Your invoices continue to be issued under your current arrangement; the invoice number, date and amount can be carried onto the customer card as fields. - Will synchronisation be real-time? | It depends on the method, and we do not give a “real-time” promise up front. API- and webhook-based flows can run close to the event; import/export is periodic. Which flow runs at which frequency sits line by line in the written scope. - What does the Odoo integration cost? | We do not write a figure on this page, because the cost depends on the scope: which objects flow, in which direction and at what frequency, how deep the customisation goes, and who writes the connection. If your own partner writes the connection, the work item on our side gets smaller. After discovery we share the scope and the cost in writing. - How long does setup take? | We do not commit to a duration before discovery. After the discovery call we give you a date, not a range: the dates of the discovery, configuration, data migration, training and go-live steps sit in the written plan. An import/export-based start can be set up within that plan; the scope and the date of the API-based flow are clarified in the same plan. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We do not have a single component in Türkiye and we do not offer a region selection. This is a transfer abroad within the scope of KVKK art. 9; we establish its legal basis together during the contract process. Your CRM data is held in a separate database belonging to you. ##### Related pages - Integrations | An overview of integration: which connection is live today, which ones we build on request, and the reason behind the three things we do not promise. - Netsis integration | The same framework applied to a closed ERP: why the access question starts at the licence and version desk. - Product | Modules, API coverage and platform controls: exactly what is set up on the CRM side. ##### Let's clarify your Odoo flow in 30 minutes Invite the team that set up your Odoo to the call as well; let's decide together which system will be the authority for which data, and who will write the connection. Request a demo The scope of the setup, and its cost if there is one, are worked out in the discovery call and shared in writing. ### [Oracle Integration: ERP and CRM Connection | Rapitek CRM](https://rapitek.com/en/oracle-integration) Account, order and invoice data from Oracle shows up on the sales screen. First we establish which Oracle product it is, then we put the scope in writing. Integration · Oracle #### Your CRM talks to Oracle — once we have established which Oracle it is. Account, order and invoice data stays on the Oracle side; your sales team sees the part it needs inside the CRM. But “Oracle” is not a single product: until it is clear which product it is, we do not promise a scope. Request a demo Schedule a discovery call ##### “Can you connect to Oracle?” has no one-word answer This page starts from a different place than our other ERP pages, because the question is different. When someone says Netsis, Nebim or Logo, what sits on the other side is more or less known. When someone says Oracle, it is not. - The same sentence can describe a cloud enterprise ERP, an installation customised on your own servers over many years, or a cloud ERP managed by a separate team. - Sometimes the ERP is an entirely different product and only the database is Oracle — a distinction that changes the answer completely. - IT asks “can you connect”; the sales side asks “will I be able to see the balance”. The two questions look the same; they are not. - The commercial cost of this ambiguity is this: a “yes, we integrate with it” given without knowing what sits on the other side may have to be taken back once the scope emerges. - The picture on the sales side comes out the same in our own projects: the lead, the meeting history, the quote and the reason for a loss sit in the space where the ERP does not begin, and nothing records them on its own. That is why on this page we make the distinction first and describe the connection second. ##### How is the connection built? There is no out-of-the-box module for Oracle, and we will not say there is. The connection is built as an integration project whose scope is determined in the discovery call, using REST API, OAuth2, webhooks and import/export. We add one more sentence to that: until it is clear which Oracle product is being discussed, we do not promise a scope. Saying “we have an Oracle integration” would be a promise made without knowing what sits on the other side; we do not make that promise before the first call. For the same reason, we also do not say that we have an “Oracle certified” or “Oracle approved” integration — we hold no such certification. Three tools are used on the Rapitek CRM side: - REST API — the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint; access is authorised with OAuth2, and no integration is ever built by sharing a user's password. - Outgoing webhooks — CRM events are delivered to the external system signed; a failed call is retried and the target address is verified. - Import/export — a four-step wizard; in organisations with long approval processes, a starting point that does not delay the first benefit. The limits of these three tools are measured, not estimated: the REST API exposes object and field definitions through the describe endpoint, processes up to 200 records in a single bulk request, and carries 25 sub-requests at once in a composite call. The import wizard works across more than 75 objects, up to 100,000 rows per job and 25 MB per file. Our general approach is on the integrations page; the same framework applied to a single-product ERP is on our Netsis integration page. The first distinction ##### First: which Oracle? This table is not a capability list; it is a list of distinctions. No scope is written until it is clear which row you are in. What sits on the other side | The first question we ask in discovery - Cloud enterprise ERP (e.g. Fusion / ERP Cloud) | With what authorisation can the integration layer be reached, and who defines that access? - An installation on your own servers, customised over many years (e.g. E-Business Suite) | Which modules are in use, and is an externally exposed interface defined today? - A cloud ERP managed by a separate team (e.g. NetSuite) | Where will authority over which data stay, and which record will flow in which direction? - A long-lived, industry-specific Oracle product | Is there an interface that gives data out today, or are we talking about periodic extracts? - The ERP is another product; only the database is Oracle | Is there an interface on the application side? We do not recommend connecting directly to the database as a first solution. A concrete scenario ##### Wednesday, 09:50 — IT asks “Can you connect to Oracle?” Here is how we walk through it: - The distinction is made in the same call | Which Oracle product, where it runs, who manages it — these three questions are answered first. Until the answers come, neither scope nor timeline is written down; this is not the half hour the call loses, it is the half hour the call gains. - Who holds access is put in writing | Is the party that defines the interface your own IT department, your Oracle partner, or your service provider? The boundary of responsibility is drawn at the start, not argued over later. - The sales side is not put on hold | If the approval process on the Oracle side is long, the CRM rollout starts on an extract-based footing. The sales team begins keeping records from the first week; when the connection is ready, the same scope is moved onto the API. - Balance and invoice visibility comes first | This is what we recommend as the first flow: account balance, due date and invoice header information sit as fields on the customer record. They are visible before a quote is written. - IT's questionnaire gets a written answer | Data location, the sub-processor list, authorisation and audit logging are written out on our security page; we also fill in your assessment questionnaire ourselves. We also state in writing that we hold no certification. - The scope comes out in writing, then the work starts | The field mapping table, flow direction, frequency and price are shared in writing. After the discovery call we give you a date, not a range. ##### Flows that can be built between Oracle and Rapitek CRM - Matching customer and account records | Records are matched using the tax number or the customer code on the Oracle side as the key. The matching rule and conflict scenarios are defined in the written scope. - Balance, due date and risk visibility | Account balance, overdue amount and risk limit are transferred onto the customer record. Transfer frequency is set in the scope; authority stays on the Oracle side. - Tracking order and invoice information | Order and invoice header information can be followed as a list on the customer record. Authority over the document stays in the ERP; the CRM adds a visibility layer for the sales team. - Notifying the ERP side of a won opportunity | A signed webhook that passes order information to the external system when an opportunity is won can be set up. Calls are signed, and a failed call is retried. - A fast start with a periodic extract | While access approval on the Oracle side is pending, the account and balance extract is transferred with the four-step wizard. It works within the limits of 100,000 rows per job and 25 MB per file. - Authorisation and audit trail | Profiles, permission sets, role hierarchy and record sharing are supported; field-level change history is kept. This is where enterprise audit questions get their answer. Choosing a method ##### Which method, and when? The method is chosen after the distinction above is clear. All four use the same REST API surface; the difference is who moves the data, and how often. Method | What it does | When it is preferred - REST API (183 business objects out of the box, each with its own data and schema endpoint) | The external system reads and writes records in the CRM; it is authorised with OAuth2, the schema is read from the API, and bulk and composite requests are supported | When an integration layer is defined on the Oracle side and the flow is meant to run automatically - Outgoing webhooks | Events in the CRM (e.g. opportunity won) are delivered to the external system signed; a failed call is retried | In flows that need event notifications from the CRM towards the ERP - Import (Data Hub) | Excel/CSV extracts are transferred with the four-step wizard: upload, map fields, preview, run. Export is done in the same module; we have not measured its limits | While the access approval process is long; to start without keeping the sales side waiting - Third-party integrator | Your consultant who knows the Oracle side can write the connection themselves using the same REST API; we provide the schema, OAuth2 access and the field mapping table | If you work with an established consultant team on the Oracle side What we can say ##### What we have verified - 183 | Business objects in the REST API - OAuth2 | Access is authorised with a token; no user password is shared - Every 6 hours | The database is backed up; local copies kept 30 days, compression checked - 100,000 rows | The ceiling per import job; 25 MB per file, 75+ objects supported Rollout ##### How is the Oracle connection put into service? - Distinction and discovery | Which Oracle product, where it runs, who manages it, and whether an externally exposed interface is defined — all of this is established. We recommend that IT and the team that knows your Oracle side be in this call. - Scope, authorisation and the boundary of responsibility | Which data flows in which direction and how often, and who will define the interface, are written down here. The field mapping table and any fee are shared in writing — no surprise line items. - Configuration and a test transfer | Objects, fields, permissions and reports are set up on the CRM side; two-way validation is done with sample data. Duplicate-record and conflict scenarios are exercised here. - Training and go-live | Team training and close follow-up in the first week. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. If access approval on the Oracle side drags on, it starts with an extract-based flow and is moved onto the API afterwards. ##### Our limits: what we do not promise on this page There are five things people ask about when Oracle comes up. We do not promise any of the five, and we write down why. - We do not say “Oracle certified / approved integration”. We hold no such certification and will not claim one without it. - While it is unclear which Oracle product is involved, we do not promise a scope. A promise made without knowing what sits on the other side gets taken back once the scope emerges. - We do not say “your stock will be in sync”. Authority over the stock record stays on the ERP side. - We do not say that the order → invoice → collection chain will flow on its own. That chain is built into the product, but we do not think it is right to sell it as an automated accounting flow. - We do not promise manufacturing and MRP automation. Bill of materials and production line definitions exist in the product; we cannot today point to a reference for work order execution. We have written the reason for the last three, and “what can be done instead”, in one place, line by line: the three things we do not promise. Rapitek CRM also does not issue e-Invoice or e-Archive documents and is not a GİB (Turkish Revenue Administration) special integrator. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Turkey and we have no region-selection feature. This is a transfer abroad under Article 9 of KVKK (Turkey's data protection law); we establish your legal basis for the transfer together during the contract process. The detail is on the security page and in the KVKK privacy notice. Certification: we hold no ISO 27001 or SOC 2 certification. We fill in your enterprise security assessment questionnaires and describe the architecture in writing; we do not give a written service level (SLA) commitment. ##### Scope comes out of discovery; plan prices are out in the open Until it is clear which Oracle product you are on, we do not promise a scope; the price comes out together with the scope. Plan prices, though, we publish in one place, with their actual figures. See pricing Three plans, a scope table and separately priced items, all on one page. FAQ ##### Frequently asked questions about Oracle integration - Is CRM integration with Oracle possible? | Yes — but first we establish which Oracle product is being discussed, and only then do we write a scope. The connection is not built with an out-of-the-box module; it is built as an integration project with a defined scope, using REST API, OAuth2, signed outgoing webhooks and import/export. - Is there a ready-made Oracle module in Rapitek CRM? | There is not; it would not be right to say there is. We have no out-of-the-box module specific to Oracle products. What we do have is a documented interface: the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe; alongside it, OAuth2, signed webhooks and a four-step import/export wizard. - We do not know exactly which Oracle product we use. How do we proceed? | This is an ordinary situation and not an obstacle. In the discovery call we make the distinction together with three questions: which product, where it runs, who manages it. The answers sit with your IT manager or with the firm that manages your Oracle side; we recommend that person be in the call. Until the distinction is clear, we do not write a scope or a timeline. - Is this an Oracle certified integration? | No. We do not have an Oracle certified or Oracle approved integration, and without such a certification we will not claim one. What we do is build a scoped connection over Rapitek CRM's own documented REST API. - Can you connect directly to our Oracle database? | It can be discussed technically, but we do not recommend it as a first solution. Connecting directly to the database bypasses the application's business rules; it is the first place that breaks on a version upgrade or a schema change. Our recommendation is to use an interface defined on the application side; if no such interface exists, to start with a periodic extract. We make the decision together with your IT team during discovery. - Can our Oracle consultant write the connection themselves? | Yes, this is a route we support. Your consultant can write the connection themselves using Rapitek CRM's REST API; we provide the API documentation, OAuth2 access, the object definitions and the field mapping table. Who writes what, how testing is done and which field flows in which direction are separated out in writing during discovery. We have no figure for how many Oracle installations have taken this route; since we have not measured it, we do not write a number either. - We use Oracle NetSuite. Does it make a difference? | It affects the scope; it does not change the framework. Once your row in the distinction table is clear, the first question becomes: where will authority over which data stay, and which record will flow in which direction? The connection is still built with REST API, OAuth2, webhooks and import/export; the Rapitek CRM side is the same in every case. - Our IT team sends a security assessment questionnaire. Do you fill it in? | Yes, we fill it in and describe the architecture in writing. Let it be known from the start: we hold no ISO 27001 or SOC 2 certification. Here is what can be written: the data is in the European Union, the database backup is taken every 6 hours and local copies are kept for 30 days, API access is authorised with OAuth2, field-level audit logging is kept, and your CRM data sits in a separate database that belongs to you. - Will our stock stay in sync with the CRM? | We do not promise real-time stock synchronisation. Authority over the stock record stays on the ERP side; the scope and frequency of the stock information moved into the CRM, and which fields it will include, are defined during discovery. We have written the reason, and what can be done instead, in the limits section on our integrations page. - Can we issue an e-invoice from the CRM? | No. Rapitek CRM does not issue e-Invoice or e-Archive documents and is not a GİB special integrator; fields such as ETTN or GİB status do not exist in the product. Your invoices continue to be issued in your current setup; the invoice number, date and amount can be carried onto the customer record as fields. - Does it replace Oracle? | No, and we do not recommend that it should. The ERP stays on the accounting, stock, order and official document side; Rapitek CRM takes the pre-sales process: the lead, the meeting history, the quote process, the reason for a loss and sales reporting. The job of the integration is to connect these two sides with a defined flow. - Will synchronisation be real time? | It depends on the method, and we do not promise “real time” upfront. API and webhook based flows can run close to the event; import/export is periodic. Which flow runs at which frequency sits line by line in the written scope. - How long does the rollout take and what does it cost? | We do not commit to a timeline before discovery. After the discovery call we give you a date, not a range: the dates for the discovery, configuration, data migration, training and go-live steps sit in a written plan. We do not put a figure on this page either, because the price depends on the scope: which product, which access, which objects and which direction. Scope and price are shared in writing. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We have no component in Turkey and we do not offer region selection. This is a transfer abroad under Article 9 of KVKK; we establish its legal basis together during the contract process. Your CRM data is held in a separate database that belongs to you. ##### Related pages - Integrations | An overview of integration: which connection is live today, which ones we build on request, and the reason for the three things we do not promise. - Netsis integration | The same framework applied to a single-product ERP: which direction account, balance, order and invoice information flows. - Security | Everything IT will ask: data location, the sub-processor list, backups, the audit trail and what we do not yet offer. ##### Let us establish which Oracle it is, in 30 minutes Bring your IT manager to the call as well; let us make the distinction together and settle the scope and the method in the same call. Request a demo The scope of the rollout, and any fee for it, is worked out in the discovery call and shared in writing. ### [Petroyağ Customer Story | Rapitek CRM Projects](https://rapitek.com/en/petroyag-customer-story) How a chemicals manufacturer with 800+ customers and 8 dealers connected B2B sales, orders and production planning. Customer story · Chemicals and lubricants #### Petroyağ: B2B sales, orders and production met in one system. An industrial lubricants manufacturer founded in 1993. More than 800 customers, 8 dealers and exports to over 40 countries had made the B2B sales process impossible to track on its own. Let's talk about a similar rollout Other customer stories The company ##### The numbers describe Petroyağ's own scale. - 800+ | Customers - 8 | Dealers - 14 | Industries served - 40+ | Countries exported to The project ##### What was there, what we built, what changed. - The challenge | As a producer of white oils and speciality chemicals, they needed an integrated system to manage customer relationships, track sales processes and coordinate production operations. The complexity of B2B selling called for a central platform. - What we built | The system was configured around the needs of the chemicals industry: customer tracking, order management and production planning were brought into one flow. Custom modules were developed for tracking product specifications and quality standards. - The result | Data duplication was prevented and the efficiency of the system improved. Customer orders became easier to manage, the sales team's productivity rose and B2B processes were simplified. In the customer's own words With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. Ögetay Can Sales Director, Petroyağ ve Kimyasalları San. Tic. A.Ş. Scope ##### What was built in the project? Scope is project-specific; in every rollout it is defined together in the discovery call. Area | What was done - Customer tracking | More than 800 customers and 8 dealers were brought into a single record structure - Order management | The order process was moved onto the sales record - Production planning | Production operations were connected to the same system as sales - Product specifications | Product information fields specific to the chemicals industry were defined - Quality standards | Custom modules were developed for quality tracking - Duplicate records | A structure was put in place to prevent data duplication ##### This project belongs to our Salesforce era This implementation belongs to Rapitek's Salesforce implementation era; afterwards we built our own product, Rapitek CRM. Manufacturing and inventory are today part of the standard installation on our own platform — see the pricing page for detail. ##### What would change if sales and production were on the same screen? In a 30-minute discovery call we'll listen to your B2B sales process and map the scope together. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Moving from Pipedrive: Setup and Migration | Rapitek CRM](https://rapitek.com/en/pipedrive-alternative) Data migration, setup and training when you move from Pipedrive to Rapitek CRM. Quotes, orders and WhatsApp on one record; ERP connections built per project. For teams coming from Pipedrive #### Everything after the deal closes, on the same record If quotes, orders, stock, ERP and support requests pile up in separate places, Rapitek CRM ties them to a single record. We do the setup ourselves; support and training are in Turkish. Request a demo See pricing ##### The short answer We do not compare ourselves with another product on this page. We write down what we do and what we don't do. Our scope starts to make sense at these thresholds: the team has passed 15-20 people, an operation has grown up behind sales (quotes, orders, shipping, stock), WhatsApp traffic has become unmanageable, or the system has to talk to an ERP. We drew these thresholds from our own conversations; they are not measured industry data. Scope ##### What Rapitek CRM does and doesn't do Area Rapitek CRM - Sweet spot | At least 5 users; B2B companies with a sales or field team, sales and operations together - Simplicity | We try to keep it simple, but the scope is wide; during setup we trim the screens around the team's daily flow - Quotes, orders, invoices | They run on the same record - Manufacturing, inventory, work orders | Work order and quality control objects ship with the standard installation; we cannot yet point to a live installation running manufacturing execution - WhatsApp | Inside the product, attached to the customer record - ERP connection | Built per project (Logo, Netsis, SAP, Mikro) - Setup and training | We do the setup; we do not commit to a duration before discovery, and after the discovery call we give you a written date, not a range - Support language | Turkish - Role hierarchy and audit trail | Field-level audit trail, role-based sharing - Ecosystem and partner network | Narrow. We have no app marketplace and no trained partner network — we say so plainly; we build integrations per project Signals ##### If you see these signals, let's talk - Everything after the deal closes happens somewhere else | The quote is in Excel, the order in email, the shipment on WhatsApp. The records sit in the pipeline, but the story ends the moment the deal is won. - The answer you need isn't in the CRM | If “what did this customer order and when, is it in stock, has it been invoiced” gets answered from other systems, the CRM is no longer the company's memory. - WhatsApp traffic lives on personal phones | If every rep writes from their own number, the customer gradually becomes the rep's customer rather than the company's. We have seen this in our own projects. - The team has passed 15-20 people | At that size the question of who sees which record comes up; the product supports role-based sharing and a field-level audit trail. We drew the threshold from our own conversations; it is not a measured figure. ##### When we are not the right product - If your team is under 5 people. Our Sales and Platform tiers require at least 5 users, so we cannot take you on at that size. - If you run sales only. With no operation behind it, our broad scope is a burden rather than a benefit. - If you don't want a setup phase. If you want to configure it yourself today and start using it tomorrow, our model doesn't suit you — we work through discovery, configuration, data migration and training; we do not commit to a duration before discovery, and after the discovery call we give you a date, not a range. - If simplicity is your single most important criterion. We can't match that, and we won't claim we can. - If you are looking for an app marketplace and off-the-shelf add-ons. We have no app marketplace and no trained partner network; integrations are built per project. FAQ ##### About the migration and setup - Can our Pipedrive data be migrated? | Yes. Your persons, organisations, deals and activity records, along with your custom fields, are migrated and duplicates cleaned out. - Will the product be too heavy for our team? | The scope is wide, that's true. But during setup we simplify the screens around the team's daily flow: who sees which field is part of the configuration. Modules you don't use don't get switched on. - How much does Rapitek CRM cost? | Our plans start at 39 USD per user per month (billed annually). The tiers, the minimum number of users per tier and the items priced outside the plan are all on the pricing page — we keep the figures in one place so you never read a different number in two. When you evaluate any quote you receive, put setup, customisation and training next to the licence line. - How long does the migration take? | We do not commit to a duration before discovery. After the discovery call we give you a date, not a range: the schedule, including data migration and training, comes to you in writing. ##### Let's look at your current setup together. Tell us where the work happens after a deal closes. If it's still too early for us, we'll say that too. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [CRM Pricing | Plans and Separately Priced Items | Rapitek CRM](https://rapitek.com/en/pricing) Rapitek CRM pricing: Sales, Platform and Enterprise, per user/month. Pay monthly or save ~20% paying annually. Setup scope and any fee shared in writing. Pricing #### Clear plans, scope defined together. Plan pricing is per user. Pay monthly if you prefer; paying annually makes plan prices about 20% lower. The scope of setup, data migration and training is not the same in every project; we work it out together in the discovery call and, if there is a fee, put it in writing before the work starts. Get a demo and quote Explore the product One unit: per user, per month · paying annually ##### Three tiers. Each one includes the last. - Sales | 39 USD | user/month · annual | Paying monthly: 49 USD · Minimum 5 users · Sales pipeline, activity and task management · Quote generation, price lists and PDF output · Rapi AI assistant — usage draws from your AI credit, purchased separately · REST API, OAuth2 and webhook access open · Module scope is agreed during setup | Book a demo | 39 - Platform | 69 USD | user/month · annual | Paying monthly: 85 USD · Everything in Sales · Marketing, Communication and Operations centres · Role hierarchy, sharing rules and field-level audit trail · There is no call centre on our support line. Your question is answered by the team that builds and develops the product | Demo for your team | 69 - Enterprise | from 119 USD | user/month · annual | Minimum 10 users · From this amount paying annually, from 149 USD paying monthly · Everything in Platform · You run setup and support with the same team: no call centre, the team that builds and develops the product answers · Scope, rollout plan and integrations are defined per project | Let's scope it | 119 Not a tier — a separate starting point ##### If your team is under 5 and you mainly want to gather demand from a single channel. - Inbox | 149 USD | company/month · annual | Paying monthly: 185 USD · Up to 5 users — no per-seat charge · One inbound messaging channel included: WhatsApp or Instagram · Email and the web form are in every plan — they do not count as channels · The Meta Lead Ads connection cannot be set up today · Additional channel, or a second account of the same channel: 49 USD per month · Rapi AI assistant — usage draws from your AI credit, purchased separately · Lead, opportunity and quote run on the same record · REST API and webhook access open · Past 5 people you move to the Sales tier; your records stay exactly as they are · Setup and onboarding are priced separately — scope defined in the discovery call | Book a demo | 149 ##### What is in scope? The plan is a billing template only; module scope is determined during setup. Every plan includes a separate database for your company, and the application routes each request to it. Capability | How it is determined - Sales pipeline and activity management | Enabled during setup with the module list - Sending from your own Gmail | Enabled during setup with the module list - iOS and Android mobile apps | Both live; in every installation - WhatsApp inbox inside the mobile app | The same shared inbox on the phone as on the desktop — included in Inbox, enabled during setup on the tiers. Instagram direct messages land in the same inbox. - Custom fields, objects and validation rules | Configurable — we do the setup - Report builder (tabular, summary, matrix) | Enabled during setup with the module list - WhatsApp shared inbox | Included in Inbox; enabled during setup on the tiers. Email and the web form are in every plan as well, and do not count as channels. - Rapi voice AI assistant (in the mobile app) | On every plan; usage draws from your AI credit, which is purchased separately, and must be enabled on your account - Sales sequences and approval processes | The objects ship with the standard installation and are configured together during setup; today we cannot show you the sequence and the approval flow on a live installation. - Inventory and stock management | The objects ship with the standard installation; today we cannot show you stock movement on a live installation. - Work orders and quality control | The objects ship with the standard installation; today we cannot show you production execution on a live installation. - Production planning (MRP, bill-of-materials explosion) | Optional — 25 USD per user per month - Field sales: route plans and mobile visit records | Optional — 25 USD per user per month - Webhooks and full API access | Open on every plan — not restricted on the entry tier - CPQ quoting and pricing | Enabled during setup with the module list - AI meeting capture and notes | Enabled during setup with the module list; usage draws from your AI credit - İYS consent management and campaign sending | Enabled during setup with the module list - Seat (user) limit | Inbox is capped at 5 users; Sales, Platform and Enterprise are priced per user - Support | There is no call centre. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity No hidden costs — what sits outside the plan ##### Priced separately Everything outside the plan price is listed here. After the discovery call you receive all of it in writing. Item | How it is priced - Setup, data migration and training | Scope is worked out together in the discovery call and the cost is put in writing before the work starts. On Inbox, setup is a separately priced item; on the other plans it varies with scope. We do not publish a single figure because no two projects take the same effort. - Additional inbound channel (Inbox plan) | 49 USD per month for each additional channel, or for each additional account of the same channel - Production and warehouse | 25 USD per user per month: bill of materials, multi-level cost explosion and production planning (MRP) - Field sales | 25 USD per user per month: route plans by territory and date, the rep's visit list on the phone, visit records with the check-in location, and quoting from the price list in the field that converts to an order. No automatic route optimisation and no continuous location tracking. - Rapi AI credit | Not included in the plan price; purchased separately. The credit balance is loaded onto your account and usage draws from it: the Rapi assistant, AI meeting capture and the business-card scanner. The balance and its renewal scope are agreed together in the discovery call. It must be enabled on your account. - ERP and accounting integration | Not an off-the-shelf connector. Built per project over REST API, OAuth2, webhooks and import/export; scope and cost are shared in writing. - Out-of-scope development | Work that falls outside the setup scope is priced separately. You see the scope and the cost in writing before the work starts. As a newly established company aiming to make rapid progress, we realized we needed an overall infrastructure for sales management, team tracking, and inventory management. With that need, we started the project with Rapitek, and we are still continuing our work together today. Rapitek is truly a solution partner. Ceren Karaman Operations Manager, Hürriyet Projeland — from our CRM implementation projects The reference above relates to CRM implementation and integration projects carried out by Rapitek; it does not mean that the organisation named uses the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### See the 12-month return before you decide Enter your figures and the calculator shows what the first year looks like. Every assumption is visible and editable — if the result does not convince you, change the assumption and look again. Open the ROI Calculator No signup, no email required. ##### About pricing. - How much does Rapitek CRM cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. These prices apply when paying annually; paying monthly, Sales is 49 USD, Platform 85 USD and Enterprise from 149 USD. Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month paying annually, 185 USD paying monthly. - Do you charge a setup fee? | It depends. The scope of setup, data migration and training is not the same in every project: how prepared your data is, how much customisation is needed and how wide the integration work runs all vary from project to project. That is why we do not put a single number on this page. We work the scope out together in the discovery call and, if there is a fee, put it in writing before the work starts. Nothing appears later as a surprise; whatever will be charged, you see it in writing first. - Are there hidden costs? | No — but we also do not claim "everything included", which is a different thing. What sits outside the plan price is listed one by one in the table above: setup scope, extra channels on Inbox, production and warehouse modules, the field sales module, the Rapi AI credit, ERP integration and out-of-scope development. All of these reach you in writing after the discovery call. - Can we pay monthly? | Yes, there are two options. Paying annually, the subscription is invoiced in advance for a one-year term and plan prices are about 20% lower. Paying monthly, we invoice every month. Setup, data migration and training, if any, are a separate item from the subscription; the payment plan and terms are set out in the written quote. Details are in the Payment Terms section of our Terms of Service. - Can I change my plan later? | Yes. You can upgrade or downgrade and the change applies immediately. You can add users during the term. Moving from Inbox to a seat-based tier leaves your records exactly as they are. - Can we try it before buying? | There is no trial you start yourself. We begin with a 30-minute live demo; afterwards, if you would like to explore the product at your own pace, we open a time-limited demo account for you. In the demo we show the product live on your own scenario: we define the scope together and answer your questions. The call carries no obligation to buy. - Why is there a minimum user requirement? | The effort of a setup does not shrink as the team gets smaller: fields, stages, roles and reports have to be set up once, however many people end up using them. That is why Sales and Platform require at least 5 users, Enterprise at least 10. If your team is under 5 and you mainly want to gather demand coming from a single channel, Inbox exists for exactly that: it is priced per company, not per seat. ##### Let's talk numbers with your own team. Tell us your user count, team structure and integration needs, and we'll map out a clear scope together. Get a demo and quote Starts with a 30-minute discovery call · No obligation · The call is held in Turkish ### [Privacy Policy | Rapitek CRM](https://rapitek.com/en/privacy) Rapitek CRM privacy policy: what data we process, where it is stored (EU/Finland), AI processing, biometric voiceprints and your rights under GDPR and KVKK. Legal #### Privacy Policy Last updated: September 26, 2026 ##### On this page At Rapitek CRM, we take your privacy seriously. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website or use our services. ##### 1. Information We Collect ###### Personal Information We may collect personal information that you provide directly to us, such as: - Name and contact information (email address, phone number) - Company name and job title - Billing and payment information - Account credentials - Communications you send to us - Voice recordings and, only if you enable it, your biometric voiceprint (see Section 11) - Meeting audio you choose to record, and the transcripts derived from it - Messages, comments and attachments exchanged through connected channels such as WhatsApp and Instagram (see Section 12) - Photographs you upload, including scanned business card images - Your approximate or precise location when you check in to a visit from the mobile app ###### Automatically Collected Information We never measure how long you spend on our pages. If you accept the cookie banner, we record the pages you visit in that session, the page language, the site that referred you, and the time of your visit on our website's server, linked to the rgo_oturum measurement cookie (a random identifier); if you don't accept, no such record is created, and you can withdraw your consent at any time. This browsing record is deleted after 90 days. If you submit a form on our site while the consent you gave in the cookie banner is in effect, a short summary of your browsing (at most 50 steps) is saved with your enquiry, and that summary is not deleted after 90 days: on our site it is kept with your enquiry for 24 months from the date the form was submitted, and its copy in our customer relationship management (CRM) system is kept there together with your enquiry record for as long as that record exists. Our website's server also keeps technical access logs for security and troubleshooting: for normal requests, only the last segment of your IP address is truncated (the last octet for IPv4, all but the first three groups for IPv6) — kept for at most 15 days together with the requested address, the referring site, your browser information, the status code and duration. If a request errors, that request's log entry keeps your IP address untruncated, also for at most 15 days. Application and security logs (which may contain IP addresses) are kept for security and debugging purposes; on our website's server, these logs are kept for at most 90 days. On the servers of the Rapitek CRM application, server access and error logs (which contain full IP addresses) are kept for at most 365 days and API usage records (which contain IP addresses) for at most 400 days; no automatic deletion period is yet applied to application error and login records (which may contain IP addresses). Records matching a security incident (an attack, harassment or a threat) are additionally kept as evidence, as a copy. This copy is not subject to the automatic periods above; it is kept for as long as the investigation and any legal proceedings require, and deleted when it is no longer needed. We do not use Google Analytics or any other third-party analytics, advertising or remarketing cookies. ###### Special Categories of Personal Data The only special-category (sensitive) personal data Rapitek processes is the biometric voiceprint described in Section 11, and only where you have given separate, explicit consent. Beyond that, Rapitek does not need health, religious, political, trade-union, sex-life, criminal-record or similar sensitive data in order to deliver the service, and we strongly ask that you do not enter such data into free-text CRM fields. ##### 2. How We Use Your Information We use the information we collect to: - Provide, maintain, and improve our services - Process transactions and send related information - Send you technical notices and support messages - Respond to your comments and questions - Send marketing communications (with your consent) - Monitor and analyze trends and usage - Detect and prevent fraudulent transactions - Comply with legal obligations ##### 3. Information Sharing and Disclosure We do not sell, trade, or rent your personal information to third parties. We may share your information only in the following situations: - With your consent - With service providers who assist in our operations - To comply with legal obligations - To protect our rights and prevent fraud - In connection with a business transfer or merger - With the AI, email and messaging service providers named explicitly in Section 13, processing only on our instructions and on our behalf ##### 4. Data Security We implement appropriate technical and organizational security measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security. ##### 5. Data Retention We retain your personal information for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law. ##### 6. Your Rights Depending on your location, you may have the following rights regarding your personal information: - Access and receive a copy of your personal information - Correct or update your personal information - Delete your personal information - Object to or restrict processing of your personal information - Data portability - Withdraw consent ##### 7. Cookies and Tracking Technologies We use cookies and similar tracking technologies to track activity on our website and hold certain information. You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. See our Cookie Policy for details. Measurement in e-mails. In the e-mails we send you, we measure whether the message is opened and whether the links inside it are clicked. To do this a small invisible image is placed in the message and links are routed through our measurement address; in the process the time of opening, your IP address and information about the e-mail program you use are recorded. This processing rests on our legitimate interest under article 5(2)(f) of Law No. 6698. For details and how to reach us, see our KVKK Privacy Notice. E-mails sent by our customers. The same measurement runs when a business using Rapitek CRM e-mails its own customers. In that case the data controller is that business; Rapitek acts as a data processor. If you received an e-mail from such a business, you should direct any request about this measurement to that business. ##### 8. International Data Transfers Your information may be transferred to and maintained on servers located outside of your state, province, country, or other governmental jurisdiction where data protection laws may differ from those in your jurisdiction. Our infrastructure is within the European Union and consists of three separate locations: the application and the database are in Helsinki (Finland), the files you upload (attachments, images and any meeting audio you choose to record) are in Frankfurt (Germany), and database backups are in Falkenstein (Germany). The specific recipients, the countries they operate in, and the legal basis for each transfer are set out in detail in Section 13. ##### 9. Children's Privacy Our services are not intended for individuals under the age of 18. We do not knowingly collect personal information from children under 18. ##### 10. Mobile Application The Rapitek mobile app accesses, with your permission: location (while-in-use only, for visit check-in and showing nearby records — never tracked in the background), camera (to scan business cards and barcodes), microphone (to record voice notes and to record meetings you choose to record), photo library (to attach card images), and your phone's contacts (only to WRITE a lead you pick into your address book — your address book is never read and never uploaded to our servers). The app also registers a push notification token so your company's CRM can alert you. This data is processed solely within your company's CRM account, encrypted in transit (HTTPS/TLS), never sold to third parties, and deletable on request. The app requires a Rapitek account provided by your company. Meeting recording and voice notes. Audio you record is uploaded to your company's CRM account and transcribed on Rapitek's own servers — the audio file itself is never sent to any AI provider. As a file, it is held with the storage provider named in Section 13 (DigitalOcean Spaces, Frankfurt / Germany), in the space allocated to your company. What happens to the resulting text is described in Section 13. You are responsible for obtaining the consent of everyone present before recording a meeting. If you are considering enabling the optional voice profile feature, please read Section 11 — that feature processes biometric data. ##### 11. Biometric Voice Profile (Voiceprint) This feature is optional, off by default, and is never required in order to use Rapitek. Only if you turn the feature on yourself in the mobile app (Profile → My Voice Profile), Rapitek records a roughly 30-second sample of you speaking and derives a voiceprint from it: a numeric representation of your voice (a vector of about 192 values). The voiceprint's sole purpose is to let meeting analytics tell your speech apart from everyone else's, so it can measure how much of a meeting you spoke versus the other side. What happens to the raw clip. The 30-second clip is uploaded over an encrypted connection and used once to compute the voiceprint. The raw voice recording taken to create the voiceprint is deleted immediately after it has been processed (the version copy at the storage provider is removed within 30 days at most); if processing is interrupted, the recording may remain until it is deleted separately. The only thing kept permanently is the voiceprint itself, stored encrypted at rest. The raw clip is never used to train any AI model and is never shared with any third party. Whose voice. A voiceprint is only ever created for the person who enabled the feature, from their own account and their own voice. We do not create or store a voiceprint for anyone else in a meeting — other speakers' audio is compared segment by segment during the analysis and discarded immediately afterwards. Legal basis. A voiceprint is biometric data and constitutes a special category of personal data under Article 6 of Turkish Personal Data Protection Law No. 6698 (KVKK) and Article 9 of the GDPR. We process it solely on the basis of the data subject's explicit consent. That consent is given by ticking a dedicated, purpose-specific box in the app before any recording starts; it is not bundled into acceptance of the general terms or any other permission. The consent is recorded with a version number and a timestamp. Withdrawing consent and deletion. You can withdraw your consent at any time, without giving a reason and with no adverse effect on your use of the product: in the mobile app, go to Profile → My Voice Profile → Delete my voice profile. When you withdraw your consent, when your user account is closed or when your account is scheduled for deletion, your voiceprint is deleted from the live system immediately and irreversibly; it is deleted from backup copies when those backups are deleted (backup retention periods and their exceptions are set out on our security page). Once consent is withdrawn, meeting analytics falls back to an approximate mode that uses no biometric data at all, and the rest of the feature keeps working. You can also request deletion through the contact details in Section 16 or via our data deletion page. Retention. The voiceprint is kept only while your explicit consent stands and your account is active. It is deleted from the live system when you withdraw consent, when your account is closed or when your account is scheduled for deletion — whichever happens first; it is deleted from backup copies when those backups are deleted. If we discontinue the feature, we will also delete voiceprints from the live system. The voiceprint is never transferred to any AI provider, any advertising network or any third party; it never leaves your company's own database. ##### 12. Instagram and Connected Messaging Channels Rapitek's shared inbox connects to messaging channels on behalf of the business that uses it. When a business connects its WhatsApp Business number or its Instagram professional account, Rapitek receives and stores the following, inside that business's own CRM account only: - direct messages exchanged with the account, and any photos, voice notes, videos, documents and locations sent in them - public comments on the account's Instagram posts, and the replies made to them - the sender's platform identifier, public username or display name, and profile picture. For Instagram this identifier is a page-scoped ID — it is not a phone number and it does not include your Instagram password or login details - delivery, read and timestamp metadata For this content Rapitek acts as the data processor; the business operating the account is the data controller and decides why the data is kept and for how long. Message and comment content is not used for advertising, is not sold, and is not used to train AI models. Instagram data reaches us through Meta's official Graph API, within the permissions the business granted when connecting the account, and the business can disconnect it at any time from the Setup screen, which stops all further processing immediately. If you messaged a Rapitek customer on Instagram or WhatsApp and want your messages deleted, you need to contact that business directly. If you messaged Rapitek's own account, use the contact details in Section 16 or our data deletion page. ##### 13. AI Processing and Transfers Abroad Some Rapitek features are powered by large language models. When those features are used, only the content needed for that specific task leaves our servers and is processed by the provider named explicitly below: - Rapi, the in-CRM assistant — the text of your request, or its speech-to-text transcription, together with the CRM records needed to answer it, is sent to Anthropic PBC (United States). - Business card scanning — the photo of the card you scan is sent to Anthropic PBC (United States) so the contact details on it can be read. - Meeting summaries and coaching notes — the audio is transcribed on Rapitek's own servers; the audio file itself is never sent to any AI provider. Only the resulting text transcript and the computed statistics are sent to Anthropic PBC (United States). - Your voiceprint is never sent to any AI provider. It is encrypted at the application level and stays inside your company's own database. Anthropic processes this content for one purpose only — returning the result to us. Under Anthropic's commercial terms of use, content sent through the API is not used to train their models — this rests on the provider's own publicly available commercial terms and is accurate as of August 2026. We do not use OpenAI or any other model provider for these features. The other sub-processors we rely on to provide the service, and the countries they operate in: - Cloudflare, Inc. — content delivery network, TLS termination, web application firewall and bot protection; the edge server nearest the visitor, company headquartered in the United States. No content is stored there; connection traffic and the visitor's IP are processed at that layer. - Hetzner Online GmbH — application server and database hosting; Helsinki / Finland (European Union). - Hetzner Storage Box — storage of database backups; Falkenstein / Germany (European Union). - DigitalOcean Spaces — storage of the files you upload (attachments, images and any meeting audio you choose to record); Frankfurt / Germany (European Union). A separate storage space is used for each customer. - Amazon Web Services (Simple Email Service) — delivery of outbound email; Frankfurt / Germany (European Union). - Sentry — application error monitoring; Germany (European Union). It is configured with personal data transmission switched off. - Meta Platforms (United States / Ireland) — the WhatsApp Business and Instagram channels described in Section 12. - Google LLC (United States) — the Gmail (sending) and Google Calendar (reading, creating, updating and deleting events) connection described in Section 14, only when a user connects their own Google account. This is Section 8 in concrete terms. For data subjects located in Türkiye, these operations constitute a transfer of personal data abroad within the meaning of Article 9 of Law No. 6698, and there is no adequacy decision issued by the Board for the countries to which the transfer is made. For data subjects in the European Economic Area, transfers to the United States are made under the European Commission's Standard Contractual Clauses. As stated in Section 3, we do not sell, trade or rent your personal information; the providers named here process it only on our instructions. ##### 14. Google Workspace Data (Gmail and Google Calendar) Rapitek lets a user connect their own Google account so that the CRM can act on their behalf. The connection is made through Google OAuth: Rapitek never sees, receives or stores your Google password. A user connects only their own Google account. Rapitek reads and writes events only in that account's primary calendar and does not access the user's other calendars; connecting one account gives Rapitek no access to any other person's Google account. When a Google account is connected, Rapitek requests these permissions and no others: - Send email on your behalf (gmail.send) — to send quotes, follow-ups and campaign messages that you compose in Rapitek from your own address, so that replies come back to you. Rapitek never sends without an action you started or a campaign you configured yourself. - See and download your calendars (calendar.readonly) — to show your meetings on the timeline of the matching customer record, and to check your availability when scheduling. - View and edit events on your calendars (calendar.events) — to let you create, update or delete calendar events (for example, customer meetings) from inside Rapitek so that the change is reflected in the primary calendar of your own connected Google account. Deleting an event in Rapitek also deletes it from that Google calendar; marking a meeting as cancelled in Rapitek does not change it in Google. When an event has guests, Google may email them an invitation, update or cancellation; Rapitek does not send update or cancellation notices for events that have already taken place. - Your email address and basic profile (userinfo.email, userinfo.profile) — to identify which mailbox was connected and to show it back to you. Events in the connected primary calendar within a limited time window (30 days back, 90 days ahead), including invitations received from other people, are copied into Rapitek (title, start and end time, description and location). Attendee, organizer and creator email addresses are used only to link an event to a matching Rapitek user, lead or contact and are not stored as separate fields. Copied events are visible to other users in your Rapitek organization only as permitted by its sharing and permission settings. When a lead or contact is attached to a meeting in Rapitek, that person's email address is sent to Google as an attendee. Rapitek does not request permission to read the contents of your Gmail mailbox. Where an account was granted mailbox reading separately and explicitly, incoming and outgoing mail is recorded on the matching customer record inside that organisation's own CRM account; where it was not granted, Rapitek has no technical ability to read your messages at all. Access and refresh tokens are stored encrypted, inside the separate database belonging to the customer organisation whose CRM account you use. Calendar events and messages copied into the CRM are visible only within that organisation's own CRM account and are subject to its own sharing rules. For this content the organisation operating the CRM account is the data controller and Rapitek acts as the data processor. If you use Rapi, our in-app AI assistant, it may read email messages and calendar events that were copied into the CRM from your connected Google account — such as subject, sender and recipients (including Cc/Bcc), dates, labels, the first 500 characters of the message body (plain-text and HTML versions), and event title, time, location and description — and send them to Anthropic PBC (see Section 13) only as needed to answer a request you make to Rapi. Rapitek's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically: data obtained through these scopes is used only to provide and improve the user-facing features described above; it is never sold, and never transferred to advertising platforms, data brokers or information resellers; it is not used for advertising; it is not used to train generalised artificial intelligence or machine-learning models; and it is not read by our staff except with your explicit permission, for security purposes such as investigating abuse, to comply with applicable law, or in aggregated and anonymised form for internal operations. You can disconnect a Google account at any time from the Setup screen in Rapitek. Disconnecting stops all further access by Rapitek — no further mail is sent and no further calendar data is read. Because disconnecting inside Rapitek does not by itself withdraw the permission you granted at Google, we recommend that you also remove Rapitek from your Google Account permissions page. To have data that was already copied into a CRM account deleted, contact the organisation that operates that account, or use the contact details in Section 16 and our data deletion page. ##### 15. Changes to This Privacy Policy We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the 'Last updated' date. ##### 16. Contact Us If you have any questions about this Privacy Policy, please contact us: Rapitek Bilişim Teknolojileri A.Ş. Maslak Mah. Büyükdere Cad. Nurol Plaza 255, B02 34485 Sarıyer / Istanbul, Turkey E-mail: info@rapitek.com FAQ ##### Frequently asked privacy questions - What personal data does Rapitek collect? | Information you give us directly: your name and contact details, company name and job title, billing and payment information, account credentials, communications you send us, photographs you upload (including scanned business cards), meeting audio you choose to record and its transcripts, messages, comments and attachments exchanged through connected WhatsApp and Instagram channels, and your approximate or precise location when you check in to a visit from the mobile app. If you accept cookies, we log pages visited, referrer and visit time; else no such record exists; time-on-page is never measured. The only special-category data we process is the biometric voiceprint, and only if you enable it yourself; we ask you not to enter health, religious or political data into free-text CRM fields. - Where is my data stored? | Our infrastructure is in the European Union and consists of three locations: the application and the database in Helsinki (Finland), the files you upload in Frankfurt (Germany), and database backups in Falkenstein (Germany). Outbound email is delivered through Amazon Web Services (Simple Email Service) in the Frankfurt region, also in the European Union. The specific recipients, the countries they operate in and the legal basis for each transfer are set out in detail in Section 13 of the policy. - Is my data transferred abroad, and to whom? | With the AI-powered features, only the content needed for that task leaves our servers: the text of your request to Rapi and the CRM records needed to answer it, the photo of a business card you scan, and a meeting transcript with its statistics — sent to Anthropic PBC (United States). Meeting audio is transcribed on our own servers and the audio file itself is never sent to any AI provider; as a file it is held with DigitalOcean Spaces (Frankfurt), named in Section 13. Your voiceprint is never sent to any AI provider either. For data subjects in Türkiye this is a transfer abroad under Article 9 of Law No. 6698, with no adequacy decision from the Board; for the EEA, US transfers use the Standard Contractual Clauses. Full list in Section 13. - What is the biometric voiceprint, is it required, and how do I delete it? | The voice profile feature is optional, off by default, and never required to use Rapitek. Only if you turn it on yourself (Profile → My Voice Profile) does Rapitek record a roughly 30-second sample and derive a voiceprint: a vector of about 192 values whose sole purpose is to let meeting analytics tell your speech apart from everyone else's. The raw clip is used once and deleted immediately unless processing is interrupted; the only thing kept permanently is the voiceprint, stored encrypted. A voiceprint is special-category biometric data under Article 6 of Law No. 6698 and Article 9 of the GDPR, processed solely on the explicit consent you give through a dedicated checkbox before any recording starts. You can withdraw it at any time: Profile → My Voice Profile → Delete my voice profile. - What happens to the messages I send through WhatsApp or Instagram? | When a business connects its WhatsApp Business number or Instagram professional account, Rapitek stores the following inside that business's own CRM account only: direct messages and any photos, voice notes, videos, documents and locations in them; public comments on the account's Instagram posts and the replies; the sender's platform identifier, username and profile picture; and delivery, read and timestamp metadata. For Instagram that identifier is a page-scoped ID — not a phone number. Here Rapitek is the data processor, while the business operating the account is the data controller and decides why and how long data is kept. Content is not used for advertising, not sold, and not used to train AI models. - What rights do I have over my personal data and how do I exercise them? | Depending on your location you may have the right to access your personal information and receive a copy of it, to correct or update it, to have it deleted, to object to or restrict its processing, to data portability, and to withdraw consent you previously gave. If you are located in the European Union or Türkiye you have additional rights under the GDPR and Türkiye's data protection law (KVKK, Law No. 6698). To exercise your rights or ask for more information, reach us through our contact form; for deletion requests you can use our Data Deletion Instructions page. Our company name and postal address are given in Section 16 of the policy. ##### For EU and Turkish Residents If you are located in the European Union or Turkey, you have additional rights under the GDPR and Turkey's data protection law (KVKK, Law No. 6698). For more information or to exercise your rights, please reach us through our contact form; for deletion requests you can use our Data Deletion Instructions page. ### [CRM Features and Modules | Rapitek CRM](https://rapitek.com/en/product) Rapitek CRM features: sales pipeline, quote and case management, WhatsApp shared inbox, reports, mobile app, and a REST API covering every standard-install object. Product #### Everything you need in a CRM. Sales, marketing, customer service, and operations on the same data model. We built the product around the needs we ran into on the enterprise CRM projects we delivered during our Salesforce years. Request a demo See pricing ##### Four hubs, one platform. - Sales Hub | Sales pipeline and Kanban, lead, opportunity, and activity management, quote generation — including price lists, discounts, PDF output, and conversion to orders; quote-to-order conversion runs through the product's own conversion action. Case management runs in this hub as well. - Marketing Hub | Campaign management, WhatsApp campaigns, and commercial-message consent management. If you connect your own İYS account (Turkey's national consent registry) via Verimor, SMS, call and e-mail consents and opt-outs go to İYS, and those made in İYS come back to the CRM; WhatsApp is outside this sync. The Meta Lead Ads connection cannot be set up today; there is no out-of-the-box ad-form module. - Communications | WhatsApp, email, and SMS conversations land in a single shared inbox; campaigns and message templates are managed here. Instagram direct messages land in the same inbox; campaigns and templates do not cover Instagram. - Operations Hub | Bill of materials, multi-level cost roll-up, production line and work order screens are in the product; the production and warehouse side is an optional add-on module. We cannot point to a customer reference for work order execution today — and we don't sell what we can't demonstrate. - AI assistant | In the mobile app, Rapi creates and updates CRM records by speaking Turkish; the business-card scanner also runs in the mobile app. It can be set to ask for confirmation before saving risky changes. The call is yours: Rapi is off by default — unless you turn it on, your CRM data is never sent to any AI provider. Details on the Security page. - Platform controls | Two-factor authentication (email code or authenticator), OAuth2, a field-level audit trail, and a recycle bin. Role hierarchy and record sharing rules are supported; we define them together during setup. When the hubs reach your work ##### The Monday after go-live: what changes in each hub These scenes come from what the product does today. We do not publish a number for how many customers work this way. Hub | What goes missing today | The Monday after go-live - Sales Hub | The rep leaves a visit meaning to write the note that evening; when it never gets written, nobody's screen shows where the opportunity stands. And whoever prepares the quote does not know the customer's overdue balance. | The note goes in from the car, spoken into the phone as soon as the meeting ends: Rapi writes the record and opens the follow-up task. When a quote is prepared, the customer's overdue balance sits on the same screen — once the ERP connection is in place; no call to accounting. - Marketing Hub | Bulk commercial messages go out from a list someone keeps by hand; if a number on it has opted out, that does not show up before the send. | If you have connected your own İYS account through Verimor, opt-outs the recipient makes directly in İYS are checked every 6 hours and can take up to a day to reach the CRM; once they arrive they land on a local suppression list, and no commercial message goes to that recipient. Informational messages are not affected by this restriction. - Communications | The customer writes to the rep's personal phone; when that person goes on leave the conversation stalls, and when they leave the company the message history goes with them. | The message lands on the company's single business number and the conversation is attached to the customer record. When the rep changes, the conversation is handed over with an internal note; the customer never notices the handover — they are always writing to the same number. - Operations Hub | The bill of materials sits in one spreadsheet and the cost calculation in another file; when a quote goes out, the two never meet. | The bill of materials and multi-level cost roll-up sit on the same data model as the customer and quote records; you do not open a separate file to look at cost. The production and warehouse side is an optional add-on module, scoped at discovery. Sales pipeline #### Every lead, on one screen. Who's interested, what stage they're at, where they came from, who owns them — all in one list. Instead of chasing who's tracking what across a scattered team, you see the whole pipeline at a glance. The channel a record came from sits in the source field; channel-level reporting is produced from that field. ##### What is Rapitek CRM? Rapitek CRM is a cloud-based customer relationship management (CRM) application built and operated in Istanbul by Rapitek Bilişim. Founded in 2018, Rapitek helps sales, marketing, and customer service teams manage leads, contacts, accounts, opportunities, quotes, invoices, and customer communication on a single platform. What it connects to is listed on our integrations page, and how it is set up per industry on our industries page. Each customer gets its own separate database — separation at the database level, not a row filter in a shared table. Your data is hosted in the European Union: the database in Helsinki, files in Frankfurt, backups in Falkenstein. A few sub-processors operate outside the EU; we name each one and say where it processes data in our privacy policy. Seen from Turkey, this counts as an international data transfer under Article 9 of KVKK, Turkey's data protection law (No. 6698); we establish the basis for that transfer together during the contract process. For the customer data you enter into your CRM, you are the data controller and Rapitek is the processor — the obligation to establish that basis sits with the controller, that is, with you. The technical measures are listed one by one on our security page. Salesforce experience, independent consulting. Our team delivered enterprise implementation projects in the Salesforce ecosystem; that period has ended, and we hold no official partnership today. We provide independent consulting on performance tuning, data migration, integration, and security reviews. For official partnership benefits, you would need to talk to Salesforce directly. We wrote that history out in full on our about page. ##### Your data, under your control. Area Rapitek CRM - Data separation | A separate database that belongs to your company — the application routes each request to your company's database based on the web address it arrives at - Data location | European Union — database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany) - Customization | Fields, objects, flows, and page layouts are configurable without code — we do the setup - Setup and training | Scope and any fee agreed in writing at discovery - Support | From the team that builds and runs the product. We do not commit to a written response time (SLA) - Data ownership | Export your data and take it with you; we charge nothing for the export when you leave ##### What it connects to There is no out-of-the-box connector for ERP and accounting; they are built per project by the team that builds and runs the product, over REST API and webhooks. Area | Scope - Email | You connect your own Gmail account over OAuth; the connection covers sending email and calendar sync, not two-way inbox sync — inbox reading is switched off. Outlook and Microsoft 365 connections are not live. Generic IMAP/SMTP is not supported - Calendar | Two-way appointment and event sync with Google Calendar; calendar sync is Google-only — Outlook and Microsoft 365 connections are not live - Messaging | Two-way shared inbox via the WhatsApp Business Cloud API; you connect your own WhatsApp Business account - Ad forms | The Meta Lead Ads connection cannot be set up today. There is no out-of-the-box ad-form module; leads from forms you host yourself can be posted to the CRM with their source tagged, over REST API or a signed webhook - ERP and accounting | Connected per project by the team that builds and runs the product, over REST API, OAuth2, webhooks and import/export - API | REST API covering the 183 business objects that ship in a standard install, OAuth2/JWT, rate limiting, and usage analytics - Mobile | iOS and Android apps are both live, with a Turkish interface; push notifications are sent. GPS visit check-in is supported; we define it together during setup. WhatsApp and Instagram conversations are handled in the single in-app shared inbox - Currency | Multi-currency; automatic daily conversion using Turkish central bank (TCMB) rates ##### What each plan covers, on one page Three tiers, a scope table and separately priced items — with the numbers. We do not put prices on this page, so you never read two different figures for the same thing. See pricing Scope and any setup fee come out of the discovery call. ##### Product questions, answered. - Can we customize the system ourselves? | Fields, objects, sales stages, page layouts, and automation flows are all configured from the admin panel — no code required. But let's be honest: setting up a CRM well takes knowing what to configure and how, and that is a specialty of its own. That's why we do the setup — you don't need to hire a CRM administrator. The scope of setup, and any fee for it, is worked out in the discovery call and put in writing before the work starts. After go-live, your team comfortably handles day-to-day changes (adding a field, building a report, renaming a stage); for deeper changes, we're there. - Which modules does Rapitek CRM include? | Four hubs: Sales, Marketing, Communications, and Operations. Sales covers the pipeline, quotes, and orders; case management runs there too. Marketing covers campaigns and commercial-message consent. Communications brings WhatsApp, Instagram, email, and SMS into one shared inbox. Operations has bill of materials, cost roll-up, production line and work order screens; the production and warehouse side is an optional add-on module. We cannot point to a reference for work order execution today, and we don't sell what we can't demonstrate. We have no separate customer or dealer portal product: a portal user signs in like any other user, differing only in permissions. - Does it integrate with our existing ERP? | We don't offer an out-of-the-box ERP connector — we say that plainly. Integrations are built per project by the team that builds and runs the product, through our REST API — which covers the 183 business objects that ship in a standard install — OAuth2, webhooks and import/export. We have worked alongside teams running Logo, Netsis, Mikro, and SAP in enterprise projects; we define the scope and cost in the discovery call and put it in writing. - How do email and calendar connect? | You connect your own Gmail account over OAuth. The connection covers sending email and calendar sync; it is not two-way inbox sync — inbox reading is switched off, so we do not read your inbox. Email you send from the CRM is linked to the related customer or lead record. Generic IMAP/SMTP is not supported. Outlook and Microsoft 365 connections are not live, so there is no Microsoft email or Outlook calendar sync. Google Calendar sync works two ways: fetching, creating, updating, and deleting events. - Can I manage multiple business units in one CRM? | Yes. Rapitek CRM supports multiple sales processes; you can run different business units, sectors, or product lines inside a single CRM. Each process gets its own stages, automations, and reporting. - What exactly does the AI do? | Rapi, the voice assistant, works in the mobile app: speaking Turkish, it fetches, creates, and updates core records such as leads, contacts, accounts, and opportunities. For risky changes — money fields, closing statuses, deletions — it can be set to ask for your confirmation before saving; that setting can also be widened to cover every operation. Every field it changes on existing records lands in the product's field-level change history; the initial values of a record it creates are not recorded there. The business-card scanner that turns a photo into a lead runs in the mobile app. You can add an AI step to the visual flow designer. Rapi is off by default: unless you turn it on, your CRM data is never sent to any AI provider. - Is there a mobile app? | Yes — both of them. The iOS and Android apps are live on the App Store and Google Play, with a Turkish interface. Field teams see the same pipeline on their phone, with GPS visit check-in and push notifications. One difference worth naming: WhatsApp conversations are handled inside the app, in the same shared inbox, so a field rep can answer without going back to the office. Instagram direct messages land in the same inbox; replying to them from the mobile app has not yet been measured in a customer deployment. - Is there multi-currency support? | Yes. You set your base currency and create quotes and opportunities in different currencies. The system automatically pulls daily exchange rates from Turkey's central bank (TCMB) and converts using the rate on the record's date. Price lists let you keep product catalogs in multiple currencies. - Who provides support? | There is no call center on our support line. Your question is answered by the team that builds and runs the product — that is a choice, not a matter of capacity. You talk directly to the team that did your setup; support and training are in Turkish. We do not commit to a written response time (SLA) — we listed that, and the other items we do not offer, one by one on our security page. ##### See all of it with your own data. There is no trial you start on your own. We begin with a 30-minute live demo; afterwards, if you want to explore at your own pace, we open a time-limited demo account for you. We prepare the demo around your own use cases. Request a demo The demo is free and carries no obligation. ### [Real Estate CRM: Portfolio & Appointment Tracking | Rapitek](https://rapitek.com/en/real-estate-crm) Property portfolio, client criteria and viewing appointments in one system; branch-based permissions, Google Calendar sync, WhatsApp from one number. Industry solution · Real estate #### CRM for growing real estate agencies Your property portfolio, your client requirements and your agents in one system. Branch-based permissions, viewing-appointment tracking and consolidated reporting — configured around your process, and we do the setup. Request a demo Talk to an industry specialist ##### When the portfolio, the agent and the client request all sit in different places, matching comes down to one person The listing side is already handled by separate software in your office. The place that bleeds is the space between the listing and the client: who was looking for what, which property they saw, why they didn't like it, when to call them back. Here is the picture we have seen again and again in our own CRM projects: - Client criteria (budget, area, number of rooms) sit in the agent's notebook or in the notes on their phone; the office cannot see them. - Conversations stay on the agent's personal WhatsApp number. When the agent leaves, the client history leaves with them. - Viewing appointments get forgotten; a cancelled appointment is not recorded anywhere. - Once the sale closes the relationship goes quiet — asking a happy client for a referral is nobody's job. - When a new branch opens, the offices cannot see each other's portfolio; the manager adds up the consolidated figures by hand in Excel. None of this is solved by a new listings portal. It takes record-keeping discipline and permissions — and that is exactly what a CRM is for. The same structure works the same way outside real estate; the part about correspondence staying with the office rather than on the agent's own phone is set out further down this page. A concrete scenario ##### Saturday, 2:20pm — a buyer calls about one of your listings. - The criteria are recorded as fields during the call | Budget range, target areas, number of rooms and move-in timing go onto the client record as separate fields, not as free-text notes. Information sitting in a free-text note cannot be filtered; written as a field, it can. - Matching properties are filtered on the same screen | The portfolio list is filtered by the criteria that were saved. The agent links the properties of interest to the client record and marks the ones that were ruled out along with the reason — so the next conversation does not start from scratch. - Photos and locations go out from the office's single business number | The conversation is not on the agent's personal phone but in the team inbox. The message history is written to the client record; while an agent is away, someone else can pick the conversation up where it left off. - The viewing appointment is written to the calendar and to the sales pipeline | The appointment is recorded, synced with Google Calendar, and a reminder and a follow-up task are defined. If the viewing did not take place, the opportunity stays at the relevant stage and shows up in the report. - Feedback after the viewing turns into criteria | Once a note such as “the living room felt small, the aspect is good” is saved and the criteria fields are updated, the next match is more accurate. The assessment does not stay in the agent's head. - After closing, the relationship can be put on a schedule | When the sale closes, periodic check-in tasks, a short satisfaction survey and a referral request can be planned. How many referrals came from which client can be tracked as a record. ##### The building blocks we set up for real estate teams - Property records | Every property is its own record: price, square metres, number of rooms, floor, area, status (for sale / to let / under option), images and the responsible agent. The fields are configurable — which ones you actually need is something we decide together during setup. - Criteria-based matching | Because the client's budget, area and room count are held as fields, the portfolio is filtered on those fields and saved as list views. There is no magic here: correctly built fields and correctly built lists. - Viewing appointments | Appointments are recorded and synced with Google Calendar; reminders and post-viewing follow-up tasks are defined. Appointments that did not take place show up in the reports. - Branch and agent permissions | Which branch sees which properties, clients and reports is set on a role basis. The manager looks at the consolidated view, the agent sees their own work. Even if an agent leaves, the records stay with the office. - WhatsApp from a single number | All agents write from the office's single business number; messages land in the team inbox and are written to the client record. The route we recommend and set up is Meta's official WhatsApp Cloud API. We do not offer QR-code phone pairing as a product promise: it is not Meta's official API and risks the number being restricted by Meta; if that happens, your business number goes down. - Area and agent reports | Which area has stock piling up, which price band is in demand, how many viewings and how many closings there are per agent — with tables and summary reports and a drag-and-drop dashboard designer, without writing code. Matrix and joined report types are supported as well. ##### When the agent is out in the field, and connecting to your existing software ###### Mobile in the field Real estate work does not happen at a desk. Both our iOS and Android apps are live and come with a Turkish interface; on the way out of a viewing an agent can update the client record, the note and the follow-up task from their phone. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp messages are handled in the single inbox inside the app — the agent can reply without going back to the office. Instagram direct messages land in the same inbox. You can see the details on the mobile app page, and the product as a whole on the product page. ###### Connecting to your listing and accounting software Rapitek CRM does not replace your listing-publishing software; it adds a customer relationship layer on top of it. The connection to your portfolio or listing tool, to your accounting or ERP program, is built like this: via REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data flows in which direction is defined together during setup. We have collected which systems we connect to and how on the integrations page. There is no out-of-the-box module — saying there is would not be true. Because access differs from one installation to the next, no single button can be built that works the same way in every installation; the connection is a scoped integration job and is planned as part of the setup. We have written out plainly on the pricing page which items are included in the plan price and which are priced separately. Division of labour ##### Listing software or CRM? Both. Rapitek CRM does not replace your listing and portfolio software; it adds the customer relationship layer on top. The data flow between them is built with the API and import/export. Layer | What it does - Listing and portfolio software | Preparing listings, publishing them on portals, listing the portfolio and operational tracking - Rapitek CRM | Client records and requirement criteria, viewing-appointment tracking, the sales pipeline, WhatsApp message history, branch-based permissions and reporting - The connection between them | REST API, OAuth2, webhooks and import/export; the scope is defined during setup with the team that builds and develops the product Verifiable figures ##### Not a marketing line — measured data - 200+ | Enterprise CRM projects delivered during the Salesforce era (before Rapitek CRM) - 277 | Custom fields added by 19 tenants without writing code - Every 6 hours | Automatic backup frequency; backups are copied to a separate country - 183 | Business objects in the REST API — each with a data and a schema endpoint - EU | Data location: Helsinki (Finland), media in Frankfurt, backups in Falkenstein Rollout ##### How is a CRM rolled out in a real estate agency? - Discovery and analysis | We map out your portfolio flow, your agent roles, your branch structure and your commission-sharing model. This is where it is decided which fields you actually need. - Configuration | Property and client fields, pipeline stages, list views, the permission matrix and reports are set up around your process. No code is needed; setting it up well takes expertise, and that part we do. - Data migration | Portfolio and client records from your Excel files or from your existing system are imported; duplicate records are weeded out. - Training and go-live | Training for agents and managers, close follow-up in the first week, then ongoing support. There is no call centre on our support line: the team that builds and develops the product answers you. We do not commit to a timeline before discovery; after that call we give you a date, not a range. From our CRM implementation projects ##### What do the teams we work with say? - As a newly founded company that wanted to make fast progress, we realised we needed a general infrastructure for sales management, team tracking and inventory management. With that need in mind we started the project with Rapitek, and we are still continuing our work together today. Rapitek really is a solution partner. | Ceren Karaman | Operations Manager | Hürriyet Projeland - At Anatolia Tile we have placed great importance on digital transformation in order to maintain our leading position in the global market since 1995. The CRM project we began with Rapitek transformed our sales processes completely. By bringing our customer data together on a single platform we increased our team's productivity and sped up our decision-making. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Case study - The most important element in bringing new business ideas to life is your IT infrastructure and your applications. Rapitek offered far more than just supplying an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during development, we reached our first product quickly and maintained healthy project continuity. | Denizhan Edeer | CEO | Aktif Filo The testimonials above relate to CRM implementation and integration projects carried out by Rapitek; they do not mean that the organisations concerned use the Rapitek CRM product today. Brand names, logos and job titles belong to their owners. ##### Data location, KVKK and security — as it is Real estate data is sensitive: identity details, budgets, addresses, title-deed processes. So we speak plainly here. - Your data is held in the European Union. The database is in Helsinki (Finland), media files in Frankfurt, and backups in Falkenstein (Germany). We do not say that the data is held in Türkiye, because it is not. - This amounts to a transfer abroad under KVKK art. 9. That is why a privacy notice is presented on our forms; the basis for the transfer is established together with you during the contract process. - TLS is used in transit. Passwords are hashed one-way; two-factor authentication secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. A separate database is used for each customer. - There is role-based and record-level permissioning; which agent sees which properties is defined. We do not hold an information security certificate and we do not claim to. Every technical detail we state has a counterpart in the system; we answer your security questions in writing before the rollout. We have written out all of the technical measures point by point on the security page. ##### Work out the return with your own numbers Enter your own figures and see the 12-month return. Every assumption is out in the open and editable — if you do not find the result convincing, change the assumption and look again. Open the ROI Calculator No sign-up, and we do not ask for an email address. FAQ ##### Frequently asked questions about CRM in real estate - What is a real estate CRM system? | A real estate CRM system is customer relationship software that brings the property portfolio, client requests, viewing appointments, the sales pipeline and the post-sale relationship together in one place. It does not replace listing-publishing software; it builds the follow-up layer between the listing and the client. Rapitek CRM configures that layer around your process and takes it live. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. - How is portfolio management set up in the CRM? | Every property is held as its own record: price, square metres, number of rooms, floor, area, status (for sale, to let, under option), images and the responsible agent. Filtering is done by area, price range and features, and frequently used filters are saved as list views. Which fields there should be is decided together during setup; we do the configuration. - How does matching clients to properties work? | Criteria such as the client's budget, target areas and number of rooms are recorded as separate fields rather than as free-text notes. The portfolio is filtered on those fields to list suitable properties, and the ones of interest are linked to the client record. So the quality of the matching depends on how disciplined the recording of the criteria is — during setup we define those fields and which of them are mandatory together. - Can several agents use the same WhatsApp number? | Yes. Agents can write from the office's single business number. Messages land in the team inbox and are written to the relevant client record; managers can see the conversations. Even if the agent changes, the history stays with the office. The route we recommend and set up is Meta's official WhatsApp Cloud API. Pairing a phone by QR code is also possible, but we do not offer it as a product promise: that method is not Meta's official API and carries the risk of the number being restricted by Meta; if that risk materialises, your business number goes down. If you prefer that route, we share the risk with you in writing and take the decision together. - Can my Sahibinden, Hepsiemlak or Zingat listings be connected to the CRM? | There is no out-of-the-box module for these portals; saying there is would not be true. The connection is built like this: via REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. The flow that can be built is one where calls and forms coming from the portal land in the CRM as records with their source tagged; we cannot show you such a flow on a live installation today, so we work the scope out together in discovery. - Does it connect to our accounting or ERP program? | We have no out-of-the-box module on the ERP or accounting side. The connection is built like this: via REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data flows in which direction, and how often, is defined within the scope of the setup. - Can we track commission sharing? | Commission rates, the office/agent sharing model and the related amounts can be modelled as fields on the record; agent- and branch-level reports are produced from those fields. This structure is configured around your sharing model during setup — it does not arrive as an out-of-the-box payroll module. - How do permissions work in a multi-branch agency? | Role-based permissions determine which branch sees which properties, clients and reports. The branch manager sees their own team; head office sees the consolidated view. Agents can be restricted so that they reach only the records assigned to them. - Is there a mobile app for use in the field? | Yes. Both our iOS and Android apps are live and come with a Turkish interface; on the way out of a viewing an agent can update the client record, the note and the follow-up task from their phone. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp and Instagram messages are handled in a single inbox inside the app; replying to Instagram from the mobile app has not yet been measured in a customer deployment. - Can we get a trial account? | There is no trial you can start on your own. First we run a live 30-minute demo; then, if you want to explore the product at your own pace, we open a time-limited demo account for you. In the demo we show the product live on your own scenario. Configuration specific to your industry and your process is done during setup, after purchase. - How long does the rollout take and what is included? | We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. The rollout consists of these steps: discovery and analysis, configuration, data migration from Excel or from your existing system, team training and go-live. The duration varies with the number of branches, the volume of data and the scope of the integrations; the scope and any fee are worked out in the discovery call and shared in writing before work begins. - Where is our data held? | The database is held within the European Union, in Helsinki (Finland); media files are stored in Frankfurt and backups in Falkenstein (Germany). This amounts to a transfer abroad under KVKK art. 9; the basis for it is established according to the tiers in that same article: first an adequacy decision, failing that appropriate safeguards, and exceptionally the incidental cases. TLS is used in transit and a separate database is kept for each customer. ##### Related solutions - Customer tracking software | Customer tracking independent of the sector: which fields need to be recorded, how the sales pipeline is designed, and reporting. - WhatsApp CRM | The office's single business number instead of the agent's personal one; the message history stays on the client record. - Field sales software | Mobile record-keeping while the agent is out in the field, visit and appointment tracking, team-level reports. ##### See your agency's flow live In a 30-minute demo, let us show you property records, criteria-based matching, appointment tracking and branch reports on your own scenario. Request a demo The scope of the rollout and any fee are worked out in the discovery call and shared in writing. ### [CRM Resources: Tools, Guides and Migration | Rapitek](https://rapitek.com/en/resources) Free tools and plain-language guides for choosing and rolling out a CRM — no email required. Resources #### Everything worth reading before you decide. Three tools that ask for no sign-up, five pages for moving off another CRM, three migration guides and real customer stories. None of them asks for your email. Ask us your question See pricing ##### Free tools — no sign-up - CRM Readiness Quiz | 8 questions, 2 minutes. See whether your company is ready for a CRM and which steps should come first. - Rapitek CRM Fit Check | 5 questions, 60 seconds. It tells you whether Rapitek CRM fits — the answer may be "waiting is the better call for now". The scoring is out in the open. - ROI Calculator | Enter your own numbers and see the 12-month return. Every assumption is visible and editable. ##### If you're moving off another CRM - Salesforce alternative | A migration page from a team that delivered 200+ Salesforce projects — including when staying on Salesforce is the right call. - HubSpot alternative | Is marketing or sales the heavier side? That question decides it. - Zoho CRM alternative | The licence is cheap — but who does the setup? That's where total cost appears. - Pipedrive alternative | Four signals that you've outgrown Pipedrive. - Dynamics 365 alternative | Microsoft ecosystem, or speed to go live — which comes first? - Start with the fit check | If you can't decide which one to read, start with the 60-second fit check. ##### Migration guides - From Excel to a CRM | Preparing your data, cleaning duplicates, and the step where a migration gets stuck — what we've seen in our own import work. - Salesforce migration guide | What to move, what to leave — and why the right moment is your renewal date. - HubSpot migration guide | A full exit or a split? What happens to the marketing side. ##### Product and proof - Customer stories | Anatolia Tile, the SEV Foundation and Petroyağ — CRM implementation projects we delivered during our Salesforce era, in the customers' own words. - CRM Buyer's Guide | The questions to ask when buying a CRM, and the criteria to compare on. - Integrations | WhatsApp, Instagram, Google and the REST API — what's ready and what's built per project. Meta Lead Ads connections cannot be set up today. - Instagram CRM | Including the 24-hour window and Instagram's limits, as they are. Instagram direct messages land in the same shared inbox. - Mobile app | Live on iOS and Android; the inbox, the voice assistant and field tracking in your pocket. - Blog | Writing on CRM, sales and integration. ##### If you'd rather ask than read. In a 30-minute discovery call we listen to your process and work out the right answer together. If we're not a fit, we'll say so. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [CRM ROI Calculator | See Your 12-Month Return | Rapitek](https://rapitek.com/en/roi-calculator) Enter your own numbers and see the 12-month picture. Every assumption is visible and editable — no email required, no sign-up. Free tool · No sign-up #### What would a CRM actually earn you? Enter your own numbers, hit Calculate, and see the 12-month picture. Every assumption is out in the open and editable — if you disagree with one, change it and run it again. Talk through your own numbers See pricing ##### Your 12-month return The defaults describe a typical B2B sales team. Replace them with your own numbers. - Number of sales reps - Your monthly sales revenue | USD - Hours per person per week spent on data entry | hours - Expected productivity gain | % - Expected sales uplift | % - Share of opportunities you believe you lose today | % - Portion of those you believe could be recovered | % - CRM unit cost (per user per month) | USD - haftalik_ham - verimlilik_orani - haftalik_kazanc - yillik_saat - yillik_ciro - satis_orani - ek_gelir - kayip_oran_ondalik - kayip_tutar - kurtarma_orani - kurtarilan_firsat - toplam_fayda - maliyet_kisi_yillik - maliyet_yillik - net_fark - roi_orani - roi_yuzde - Hours recovered per year | yillik_saat | hours - Extra revenue from the sales uplift | ek_gelir | $ - Revenue from recovered opportunities | kurtarilan_firsat | $ - Total annual benefit | toplam_fayda | $ - Annual CRM licence cost | maliyet_yillik | $ - Estimated return on investment | roi_yuzde | % This is an estimate, not a measurement. The whole calculation rests on the values you enter: the productivity gain, the sales uplift and the recoverable-opportunity rate are your assumptions, not figures we measured. The default CRM unit cost is the current price of our Sales plan; the setup fee is not included, because its scope differs from project to project. The real outcome depends on how the system is set up and on whether the team actually uses it. Calculate ###### Estimated 12-month picture ##### Why you can trust these numbers — and where you shouldn't The logic is simple and fully visible: part of the time your team spends on data entry comes back, the sales uplift shows up in revenue, and part of the opportunities you lose today get recovered. Add those three, subtract the licence cost. The part you can trust: the arithmetic. What you type is what gets calculated — no hidden multiplier. The part you shouldn't trust: the assumption rates. “20% productivity gain” or “30% of lost opportunities recovered” are not figures we measured; they are rough numbers commonly used in this market. You know your own business better than we do — if you disagree, change them. If the result still looks worthwhile after you enter a conservative figure, you can make the decision with more confidence. What the calculation leaves out: the cost of setup, data migration and training. We don't put a single number here because the scope differs in every project; it is worked out in the discovery call and put in writing. Your answers never leave your browser. The calculation runs on your device; nothing is sent to us and we don't ask for an email address. ##### Let's talk through your number with your own team. In a 30-minute discovery call we listen to your user count, your process and your integration needs, and map out a clear scope together. Get a demo and quote 30 minutes · No obligation · The call is held in Turkish ### [Moving from Salesforce: CRM Setup in Türkiye | Rapitek CRM](https://rapitek.com/en/salesforce-alternative) Built by a team that delivered 200+ Salesforce projects: Turkish interface, a WhatsApp inbox inside the product, a separate database per customer, setup done by us. For teams coming from Salesforce #### The team that rolled Salesforce out on 200+ projects built its own CRM. During our Salesforce era we delivered enterprise projects in that ecosystem. What we learned went into our own product: a WhatsApp inbox built in, an assistant that writes records by voice, and a rollout we perform ourselves. We hold no formal Salesforce partnership today. Request a demo Read the migration guide ##### The short answer: what we are, and what we are not For Turkey-based B2B teams with at least 5 users, this is what Rapitek CRM is: the web interface is available in Turkish, English and Arabic while support and training are in Turkish, the WhatsApp inbox is part of the product rather than a project, and each customer gets a separate database. We do the setup, the data migration and the training ourselves; the scope, and any fee, is put in writing at discovery. We do not compare ourselves with another product on this page. We write down what we do and what we do not do; which of those matters for your business is your call. How to decide what to move is written out step by step in our migration guide. Structural properties ##### What Rapitek CRM does, and how Area Rapitek CRM - Who does the rollout | The team that builds the product; scope is worked out in discovery and the fee put in writing - Typical time to go live | We do not commit to a duration before discovery; after the discovery call we give you a date, not a range - Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery - Support and training language | Turkish — from the team that builds and runs the product - WhatsApp | Inside the product: shared inbox, logged on the customer record - Approach to AI | You connect your own Claude account over MCP; access is capped by that user's permissions. Rapi is off by default - Data separation | A separate database per customer; the application routes each request to that customer's database based on the web address it arrives at - Data location | European Union: database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany) - Customization | Fields, objects, flows and page layouts are configurable without code; we do it as part of setup - Ecosystem breadth | Narrow. We have no marketplace and no trained partner network — we say so plainly - Global multi-region operations | Not our focus; we have no local partner support outside Türkiye ##### What stands out in Rapitek CRM - Rapi — an assistant that writes records by voice | In the mobile app it creates and updates records from speech. It asks for your confirmation before writing — control stays with you. - Connect your own AI | Your CRM is open to AI over MCP. You connect your own Claude account and you decide what it does. Access can never exceed the permissions of the user who connected it. - Shared WhatsApp inbox | The team writes from a single work number and every message is logged on the customer record. Even when a rep leaves, the conversation history stays with the business. - A mobile app that scans business cards | Fields are extracted from a photo of the card and a lead record is created. The iOS and Android apps are both live. - Field sales and visit tracking | Mobile record-keeping, GPS visit check-in and performance reports for teams that sell in the field. Route plans and field visit records are a separately priced module — 25 USD per user per month. - A separate database and an audit trail | A separate database per customer, two-factor authentication, role-based access and a field-level audit trail. Migration ##### How does a migration from Salesforce work? - Current-state analysis | We map together which objects, fields and automations you use today. This step is run by a team that has delivered more than 200 Salesforce projects — we know what to look for. - Scope and a written quote | What moves, what gets rebuilt, what gets left behind — all in writing. If there is a setup fee, you see it before the work starts. - Data migration and configuration | Your records are migrated and duplicates cleaned out; fields, stages, roles and reports are set up around your process. - Training and go-live | We train your team ourselves and stay close through the first week. Go-live is on the date we gave you after the discovery call — a date, not a range. ##### When we are not the right product We are not the right fit for every company, and we would rather say so upfront. We do not recommend moving in these four cases: - Your current system has settled in and your team is trained. Replacing a working implementation carries a cost that never shows up on an invoice — the team relearns and the processes get rebuilt. - You depend on marketplace add-ons. We have no marketplace; the add-ons you rely on may have no equivalent here, and we can only tell you which ones by going through them in discovery. - You run a global, multi-region operation. We have no local partner support outside Türkiye; this is not where we are strong. - You are mid-contract on your current software. The right moment to move is at renewal; before that you pay for two systems at once. If one of these describes you, we will say the same thing in the discovery call — we do not write it on the page and soften it in the meeting. FAQ ##### Frequently asked questions - What does Rapitek CRM cover? | For Turkey-based B2B teams with at least 5 users we cover the sales, marketing and customer-service capability they need. We write down what we do not cover with the same clarity: we have no marketplace and no trained partner network, global multi-region operations are not our focus, and we do not commit to a written response time (SLA). - Can our existing CRM data be migrated? | Yes. Your records, custom fields and historical activity are migrated and duplicates cleaned out. What moves is decided in the discovery call and put in writing. We do not promise zero data loss: our own measurement is that across 8 tenants, 34 import jobs ran and 16 of them ended in error. Errors are found, corrected and the job re-run; migration is a step that has to be checked together. - How much does Rapitek CRM cost? | Our plan prices are public: Sales 39 USD, Platform 69 USD, Enterprise from 119 USD (per user per month, billed annually). Whatever quote you are evaluating, put setup, customization and training next to the licence — when those lines are missing from a quote, the total looks smaller than it is. Our setup scope, and any fee, is worked out in discovery and put in writing. - How long does the migration take? | We do not commit to a duration before discovery. After the discovery call we give you a date, not a range: once it is clear what moves, what the integration scope is and how ready your data is, the schedule comes to you in writing. - Can we try it first? | There is no trial you start yourself. We begin with a 30-minute live demo; afterwards, if you want to explore at your own pace, we open a time-limited demo account. The reason is simple: an unconfigured CRM looks like every other CRM — the value appears once it is set up around your process. ##### Let's work out together whether moving makes sense. Tell us about your current Salesforce implementation and we'll talk through what would move, what wouldn't, and whether the migration is right for you. If it isn't, we'll say so. Book a migration call 30 minutes · No obligation · The call is held in Turkish ### [Salesforce Migration Guide | What Moves, What Doesn't | Rapitek](https://rapitek.com/en/salesforce-migration-guide) A migration guide from a team that delivered 200+ Salesforce projects: what transfers, what has to be rebuilt, and when not to move at all. Migration guide #### Leaving Salesforce? The costliest mistake is moving everything. Salesforce implementations accumulate over the years. What needs to move is not the history but the part still in use today. This guide is written from the perspective of a team that has run 200+ Salesforce projects. Book a migration call What Rapitek CRM offers ##### Timing first: the right moment to move is your renewal date We put this first because it is where most companies lose money: moving in the middle of a live Salesforce contract means paying for two systems at once. So plan the migration around your renewal date and start early. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range — but if you only start that conversation a few weeks before renewal, you will either rush it or pay for another year. Steps ##### How do you plan a Salesforce migration? - 1. Work out what is actually being used | List your standard and custom objects, fields and reports, and note against each whether it has been used in the last 90 days. Over the years some of those fields stop being filled in; only this list shows which ones. The decision about what moves follows from that list. - 2. Inventory the automations | Write down what your automations actually do. These don't migrate — they get rebuilt — but you need to know what they do first. This is usually where you discover some of them are no longer needed. - 3. Map the integrations | Every system connected to your current CRM — ERP, accounting, marketing tool, phone system — is its own line item. Which ones are still needed in the new system, and which are no longer used at all? - 4. Export the data | Accounts, contacts, leads, opportunities, activities and attachments. Don't forget files and attachments; you need to export them while your account is still open, because what access you have after the contract closes is set by your own contract — and we have not measured it. - 5. Define a parallel-running period | Rather than running two systems side by side indefinitely, it works better to set a cut-over date and leave the old system read-only: when data goes into two places at once, it becomes unclear which record is current. We have seen this in our own projects. ##### What you won't move A migration is the best opportunity you'll get to drop accumulated weight. What usually shouldn't move: - Unused custom fields. A field carried over “in case we need it” stays empty in the new system too. - Reports nobody opens. You don't migrate a report, you migrate a need. Asking “what question are we trying to answer” and rebuilding it is faster. - Old campaigns and duplicate records. Migrating the cleanup is the same as postponing the cleanup. - Automations that stopped working. Don't rebuild flows that were set up years ago and have since broken. For historical data you want to keep, exporting and archiving it is usually better than migrating it — it stays out of daily use. FAQ ##### About the Salesforce migration - Can Salesforce data be fully exported? | Yes, the data in your standard and custom objects can be exported. The item to watch is attachments and files; their migration is planned separately. What gets migrated is decided and written down in the discovery call. - What happens to our custom development (Apex, Lightning)? | Code doesn't migrate. We work out what it does and rebuild the same need in the new system, either through configuration or over the API. This is the most variable part of a migration; the scope is worked out in discovery and put in writing. - Our team is used to Salesforce — won't they struggle? | There is an adjustment period; we won't pretend otherwise. What works in our favour: the team doing the training spent years implementing Salesforce, so we can say “the Salesforce equivalent of this was that.” - Does selling stop during the migration? | No. Salesforce is used up to the cut-over date; after cut-over the old system is left read-only. What matters is keeping the period of entering data in two systems short. - How long does it take? | We do not commit to a duration before discovery. After the discovery call, we give you a date, not a range. The timeline is driven by automation and integration scope; we work both out together in discovery. ##### Let's look at your implementation together. We'll work out which objects and automations you actually use. If a migration isn't right for you, we'll say so. Book a migration call 30 minutes · No obligation · The call is held in Turkish ### [SAP Integration: Connecting ERP and CRM | Rapitek CRM](https://rapitek.com/en/sap-integration) SAP is not one product; product, version and who holds access set the method. Account, balance and invoice data flow to the CRM; we are not an SAP partner. Integration · SAP #### If you use SAP, your CRM talks to SAP. The authority for customer account, balance, order and invoice data stays in SAP; your sales team sees the same information on the CRM screen. The connection is built with a REST API, OAuth2, signed webhooks and import/export; which data flows in which direction and at what frequency is worked out during discovery and written into an agreed scope. Request a demo Schedule a discovery call ##### The data is in SAP; the sales side cannot reach it in their daily work In a company running SAP, the ERP side does its job: customer accounts are kept, orders are entered, invoices are issued, the books are closed. This page is not arguing about SAP; it describes what happens on the side that never falls within SAP's scope. This is the picture we have seen in our own projects: - The SAP licence and the training sit in finance, purchasing and logistics; it is not a screen the sales rep uses every day. Finding out a balance comes down to a phone call. - Even a small field the sales side asks for goes into the IT queue; the change request is tied to the release plan, and its timing is set by that plan's own rhythm. - So the field team builds its own shadow system: Excel, a personal calendar, a personal phone. The data lives in two places, and one of them is not audited. - Leads, conversation history, the quotation process and the reason for a loss are not held anywhere — an ERP was not built for that. - A new quote goes out to a customer whose payment is overdue, because the open balance is not on the screen of the person writing the quote. - At the quarter close the pipeline report is put together by hand; two different figures turn up in the meeting. Trying to replace SAP does not close this gap: finance, logistics and the official document side carry on living in the ERP. The setup that works in our own projects is this: the ERP stays where it is, the sales side moves to the CRM, and the two sides are connected by a defined and written flow. ##### How is the connection built? There is no out-of-the-box module for SAP, and we will not say there is. The connection is built as an integration project whose scope is set in the discovery call, using a REST API, OAuth2, webhooks and import/export. These are the three tools we use on the CRM side: - REST API — the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint; access is authorised with OAuth2. Schema reading (describe), composite operations and bulk endpoints are supported. - Outbound webhook — events in the CRM (an opportunity being won, for example) are sent to the external system signed; a failed call is retried. - Import/export — Excel/CSV transfer through a four-step wizard: upload, map fields, preview, run. You approve the mapping on screen. Who does the work on the SAP side? In practice your own SAP partner or your in-house integration team — they are the ones who know the interface, the permissions and the change process on the SAP side. Our side is documented: we provide the object schema, OAuth2 access and the field mapping table in writing. If you wish, we can also take on the development on the CRM side. The limits on our side are measured, not estimated: the REST API exposes object and field definitions through the describe endpoint, processes up to 200 records in a single bulk request, and carries 25 sub-requests in one composite call. The import wizard works on more than 75 objects, up to 100,000 rows per job and 25 MB per file. Let us also write down what we are not saying: we have no reference customer running SAP, and we have no figure for how many enterprise installations have chosen this route. Why a connection that gets built, rather than an out-of-the-box add-on? Because SAP is not a single product and access differs from one installation to the next: which product and which version, on-premise or hosted, and who holds the authority to open an interface. Handing everyone the same button and saying it will connect at a single press would be a promise that stops working the moment the access conditions change. Instead we choose the method together during discovery and share the scope, and any cost, in writing. We have set out our general approach with the same openness on the integrations page. A concrete scenario ##### Tuesday, 16:00 — the regional sales manager is reviewing the pipeline for the quarter close. Once the connection is in place, this is what changes: - The open balance and the payment term are on screen while the quote is being prepared | The account balance and payment term transferred from SAP sit as fields on the customer record. The rep sees an overdue balance while preparing the quote; no call to finance. - A balance over the threshold opens a follow-up task | When a balance passes the threshold you set, a task is assigned to the owner. Collections follow-up is tied to a record rather than to someone's memory. - Order and shipment status can be read without going into SAP | Orders continue to be entered in SAP and invoices continue to be issued on the SAP side. Status information and amounts are written into the CRM at the frequency defined in the scope; you do not need to open ERP licences for the sales team. - A field request from sales is not tied to the release plan | Fields such as a risk limit, a payment term or a dealer code are added on the CRM side by an administrator without writing code. Because nothing is touched on the SAP side, the change does not wait in the IT queue. - A won opportunity is passed to the SAP side with its order details | When an opportunity is won, the order details can be sent to the external system through a signed webhook; the endpoint is consumed by your team on the SAP side. Entering the same data a second time by hand is reduced. - The quarter close does not arrive with two different totals | Sales and collections by customer and by region appear in the same report, through tabular and summary report types and the drag-and-drop dashboard designer. One figure goes into the meeting. ##### Flows that can be set up between SAP and Rapitek CRM - Customer record – matching the SAP customer number | Records are matched using the tax number or the SAP customer number as the key. Duplicate records are cleaned up during setup; the matching rule and which side generates the key are stated in the written scope. - Balance and payment term visibility | The account balance and the overdue amount are transferred onto the customer record as fields; they are visible without opening ERP licences for the sales team. The transfer frequency is set in the scope. - Following order and invoice information | Order and invoice header information is followed as a list on the customer record. The authority for the document stays in SAP; the CRM only adds a visibility layer. - Transferring the material and price list | The material catalogue and the price list are transferred from the ERP to the CRM so that quotes are prepared with the right prices. The transfer can be periodic, or it can be built over the API. - Passing a won opportunity to the SAP side | A signed webhook that sends the order details to the external system when an opportunity is won can be set up; the endpoint is consumed by your team on the SAP side. Entering the same data a second time by hand is reduced. - Adding sales fields without waiting for the release plan | Field and object definitions on the CRM side are added by an administrator without writing code; because nothing is touched on the SAP side, the change does not enter the IT queue. Adding custom objects and fields is standard in the product. Choosing a method ##### Which method, and when? The method is chosen during discovery according to the access and the permissions on the SAP side. All four use the same REST API surface; the difference is who moves the data, and how often. Method | What it does | When it is preferred - REST API (183 business objects out of the box, each with its own data and schema endpoint) | The external system reads and writes records in the CRM; it is authorised with OAuth2 and supports schema reading and composite operations | When a suitable interface and permissions exist on the SAP side, and the flow is meant to run automatically - Outbound webhook | Events in the CRM (an opportunity won, for example) are sent to the external system signed; a failed call is retried | For flows that need a notification from the CRM towards SAP; the endpoint is consumed by your side - Import (Data Hub) | Excel/CSV extracts are transferred through a four-step wizard: upload, map fields, preview, run. Export is done in the same module; we have not measured its limits | Because it does not require access to be opened on the other side, it can start before the access question is answered; when a periodic sync is enough, or when external access to SAP cannot be opened - Your SAP partner or your in-house integration team | The team that knows the SAP side can write the connection itself using the same REST API; we provide the schema, the access and the field mapping table | When the change process on the SAP side runs within your own team What we can say ##### What we have verified - 183 | Business objects in the REST API - 200 records | Records per bulk API request; 25 sub-requests in a composite call - 100,000 rows | Upper limit per import job; 25 MB per file - Every 6 hours | Database backup frequency; local copies kept 30 days, a copy in another country - EU | Database in Helsinki, files in Frankfurt, backups in Falkenstein Implementation ##### How is the SAP connection put into service? - Discovery | We work out which SAP product and version you use, where the system runs and who holds the authority to open an interface. We recommend that your IT lead and your SAP partner join this call. - Security and architecture review | We fill in your IT team's security assessment questionnaire and describe the architecture and the data flow in writing. We have written down what we have and what we do not have exactly as it stands — it is all listed, item by item, on our security page. - Scope, boundary of responsibility and method | Alongside which data flows in which direction and how often, the boundary of responsibility between the two sides is written here as well: who will do the development on the SAP side, and who will consume the endpoints. The field mapping table, the scope and the cost are shared in writing. - Configuration and test transfer | Fields, list views, roles and permission sets are set up on the CRM side; a test transfer is run with sample data. Mappings are verified in both directions, and duplicate and faulty record scenarios are tried out here. - Training and go-live | Training for the sales team and for managers, then close support during the first week. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. The schedule for API-based flows depends on the change process on the SAP side. ##### Our limits: what we do not promise on this page In a company running SAP, the person reading this page may well be from IT, and they ask the right question: what can you not do? Our answers are here, in one place. - We are not SAP certified and we are not an SAP partner. We have no out-of-the-box connection for SAP Business One or S/4HANA; the connection is a project built with the tools described above. - We have no reference customer running SAP. Today we cannot describe such an installation under a customer's name, and we will not write as though we could. What we can commit to is that the CRM side is documented and open: the object schema, OAuth2 access and the field mapping table are provided in writing; the work on the SAP side is carried out by your partner or your in-house team. - There are three things we categorically do not promise: that stock will be in sync, that the order → invoice → collection chain will flow by itself, and that the production/MRP side will work as an integrated whole. The reason for each, and what can be done instead, is written out line by line in the limits section of the integrations page; we are not repeating it here. - We do not issue e-Invoice or e-Archive documents. Rapitek CRM is not a GİB-authorised special integrator; it does not produce official documents and does not track ETTN or GİB status. Information such as the invoice number and the amount can be carried into the CRM as fields. - Let us be honest about scale. The business Rapitek CRM describes is a B2B company with at least 5 users and a sales or field team. A group running SAP may be at a far larger scale; if so, we do not commit today to being the enterprise CRM for the whole group — rather than making a promise about scale we cannot prove, we say this up front. A realistic scope is one sales unit, one subsidiary or one dealer channel; it grows from there. - Identity management: single sign-on with OIDC is supported in the product; we have no SAML support and we do not have a configured SSO installation in production today. Two-step verification is mandatory for the administrator web login; API and mobile channels fall outside that requirement. Roles, profiles, permission sets, record sharing and IP restrictions are supported in the product; we configure them according to your policy during setup. - Certification and commitments: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. Nor do we give an availability (uptime) commitment based on external monitoring — we do not think it is right to commit to something we do not measure. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no region selection feature. This is a transfer abroad within the meaning of Article 9 of the KVKK; we establish your basis for that transfer together during the contract process. The full architecture, the sub-processor list and what we do not offer yet are on the security page, and the personal data side is in the KVKK privacy notice. ##### The scope comes out of discovery; the plan prices are out in the open The cost of the SAP connection depends on the data volume, the direction of the flow and the access available on the SAP side; it is shared in writing after discovery. The plan prices, on the other hand, we publish in one place, with the figures. See pricing Three plans, a scope table and the separately priced items, all on one page. FAQ ##### Frequently asked questions about SAP integration - Is integration between SAP and a CRM possible? | Yes, we build it — not with an out-of-the-box module, but as a project whose scope is defined in advance. The connection is built with a REST API, OAuth2, signed webhooks and import/export. During discovery we work out which of the customer account, balance, order and invoice data flows in which direction and how often, and share it in writing together with the field mapping table. - Is there a ready-made SAP module in Rapitek CRM? | There is no out-of-the-box module; it would not be right to say there is. We have no SAP-specific module that you switch on during setup and connect. What we do have is a documented interface: the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe; alongside it, OAuth2, composite operations, signed outbound webhooks and a four-step import/export wizard. - Are you an SAP-certified solution? | No. We hold no SAP certification and no SAP partnership, and we do not say we do. What we commit to on our side is that the CRM has a documented and open interface: the object schema, OAuth2 access and the field mapping table are provided in writing, and the connection is built on top of that. - Does it matter which SAP product we use? | Yes, it determines the method directly. SAP is not a single product — S/4HANA and SAP Business One are different systems; which product and version you are on, whether the system runs on an in-house server or in a hosted environment, and who holds the authority to open an interface all change whether the connection is built over the REST API or through periodic transfers. That is why we do not promise a scope before the discovery call. - Who does the development on the SAP side? | In practice your own SAP partner or your in-house integration team — they are the ones who know the interface, the permissions and the change process on the SAP side. We take on the CRM side; we provide the REST API documentation, OAuth2 access, the object definitions and the field mapping table. Who writes what, how testing will be done and which field flows in which direction are separated out in writing during discovery. - Is Rapitek CRM's REST API documented, and can it be used from outside? | Yes. The product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint — objects are read and written, and you can read the field structure from outside through the describe endpoint. Access is authorised with OAuth2; the bulk endpoint processes up to 200 records in a single request, and the composite endpoint carries 25 sub-requests in one call. Events in the CRM are sent to the external system through a signed outbound webhook, and a failed call is retried. We provide the API documentation, the object definitions and the field mapping table in writing after discovery. - Our IT team sends out a security assessment questionnaire — do you fill it in? | Yes, we fill it in and we describe the architecture in writing. Let us say it up front: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We have written down what is offered and what is not offered yet exactly as it stands, on our security page; starting your assessment from that page will be the fastest route. - Can we use single sign-on (SSO)? Do you support SAML? | Single sign-on with OIDC is supported in the product; we have no SAML support and we do not have a configured SSO installation in production today. Two-step verification (TOTP, email code, backup codes) exists and is mandatory for the administrator web login — API and mobile channels fall outside that requirement. Roles, profiles, permission sets, record sharing and IP restrictions are supported in the product and are configured according to your policy during setup. - Our company is at the scale that uses SAP — is Rapitek CRM a fit for that? | The honest answer: the businesses we describe are B2B companies with at least 5 users and a sales or field team. A group running SAP may be at a far larger scale, and in that case we do not commit to being the enterprise CRM for the whole group — we do not think it is right to make a promise about scale we cannot prove. A realistic starting point is one sales unit, one subsidiary or one dealer channel; the scope grows from there. - Will we have to open SAP licences for the sales team? | The point of the setup is precisely that this is not required. The sales side works in the CRM; the balance, order and invoice information coming from SAP appears as fields on the customer record. Which fields are carried across and who sees them is defined in the scope; visibility can be restricted with roles and permission sets. - Our SAP system is in-house and closed to the outside. Is integration still possible? | Yes, only the method changes. If external access to SAP cannot be opened, the flow runs over extracts: extracts taken from SAP are transferred into the CRM periodically using a template. This route does not require access to be opened on the other side; it can start before the access question is answered. If the access conditions change later, the same scope can be moved to an API-based flow. - Will our stock be in sync with the CRM? | We do not promise real-time stock synchronisation. The authority for stock records stays in SAP; the scope, the frequency and the fields of the stock information to be carried into the CRM are defined during discovery. We have written the reason, and what is done instead, in the limits section of the integrations page. - Can we issue e-invoices from the CRM? | No. Rapitek CRM does not issue e-Invoice or e-Archive documents and is not a GİB-authorised special integrator; fields such as ETTN or GİB status do not exist in the product. Your invoices continue to be issued in your current arrangement. The invoice number, date and amount can be carried onto the customer record through the REST API or a periodic transfer. - Does it replace SAP? | No, and we do not recommend that it should. SAP stays on the finance, logistics and official document side; Rapitek CRM takes the lead, the conversation history, the quotation process and sales reporting. The job of the integration is to connect these two sides with a defined flow. - Will the synchronisation be real time? | It depends on the method, and we do not promise “real time” in advance. API- and webhook-based flows can run close to the event; extract-based transfers are periodic. Which flow runs at what frequency, and the latency to expect, are set out line by line in the written scope. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, and database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. This is a transfer abroad within the meaning of Article 9 of the KVKK; we establish the basis for it together during the contract process. Your CRM data is held in a separate database that belongs to you. - What does SAP integration cost, and how long does it take? | We do not put a figure on this page, because both depend on the scope: the data volume, the direction of the flow, its frequency and the access available on the SAP side. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. The integration is a separate line item; its scope, its cost and its schedule are shared in the same written plan. ##### Related pages - Integrations | An overview of integration: which connection is live today, which ones we build, and the reasons behind the three things we do not promise. - Security | For an IT assessment: data location, the sub-processor list, authorisation, backups, the audit trail and what we do not offer yet. - Netsis integration | The same framework applied to another ERP: which direction customer account, balance, order and invoice information flows, and how the method is chosen. ##### Let us map out your SAP flow in 30 minutes In the demo call, let us talk through how your customer account, balance, order and invoice data will flow into the CRM, using your own scenario; we will choose the method and the scope together. Bring your IT team along too. Request a demo The scope of the setup, and any cost, are worked out in the discovery call and shared in writing. ### [CRM Configured for Your Industry | Rapitek CRM](https://rapitek.com/en/sectors) No canned industry packages: one CRM backbone — customer record, sales pipeline, WhatsApp, reports. Fields, stages and roles are configured for your business. Industries #### A CRM for your industry: not a canned template, a setup around your process From real estate to auto parts, the backbone is the same: customer record, sales pipeline and WhatsApp. Fields, sales stages, roles and reports are configured for your industry. We do the configuration, and after the discovery call we give you a date, not a range. Request a demo Tell us about your process ##### What does "industry-specific CRM" mean at Rapitek? In this market “industry-specific CRM” usually means one thing: dozens of industry pages placed in front of the same product. We do have industry pages and we keep them — because the question the person doing that job asks is a real one: what goes wrong here, and where does information get lost. But none of those pages describes a “ready industry package”; every one of them leads to the same door: one product, a different setup. What we saw across more than 200 enterprise CRM projects is this: the backbone of a good CRM is industry-agnostic. The customer record, the sales pipeline, team-wide WhatsApp, permissions and reporting do the same job at a real-estate office as at an auto-parts wholesaler. What is industry-specific is not the product but its setup: which fields are kept, how the stages are named, who sees what, which report goes to whom. That is why we don't sell a “ready CRM package for industry X”. We configure Rapitek CRM around your process, and we do the configuration ourselves; the scope of setup — and any fee for it — is worked out in the discovery call and put in writing before the work starts. ##### The backbone that stays the same in every setup - Customer record | Account, contact, call notes, quotes and tasks on a single record. Who called when, what was discussed, what comes next — everyone on the team sees the same history. - Sales pipeline | Opportunities move stage by stage, tracked in Kanban and list views. Steps that stall or never happen show up in reports. - Shared WhatsApp inbox | The team writes from the business's single work number; messages land in a team inbox and are logged on the customer record. When an employee leaves, the conversation history stays with the business. - Role-based permissions | Decide who sees which records and reports by branch, dealer, region or team. Managers get the consolidated view; reps see their own work. - Reports and dashboards | Tabular, summary and matrix report types, plus a drag-and-drop dashboard designer. Built on your metrics, without writing code. - Tasks and calendar | Follow-up tasks, reminders and two-way appointment sync with Google Calendar. Follow-ups are entrusted to the system, not to somebody's memory. Configuration #### The same screen, your fields This is the standard lead list. For a real estate office, budget and target-area columns are added; for a tire dealer, vehicle and season data; for an auto parts wholesaler, dealer and brand fields. Same screen — we define the fields, filters and saved list views for your business during setup. Configuration map ##### What changes by industry — and what stays the same? One product; the setup makes the difference. The Rapitek team does the configuration; the scope of setup — and any fee for it — is agreed in writing before the work starts. Layer | Same in every setup | Configured for your industry - Fields | Lead, account, contact, opportunity, quote and task records | Budget and target area for real estate, vehicle and season for tire dealers, dealer and brand for auto parts — defined during setup - Sales pipeline | Stage-based opportunity tracking with Kanban and list views | Stage names and count follow your process: viewing appointment, discovery, quote revision, installation and so on - Roles and permissions | Role hierarchy and record-level sharing | The visibility matrix — by branch, dealer, region or team — is drawn for your organization - Reports | Tabular, summary and matrix reports plus a dashboard designer | Which metrics get tracked: portfolio by region, viewings per agent, orders per dealer and the like - Automation | Visual flow designer | Which event triggers which task: a missed appointment, a pending quote, an approaching seasonal peak - Mobile | iOS and Android apps, both live; WhatsApp and Instagram messages are handled in a single in-app inbox | What the field team sees and updates on their phones is configured for your workflow ##### Setups we know inside out - Real estate | Real estate offices: property records, buyer requirement criteria, viewing appointments and agent-level permissions — step by step. - Tire dealers | Tire sales points: handling the seasonal rush, tracking customers and their vehicles, and building a relationship that brings customers back. - Auto spare parts | Wholesale and retail parts sales: customers, dealer relationships and order tracking on the CRM side. - Field sales teams | A way of working rather than an industry: visit planning, GPS visit check-in and updating records from the phone for teams that sell in the field. - Customer follow-up | For teams moving customer follow-up out of Excel files and personal phones — the core setup that makes nothing fall through the cracks. - WhatsApp as a channel | A shared team inbox on the business's single work number, with the full message history logged on the customer record. ##### Our industry pages and the language they are in We have 188 industry pages in English, and you can reach all of them from the list below. They are translated from our Turkish originals, and the Turkish set is the wider one — 281 pages — so there are industries you can read about in Turkish but not in English. The six setups above are a different case: those are the ones we have gone deepest on, and they have English pages of their own rather than entries in the industry list, so the cards link straight to them. Field sales is the exception — that one is written up in Turkish. This is about the pages, not the product: the backbone is the same in every setup, and the setup is built around your process whatever your industry. In English the same ground is also covered by the product page and the CRM buyer's guide; if you want the specifics of your own industry in English, bring them to the discovery call — request a demo. ##### All industry pages in English ###### Healthcare and clinics Healthcare CRM · Clinic CRM · Medical Centre CRM · Obstetrics and Gynaecology Clinic CRM · IVF Clinic CRM · Eye Center CRM · Optician and Eyewear CRM · Dermatology Clinic CRM · Physiotherapy CRM · Psychology Clinic CRM · Psychology and Psychotherapy CRM · Dietitian CRM · Weight Loss Clinic CRM · Home Healthcare CRM · Pharmacy CRM ###### Dental Dental Clinic CRM · Dental Implant Clinic CRM · Orthodontic Clinic CRM ###### Aesthetics, beauty and personal care Aesthetic Clinics CRM · Hair Transplant Centre CRM · Laser Hair Removal Center CRM · Skincare Center CRM · Beauty Centre CRM · Beauty Salon CRM · Spa and Wellness CRM · Cosmetics CRM ###### Pharma, medical devices and laboratories Pharmaceutical CRM · Medical Device CRM · Laboratory CRM · Biotech CRM · HealthTech CRM ###### Pet services Veterinary Clinic CRM · Pet Shop CRM · Pet Grooming CRM ###### Education and training Preschool and Nursery CRM · Private School CRM · University CRM · Language School CRM · Tutoring Centers & Private Lessons CRM · Course Centre CRM · Driving School CRM · Music School CRM · EdTech CRM ###### Manufacturing and industry Manufacturing CRM · Enterprise Manufacturing CRM · Metal Industry CRM · Electronics CRM · Plastics CRM · Glass CRM · Ceramics CRM · Chemical CRM · Furniture CRM · Robotics CRM · Defense Industry CRM · Aviation CRM ###### Printing and packaging Printing CRM · Label and Sticker Manufacturer CRM · Packaging CRM · Paper CRM ###### Textile, fashion and leather Textile CRM · Fashion CRM · Leather CRM · Footwear CRM · Accessories CRM ###### Food and beverage Food CRM · Butcher CRM · Bakery and Patisserie CRM · Organic Farming CRM · Water Dealer / Carboy CRM ###### Agriculture, livestock and aquaculture Agriculture CRM · AgriTech CRM · Farming CRM · Greenhouse and Nursery CRM · Landscaping CRM · Aquaculture CRM ###### Retail Retail CRM · E-commerce CRM · Grocery and Corner Shop CRM · Building Materials CRM · Jewelry Store CRM · Jewelry CRM · Florist CRM ###### Travel, hospitality and food service Tourism CRM · Hotel CRM · Camping CRM · Travel Agency CRM · Marina CRM · Theme Park CRM · Restaurant CRM · Cafe CRM · Catering CRM ###### Construction and building Construction CRM · Engineering CRM · Architecture Office CRM · Renovation CRM · Interior Design CRM · Elevator CRM · Plumbing CRM · HVAC / Ventilation CRM · Swimming Pool CRM ###### Real estate and facility management Real Estate Development / Contractor CRM · PropTech CRM · Facility Management CRM · Coworking Space CRM ###### Logistics and transport Logistics CRM · Haulage and Transport CRM · Home Removals CRM · Warehouse CRM · Courier CRM · Fleet Management CRM · Maritime CRM ###### Foreign trade and customs Import Export CRM · Customs CRM ###### Automotive and vehicle services Automotive CRM · Automotive Dealer CRM · Auto Repair CRM · Auto Body and Paint Shop CRM · Vehicle Inspection CRM · Car Wash CRM · Car Rental CRM ###### Finance and insurance Finance CRM · Banking CRM · Enterprise Banking CRM · Fintech CRM · InsurTech CRM · Insurance Agency CRM · Wealth Management CRM ###### Accounting, audit and legal Accounting Firm CRM · Independent Accountant CRM · Legal CRM · LegalTech CRM · Notary CRM · Patent Attorney Office CRM · Pre-Accounting CRM ###### Consulting and professional services Consulting CRM · HR and Recruitment CRM · Staffing Agency CRM · Translation Agency CRM · Call Centre CRM ###### Technology and software Software Development CRM · B2B SaaS CRM · IT Services CRM · Cloud Services CRM · Hosting and Domain CRM · Cybersecurity CRM · AI Services CRM · Blockchain CRM · VR AR CRM · Gaming CRM · Smart City Technologies CRM · Drone Services CRM · Telecom CRM ###### Energy, environment and natural resources Energy CRM · Electricity Distribution CRM · Oil and Gas CRM · Solar Energy CRM · Solar Panel Installation CRM · Wind Energy CRM · Mining CRM · Waste Management CRM · Recycling CRM ###### Agencies, media and design Agency (Advertising, Marketing, PR) CRM · Advertising CRM · Digital Agency CRM · Digital Marketing Agency CRM · PR Agency CRM · Graphic Design CRM · Media CRM · Photography CRM ###### Events Event Management CRM · Wedding and Event Planning CRM ###### Culture, sport and the arts Cinema CRM · Theater CRM · Art Studio CRM · Sports Club CRM · Athletic Club CRM · Fitness and Gym CRM · Pilates CRM ###### Security and workplace safety Security Services CRM ###### Local services, repair and maintenance Cleaning Services CRM · Dry Cleaning CRM · Air Conditioning and Boiler Service CRM · Funeral Services CRM ###### Public sector, enterprise and non-profits Government CRM · Nonprofit CRM · Enterprise Cooperative CRM · Holding Company CRM · Franchise CRM ##### If your industry isn't listed here Having an industry page is not a promise of a canned package: each one describes what gets set up differently in that line of work — which fields are kept, which step turns into a task — and the setup still follows your process. Across more than 200 enterprise projects we have worked with a wide range of industries — and we still won't claim to have a ready package for every one of them. In our experience, how you work matters more than the industry: how large your sales team is, whether it goes out into the field, and how many places the work is run from. Two businesses that answer those the same way have more in common, CRM-wise, than two businesses in the same industry that work differently. If your industry isn't listed, here is how it works: - In a discovery call we listen to your process — how a sale starts, where it gets stuck, who needs to see what. - We put the fields, stages, roles and reports to be configured into a written configuration plan. - If it works for you, we do the setup; after the discovery call we give you a date, not a range. A message is enough to start — our WhatsApp line is open: +90 212 963 22 84 Implementation ##### How does an industry-specific setup proceed? - Discovery and analysis | We map your sales process, team and branch structure, and current tools. This is where we decide which fields are genuinely needed. - Configuration | Fields, pipeline stages, list views, the permission matrix and reports are set up around your process. No code is needed — but configuring it well takes expertise, and that part is on us. - Data migration | Customer records from your Excel files or your current system are imported, with duplicates cleaned out. - Training and go-live | User and admin training, close support through the first week, then ongoing support. After the discovery call we give you a date, not a range. Verifiable numbers ##### Constants that don't depend on your industry - 200+ | Enterprise CRM projects completed for other companies during our Salesforce era - A date, not a range | We give you a go-live date after the discovery call - 183 | Business objects in the REST API — each with its own data and schema endpoint - EU | Data location: database in Finland, media in Frankfurt From our CRM implementation projects ##### From our CRM projects - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Read the customer story - As a newly established company aiming to make rapid progress, we realized we needed an overall infrastructure for sales management, team tracking, and inventory management. With that need, we started the project with Rapitek, and we are still continuing our work together today. Rapitek is truly a solution partner. | Ceren Karaman | Operations Manager | Hürriyet Projeland - The most important element of bringing new business ideas to life is your IT infrastructure and applications. Rapitek offered much more than just providing an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during the development process, we reached our first product quickly and ensured healthy project continuity. | Denizhan Edeer | CEO | Aktif Filo The testimonials above come from CRM implementation and integration projects Rapitek delivered; they do not mean that those organizations use the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### We write the number on the pricing page, not here Setup, data migration and training differ from project to project; that scope is shared in writing after the discovery call. Plan prices we keep in one place, so you never read two different figures. See pricing Three plans, a scope table and separately priced items. FAQ ##### Frequently asked questions about industry CRM - What is an industry-specific CRM? | Two different things get sold under this name: a vertical product written for one industry, or a general CRM configured for it. Rapitek CRM is the second: the customer record, sales pipeline, WhatsApp, permission and reporting backbone is the same in every industry; fields, stages, roles and reports are configured around your process. We do the configuration; its scope, and any fee for it, is agreed in the discovery call. - Does Rapitek CRM support my industry? | Since the backbone is industry-agnostic, the real question is whether it can be configured to your process. We settle that in a discovery call: we listen to your process and produce a written plan of the fields and reports to be set up. We don't claim a ready package for every industry; process modeling is the work we have done across more than 200 projects. - Should I buy a vertical (industry-built) CRM or a general one? | The honest answer: it depends. Vertical products ship industry features out of the box, but flexibility can run out when your process strays from their template. A configurable CRM is set up to match your process exactly, but the setup takes effort. In our model that effort is ours, not yours — its scope, and any fee for it, is worked out in the discovery call and put in writing. - Can the CRM be customized for my industry? | Yes — fields, sales stages, page layouts, list views, the permission matrix and reports are all configurable. And we don't mean "you get to figure it out": the Rapitek team does the setup. After go-live your team can comfortably handle day-to-day changes themselves; for deeper changes, we're there. - Does setup time vary by industry? | The rollout covers the same steps in any industry: discovery, configuration, data migration, training and go-live. What drives the timeline is less the industry than data volume, the number of branches and users, and integration scope — so we don't commit to a timeline before discovery. We map the scope in the discovery call and share it in writing — and after that call we give you a date, not a range. - Does it replace my industry software (listings, accounting, ERP)? | No, and it doesn't try to. Listing or portfolio software, accounting and ERP are your operational layer; Rapitek CRM adds the customer relationship layer on top. The connection between them is built through REST API, OAuth2, webhooks and import/export, delivered by our professional services team; we don't claim ready-made connectors, and the scope is defined per project. - Which industries do you know best? | We have gone deepest in real estate, tire dealers and auto spare parts, plus two ways of working that cut across industries — field sales teams and structured customer follow-up — and WhatsApp as a channel. If your business is outside those, just describe your process when you request a demo; we draw up the configuration plan together. - How do permissions work in a multi-branch or dealer structure? | Role-based permissions decide which branch or dealer sees which records and reports. Management looks at the consolidated view; each branch or dealer sees its own work. Reps can be limited to the records assigned to them, and records stay with the business when an employee leaves. - Is there a mobile app for field teams? | Yes — on both platforms. Our iOS and Android apps are live on the App Store and Google Play, so an Android-heavy field team is not left out. A rep can update the customer record, notes and follow-up tasks from the phone right after a visit. Rapi, the voice assistant available only in the mobile app, creates and updates records by voice — in Turkish — across 11 objects. WhatsApp conversations are handled in the same in-app shared inbox, so a rep standing in front of a customer can answer a message without going back to a desk. Instagram direct messages land in the same inbox; replying to them from the mobile app has not yet been measured in a customer deployment. - Where is our data stored? | The database is hosted in the EU, in Finland; media files are in Frankfurt. A few sub-processors operate outside the EU, and we name each one, with where it processes data, in our privacy notice. For companies subject to KVKK (Turkey's data protection law No. 6698), EU hosting counts as an international transfer under Article 9, and we state this plainly in our privacy notice and contract. TLS protects data in transit and each customer gets a separate database. Passwords are hashed one-way; 2FA secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. - Can we explore the product ourselves? | There is no trial you start yourself by signing up. We begin with a 30-minute live demo on your own scenario and answer your questions on the real product screen; afterwards, if you would like to explore the product at your own pace, we open a time-limited demo account for you. Industry-specific configuration happens during setup after purchase. - Does pricing change by industry? | Plan prices don't depend on industry. What can vary is the scope of setup and any integration work, which is scoped separately — we put both in writing during discovery. Current plans, and the items priced outside the plan, are on our pricing page. ##### Tell us about your process — we'll draw up the configuration plan together In a 30-minute demo we show the product on your own scenario and talk through which fields, stages and reports would be configured for your industry. Request a demo The scope of setup — and any fee for it — is agreed in writing before the work starts. ### [Security and Data Protection | Rapitek CRM](https://rapitek.com/en/security) Rapitek CRM security architecture: a separate database per customer, EU (Finland) hosting, two-factor authentication and a field-level audit trail. Security #### You know where your data lives. Most CRM security pages say "enterprise-grade protection" and move on. We wrote ours concretely: which country your data sits in, who can reach it, how far we can tell who changed which record — and which third parties touch your data, every one by name and country. Request a demo Privacy Policy ##### The foundation of the architecture. - A separate database per customer | Every customer runs in its own separate database. Not a "company ID" filter in a shared table — each customer's data sits in its own database, and the application routes each request to the right database based on the web address it arrives at. One exception we state openly: the application's technical error logs are kept in a single table shared by all customers. - Hosted in the EU, stated openly | The database is in Helsinki (Finland), the files you upload are in Frankfurt, and database backups are in Falkenstein — all three inside the European Union. We have no component in Turkey and no region-selection feature. Seen from Turkey this is a transfer abroad under Article 9 of KVKK; we establish the basis for that transfer together with you during the contract process. - Field-level audit trail | A separate history row is kept for every field change users make to an existing record — the time, the old value, the new value (protected fields: a marker, not the values). The record's initial creation and some bulk updates the system makes in the background are not recorded. Field history is on by default across every object that ships in a standard install; you do not need to enable it. - Recycle bin | Deletion is soft deletion: the record does not leave the database at once, it moves to the recycle bin, where an authorised user can restore it. The bin's 30-day clean-up is not running, so older records stay there too. Bulk restore is not working at the moment; records are restored one at a time. An authorised user can permanently delete records from the bin. ##### Access, identity and the third parties that touch your data Subprocessor list. Hosting and storage are inside the EU; Anthropic (US), Cloudflare (a US company) and Meta (Ireland/US) sit outside it. We update this page whenever the list changes. Control or party | How and where it works - Two-factor authentication (2FA) | On by default for every user. The default method is an email code; an authenticator app is also supported (set up with a QR code, backup codes). - API authentication | OAuth2; API client secrets are stored as one-way hashes. Each API client can be granted read, write and delete scopes separately; the server checks these scopes on the general record API (create, update, delete and bulk record operations), on quote creation and on message sending. Every customer has its own separate database; automated tests check that an access token issued for one customer is rejected on a request made to another customer's web address. - Roles and sharing | Record visibility is controlled with role-based access and sharing rules; field-level hiding is supported. - Brute-force protection | Login attempts are limited both per user and per IP address (10 attempts in 15 minutes), and two-factor authentication allows 5 attempts. The counters are kept atomically. - Rate limiting | The mechanism is in place: once a limit is exceeded the request is rejected with a 429 and a Retry-After header. Usage analytics show you how many requests each integration is making. We have no published fixed quota figure. - Encryption | Browser connections to Rapitek CRM are redirected to HTTPS and encrypted with TLS; in our 23 September 2026 measurement TLS 1.3 and 1.2 were accepted and TLS 1.0 and 1.1 were refused. Passwords are not stored in plain text: they are hashed one-way with PBKDF2-SHA256 and cannot be reversed; API client secrets are stored as one-way hashes too. Email account OAuth tokens; WhatsApp Business, Instagram and Meta access tokens and webhook secrets; payment and İYS provider credentials; two-factor authentication secrets and backup codes; and voiceprints are encrypted at the application level before they are written to the database. Encryption at rest is not applied to the whole database — we do not claim that: the database files are not additionally encrypted on the server's disk. - Backups | Rapitek CRM database backups are taken automatically every six hours; each run checks that the dump completed without error and that the compressed file can be opened; the content of the copy sent to Germany is not additionally compared against the original. Local copies on the server are deliberately kept unencrypted and retained for 30 days. The off-server copy sits in a separate country, Germany (Falkenstein): database backups sent since 2 September 2026, 03:11 Turkey time, are encrypted with OpenPGP before they leave the server, and the decryption key is not on the production server; database backups sent before that are unencrypted. Encrypted off-server backups are deleted automatically after 90 days; the unencrypted backups kept there are not covered by this automatic deletion. This 90-day period keeps the newest 28 copies of every database regardless of their age, so that the last copies are not deleted as well if backups stop or fail; as a result, the last 28 copies of the database of a customer whose account has been terminated are not deleted by this period, and today there is no separate step that deletes them. Files attached to a record (for example, CVs) are not deleted from storage (DigitalOcean Spaces, Frankfurt) whether you delete the file from the record card or delete the record; today the product does not delete these files by itself. To have them deleted, you need to write to our support team. We have verified a restore once: on 19 August 2026 a manually taken database dump was restored into a temporary schema and 239 of 239 tables came back. No restore has yet been attempted from the automatic backups — neither from the local copies nor from the encrypted off-server copies — and we do not commit to any restore time. - Subprocessor — Cloudflare, Inc. | Content delivery network, TLS termination, web application firewall and bot protection · the edge server nearest the visitor, company in the United States. It is in the path of every request and the TLS connection terminates at the edge rather than at the hosting server, so data in transit and the visitor's IP are processed at that layer. No content is stored there. The requests we measured went through EU edge nodes (Amsterdam from Turkey, Stockholm from Helsinki); the node is chosen by proximity to the visitor and is not fixed. - Subprocessor — Hetzner | Application server and database · Helsinki, Finland (EU) - Subprocessor — Hetzner Storage Box | Database backups · Falkenstein, Germany (EU) - Subprocessor — DigitalOcean Spaces | Files and media you upload · Frankfurt, Germany (EU) — those attached to a record stay here whether you delete the file from the record card or delete the record; to have them deleted, write to our support team - Subprocessor — Amazon SES | Delivery of system email · Frankfurt, Germany (EU) - Subprocessor — Sentry | Application error monitoring · Germany (EU). Configured not to send personal data. - Subprocessor — Anthropic (Claude) | The Rapi AI assistant, only if you top up credit and enable it · United States — an Article 9 KVKK transfer - Subprocessor — Meta Platforms Ireland Ltd. | WhatsApp Business and Instagram messaging, only if you connect those channels · Ireland, with onward transfer to the United States. Message content and the other party's number or account pass through Meta's infrastructure. ##### Where the legal counterpart of this page lives Every technical statement on this page has a legal counterpart, and we wrote those out one by one on separate pages. The full list of parties that touch your data is in the subprocessor table above; who each transfer goes to, to which country, and on what legal basis is set out one by one in Sections 8 and 13 of our Privacy Policy. The obligations we take on contractually, and the limits of each one, are on the Terms of Service page. Our KVKK Privacy Notice covers the notice we give for data that reaches us through the forms on this site. During an enterprise evaluation, the same team that builds the product fills in your security assessment forms; if you ask about something beyond this page, we answer it in writing. ##### What each plan covers, on one page Three tiers, a scope table and separately priced items — with the numbers. Scope and any setup fee are worked out in the discovery call and shared in writing. See pricing We publish the figures rather than asking you to request them. ##### Frequently asked security questions. - Where exactly is our data kept? | In the European Union, in three locations: the database in Helsinki (Finland), the files and media you upload in Frankfurt (Germany), and database backups in Falkenstein (Germany). We have no component in Turkey and no region-selection feature. Seen from a company in Turkey this is a transfer abroad within the meaning of Article 9 of Law No. 6698; we establish the basis for that transfer together with you during the contract process and give you in writing which component sits in which country. The full list of parties that touch your data is in the subprocessor table on this page; the legal basis for each transfer is set out in Sections 8 and 13 of our Privacy Policy. - Do you claim GDPR compliance? | We do not make that claim, because we have not measured it: we hold no GDPR certification and have been through no external compliance audit. What we can state is concrete, and it is what a legal team usually asks first — where the data sits. Your database is in Helsinki (Finland), your files in Frankfurt (Germany), your backups in Falkenstein (Germany); all three are inside the European Union. Hosting and storage sit inside the EU; Anthropic (US), Cloudflare (a US company) and Meta (Ireland/US) do not. Anthropic applies only if you enable Rapi, Meta only if you connect WhatsApp or Instagram. The subprocessor table on this page names every party that touches your data and gives the country for each one, including outbound email through Amazon SES in the Frankfurt region. - Do you sign a data processing agreement (DPA)? | We do not publish a data processing agreement, and there is no DPA document on this site to download. We are not going to describe a document we have not written. What exists today is this: the contractual counterpart of everything on this page — who processes your data, in which country, and on what basis the transfer abroad is made — is drawn up with you during the contract process, and we put the details in writing during an enterprise evaluation. If your procurement process needs a signed data processing agreement before a technical evaluation can begin, raise it at the first call: it is a legal step, not a product setting, and it is better on the table from the start than discovered late. - Where does the Rapi AI assistant send our data? | Rapi is off by default; to use it you have to top up credit on your account separately. Until you do, none of your CRM data is sent to any AI provider. Once you enable Rapi, the record content relevant to the question you ask is sent to Anthropic's Claude model in the United States — a second transfer abroad under Article 9 of KVKK, separate from the hosting in Finland, and one we state in our privacy notice. Anthropic commits not to use data sent through its API to train models. - Can another customer see our data? | Not your CRM records. Every customer runs in its own separate database; data is not filtered by company ID in a shared table. The application picks which customer's database a request goes to from the web address it arrives at; automated tests check that a token issued for one customer is rejected at another customer's web address. Against that, we make no claim of a separate server, customer-specific hardware or a customer-specific database password: what we state is separation at the database level. · There is one exception and we state it explicitly: the application's technical error logs are kept in a single table shared by all customers, and an entry can contain personal data from the request that failed. Those logs are kept only for fault diagnosis; they are not your CRM content. - Can Rapitek staff reach our data? | Access to customer data is limited to authorised personnel. We do not say "nobody ever looks at your records" — we have not measured that, and we do not commit to something we have not measured. Here is what we did measure: when an error occurs, the application writes the trace to an error log table shared by all customers, and that table can hold the user's email address, IP address and the body of the request; this is the place the support and debugging flow reads. Against that, the field changes users make to existing records inside the application are written to the audit trail, and you see that trail too. Operations run directly on the database are not written to this trail. During an enterprise evaluation we share our access policy in writing. - Can we see who changed what? | Partly. A separate history record is kept for every field change users make to an existing record: which user, when, the old value and the new value (for protected fields, only a marker instead of the values). The record's initial creation and some bulk updates the system makes in the background are not recorded. For record deletions, user and permission settings, automations and background processes, the recorded user may not be the person who actually made the change. The history is shown in the History tab on record screens and can be queried field by field from the API; an admin can set a retention period, but expired history rows are only marked as deleted and the old values stay in the database. Field history is on by default across every object that ships in a standard install. - Will you tell us if there is a data breach? | Yes. Our breach process is built on Law No. 6698: notification is made to the Turkish Personal Data Protection Board and to the individuals concerned within the period and in the manner that Law requires. Because you will have your own notification obligation as the data controller, you are informed without delay. Two limits, stated plainly: we do not give a contractual notification deadline of our own, and our process is not written against a second breach-notification regime in addition to Law No. 6698. If a fixed deadline or a particular regime is one of your procurement requirements, bring it to the call and we will tell you what we can commit to. - Do you hold a security certification? | No. We hold neither an ISO 27001 certificate nor a SOC 2 report — and we will not claim one until we have it. We do not use in-between phrases such as “we are in the certification process” or “we are compliant with the standards” either. If you have a requirement for a certified supplier, it is worth knowing that at the start of your evaluation. Against that, the same team that builds the product fills in your enterprise security assessment forms and walks through the architecture on a screen share. - Do you give a written uptime commitment? | No. We publish no uptime percentage; we do not measure uptime with an independent external monitoring service, and we do not publish a figure we have not measured. We give no written response-time commitment either. If a guaranteed service level is one of your requirements, let us talk about it at the start of the evaluation; every obligation we take on contractually, and the limits of each one, is written out on our Terms of Service page. - Have you had an independent penetration test? | We have no independent penetration test report, and we do not say we have had one done. With the organisations that ask for a security assessment, we go through that process together in a call. - Can a record deleted by mistake be recovered? | Deletion is soft: the record does not leave the database at once but moves to the recycle bin, from where it can be restored one at a time; bulk restore does not work today. Restoring is open to the owner with edit rights and to any user who can edit all records (admins included); which profiles have these rights depends on your setup. The automatic clean-up that should permanently delete records from the bin after 30 days has never run, so records deleted over 30 days ago are still there. An authorised user can permanently delete records from the bin; evidence and consent records are protected from permanent deletion. To have attached files and field history deleted, write to our support team; this cannot be undone, although copies remain in backups until those backups are deleted. - What happens to an employee's data when they leave? | Records belong to the company, not to the user. When a user account is closed, the records they created stay in place and can be reassigned to another owner; the account can no longer be used to sign in, its API and mobile access tokens are revoked, and the closure is recorded with its date in the user's change history; however, that history entry does not currently show who actually made the change. - Can we get our data whenever we want? | Yes. You can export your data in standard formats, and you can also pull it programmatically through our REST API, which covers the 183 business objects that ship in a standard install. If you decide to leave, we charge no extra fee for data export; this is written into our Terms of Service. - Who answers support requests? | There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. The same team fills in your enterprise security assessment forms and walks through the architecture on a screen share. We give no written response-time commitment. - Can you support our teams in other countries? | Support is provided during Turkish business hours. If you have teams in other time zones, let us discuss the scope together in a call. ##### Ask our team your security questions. We fill in enterprise buyers' security assessment forms and walk through the architecture on a screen share. A technical conversation, not a sales call. Request a call The team that builds the product answers your questions ### [SEV Foundation Customer Story | Rapitek CRM Projects](https://rapitek.com/en/sev-foundation-customer-story) How a foundation running ten schools, a hospital and a publishing house brought alumni, donations and scholarships into one system. Customer story · Non-profit #### SEV: alumni, donation and scholarship data moved into one system. Founded in 1968, the Health and Education Foundation runs ten schools, a hospital and a publishing house. Records for thousands of alumni, donors and scholarship students were not kept in one place. Let's talk about a similar rollout Other customer stories The organisation - 1968 | Founded - 10 | Schools it runs - 1 | Hospital, plus one publishing house - NGO | Non-profit organisation The project ##### What was there, what we built, what changed. - The challenge | Alumni data, donation tracking for alumni, scholarship tracking for students and contact details — all kept in separate places, making updates and checks harder every year. The foundation needed a modern, cloud-based data management solution. - What we built | From the implementation onwards, development, new suggestions and problem-solving ran together. The system was adapted to the foundation's own way of working, with ease of use as the priority. - The result | Daily workflows became markedly easier in terms of data analysis and data management. Donors started receiving faster responses and the relationship with supporters strengthened. In the foundation's own words, the biggest change came in data analysis. In the customer's own words Our foundation needed a cloud-based software system for data management. Rapitek is a company that is careful and attentive in understanding our wishes and needs; they also translated our requirements into the system very well. When we have new requirements, they support us with extremely fast and thorough solutions. As SEV, we are highly satisfied with working with Rapitek. Meryem Boğa Project and Resource Development Manager, Health and Education Foundation Scope ##### What was built in the project? Scope is project-specific; in every rollout it is defined together in the discovery call. Area | What was done - Alumni records | Alumni data and contact details were brought onto a single record - Donation tracking | Donations from alumni were attached to the donor record - Scholarship tracking | The scholarship students' process became trackable in the system - Data analysis | The area the foundation itself points to as the biggest gain - Ease of use | Screens were simplified around the daily flow of the foundation's staff ##### This project belongs to our Salesforce era This implementation belongs to Rapitek's Salesforce implementation era; afterwards we built our own product, Rapitek CRM. Our discipline around setup, data migration and training comes from the same team — only now on our own platform. ##### How many separate places does your organisation's data live in? In a 30-minute discovery call we'll map your existing records, your process, and how they would move into one place. Request a demo 30 minutes · No obligation · The call is held in Turkish ### [Shopify Integration: CRM Connection | Rapitek CRM](https://rapitek.com/en/shopify-integration) Shopify customer and order data moves into the CRM; repeat sales, consent records and wholesale run on one record. We build the link with REST API and OAuth2. Integration · Shopify store #### Your Shopify store makes the sale; the CRM knows the customer. Products, cart and checkout run in Shopify; the buyer, repeat sales and wholesale enquiries are recorded in the CRM. We build the connection ourselves with REST API, OAuth2, webhooks and import — and we work the scope out together during discovery. Request a demo Schedule a discovery call ##### You know your store; you do not know your customer Shopify does its own job well: storefront, cart, checkout and orders all run in one place. Here is where the mechanism splits: store software records the order, not the relationship — there is no field there to hold the relationship in. These are the five problems we have seen in our own projects with brands that sell direct: - The customer list is an order list. Who has talked to you before, what they complained about and what they said no to is not written there. - When a new collection launches, who gets told first is a guess; the segment definitions live in the marketer's head. - A high-value buyer and a one-off buyer get the same treatment; personal follow-up falls to no one. - Wholesale and corporate enquiries do not come through the site; they land in an inbox or a DM, the quote stays in a file, and no one follows up. - Permission-based messaging runs in a separate tool; the record of when consent was given, and with what wording, gets looked for on audit day. None of this is a shortcoming of the store software; store software manages the sale, not the relationship. The right setup is to leave the storefront in Shopify and move the customer side into the CRM. ##### How the connection is built — and why we are not in the Shopify App Store There is no out-of-the-box module for Shopify and we will not say there is. The connection is built as an integration project whose scope is set in the discovery call, using REST API, OAuth2, webhooks and import/export. We also have no app published in the Shopify App Store; we cannot say “install it from the store and it works”. Rapitek is not an e-commerce platform. Storefront, theme, cart, checkout, stock and shipping stay on the Shopify side; we take over none of them. What the CRM adds is the customer side: the buyer's record, the communication history, repeat sales, consent status and wholesale enquiries. Let us be explicit about direction too, because this is where things are easily overstated: - From outside into the CRM — order and customer data is written to the CRM's REST API; access is authorised with OAuth2 and no user password is shared. The layer that does this writing is the integration project itself. - From the CRM outwards — the outgoing webhook infrastructure is complete in the product: calls are signed, failed calls are retried and the target address is verified. - Via file — a four-step wizard: upload, map fields, preview, run. 100,000 rows per job, 25 MB per file, more than 75 objects. The proof that this is not bluff lies in how the product itself is used: in one live customer installation today, a third-party ERP integrator reads and writes records over that same REST API. We do not name the customer or the integrator because we do not have permission to publish their names; what we are stating is a measured fact. This is a single installation, not a case list. We described our general approach on the integrations page, and how the same framework is set up for a store on your own server on the WooCommerce integration page. A concrete scenario ##### Friday, 4 p.m. — the new collection drops on Monday; who gets told first? - The segment is picked from records, not from guesswork | People who bought twice, people who spent above a certain amount, people who have not come back for six months — the filter runs on the fields of the customer record, not on the marketer's memory. - Consent status is visible on the same screen | People with and without commercial electronic message consent are separated. Consents are synced two-way with İYS through an authorised integrator; the wording, the version and the time of the consent are held in the data model. - The announcement channel is chosen per customer | If your own WhatsApp Business account and your own Verimor SMS account are connected to the CRM, sending happens through the CRM. You are invoiced directly; we do not resell message bundles in between. - Replies land on the record, not on someone's phone | A reply to the announcement lands in the shared inbox and is logged on the same customer record; first-response and resolution targets are tracked, and paused and resumed against the business-hours calendar. - Wholesale questions are separated from retail | Someone who says “I want to sell this in my own shop” moves onto the corporate track: an opportunity is opened, a price list is selected, the quote comes out as a PDF and the approval process runs. - Campaign results are read channel by channel | Which channel a record came from is tagged in the source field; which announcement brought business on which channel is visible in tabular and summary reports, and can be placed on a dashboard. ##### Flows that can be built between Shopify and Rapitek CRM - Moving customer and order data into the CRM | Customer and order records in Shopify are moved into the CRM through the REST API or the four-step import. The matching key and the frequency are defined in the written scope. - Repeat-sales and customer-value fields | Order count, last order date and total amount are written onto the customer record; a task can be opened for the owner when a customer crosses a threshold. - Consent records and İYS sync | Commercial message consents are synced two-way with İYS through an authorised integrator; the consent evidence chain — wording, version, time, IP, source address — sits in the data model. - Wholesale and dealer track | While retail sales stay in Shopify, wholesale enquiries run in the CRM as opportunities: price list, quote PDF, approval process and won/lost reason. - Multi-currency sales and reporting | If you sell abroad, quotes and reports run in different currencies; rates are refreshed daily. On the day we measured, 21-23 currencies were up to date in eight tenants out of eight. - Signed notifications from the CRM outwards | When a record is created or changed, a signed webhook goes to your system; failed calls are retried and the target address is verified. Choosing a method ##### Which method, and when? The method is chosen together during discovery, according to your store's volume and how fresh the data needs to be. Method | What it gives you | When it is chosen - Import (Data Hub) | The customer and order export taken from Shopify is transferred in four steps: upload, map fields, preview, run. Export is done in the same module; we have not measured its limits | Migrating initial and historical data; when periodic freshness is enough - REST API (183 business objects, each with its own endpoint) | An event on the store side is written into the CRM as a record; every object has its own data and schema endpoint, access is authorised with OAuth2, and batch and composite requests are supported | When a continuous flow is wanted; the layer that does the writing is built within the project scope - Outgoing webhook | Events in the CRM are delivered to the external system with a signature; failed calls are retried | When something that happens in the CRM needs to trigger the store or ERP side - Third-party developer | The agency that built your store, or your own developer, can write the connection themselves using the same REST API; we provide the schema, the OAuth2 access and the field mapping table | If you already have a team managing the Shopify side What we can say ##### What we verified — and what we could not verify - Signed | Outgoing webhooks are signed; failed calls are retried - 183 | Business objects in the REST API - 0 records | Sales sequence table empty in 8 of 8 installs — no abandoned-cart flow promised - 21-23 currencies | Currencies up to date in eight of eight tenants on the day we measured Rollout ##### How is the Shopify connection put live? - Discovery | We work out your store's volume, your customer count, the state of your historical data and whether you have a wholesale side. If an agency built your store, we recommend they join this call. - Scope, field mapping and method | Which data flows which way and how often, and what the matching key will be, are settled. The field mapping table, the scope and any fee are shared in writing. - Configuration and test migration | Customer fields, channel lists, consent fields and permissions are set up; a test migration is run with a sample export, duplicate records are weeded out and the mapping is confirmed on screen. - Training and go-live | Team training and close follow-up in the first week. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. ##### Our limits: what we do not promise on this page There are six things that are easy to overstate in an e-commerce context, and we rule them out by name. The refusal itself is the most important part of this page. - We do not promise stock sync. We do not say “your stock will be in sync with the store”; authority over the stock record stays in Shopify and in your warehouse system. - We do not say the order → invoice → collection chain will flow by itself. The chain is built into the product, but we do not think it is right to sell it as an automated accounting flow. - We do not promise manufacturing or MRP automation. Bills of material and production line definitions exist in the product; we cannot point to a reference for work-order execution today. - We do not build abandoned-cart automation. The sales sequence table in the product is empty in 8 measured installations out of 8; we do not sell an automation we cannot show working. For an abandoned cart, the route we recommend is Shopify's own tools or a marketing tool built for that job. - We do not do shipment tracking. The tracking number is a plain text field and no courier service is called. - Rapitek is not an e-commerce platform. Storefront, theme, cart, checkout and returns stay on the Shopify side. If you are looking for store software, we are not the right address; if you are looking for a CRM to manage the customer side, we are. We wrote the reason for the first three, and “what can be done instead”, line by line in one place: the three things we do not promise. We do not repeat it here, so that we do not end up writing two different sentences in two places. One more thing: we have no app published in the Shopify App Store. We cannot say “install it from the store and it works” — the setup is work we do ourselves. Data location: your data is held in the European Union — the database in Helsinki (Finland), the files in Frankfurt, the backups in Falkenstein (Germany). We have no component in Turkey and we have no such thing as a region-selection feature. This is a transfer abroad within the meaning of KVKK art. 9; we establish your basis for the transfer together during the contract process. The detail is on the security page and in the KVKK privacy notice. Certification: we have no ISO 27001 or SOC 2 certificate, and we will not claim one until we have it. We do fill in your enterprise security assessment questionnaires and describe the architecture in writing. ##### Plan prices are out in the open; scope comes out of discovery The scope of the Shopify connection, and any fee for it, is worked out in the discovery call and shared in writing. Plan prices and the separately priced items, on the other hand, we publish on a single page, with the numbers. See pricing Three plans, a scope table and the separately priced items, on one page. FAQ ##### Frequently asked questions about the Shopify integration - Is a Shopify–CRM integration possible? | Yes — not with an out-of-the-box module, but as an integration project with a defined scope. The connection is built with REST API, OAuth2, outgoing webhooks and import/export. Which of your customer, order and consent data flows which way, and how often, is worked out in the discovery call and shared as a written scope. - Do you have a ready-made app in the Shopify App Store? | No. We have no app published in the Shopify App Store and we will not write as if we did. What we do have is a documented interface: the product ships out of the box with 183 business objects, and each is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there is OAuth2, signed outgoing webhooks and a four-step import/export wizard. The connection is built on top of these, specifically for your store. - Can you build abandoned-cart automation? | We cannot say that we do. The sales sequence table in the product is empty in 8 measured installations out of 8; that is, we cannot show this feature working in a real installation, and we do not sell what we cannot show. For an abandoned-cart reminder the right tool is Shopify's own solutions or a marketing tool built for that job. What the CRM adds is the relationship after the purchase. - Which way does data flow from Shopify to the CRM? | There are two separate routes and they should not be confused. Writing from outside into the CRM happens over the CRM's REST API and is authorised with OAuth2; the layer that does this writing is the integration project itself. Notification from the CRM outwards goes through the signed outgoing webhook that is ready in the product; failed calls are retried. The third route is the file route: the four-step import wizard. - Can we transfer our Shopify customer list into the CRM? | Yes, and this is the starting point we recommend. You export from Shopify as CSV and import it with Data Hub's four-step wizard: upload, map fields, preview, run. A suggestion is offered for the field mapping, and you confirm the mapping on screen. 100,000 rows per job, 25 MB per file. We do the first migration ourselves as part of setup. - Shopify has its own customer panel — why do we need a CRM? | Because the two answer different questions. The store panel answers “what was sold”; the CRM answers “where does our relationship with this person stand”. Conversation history, consent status, open enquiries, the quote process, the owner and channel attribution are the CRM's territory. On the wholesale side the store panel is not in play at all: quotes, approvals and price lists have to run somewhere else. - Our wholesale and dealer side is not in Shopify. Can that run in the CRM too? | Yes, it can. A wholesale enquiry is opened as an opportunity, a price list is selected, the quote comes out as a PDF and the approval process runs; quote → order conversion is a ready-made action in the product. You edit the quote template yourselves. The retail side carries on staying in Shopify. - We sell abroad as well. Do different currencies and languages work? | They do. The product is multi-currency and works with the daily TCMB rate; on the day we measured, 21-23 currencies were up to date in eight tenants out of eight. Quotes and reports work in different currencies. The interface texts sit in your own database, an administrator edits every string from the screen and no code deployment is needed. Language is chosen per user. - Will our stock work in sync with Shopify? | We do not promise real-time stock synchronisation. Authority over the stock record stays in Shopify and in your warehouse system; a stock mirror fed from the CRM produces two numbers in two places that do not agree. We wrote the reason, and what can be done instead, line by line in the limits section of the integrations page. - Does an order turn into an invoice and a collection in the CRM? | We do not say it turns by itself. The order → invoice → collection chain is built into the product and can be switched on or off per tenant, but we do not think it is right to sell it as an automated accounting flow. Rapitek CRM does not issue e-Fatura or e-Arşiv documents and is not a GİB private integrator. - Do you connect the payment side as well? | The payment flow in Shopify stays in Shopify; we do not take it over. On the CRM side, the payment adapters built into the product are for iyzico and PayNkolay. We cannot point to a reference for a live collection flow today, so we do not say “we take live payments”. Moving payment or collection information into the CRM as a field, on the other hand, is a piece of work with a defined scope. - What does the Shopify integration cost? | We do not put a number on this page, because the fee depends on the scope: the number of records to be moved, the direction of the flow, its frequency and the development needed on the store side. After the discovery call we share the scope and the fee in writing. A project-specific integration is a separate line item outside the plan price. - How long does the setup take? | We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. The setup consists of these steps: discovery, configuration, data migration, training and go-live. An import-based store flow is built within that plan; the scope of API-based work that needs a continuous flow is settled in the same discovery. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We have no component in Turkey and we do not offer region selection. This is a transfer abroad within the meaning of KVKK art. 9; we establish its basis together during the contract process. Your CRM data is held in a separate database that belongs to you. ##### Related pages - Integrations | An overview of integration: which connection is live today, which ones we build on request, and the reason for the three things we do not promise. - WooCommerce integration | How the same framework is set up for a store on your own server; choosing a method for installations that are not exposed to the outside. - Netsis integration | The ERP side behind the store: account, balance, order and invoice information showing up on the sales screen. ##### Let's pin down your Shopify flow in 30 minutes In the demo call, let's talk through how your customer and order data will flow into the CRM and how your wholesale side will be separated out — on your own store. Request a demo The scope of the setup, and any fee for it, is worked out in the discovery call and shared in writing. ### [Slack Integration: CRM Notifications & Webhook | Rapitek CRM](https://rapitek.com/en/slack-integration) CRM events reach your Slack channel via a signed outgoing webhook; infrastructure complete in the product. Measured: 0 webhook subscriptions in 24 tenants. Integration · Slack #### If you run on Slack, your CRM tells Slack. The infrastructure that carries CRM events into your channel is ready in the product: a signed outgoing webhook, retry on failed calls, and a notification node in the workflow engine. We decide together in the discovery call which event lands in which channel, and we set up the subscription. Request a demo Schedule a discovery call ##### Decisions are made in the channel, the record sits somewhere else In a team built around Slack, work is discussed in the channel. Decisions are made in the channel, news is heard in the channel, files circulate in the channel. The CRM, meanwhile, is a separate tab. Here is where the mechanism breaks: the news is produced in the channel, the record is kept somewhere else, and the only thing connecting the two is someone switching tabs. This is the picture we have seen in our own projects: - When a deal closes, the first to announce it is the person who writes in the channel. When the record gets updated remains a separate question; sometimes it never does. - The question "who is handling this customer?" is asked in the channel, answered in the channel and stays there. Three months later the same question is asked again. - A lead arriving from the web form waits until a rep opens the CRM. First response time comes to depend on who switched tabs and when. - Announcements are written by hand: someone sends the "this quote was approved" message if they remember, and does not if they do not. The notification depends on a person, not on a process. - Channel history looks like an archive but is not one: a message can be found by searching, but it is not attached to the customer record. - As the number of channels grows, so does the noise. Because it was never decided which events are genuinely worth announcing, either everything gets posted or nothing does. The need here is not to turn a chat app into a CRM. Let the record stay in the CRM and let the news reach the channel on its own — with the decision about which news arrives already made in advance. ##### One direction is ready, the other is a project — we keep them apart There is no out-of-the-box module for Slack, and we will not say there is. The connection is built as an integration project whose scope is set in the discovery call, using the REST API, OAuth2, webhooks and import/export. But there is something we have to write out separately on this page, because Slack is different from the other headings: the infrastructure the notification direction rests on is complete in the product today. The outgoing webhook is signed, a failed call is retried, the target address goes through SSRF validation, and this notification sits as a node in the visual workflow designer. So it is not something to be "written", it is something to be configured. Let us write this down too: to date not one of our tenants has switched it on. We measured it — across 24 tenants, defined webhook subscriptions: zero. That is why you will not read the sentence "our customers are connected to Slack" on this page. The capability exists in the product, the usage has not been measured; we do not want to confuse the two. The workflow engine it runs on, however, is in production: across flows defined in two tenants, 617 of 617 measured runs completed successfully. The reverse direction — creating a record in the CRM from the channel — is not equally easy, and we do not present it as if it were. That direction is written over the REST API. That the API really can be used from outside, we can state only through a borrowed fact: at a live customer installation, a third-party ERP integrator reads and writes records over that same REST API. We do not give the name because we do not have permission to publish it; what we are stating is a measured fact. This is a single installation, not a list of cases. We described the same framework as it applies to an ERP on the Netsis integration page, and our general approach on the integrations page. A concrete scenario ##### Friday 17:20 — the week is closing, the sales channel is open. Once the connection is in place, this is what changes: - A won deal lands in the channel on its own | On the deal-won event, a signed notification goes to your channel. What announces the news is the record itself, not a person; nobody forgets to announce it, nobody announces it twice. - The notification arrives with the record's address | The message carries the fields you defined in scope — customer name, amount, owner — along with a link to the record. From the channel you reach the record itself in one step. - You decide which event goes to which channel | Sales, support and management channels can be fed separately. The event list per channel is defined during setup; noise is not turned down afterwards, it is limited from the start. - A new lead does not wait for a tab switch | A record arriving from a form or from the API lands in the CRM with its source tagged and is announced in the channel at the same moment. The first response no longer depends on someone opening the CRM. - If a notification cannot be delivered, it does not vanish silently | The call is signed; the receiving side verifies the signature and filters out forged notifications. A failed call is retried, so a temporary outage on the other side does not mean data loss. - Writing from the channel into the CRM is separate work, and is priced that way | If you want to create a record from a message in the channel, the route is the REST API and OAuth2. We do not offer this as an out-of-the-box feature; we build it as separate work whose scope is set during discovery. ##### The surface a Slack connection rests on - Signed outgoing webhook | On record-created and record-changed events, a notification goes to an external endpoint. The call is signed; the receiving side verifies the signature and filters out forged notifications. - Retry on failed calls | If the other side cannot respond at that moment, the call is retried. A temporary outage does not mean a notification that never arrives. - SSRF validation | The webhook target is validated; an endpoint pointed at the internal network is not accepted. This is the notification infrastructure's own security control. - Notification node in the workflow engine | The notification is a node in the visual workflow designer: conditions, filters and ordering are set up inside the same flow, and no code is written. - Records that arrive with a source tag | Which channel the record behind a notification came from is held in the source field. Which channel brings in business shows up in the report, not in the channel. - REST API and OAuth2 for the reverse direction | If you want to create records in the CRM from the channel, this is the surface you rely on: the product ships out of the box with 183 business objects, each published in the REST API with its own data and schema endpoint; access is authorised with OAuth2, and the field structure is read from outside with describe. Choosing a direction ##### Which direction is ready, and which is a project? On the Slack side, the direction ready today is CRM-to-channel notification. For the reverse direction and an embedded interface there is no out-of-the-box module; both are scoped separately. Direction | What exists today | How it is set up - CRM → channel notification | Signed outgoing webhook, retry, SSRF validation and the workflow node all work in the product | The subscription and the event-to-channel mapping are configured during setup; no code is written - Creating a record in the CRM from the channel | We have no Slack app, bot or slash command | Written over the REST API and OAuth2, as separate work whose scope is set during discovery - A CRM screen embedded inside Slack | None; we do not offer an interface that opens inside Slack | We do not offer it. The link in the notification takes you to the record itself, and the screen opens in the CRM - Logging a Slack conversation onto the customer record | None; the messaging channel list is closed — email, WhatsApp Business API, WhatsApp QR pairing and SMS | If you want the conversation recorded, the route that works today is the WhatsApp Business API and email. WhatsApp QR pairing is not an official API and carries the risk of the number being restricted; we do not offer it as a product promise What we can state ##### What we have verified - Ready | Outgoing webhook infrastructure: signed, with retry, with SSRF validation - 0 subscriptions | Webhook subscriptions defined across 24 tenants — we do not say anyone uses it - 617/617 | Workflow runs measured in two tenants; no failed runs - 183 | Business objects in the REST API - Closed channel list | The messaging channel list is closed; Slack is not on that list Implementation ##### How is Slack notification put into service? - Discovery | We work out which events should land in the channel and which channels will be fed. We recommend that whoever holds the right to add apps on the Slack side joins the call. - Scope and event list | The event-to-channel mapping, the fields to appear in the message and the noise limit are put in writing. The scope and the cost, if any, are shared in writing before work begins. - Configuration and test notification | The subscription is defined, signature verification is tested on the receiving side, and test notifications are sent with sample events. Retry behaviour is also observed at this stage. - Go-live and first-week tuning | The channel layout is settled together with the team. Notification volume is watched during the first week; if too much arrives, the event list is narrowed. Noise is a matter of tuning, not of fate. ##### Our limits: what we do not promise on this page The notification infrastructure being ready does not mean we can promise everything. We write out by name the things we do not promise. - We do not offer a Slack app, bot or slash command. There is no listing from us in the app directory, and we do not say there is. - We do not say "our customers are connected to Slack". We measured it: across 24 tenants, defined webhook subscriptions: zero. The capability exists, the usage does not; those are two separate sentences. - Slack conversations do not land on the customer record. The messaging channel list is closed: email, WhatsApp Business API, WhatsApp QR pairing and SMS. Today the route that ties a conversation to a record is the WhatsApp Business API and email. - We do not offer WhatsApp QR pairing as a product promise. The same inbox can also be connected this way, but the method is not Meta's official API and carries the risk of the number being restricted by Meta. The route we recommend is the official Cloud API; if you still prefer this one, we share the risk in writing and take the decision together. The details are on the WhatsApp integration page. - We do not say your stock will stay in sync. Authority over the stock record stays in your ERP or warehouse system. - We do not say the order → invoice → collection chain will flow on its own. The chain is set up in the product; we do not think it is right for it to be sold as an automatic accounting flow. - We do not promise manufacturing and MRP automation. Bill of materials and line definitions exist in the product; we cannot describe work-order execution with a reference today. We wrote the reason for the last three, and "what can be done instead", in a single place: the three things we do not promise. We do not repeat it here, so that we do not end up making two different statements in two places. Data location: your data is kept in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye, and we have no such feature as region selection. When you send a notification to Slack, the content of that message goes to Slack's own infrastructure; you decide which fields appear in the message when the scope is set. This is a transfer abroad under KVKK art. 9; we establish its legal basis together during the contract process. The details are on the security page and in the KVKK disclosure notice. Certification: we hold no ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### We put the number on the pricing page, not on this one The scope of Slack notifications, and the cost if there is one, are worked out in the discovery call and shared in writing. Plan prices we keep in one place — so that you never read a different number in two places. See pricing Three plans, a scope table and separately priced items, all on one page. FAQ ##### Frequently asked questions about the Slack integration - Does Rapitek CRM integrate with Slack? | Yes — in the notification direction, and we say this as a configuration job, not as a development promise. Events in the CRM are delivered to your channel through a signed outgoing webhook; the infrastructure works in the product, and the subscription and the event-to-channel mapping are defined during setup. The reverse direction, creating a record in the CRM from the channel, is separate work written over the REST API. - Does Rapitek CRM have a ready-made Slack app? | No; it would not be right to say there is one. There is no listing from us in the Slack app directory, and we have no bot and no slash command either. What we do have is a more general surface: a signed outgoing webhook, retry, SSRF validation and the notification node in the workflow engine. The connection is built on top of these. - Which events can be sent from the CRM to Slack? | Record-created and record-changed events can be notified; for example a deal being won, a stage change, a new lead and a quote approval. Which event goes to which channel, and which fields appear in the message, are defined during setup. This list is not fixed; it can be narrowed or widened later. - Can we create records in the CRM from Slack? | It can be built, but this is separate work and we do not offer it as an out-of-the-box feature. The route is the REST API and OAuth2: the product ships out of the box with 183 business objects, each published with its own data and schema endpoint — you can read the field structure from outside with describe. The scope — which message creates which record, how the fields are filled — is set in the discovery call and finalised in a written proposal. - Do Slack conversations land on the customer record? | No. The messaging channel list is closed and today consists of email, the WhatsApp Business API, WhatsApp QR pairing and SMS; Slack is not on that list. We do not offer WhatsApp QR pairing as a product promise: the method is not Meta's official API and carries the risk of the number being restricted; the route we recommend is the official Cloud API. If you want the conversation logged onto the customer record, the route that works today is the WhatsApp Business API and email. The job on the Slack side is to announce the event, not to carry the conversation. - Are the notifications secure, and can a forged notification be told apart? | The call is signed: the receiving side verifies the signature and filters out a forged notification that did not come from you. The target address additionally goes through SSRF validation, so an endpoint pointed at the internal network is not accepted. These are not controls we added; they are the notification infrastructure's own standard behaviour. - What happens if a notification cannot be delivered? | It is retried. If the other side cannot respond at that moment, the call is repeated; a temporary outage does not mean a notification that never arrives. If there is a persistent problem, it is a configuration problem at the endpoint defined during setup, and you talk to the team that built the connection — there is no ticket queue in between. - Can we send notifications to a tool other than Slack? | Yes. The outgoing webhook is not tied to a particular provider; it sends to any endpoint that accepts a signed notification. We described the Microsoft Teams side on a separate page. The only condition is that the endpoint address passes validation and checks the signature. - How many of your customers use the Slack connection? | As far as we know, none — and we do not want to hide it: across 24 tenants, defined webhook subscriptions: zero. So what we describe on this page is a measured capability of the product, not a measured usage. The day we can tell a customer story, we will write it here; until that day we will not. - Is the Slack connection included in the plan price? | The outgoing webhook and the workflow engine are built into the product; configuring the subscription during setup is within the scope of the installation. Project-specific development, such as creating records in the CRM from the channel, is scoped and charged separately. The scope and the cost, if any, are shared in writing before work begins; plan details are on the pricing page. - How long does setup take? | The notification side is a configuration job and comes into play within the CRM installation. If you want a flow that writes from the channel into the CRM, its scope becomes clear during discovery. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. - How do you limit notification noise? | In two places. First, scope: the event list is kept narrow from the start, and what gets announced is decision-grade events rather than every record change. Second, the workflow engine: because the notification is a node, conditions and filters can be placed in front of it — for example only deals above a certain amount. We watch the volume together during the first week and narrow it if needed. - Where is our data kept? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. The content of a notification sent to the channel, however, goes to Slack's own infrastructure; you decide which fields appear in the message when the scope is set. - Can we see it before buying? | There is no trial you can start on your own. First we run a 30-minute live demo; in that call we show how the notification node is built in the workflow designer. Afterwards, if you want to explore the product at your own pace, we open a time-limited demo account. ##### Related pages - Integrations | Which connection works in the product today, which ones we build on request, and the reason for the three things we do not promise. - Teams integration | The Microsoft-side counterpart of the same notification infrastructure; that page also states that Outlook and Microsoft 365 connections are not live. - Security | Which country the data sits in, the sub-processor list, backups, the audit trail, and what we do not offer yet. ##### Let us settle which events land in the channel in 30 minutes In the demo call, let us show how the notification node is built in the workflow designer using your own scenario, and let us determine the event list and the noise limit together. Request a demo The event list and the channel mapping are worked out in the discovery call and shared in writing. ### [CRM for SMEs: Customer and Sales Tracking | Rapitek CRM](https://rapitek.com/en/sme-crm) Customer record, conversation history, sales pipeline, quote PDF and dated follow-up tasks in one record; your Excel lists are imported during setup. From Excel to CRM #### Customer tracking, sales tracking and quote tracking — one system for SMEs The customer record, conversation history, sales pipeline, quotes and follow-up tasks in a single system. Tracking that is scattered across Excel files moves into one record structured around your process — we handle the setup, the data migration and the training. Request a demo Write to us ##### When customer tracking is kept in several separate places, it becomes unclear which information is current Customer tracking already happens somewhere in every company: an Excel file, notes on a phone, the salesperson's memory and WhatsApp conversations. The wound is that these pieces do not see one another. Here is the picture we have seen again and again in our own CRM projects: - Every salesperson has their own list; there is no answer to the question "which list is the current one". Two people can call the same customer separately. - There is no such thing as a follow-up date field — the "call next week" note sits in someone's head or on a sticky note; remembering is left to the individual. - The quote is prepared in Word, goes out by email and disappears there. "How many quotes did we send last month, how many were accepted" can only be answered by counting by hand. - Conversations stay on personal phones. When a salesperson leaves, the customer history leaves with them. - At the end of the month the manager collects files from everyone and merges the figures by hand. None of this is solved by a better Excel template. It requires a shared record, reminders and permissions — and that is exactly the job of customer tracking software. A concrete scenario ##### Tuesday, 09:15 — a new enquiry has just arrived from your website. - The enquiry becomes a record, together with its source | An enquiry arriving from a form, a phone call or WhatsApp is opened as a lead; its source (web, advertising, referral) is captured as a field. At the end of the month, which channel actually brought in customers is a report, not a guess. - The first call note and the next step on the same screen | The call note is written on the record and the next step is defined as a dated task. When the day comes it appears in the task owner's list; it is not entrusted to anyone's memory. - The opportunity enters the sales pipeline | As the conversation progresses the record becomes an opportunity: amount, expected close date and stage are clear. The manager sees the whole pipeline on a Kanban board — who is chasing what, and where each deal is waiting. - The quote is generated from the price list | Line items are picked from the product catalogue, a discount is applied, a PDF is produced and sent. The version and status of the quote stay on the record; no hunting for a Word file among attachments. - Quote follow-up is secured with a task | A task saying "ask about the quote in two days" is defined. If a revision is requested, a new version is opened on the same record; an accepted quote becomes an order. - The close is recorded with its reason | If it was won, why it was won; if it was lost, to whom and why it was lost, is captured as a field. Three months later, the question "was it price, product or speed" is answered with data. ##### The building blocks for customer, sales and quote tracking - Customer record and interaction history | Company, contact, phone, email and any custom fields you need on a single record. Calls, notes, meetings, emails and WhatsApp conversations accumulate beneath the record with a time stamp; the answer to "what did we last talk about" is on the screen. - Sales pipeline and Kanban | Opportunities move stage by stage: amount, expected close, owner. The stages are configured around your process — we do the setup. The pipeline can be viewed as a list, a summary or a Kanban board. - Tasks and reminders | A dated task is attached to every record: call, ask about the quote, send the sample. When the day comes it is in front of the task owner. Follow-up moves from people's memory into the system's calendar. - Quote generation and tracking | Line selection from the product catalogue and price list, discounts, PDF output and status tracking. An accepted quote becomes an order. Multiple currencies are converted daily using TCMB exchange rates. - WhatsApp shared inbox | The team messages from the company's single business number; messages land in the team inbox and are written onto the customer record. The connection route we recommend is Meta's official WhatsApp Cloud API; QR pairing is not the official API and carries the risk of the number being restricted by Meta. We choose the method together during setup. - Reports and dashboards | Conversion by source, waiting time in a stage, quotes and closes per salesperson. Table and summary reports come ready; matrix and joined report types are supported as well. A drag-and-drop dashboard designer — without writing code. ##### Mobile in the field, and the connection to your existing software ###### Follow-up from the phone Customer tracking does not end at the desk. Both our iOS and Android apps are live and they ship with a Turkish interface; as you leave a visit, the note, the task and the opportunity update are made from the phone, and visit check-in with GPS is supported. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp and Instagram messages are managed in the single inbox inside the app. We gather the details on the mobile app page. ###### Email, calendar and other systems You can connect your own Gmail account with OAuth and send from inside the CRM; the email that goes out is linked to the relevant record. The connection covers sending and calendar sync — inbox reading is switched off, so this is not two-way inbox sync. Calendar sync is two-way and today works with Google Calendar; Outlook and Microsoft 365 connections are not live. There is no out-of-the-box module for your ERP and accounting software — it would not be right to say there is. Because access differs from one installation to the next, a single button that works the same way in every installation cannot be built. The connection is established as follows: through REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data will flow in which direction is clarified on the integrations page and in the discovery call. From Excel to CRM ##### Where does customer tracking break down today? Topic How it works today | After setup - Follow-up reminder | None — in your head or on a sticky note | A dated task; when the day comes, in its owner's list - Working at the same time | Version clashes, "list_current_v3_FINAL" | One shared record, simultaneous access - Conversation history | Cell comments and memory | Calls, notes, emails and WhatsApp on the record, time-stamped - Quote | A document template, manual version tracking | A PDF from the price list; status and version on the record - Mobile access | Scrolling a spreadsheet on your phone | iOS and Android apps live, with a Turkish interface - Permissions and handover | Wherever the file went; it leaves with the departing employee | Role-based permissions; records stay with the company - Reporting | A manual pivot at the end of the month | Ready report types and live dashboards - Data security | Copies circulating by email | TLS in transit, two-step verification, a separate database per customer Verifiable figures ##### Measured data, not a marketing sentence - 200+ | Enterprise CRM projects delivered during the Salesforce era (before Rapitek CRM) - 277 | Custom fields added by 19 tenants without writing code - Every 6 hours | Automatic backup frequency; backups are copied to a separate country - 183 | Business objects in the REST API — each with a data and a schema endpoint - EU | Data location: Helsinki (Finland), media in Frankfurt, backups in Falkenstein Implementation ##### How does the move from Excel to CRM work? - Discovery and analysis | We map out your existing Excel files, your sales flow and your team roles together. This is where it is decided which fields are genuinely needed — not every column that has piled up in Excel, only the ones that do a job. - Configuration | Fields, sales pipeline stages, the quote template, list views, the permission matrix and reports are set up around your process. No code is required; setting it up well takes expertise, and that part we do. - Data migration | The customer, contact and product records in your Excel files are imported; duplicate records are weeded out and columns are mapped to CRM fields. Your old data is in the system from day one. - Training and go-live | Training for the team and the manager, close support in the first week, then ongoing support. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The scope of the setup and its cost, if any, is shared in writing before work begins. References ##### From our CRM implementation projects: teams that moved scattered data into one system - At Anatolia Tile we have attached great importance to digital transformation in order to maintain our leading position in the global market since 1995. The CRM project we started with Rapitek completely transformed our sales processes. By bringing our customer data together on a single platform we increased our team's efficiency and accelerated our decision-making. Rapitek's sector experience and solution-oriented approach delivered results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Case study - With Rapitek's solution-oriented approach, we began the work needed to quickly complete the improvements to the Salesforce customisations and integrations we were using. With the improvements made, duplication of data was prevented and we increased the efficiency of the system. | Ögetay Can | Sales Director | Petroyağ | Case study - Our foundation needed a cloud-based software system for data management. Rapitek is a company that is careful and attentive in understanding our wishes and needs; it also transferred our requests into the system well. When we have new requirements, they support us with extremely fast and thorough solutions. As SEV, we are very pleased to be working with Rapitek. | Meryem Boğa | Project and Resource Development Manager | SEV Foundation | Case study The references above belong to CRM implementation and integration projects carried out by Rapitek; they do not mean that those organisations use the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### Data location, KVKK and security — as they are A customer list is one of a company's most sensitive assets; where and how it is kept should be clear. - Your data is held in the European Union. The database is in Helsinki (Finland), media files in Frankfurt, and backups in Falkenstein (Germany). We do not say that the data is held in Türkiye, because it is not. - This means a transfer abroad under Article 9 of the KVKK. For this reason a disclosure notice is presented on our forms; the legal basis for your transfer is established together during the contract process. If you switch on the AI features, that request goes to the United States — a second transfer, which your disclosure notice has to cover separately. - TLS is used in transit. Passwords are hashed one-way; two-step verification secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. A separate database is used for each customer's CRM records — not a row filter in a shared table. Technical error logs sit outside that scope; they are kept centrally, and each tenant sees only its own entries. - There is role-based authorisation; who sees which record is defined during setup. You can export your data and take it with you whenever you wish. We do not hold an information security certificate and we do not claim to. Every technical detail we state has its counterpart in the system; we answer your security questions in writing before setup. ##### We put the figure on the pricing page, not on this one The scope of setup, data migration and training is not the same in every project; it is shared in writing after discovery. Plan prices we keep in one place — so that you never read a different figure in two places. See the pricing Three plans, a scope table and separately priced items on a single page. FAQ ##### Frequently asked questions about customer tracking software - What is customer tracking software? | Customer tracking software keeps customer information, conversation history, sales opportunities, quotes and the follow-up tasks to be done in one place. It replaces scattered Excel files, phone notes and email inboxes with a single searchable record system. Rapitek CRM configures this layer around your process and takes it live. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. - Why does customer tracking in Excel stop being enough past a certain point? | When one person is working, Excel may be enough; the problem starts when the team grows. There are no reminders — follow-up is held in your head. Working simultaneously in the same file produces version clashes. Conversation history is not kept; the answer to "what was last discussed" is in someone's memory. When a salesperson leaves, their file and the customer relationship leave with them. A CRM turns these four into record-keeping discipline: a dated task, one shared record, a time-stamped history and role-based permissions. - Can we migrate our customer list from Excel? | Yes; this is a standard step of the setup. The customer, contact and product lists in your Excel files are imported, duplicate records are weeded out and columns are mapped to CRM fields. Export is always open as well: you can take your data and leave whenever you wish. - What is the difference between sales tracking software and customer tracking software? | In practice they are two faces of the same system. Customer tracking follows the record and the history: who, what was discussed, what the next step is. Sales tracking follows the progress of the opportunity through the stages: the pipeline, the amount, the expected close, the win/loss reason. In Rapitek CRM the two are in the same data model — a single chain from the customer record to the opportunity and from the opportunity to the quote; you do not need to buy a separate programme. - How does quote tracking work? | The quote is prepared inside the CRM: line items are selected from the product and price list, a discount is applied, a PDF is produced. The status of the quote (prepared, sent, revision requested, accepted, rejected) is tracked on the record and a follow-up task is defined; if a revision is requested a new version is opened on the same record, and an accepted quote is converted into an order. The answer to "we sent the quote, then what happened?" appears in a report, not in someone's memory. - How much does customer tracking software cost? | The price is determined by the number of users and the plan selected; we publish the current plans openly on our pricing page. The items priced outside the plan price are written out there one by one as well; the scope of the setup and its cost, if any, is worked out in the discovery call and shared in writing. - Is there a free customer tracking programme? | We do not have a free version and we do not promise something that does not exist. There is no trial you can start on your own either; first we run a 30-minute live demo, and then, if you want to explore the product at your own pace, we open a time-limited demo account for you. Rapitek CRM is an enterprise system whose setup and configuration proceed with us; that is why the first step is not opening an account but seeing the product live with your own scenario. If you are a team of one or two, our honest advice is this: a disciplined Excel may be enough for a while longer. Rapitek CRM makes sense in businesses with at least 5 users and a sales or field team. - Can we track WhatsApp conversations? | Yes. The team messages from the company's single business number; messages land in the team inbox and are written onto the relevant customer record. Conversations that would otherwise scatter across personal phones stay with the company; when needed, someone else continues the conversation from where it was left. The connection route we recommend and set up is Meta's official WhatsApp Cloud API. QR pairing is also possible, but we do not present it as a product promise: the method is not Meta's official API and carries the risk of the number being restricted by Meta; if that risk materialises, your business number goes down. If you prefer this route, we share the risk in writing and take the decision together. - Is there a mobile app? | Yes. Both our iOS and Android apps are live and they ship with a Turkish interface; the field team updates the customer record, the note and the follow-up task from the phone, and visit check-in is done with GPS. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp and Instagram messages are managed in the single inbox inside the app; replying to Instagram from the mobile app has not yet been measured in a customer deployment. - How long does setup take and what does it include? | Setup consists of these steps: discovery and analysis, configuration, data migration from Excel or your existing system, team training and go-live. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The duration varies with team size, data volume and integration scope; the scope and its cost, if any, is worked out in the discovery call and shared in writing. - Where is our data held? | The database is held within the European Union, in Helsinki (Finland); media files are stored in Frankfurt and backups in Falkenstein (Germany). This means a transfer abroad under Article 9 of the KVKK; the basis is established according to the tiers in that article: first an adequacy decision, failing that appropriate safeguards, and exceptionally incidental cases. TLS is used in transit and a separate database is kept for each customer. - What size of team is it suitable for? | The scale we target is B2B businesses with at least 5 users and a sales or field team. The product is not a self-service tool; setup, configuration and training proceed with us. For single-person use the cost-benefit balance does not work out — we say that openly in the call too. In growing businesses, businesses with a sales team or businesses that go out into the field, the return on shared record discipline is concrete. ##### Related solutions - WhatsApp CRM | Messaging with the customer is not on a personal phone but in the team's shared inbox and on the customer record. - Field sales software | When the team is not at a desk: mobile records, visit tracking and field performance reports. - Real estate CRM | Portfolio records, criteria-based matching and viewing appointment tracking for estate agencies. ##### See your customer tracking live, with your own scenario In a 30-minute demo, let us show you the customer record, the sales pipeline and the quote flow according to your process — with sample data from your own Excel file if you like. Request a demo The scope of the setup and its cost, if any, is worked out in the discovery call and shared in writing. ### [Stripe and CRM: Carrying the Payment Record | Rapitek CRM](https://rapitek.com/en/stripe-integration) Stripe payment records are carried into the customer card as fields via REST API. Adapters in the product: iyzico and PayNkolay. No subscription engine. Integration · Stripe #### If you use Stripe, payment and renewal information appears on your sales screen. The amount, date and currency of the payment record in Stripe are carried into the customer card as fields via the REST API; the subscription renewal date enters the sales pipeline as an opportunity. We build the connection ourselves, as a project whose scope is determined during discovery. The payment adapters defined in the product: iyzico and PayNkolay. Request a demo Let's define the scope together ##### A company that asks about Stripe is really asking three things The Stripe question may come from companies that sell abroad and work with recurring revenue: software, agencies, training, subscription services. The question is not “do you have a Stripe logo”; underneath it sit three real needs: - “Has the customer paid?” When a rep goes into a renewal conversation, they do not know whether the payment went through; they have no access to the Stripe dashboard either, and it would not be right for them to have it. - “When does the subscription end?” The renewal date may be sitting in an Excel file or in one person's calendar. The mechanism is this: if the date is not tied to a record, there is nothing to warn anyone when it is missed. - “Who will hear about a failed payment?” Word of the customer whose card was declined stays on the finance side; sales finds out at the end of the month. Then there is the foreign-currency side: the price is in dollars or euros, the books are in Turkish Lira. The question of “how much this customer brought in” changes depending on which day's exchange rate is used. None of these three questions is solved under the heading “Stripe integration”. All three are solved by carrying information that has already formed in Stripe onto the sales screen. ##### The honest picture first: what is and is not in the product We do not have a Stripe connection and there is no subscription/billing engine inside the product; if you want to carry the payment record in Stripe into the CRM, that is a piece of work with a defined scope, over the REST API. Let us make that concrete, because we measured it: the only thing written for Stripe in the code base is a “later on” note — there is no working connection, no adapter and no configuration screen. In the same way, the subscription, recurring billing and credit-card collection model is not defined in the product either. Saying what really is defined is our job: there are two payment adapters in the product — iyzico and PayNkolay. They are configured with your own provider account. But we do not overstate here either: we cannot point to a live collection flow with a reference today, so we do not say “we take payments in production”. If you collect payments in Turkey, the right question is not “is it Stripe”, but “does one of these two adapters do the job for you”. What remains — and what really can be built — is this: the visibility of the payment record. Payment, subscription and renewal information formed in Stripe comes into the CRM as fields, via the REST API or a periodic import. The interface is ready: the product ships out of the box with 183 business objects and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there are OAuth2, signed outgoing webhooks and a four-step import/export wizard. As a separate fact: in one live customer installation today, a third-party ERP integrator reads and writes records over the same REST API; this is a single installation, not a list of cases. The general framework is on the integrations page. A concrete scenario ##### Tuesday 10:30 — the annual subscription ends in twelve days and nobody knows. Here is what changes when the payment record flows into the CRM: - The renewal date becomes an opportunity in the sales pipeline | The subscription end date sits on the customer card as a field and upcoming renewals are opened as opportunities. The renewal is tied to the sales pipeline, not to anyone's calendar. - The rep sees whether the payment went through, on their own screen | The amount, date and status of the last payment are written onto the customer card. The rep does not need access to the Stripe dashboard — not having it is the more correct arrangement anyway. - A failed payment opens a task | When a payment comes back failed, a follow-up task lands on the owner. The customer whose card was declined is reached the same day; it does not wait for the month-end report. - Foreign-currency amounts are reported at a single rate | The product is multi-currency and works with the daily TCMB rate; on the day of measurement, 21-23 currencies were up to date in eight of eight tenants. Dollar collections are totalled in a single currency in the report. - The customer's real value comes together on one card | The quote, the won opportunity and the amount collected are tied to the same record. The question “what did this customer bring in” is answered without merging two tables. - A customer whose subscription ends does not disappear | The reason for cancellation or non-renewal is recorded as a loss reason. How many customers left for which reason is read from a report, not talked about by guesswork. ##### We do not have a Stripe connection — what do we do instead? - Carrying the payment record onto the customer card | Amount, date, currency and payment status come into the CRM as fields, via the REST API or a periodic import. The authority over the money stays in Stripe; the copy in the CRM is there for the sales team to see. - Turning the renewal date into an opportunity | The subscription end date is held as a field; an opportunity is opened for upcoming renewals and an owner is assigned. This is not a billing engine — it is follow-up on the sales side. - Task generation on a failed payment | The rule that opens a task for the owner when failed or overdue payment information arrives is defined during setup. The CRM does not charge the card again and does not attempt collection; it only ties the follow-up to a record. - Multi-currency reporting | The system is multi-currency and works with the daily TCMB rate. Dollar and euro collections are reported in a single currency; 21-23 currencies were measured as up to date in eight of eight tenants. - Pointing you to the two adapters that really are defined | If you collect payments in Turkey, there are two adapters defined in the product: iyzico and PayNkolay. They are configured with your own provider account; going live is done together, within the scope of the setup. - Defining subscription fields without writing code | An administrator adds fields such as plan name, seat count, renewal date and payment method without writing code. Adding custom fields is standard in the product: today 277 custom fields in total are defined across 19 tenants. What exists, what does not ##### What exists and what does not on the payment and subscription side The left column states what is actually wanted when Stripe is asked about. The right column shows where that need is met. What is wanted | In Rapitek CRM | Where it is done - A built-in connection from your Stripe account to the product | No. There is no working connection for Stripe in the code base | In your Stripe account; carrying it into the CRM is built with the REST API, within a project scope - A subscription and recurring billing engine inside the product | No. The subscription, invoice and payment model is not defined in the product | In Stripe or in whichever billing system you use - The CRM charging the customer's card | No. Storing cards and attempting collection is not the product's job | In your payment provider - The payment amount, date and status being visible on the customer card | Yes. It is carried as fields via the REST API or a periodic import | Rapitek CRM — with a connection whose scope is determined during discovery - Tracking the renewal date and opening an opportunity | Yes. The field, the opportunity and task generation are defined during setup | Rapitek CRM - Taking payments through a payment adapter | Partly. The iyzico and PayNkolay adapters are defined in the product; we cannot point to a live collection flow with a reference today | Rapitek CRM — with your own iyzico or PayNkolay account, within the setup scope - Reporting foreign-currency collections at a single rate | Yes. Multi-currency and the daily TCMB rate work in the product | Rapitek CRM - Issuing an e-Invoice after the payment | No. Rapitek CRM is not a GİB private integrator and does not issue official documents | In your e-Invoice provider; the information can be carried into the CRM Implementation ##### How is payment visibility put into service? - Discovery | We work out which objects you use in Stripe — one-off payments, subscriptions or invoices — and which record they will correspond to in the CRM. We recommend that your finance lead join this meeting. - Scope, field mapping and direction | Which field flows in which direction and how often is written down. This flow is built one-way — from Stripe to the CRM. We do not recommend the CRM writing back to Stripe; the authority over the money stays in one place. - Configuration and test transfer | Subscription and payment fields, renewal opportunity rules and permissions are set up; a test transfer is run with sample data. Customer matching — email or tax number — is verified here. - Training and go-live | The sales team is walked through which field shows what. We do not commit to a duration before discovery; after the discovery meeting we give you a date, not a range. ##### Our limits: what we do not promise on this page This page already opened with an absence; let us set the limits out together again so that no item is left in a footnote. - We do not say “Stripe integration”. There is no working connection for Stripe in the code base. - We do not promise credit-card subscriptions and automatic billing. The subscription, invoice and payment model is not defined in the product; the CRM does not store cards and does not attempt collection. - We do not say “we take payments in production”. The iyzico and PayNkolay adapters are defined in the product, but we cannot point to a live collection flow with a reference today. - We do not say that the order → invoice → collection chain will flow by itself, we do not promise stock synchronisation and we do not promise production/MRP automation. We have written the reason for all three, and what can be done instead, in one place: the three things we do not promise. - We do not issue e-Invoices. Rapitek CRM is not a GİB private integrator; the details are on our e-Invoice page. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Turkey and we have no such feature as region selection. This is a transfer abroad under KVKK art. 9; we establish your legal basis for the transfer together during the contract process. The details are on the security page and in the KVKK disclosure notice. Card data: no card number or card data is carried into the CRM — this is not a preference, it is a rule. What is carried is the result of the payment: amount, date, currency, status. Certification: we do not have an ISO 27001 or SOC 2 certificate and we will not claim one until we do. We also do not do work that falls within PCI DSS scope, because card data never reaches us. ##### We put the number on the pricing page, not on this one The scope of the Stripe connection, and its price if there is one, are worked out in the discovery meeting and shared in writing. Plan prices we keep in one place — so that you do not read a different number in two places. See pricing Three plans, a scope table and separately priced items on one page. FAQ ##### Frequently asked questions about Stripe and Rapitek CRM - Does Rapitek CRM have a Stripe integration? | No. There is no working connection, adapter or configuration screen for Stripe in the code base; we will not say there is. If you want to carry payment, subscription and renewal information formed in Stripe into the CRM as fields, that is a piece of work over the REST API whose scope is determined during discovery. The flow is built one-way: from Stripe to the CRM. - Is there a ready-made Stripe module in Rapitek CRM? | There is no out-of-the-box module. The payment adapters defined in the product are iyzico and PayNkolay; Stripe is not on that list. The connection is built as an integration project whose scope is determined in the discovery meeting, using the REST API, OAuth2, signed outgoing webhooks and the four-step import/export wizard. - Is there subscription management in Rapitek CRM? | In the billing sense, no: the subscription, recurring invoice and payment model is not defined in the product. In the sales management sense, yes: plan name, seat count and renewal date are held as fields, upcoming renewals are opened as opportunities, an owner is assigned and it is reported. The two are not the same thing; we write them separately so they are not confused. - Can we take credit-card payments through the CRM? | The iyzico and PayNkolay adapters are defined in the product and are configured with your own provider account; going live is done together within the scope of the setup. Let us also write this down: we cannot point to a live collection flow with a reference today, so we do not say “our customers take payments from the CRM”. Stripe is not among these two adapters. - Can we track Stripe subscription renewal dates in the CRM? | Yes; that is also the starting point we recommend. The subscription end date is held as a field on the customer card; an opportunity is opened for upcoming renewals and an owner is assigned. How the date reaches the CRM — via the API or a periodic import — is settled in the scope. The moment the renewal enters the sales pipeline, it leaves the personal calendar and enters the report. - Does the CRM notify us when a payment fails? | When failed or overdue payment information is carried into the CRM, a rule can be set up that opens a follow-up task for the owner; the threshold and the owner are defined during setup. The CRM does not charge the card again and does not make a new collection attempt — it only ties the follow-up a person will do to a record. - Can we see dollar and euro collections in a single report? | Yes. The system is multi-currency and works with the daily TCMB rate; on the day of measurement, 21-23 currencies were up to date in eight of eight tenants. Amounts in foreign currencies are totalled in a single currency in the report. This removes the problem of the report changing depending on which day's rate is used. - We collect payments in Turkey; what do you recommend instead of Stripe? | The two payment adapters defined in the product are iyzico and PayNkolay; if you collect payments in Turkey, the right question is whether one of these two does the job for you. If you insist on another provider, our answer does not change: we look at what the other side's API allows, work out the scope and give it to you in writing. - Is card information carried into the CRM? | No. No card number or card data is carried into the CRM; what is carried is the result of the payment: amount, date, currency and status. This is not a preference but a rule, and it is written on the first line of the scope. Because card data never reaches us, we also do not do work that falls within PCI DSS scope. - Do Stripe invoices count as e-Invoices in Turkey? | This is a question for your financial adviser, not for us; we will not attempt to write a general rule. What we can say is this: Rapitek CRM does not issue e-Invoice or e-Archive documents and is not a GİB private integrator. The document goes on being issued in whichever system issues it today; its information can be carried into the CRM as fields. - What does this connection cost? | We do not put a number on this page, because the price depends on the scope: which Stripe objects will be carried, the number of fields, the frequency and the customer matching rule. After the discovery meeting we share the scope and the price in writing; for the duration, we give you a date, not a range. Plan scopes are on the pricing page. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Turkey and we do not offer region selection. This is a transfer abroad under KVKK art. 9; we establish the legal basis together during the contract process. Your CRM data is held in a separate database belonging to you. - Who does support come from? | There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. Support is given during Turkish working hours; if you have teams in different time zones, let us talk through the scope together in the meeting. - Can we see this connection before buying? | There is no trial you can start on your own. First we run a 30-minute live demo; after that, if you want to explore the product at your own pace, we open a time-limited demo account. The demo shows the standard state of the product; carrying the payment record over is done after purchase, within the scope of the setup. ##### Related pages - Integrations | Which connection works in the product today, which ones we build on request — and the reason for the three things we do not promise. - e-Invoice and CRM | The question that comes after payment: who issues the document, how its information reaches the CRM, which field is not in the product. - Netsis integration | The same framework on the ERP side: current account, balance and invoice information appearing on the sales screen. ##### Let's clarify your payment and renewal flow in 30 minutes In the demo, let us talk through your own scenario: which payment provider you work with, who tracks renewals today, and which fields need to be carried into the CRM. Request a demo No card data is carried into the CRM. The scope, and the price if there is one, are worked out in discovery and shared in writing. ### [Microsoft Teams Integration: CRM Alerts | Rapitek CRM](https://rapitek.com/en/teams-integration) CRM events reach your Teams channel via a signed webhook. Microsoft 365 email and Outlook calendar connections are not live today. Integration · Microsoft Teams #### If you use Microsoft 365, your CRM lets your Teams channel know. The infrastructure that carries CRM events into your Teams channel is ready in the product: a signed outgoing webhook, retries, and a notification node in the workflow engine. The Microsoft 365 email connection, on the other hand, is not live today. On this page we set out one by one what is ready, what is a project and what does not exist at all. Request a demo Schedule a discovery call ##### IT is asking about one thing, the sales team about another In a company that has moved to Microsoft 365, Teams is not a single application; it is the company's desk. Meetings happen there, files sit there, the team writes to one another there. When new software comes up for discussion, the question IT asks follows from that: does this thing come into our world? This is the picture we see in our own implementation meetings: - In the Monday meeting, last week's numbers are shown by screen sharing; nobody looks at the report on their own, and what was looked at disappears along with the meeting. - Sales news is typed into the channel by hand. The “we closed this one” message depends on one person remembering; if it is forgotten, there is no news either. - Correspondence with the customer sits in Outlook, internal correspondence in Teams, and the record somewhere else. The only way to move data between three windows is to copy it; what moves is not the record itself but a copy of the text. - Appointments are kept in the calendar but are not tied to the record in the CRM; the question “when did we last speak to this customer?” is answered by searching the calendar. - IT is asking about enterprise sign-in and permission management; the sales team wants notifications. The two sides ask different things in the same meeting, and the vendor says “yes” to both at once. This page splits that “yes” apart, one item at a time. On the Microsoft side there is something that can be built, and there are things that do not exist at all. We do not put the two in the same sentence. ##### Three separate sentences: what is live, what gets built and what does not exist There is no out-of-the-box module for Microsoft Teams, and we will not say there is one. The connection is built as an integration project whose scope is set in the discovery call, using the REST API, OAuth2, webhooks and import/export. In the notification direction the situation is better: the outgoing webhook infrastructure is complete in the product — signed, retried when a call fails, with the target address passing SSRF validation, and sitting as a node in the visual workflow designer. That is why getting a CRM event into your Teams channel is a job to be configured, not written. Let us add this too: to date not one of our tenants has switched it on — zero subscriptions defined across 24 tenants. The capability has been measured; the usage has not. On the Microsoft 365 side, email is not live today. The Outlook and Microsoft 365 connections are not open, so a Microsoft 365 mailbox cannot be connected to the CRM. We wrote the detail of this in its canonical place, on the email integration page, and we do not repeat it here. The calendar is not on this page, because it is not in the product either. There is no Outlook calendar sync: the Microsoft 365 connection is not live today, so neither the email nor the calendar side works. Calendar sync is specific to the Google side only. It would have been easy to put the calendar under a “Microsoft 365 integration” heading as well; we are not doing that, because a gap that surfaces on implementation day costs more than a sentence said before the sale. The reverse direction — creating a record in the CRM from Teams — is written over the REST API. We can say that the API really is usable from the outside on the strength of a measured fact: at one live customer installation, a third-party ERP integrator reads and writes records over that same REST API. We do not give a name because we do not have permission to publish one; this is a single installation, not a case list. The same framework applied to an ERP is on the Netsis integration page, and our general approach is on the integrations page. A concrete scenario ##### Monday, 09:10 — the weekly sales meeting is starting. Once the connection is in place, this is what changes: - The week's numbers are in the channel before the meeting | Closed opportunities and new leads land in the channel event by event. The meeting opens with making decisions, not with recounting the past. - The announcement no longer depends on one person remembering | On the opportunity-won event, a signed notification goes to the channel by itself. Nobody forgets to announce it; nobody writes the same news twice. - You go from the notification to the record itself in one step | The message carries the fields you defined in the scope — customer, amount, owner — and the address of the record. Everyone looks at the same record without waiting for a screen share. - Notification volume is limited by conditions | Because the notification is a workflow node, conditions and filters can be placed in front of it — for example only opportunities above a certain amount. The channel does not turn into a noticeboard. ##### The surface you rely on for the Microsoft side - Signed notification to the channel | On record creation and change events a notification goes to the external endpoint; the call is signed, and the receiving side filters out forged notifications by verifying the signature. - Conditional notification node | The notification is a node in the visual workflow designer. Which record is announced under which condition is defined without writing code. - Microsoft 365 email — not live | The Outlook and Microsoft 365 connections are not open today, so a Microsoft 365 account cannot be connected. Generic IMAP/SMTP is not supported either. - Authorisation with OAuth2 | Access is granted with OAuth2; no connection is made by sharing a user password. You can withdraw the permission just as you granted it. - Enterprise sign-in: OIDC yes, SAML no | OIDC is wired into the product and supported; we do not offer SAML. We also write that to date we have not had a single setup configured in production. - REST API for the reverse direction | If you want to create records in the CRM from Teams, this is the surface you rely on: the product ships out of the box with 183 business objects, and each one is published in the REST API with its own data and schema endpoint; you can read the field structure from outside with describe. What is what ##### What exists and what does not on the Microsoft side The Microsoft 365 email connection is not live today. For the calendar, an embedded tab, chat transfer and meeting transcription we have no measured capability. Topic | What exists today | How it is set up - CRM → notification to a Teams channel | Signed outgoing webhook, retries, SSRF validation and a workflow node are ready in the product | The subscription and the event–channel mapping are configured during implementation; no code is written - Microsoft 365 email | Not live today; the Outlook and Microsoft 365 connections are not open | We do not offer it. A Microsoft 365 account cannot be connected; the detail is on the email integration page - Outlook calendar | None. The Outlook and Microsoft 365 connections are not live today; there is neither email nor calendar sync | We do not offer it. If you need appointment sync, the only route that works today is Google Calendar - A CRM tab or app inside Teams | None; we have no interface embedded inside Teams | We do not offer it. The link in the notification takes you to the record itself, and the screen opens in the CRM - Teams chat being written to the customer record | None; the messaging channel list is closed — email, WhatsApp Business API, WhatsApp QR pairing and SMS | If you want correspondence to land on the record, the route that works today is the WhatsApp Business API. WhatsApp QR pairing is not the official API and carries the risk of the number being restricted; we do not offer it as a product promise - Automatic transcription of a Teams meeting | None; we have no connection that pulls the meeting in by itself | Uploading an audio recording to the CRM and producing a transcript and a summary is a separate matter; it is written up, with its limits, on the Zoom page What we can say ##### What we have verified - No email | Outlook and Microsoft 365 connections are not live today - No calendar | No Outlook calendar sync; calendar sync works on the Google side only - Ready | Outgoing webhook infrastructure: signed, retried, SSRF-validated - 0 subscriptions | Webhook subscriptions defined across 24 tenants — no claim that anyone uses it - Closed channel list | The messaging channel list is closed; Teams is not on that list Implementation ##### How is the Microsoft side brought live? - Discovery | We work out who administers your Microsoft 365 tenant and which channels will be fed. We recommend that your IT lead is in this meeting. - Scope and event list | The event–channel mapping, the fields that will appear in the message and the noise limit are put in writing. That the calendar and Microsoft 365 email are out of scope is stated plainly in that document too — no surprise line items. - Configuration and testing | The webhook subscription is defined and signature verification is tested on the receiving side. Test notifications are sent with sample events. - Training and go-live | Team training and close follow-up in the first week. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The notification side goes live with that plan. ##### Our limits: what we do not promise on this page Under a Microsoft heading, scope is easily overstated: it is easy to write “Microsoft 365 integration” and put everything underneath it. We write down what we do not promise, by name. - We do not offer Microsoft 365 or Outlook email sync. The Outlook and Microsoft 365 connections are not live today; a Microsoft 365 account cannot be connected to the CRM. This is the measured situation today, and we do not give a date for it. - We do not offer Outlook calendar sync. Because the Microsoft 365 connection is not live today, there is no calendar sync either; calendar sync is specific to the Google side only. This is not a polite way of saying “it is not there right now, it is coming soon” — this is the measured situation today. - We do not offer a CRM tab or app that opens inside Teams. There is no listing from us in the app store. - Teams chats do not land on the customer record. The messaging channel list is closed: email, WhatsApp Business API, WhatsApp QR pairing and SMS. - We do not offer WhatsApp QR pairing as a product promise. The same inbox can also be connected this way, but the method is not Meta's official API and carries the risk of the number being restricted by Meta. The route we recommend is the official Cloud API; even so, if you prefer this route we share the risk in writing and take the decision together. The detail is on the WhatsApp integration page. - We are not saying that your Teams meetings will land in the CRM by themselves. We have no connection that pulls the meeting in; producing a transcript and a summary from an audio recording is a separate matter, and it is written up, with its limits, on the Zoom integration page. - We do not say “our customers are connected to Teams”. Webhook subscriptions defined across 24 tenants: zero. - We do not promise that your stock will be in sync, that the order → invoice → collection chain will flow by itself, or manufacturing/MRP automation. We wrote the reason for all three, and what can be done instead, in one place: the three things we do not promise. Enterprise sign-in: OIDC is wired into the product and supported; we do not offer SAML, and to date we have not had a single enterprise sign-in setup configured in production. Two-factor authentication (TOTP, email code and backup codes), on the other hand, works and is mandatory for the admin account's web login. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no such feature as region selection. When you connect an email account, the mailbox itself continues to sit on the provider's side. This is a transfer abroad under Article 9 of the KVKK; we establish its legal basis together during the contract process. The detail is on the security page and in the KVKK privacy notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment questionnaires and describe the architecture in writing. ##### Plan prices are in the open; scope comes out in discovery The scope of Teams notifications, and their cost if any, are worked out in the discovery call and shared in writing. Plan prices and separately priced items, on the other hand, we publish on a single page with the figures. See pricing Three plans, a scope table and separately priced items on a single page. FAQ ##### Frequently asked questions about the Teams integration - Does Rapitek CRM integrate with Microsoft Teams? | In the notification direction, yes: events in the CRM are delivered to your Teams channel via a signed outgoing webhook, and that is a configuration job, not a development promise. Creating a record in the CRM from Teams, on the other hand, is a separate job written over the REST API. We have no interface embedded inside Teams and we are not saying there will be one. - Does Rapitek CRM have a ready-made Teams app or tab? | No. There is no listing from us in the Teams app store, and we do not offer a CRM tab that opens inside Teams either. The link in the notification takes you to the record itself and the screen opens in the CRM. If such a tab is critical for you, say so in discovery — we will assess the scope together, but it is not something we can offer today. - Can we connect our Microsoft 365 account to the CRM? | No. The Outlook and Microsoft 365 connections are not live today, so a Microsoft 365 account cannot be connected to the CRM. Generic IMAP/SMTP is not supported either. We wrote the detail on the email integration page. - Will our Outlook calendar sync with the CRM? | No. The Outlook and Microsoft 365 connections are not live today, so there is neither email nor calendar sync; calendar sync works only with Google Calendar. We are not softening this with a roadmap promise: this is the measured situation today, and if you need appointment sync you need to know it while you are planning. - Do our Teams meetings land in the CRM automatically? | No, they do not land by themselves; we have no connection that pulls a Teams meeting in. What does exist in the product is this: you can upload a meeting audio recording to the CRM and produce a transcript, a summary and action items. We wrote plainly on the Zoom integration page where this flow has worked to date and what its limits are. - Do Teams chats land on the customer record? | No. The messaging channel list is closed and today it consists of email, the WhatsApp Business API, WhatsApp QR pairing and SMS; Teams is not on that list. We do not offer WhatsApp QR pairing as a product promise: the method is not Meta's official API and carries the risk of the number being restricted; the route we recommend is the official Cloud API. If you want correspondence with the customer to land on the record, the route that works today is the WhatsApp Business API. The job on the Teams side is not to move the conversation but to announce the event. - Which events can be announced from the CRM to a Teams channel? | Record creation and change events can be announced; for example an opportunity being won, a stage change, a new lead and a quote approval. Because the notification is a workflow node, a condition can be placed in front of it — for example only opportunities above a certain amount. The event–channel mapping is defined during implementation and can be narrowed later. - Are the notifications secure? | The call is signed: the receiving side verifies the signature and filters out a forged notification that is not yours. The target address also passes SSRF validation, meaning an endpoint pointed at an internal network is not accepted. A failed call is retried; a temporary outage on the other side does not mean the notification is lost. - Can we create records in the CRM from Teams? | It can be written, but we do not offer it as an out-of-the-box feature. The route is the REST API and OAuth2: the product ships out of the box with 183 business objects, and each one is published with its own data and schema endpoint — you can read the field structure from outside with describe. Which message creates which record is decided in discovery and settled in a written proposal. - Can we do enterprise sign-in (SSO) with Microsoft Entra? | OIDC is wired into the product and supported; we do not offer SAML — the component required for SAML is not in the product. To be honest, to date we have not had a single enterprise sign-in setup configured in production either; we discuss this item separately in discovery. Two-factor authentication, on the other hand, works and is mandatory for the admin account's web login. - How many of your customers use the Teams notification? | As far as we know, none: webhook subscriptions defined across 24 tenants is zero. What we describe on this page is a measured capability of the product; not a measured usage of it. The Microsoft 365 email connection is not a counter-example either — it is not live today. - How long does implementation take, and is it included in the plan price? | Configuring the notification subscription is within the scope of implementation. Project-specific development, such as a flow that writes from Teams into the CRM, is scoped separately and charged separately. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. - Where is our data held? | In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. When you connect an email account, your mailbox continues to sit on the provider's side; the copy that lands in the CRM sits in your database in the EU. - Can we see it before buying? | There is no trial you can start on your own. First we run a 30-minute live demo; in that call we show how the notification node is built in the workflow designer. After that we open a time-limited demo account. ##### Related pages - Email integration | The canonical page for the email side: which email connections are live today and which are not. - Integrations | Which connections work in the product today, which ones we build on request, and the reason for the three things we do not promise. - Security | Which country the data sits in, the sub-processor list, authentication, the audit trail and what we do not yet offer. ##### Let us settle the Microsoft side in 30 minutes In the demo call let us show, on your own scenario, how the channel notification is built; let us write the scope and the limits together. Request a demo The scope is worked out in discovery and shared in writing; that the calendar is out of scope is written in that document too. ### [Terms of Service | Rapitek CRM](https://rapitek.com/en/terms) Rapitek CRM terms of service: account registration, acceptable use, payment terms, data ownership, service availability, termination and governing law. Legal #### Terms of Service Version 2026.3 · Last updated: 2 October 2026 ##### On this page These Terms of Service ('Terms') govern your use of Rapitek CRM's website and services. By accessing or using our services, you agree to be bound by these Terms. ##### 1. Acceptance of Terms By accessing and using Rapitek CRM services, you accept and agree to be bound by the terms and provisions of this agreement. If you do not agree to these Terms, please do not use our services. ##### 2. Description of Service Rapitek CRM provides a customer relationship management (CRM) software platform that includes: - Contact management - Sales pipeline management - Email integration - Reporting and analytics - Team collaboration - Mobile application access ##### 3. Account Registration To use our services, you must: - Provide accurate and complete registration information - Maintain the security of your account credentials - Promptly update any changes to your information - Be responsible for all activities under your account - Notify us immediately of any unauthorized use ##### 4. Acceptable Use Policy You agree not to: - Violate any laws or regulations - Infringe on intellectual property rights - Transmit malware or harmful code - Attempt to gain unauthorized access to our systems - Use the service to send spam or unsolicited messages - Resell or redistribute the service without permission - Use the service for any illegal or unauthorized purpose ##### 5. Payment Terms ###### Billing - There are two payment options: paying annually, the subscription is invoiced in advance for a one-year term; paying monthly, it is invoiced every month - On monthly payment, any minimum subscription term is set out in the written quote - Setup, data migration, training and out-of-scope work are priced separately from the subscription; the payment plan is set out in the written quote - Prices may change; we notify you of a price change that operates to your disadvantage at least 30 days before it takes effect. A price increase is a change that operates to your disadvantage, so the notice period, the right to terminate without penalty and the refund set out in Section 12 apply to it as well - Fees are non-refundable, except where the law requires otherwise and except for the refund of the fee covering the unused part of the term under Section 12 - You are responsible for all applicable taxes ###### Evaluating the Service There is no self-service sign-up: you cannot open an account or start a subscription on your own. Before you buy, we show Rapitek CRM live in a demo built around your own scenario, and the scope and price are set out in a written quote. After the demo, if you would like to explore the product at your own pace, we open a time-limited demo account for you; that account sits in Rapitek's demo environment with sample data, is closed at the end of its term, and by itself creates no right of use or subscription. The plan price is the subscription fee; the cost of setup, data migration, training and any out-of-scope work is agreed in the discovery call and put in writing before the work starts. The minimum number of users depends on the plan you choose: at least 5 users on the Sales and Platform plans, and at least 10 users on the Enterprise plan. ##### 6. Data Ownership and Privacy You retain all rights to your data. We will: - Not sell or rent your data to third parties - Only access your data to provide support (with your permission) - Allow you to export your data at any time - Delete your data upon account termination (unless legally required to retain it) E-mail measurement and our role as processor. In the e-mails you send to your customers through Rapitek CRM, we measure whether the message is opened and whether the links inside it are clicked; in the process the time of opening, the recipient's IP address and information about the e-mail program they use are recorded. For this processing you are the data controller; Rapitek acts only as a data processor on your instructions. The duty to inform your recipients, and to obtain consent where required, is yours; you need to update your own privacy notice so that it covers this measurement. Turning the measurement off for an individual recipient is not currently possible. We recommend that you take this into account in your own assessment. ##### 7. Intellectual Property Rights Rapitek CRM and its original content, features, and functionality are owned by Rapitek Bilişim Teknolojileri A.Ş. and are protected by international copyright, trademark, patent, trade secret, and other intellectual property laws. ##### 8. Service Availability We work to maintain high service availability: - Hosting in the European Union: database in Helsinki (Finland), uploaded files in Frankfurt (Germany), database backups in Falkenstein (Germany) - Regular backups of your data - Security updates and patches We do not commit to a contractual uptime (SLA) percentage; we do not measure uptime with an independent external monitoring service, and we do not publish a rate we have not measured. If a guaranteed SLA is one of your requirements, please raise it at the start of the conversation. ##### 9. Termination Either party may terminate this agreement: - You may cancel your subscription at any time - We may terminate for violation of these Terms - Upon termination, your access will be disabled - You may export your data within 30 days of termination ##### 10. Disclaimers and Limitations of Liability THE SERVICE IS PROVIDED 'AS IS' WITHOUT WARRANTIES OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY LAW: - We disclaim all warranties, express or implied - We are not liable for any indirect, incidental, or consequential damages - Our total liability shall not exceed the amount paid by you in the last 12 months ##### 11. Indemnification You agree to indemnify and hold harmless Rapitek CRM, its affiliates, and their respective officers, directors, employees, and agents from any claims, damages, losses, liabilities, and expenses arising from your use of the service or violation of these Terms. ##### 12. Modifications to Terms We may change these Terms. We will notify you of any change that operates to your disadvantage at the e-mail address registered on your account at least 30 days before it takes effect. If you do not accept the change after that notice, you may terminate your subscription within that period without any penalty and request a refund of the fee covering the unused part of the term. Changes that are in your favour, and mandatory adjustments arising from a change in legislation, are not subject to this notice period. Every version is numbered and archived with its date; which version your contract was formed under is on record. The version in force is stated at the top of this page. ##### 13. Governing Law These Terms shall be governed by and construed in accordance with the laws of Turkey, without regard to its conflict of law provisions. Any disputes shall be resolved in the courts of Istanbul, Turkey. FAQ ##### Frequently asked questions about the terms - Can I cancel my subscription at any time, and what happens after termination? | Yes. Under the Termination section you may cancel your subscription at any time, and Rapitek may terminate the agreement if these Terms are violated. Once terminated, your access is disabled, but you have 30 days from termination to export your data. On annual payment the fee is collected in advance for the term; on monthly payment the month already paid is not refunded and any minimum term is set out in the written quote. Simply choosing to leave does not by itself entitle you to a refund; fees are refunded where the law requires it, and — under Section 12 — where you end your subscription because of a change that operates to your disadvantage, in which case the fee covering the unused part of the term is refunded. - Who owns the data I put into the system, and what does Rapitek do with it? | You retain all rights to your data. Under the Terms we do not sell or rent your data to third parties, and we access it only to provide support and only with your permission. You can export your data at any time, and it is deleted when your account is terminated — after the 30-day export window — unless we are legally required to retain it. - How far does Rapitek's liability extend if something goes wrong? | The Terms provide the service "as is" and disclaim all warranties, express or implied. To the maximum extent permitted by law, no liability is accepted for indirect, incidental or consequential damages, and total liability cannot exceed the amount you paid in the last 12 months. - Can the terms or prices change later, and how will I be told? | We may change these Terms, but a change that operates to your disadvantage is notified to the e-mail address registered on your account at least 30 days before it takes effect. If you do not accept it, you may end your subscription within that period without penalty and ask for the fee covering the unused part of the term back. Changes in your favour, and mandatory adjustments arising from a change in legislation, are not subject to that notice period. Under the Payment Terms, price changes are subject to the same rule. Each version of these Terms is numbered and archived with its date, and the version in force is stated at the top of this page. - Which law governs the terms and where are disputes resolved? | The Terms are governed by and construed in accordance with the laws of Türkiye, without regard to conflict of law provisions. Any disputes are resolved in the courts of Istanbul, Türkiye. ##### 14. Contact Information For questions about these Terms, please contact us: Rapitek Bilişim Teknolojileri A.Ş. Maslak Mah. Büyükdere Cad. Nurol Plaza 255, B02 34485 Sarıyer / İstanbul, Türkiye Email: info@rapitek.com WhatsApp: +90 212 963 22 84 For other ways to reach us, see our Contact page. ### [Tire Shop CRM: Tire Hotel and Season Tracking | Rapitek CRM](https://rapitek.com/en/tire-shop-crm) Every set in the tire hotel is recorded with warehouse, shelf and position. Customer-vehicle records, seasonal lists and appointments sit in one system. Industry solution · Tires #### CRM for tire dealers and workshops running a tire hotel Customer and vehicle records, the tire hotel, seasonal reminder lists and appointments in one system. A separate view for fleet customers, and WhatsApp from a single business number for the whole team — configured around your processes, and we do the setup. Request a demo Talk to an industry specialist ##### A season that never gets recorded cannot be listed the next season A tire dealer's year is squeezed into two peaks: October–November for the switch to winter tires, March–April for the switch back to summer. In those weeks the phone never stops and the ramp never empties — and the busier it gets, the less time is left for keeping records. And work that never gets recorded cannot be brought back later. Here is the picture we have seen again and again in our own CRM projects: - The customer's vehicle and tire size are asked for again on every call; the information sits in the foreman's memory or in an old notebook. - Sets left at the tire hotel are written into a notebook; when the customer turns up at the door, the set is hunted for shelf by shelf in the warehouse. - Nobody gets in touch this November with the customer who had winter tires fitted last November; because the fitting date is not in a record, there is also no way to list that customer when the season comes round. - Which of a fleet customer's 30 vehicles had what fitted and when sits in Excel; who holds the current version of the file is anyone's guess. - Vehicles arriving without an appointment pile up; the customer who was given an appointment is kept waiting, because the appointments are in the notes app on someone's phone. None of this is solved by working harder once the season arrives. It takes record discipline and lists built in advance — and that is exactly what a CRM is for. None of it is specific to tires, either: the same record discipline applies to any business whose customers come back on a cycle, and the same goes for keeping message threads with the dealership rather than on a technician's own phone. A concrete scenario ##### The first cold morning in October — the phone will not stop. - The caller's record opens from the plate | You search by phone number or licence plate; the vehicle, the tire size, last season's fitting date and the set in the hotel are all on one screen. Nobody asks for the size again, and the customer does not have to introduce themselves. - The set in the hotel shows with its shelf location | The winter set is in the hotel record: warehouse, shelf, position, date in, and the photo taken at drop-off. The set is brought down and made ready before the vehicle arrives; nobody is kept waiting at the door. - The appointment is written into the calendar | A time is given according to the fitting duration and the ramp plan; the appointment is recorded, synced with Google Calendar, and a reminder task is created. An appointment that is not kept stays visible in the record instead of quietly disappearing. - When the vehicle arrives, the work is written onto the record | The tires fitted and removed, the tread depth note and any observation for the next season go onto the customer and vehicle record. The information is in the office's records, not in the technician's memory. - The removed set is taken in with a hotel entry | A new hotel record for the summer set: shelf, position, photo, date in. When the customer calls in spring, the same screen opens; the loop closes. - As the season ends, next season's list is already there | The customer list is filtered by fitting date; for customers with commercial message consent, a seasonal notice over WhatsApp is planned. Who was called and who booked an appointment is followed from the list. ##### The building blocks we set up for tire dealers - Customer and vehicle record | Every vehicle is its own record: plate, make and model, tire size, rim, last fitting date and service history. Several vehicles belonging to one customer are gathered under a single account. The fields are configurable — we decide together during setup which ones you actually need. - Tire hotel tracking | Every set taken into the hotel is recorded with warehouse, shelf and position fields; dates in and out and a photo are kept, and the record is linked to the customer and vehicle record. When the customer calls, nobody goes looking for the set — it is read off the screen. - Seasonal reminder lists | Customer lists are filtered by last fitting date and kept as saved views. With commercial message consent management, a seasonal notice over WhatsApp is planned for customers who have given consent. - Appointments and calendar | Fitting and balancing appointments are recorded and synced with Google Calendar; reminder and follow-up tasks are created. Appointments that did not happen show up in the reports. - Fleet customers | Under the fleet account, every vehicle in a single view: what was fitted to which vehicle and when, and which month the next change falls in. Periodic bulk changes are scheduled as tasks; a fleet-level summary report is set up. - WhatsApp from a single number | The whole team writes from the dealership's single business number; messages land in the team inbox and go onto the customer record. The route we recommend and set up is Meta's official WhatsApp Cloud API. We do not offer QR-code pairing as a product promise: it is not Meta's official API and risks the number being restricted by Meta; if that happens, your business number is shut down. ##### Mobile at the ramp, connected to the programs you already run ###### Mobile at the counter and on the ramp Tire work does not happen at a desk. Both our iOS and Android apps are live and ship with a Turkish interface; the technician can enter the tread depth note and the service record from a phone while the vehicle is still on the ramp. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp messages are handled in the single inbox inside the app — in the rush of the season an incoming message can be answered from the counter. Instagram direct messages land in the same inbox. The details are on the mobile app page, and the product as a whole on the product page. ###### Connecting to your stock and pre-accounting program Rapitek CRM does not take the place of your stock or pre-accounting program; it adds a customer relationship layer on top of it. The connection to your existing program is built as follows: over REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. Which data flows in which direction is defined together during setup. We have gathered which systems we connect to, and how, on the integrations page. There is no out-of-the-box module — it would not be right to say there is. Because access differs from one installation to the next, no single button can be built that works the same way in every installation; the connection is a scoped integration job and is planned as part of the setup. We have written plainly on the pricing page which items are included in the plan price and which are priced separately. ###### Close the season with numbers Sales by season, conversion from the reminder list to appointments, occupancy from the hotel records and branch comparison — all built with tabular and summary reports and the drag-and-drop dashboard designer, without writing code. Matrix and joined report types are also supported. Division of labour ##### Stock program or CRM? Both. Rapitek CRM does not take the place of your stock and pre-accounting program; it adds the customer relationship layer on top of it. The data flow between them is built over API and import/export. Layer | What it does - Stock and pre-accounting program | Tire purchasing and sales, stock quantities, invoicing and cash tracking - Rapitek CRM | Customer and vehicle record with tire size, tire hotel tracking, seasonal reminder lists, appointments, WhatsApp message history and reporting - The connection between them | REST API, OAuth2, webhooks and import/export; the scope is defined during setup with the team that builds and develops the product Verifiable numbers ##### Not a marketing line — measured data - 200+ | Enterprise CRM projects delivered during the Salesforce era (before Rapitek CRM) - 277 | Custom fields added by 19 tenants without writing code - Every 6 hours | Automatic backup frequency; backups are copied to a separate country - 183 | Business objects in the REST API — each with a data and a schema endpoint - EU | Data location: Helsinki (Finland), media in Frankfurt, backups in Falkenstein Rollout ##### How is a CRM put into service at a tire dealership? - Discovery and analysis | We map out your season flow, your hotel capacity, your branch structure and your fleet customers. Which fields you genuinely need is decided here. - Configuration | Vehicle and hotel fields, the appointment layout, reminder lists, permissions and reports are set up around your own process. No code is required; setting it up well takes expertise, and that part we do. - Data migration | Customer, vehicle and hotel records from your Excel files or from your existing program are imported; duplicate records are weeded out. - Training and go-live | Training for the counter team and for managers, close support in the first week, then continuous support. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range — and we plan the switch to finish before the season peak. From our CRM implementation projects ##### What do the teams we work with say? - The most important element in bringing new business ideas to life is your IT infrastructure and your applications. Rapitek offered far more than simply supplying an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during the development process, we reached our first product quickly and maintained a healthy continuity in the project. | Denizhan Edeer | CEO | Aktif Filo - With Rapitek's solution-oriented approach, we began the work needed to complete the improvements to our Salesforce customisations and integrations quickly. With the improvements made, data duplication was prevented and we increased the efficiency of the system. | Ögetay Can | Sales Director | Petroyağ | Case study The references above relate to CRM implementation and integration projects carried out by Rapitek; they do not mean that the organisations named use the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### Data location, KVKK and security — as it is Your customer data is personal data: name, phone number, licence plate, address, vehicle details. That is why we speak plainly here. - Your data is held in the European Union. The database is in Helsinki (Finland), media files in Frankfurt, and backups in Falkenstein (Germany). We do not say the data is held in Türkiye, because it is not. - For organisations in Turkey this counts as a transfer abroad under Article 9 of the KVKK; we establish the basis for that transfer together during the contracting process. The disclosure obligation is separate: on our own forms we present a privacy notice; for the customer data you enter into your CRM you are the data controller, and you provide the privacy notice to your customers. - TLS is used in transit. Passwords are hashed one-way; two-factor authentication secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. A separate database is used for each customer. - Role-based authorisation is in place; which branch and which user sees which records is defined. We do not hold an information security certificate and we do not claim to. Every technical detail we state has its counterpart in the system; we answer your security questions in writing before installation. We have written out all the technical measures point by point on the security page. ##### Work out the return with your own numbers Enter your own figures and see the 12-month return. Every assumption is visible and editable — if you do not find the result convincing, change the assumption and look again. Open the ROI Calculator No signup, we do not ask for your email. FAQ ##### Frequently asked questions about CRM in the tire industry - Can it be used as tire hotel software? | Yes. Every set taken into the hotel is recorded with warehouse, shelf and position fields; dates in and out and a drop-off photo are kept, and the record is linked to the customer and vehicle record. When the customer calls, the location of the set is read off the screen. This is not an out-of-the-box 'hotel module'; it is a record model we configure during setup around your own warehouse and shelf layout — and we do the configuring. - Do the seasonal change reminders go out automatically? | The honest answer has two parts. The list is automatic: customers are filtered by last fitting date and the saved view is ready every season. Sending, however, depends on consent: with commercial message consent management, a seasonal notice over WhatsApp is planned for customers who have given consent. WhatsApp is outside İYS sync; SMS, call and e-mail consents are sent to İYS when you connect your own İYS account through Verimor. Who was notified and who booked an appointment is followed from the list. Commercial messages are not sent to customers who have not given consent; this is not a shortcoming but a requirement of the regulations. - How is the customer's vehicle and tire size information kept? | Every vehicle is a separate record: plate, make and model, tire size, rim size, last fitting date and service history. Several vehicles belonging to one customer are gathered under a single account. When they call, the record is found by searching the number or the plate; the size is not asked for again. Which fields will be mandatory we decide together during setup. - Can we manage fleet customers? | Yes. Under the fleet account all vehicles are kept in a single view: what was fitted to which vehicle and when, and which month the next change falls in. Periodic bulk changes are scheduled as tasks, and fleet-level summary reports are set up. This structure is configured during setup around your own fleet process. - Is there an online appointment system? | Appointments are opened as records in the system, synced with Google Calendar, and reminder and follow-up tasks are created; appointments that were not kept show up in the report. A self-service online booking page where the customer picks a time themselves is something we do not offer — it would not be right to say we do. In practice your team opens the appointment on the phone or in a WhatsApp conversation; we set that flow up together during installation. - Do you do tire stock tracking? | Rapitek CRM does not take the place of your stock and pre-accounting program; purchase-and-sale and stock quantity tracking stay in that layer. On the CRM side, inventory and stock movement objects ship with the standard installation; we build your own record model, such as the tire hotel, on top of that — but today we cannot show you stock execution on a live installation. The connection to your existing stock program is built as follows: over REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. - We have more than one branch; how does authorisation work? | Role-based authorisation defines which branch sees which customer, which hotel record and which report. A branch sees its own business; a manager looks at the consolidated view. Even if staff change, the customer history and the hotel records stay with the dealership. - Can more than one person use the same WhatsApp number? | Yes. The whole team writes from the dealership's single business number; messages land in the team inbox and are written onto the relevant customer record; a manager can see who wrote what. The connection route we recommend and set up is Meta's official WhatsApp Cloud API. Pairing a phone by QR code is also possible, but we do not offer it as a product promise: the method is not Meta's official API and carries the risk of the number being restricted by Meta; if that risk materialises, your business number is shut down. If you choose that route, we share the risk with you in writing and take the decision together. - Which reports can we get? | Reports such as sales by season, conversion from the reminder list to appointments, appointments that did not happen, occupancy from the hotel records and branch comparison can be set up. There are tabular and summary report types and a drag-and-drop dashboard designer; matrix and joined report types are also supported. Reports are built over your own fields, without writing code. We prepare the first report set together during setup. - Is there a mobile app for use in the workshop? | Yes. Both our iOS and Android apps are live and ship with a Turkish interface; the technician can enter the service note and the tread depth observation from a phone while the vehicle is on the ramp. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. WhatsApp and Instagram messages are handled in the same single inbox inside the app; replying to Instagram from the mobile app has not yet been measured in a customer deployment. - Can we see the product first? | There is no trial you start yourself. We begin with a 30-minute live demo; afterwards, if you would like to explore the product at your own pace, we open a time-limited demo account for you. In the demo we show the customer and vehicle record, the tire hotel record, the seasonal reminder lists and appointment tracking on your own scenario. Industry-specific configuration such as tire hotel fields and seasonal lists is done during setup. - How long does setup take and what is included? | We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. Setup consists of these steps: discovery and analysis, configuration, data migration from Excel or from your existing program, team training and go-live. We plan the switch so that it is completed before the season peak. The scope of the setup and any fee are worked out in the discovery call and shared in writing before the work starts; for plan information you can look at the pricing page. - Where is our data held? | The database is held within the European Union, in Helsinki (Finland); media files are stored in Frankfurt and backups in Falkenstein (Germany). This means a transfer abroad under Article 9 of the KVKK; the basis is established according to the tiers in that article — first an adequacy decision, failing that appropriate safeguards, and exceptionally incidental cases; the disclosure obligation is separate from all of this. TLS is used in transit and a separate database is kept for each customer. ##### Related solutions - Auto Spare Parts CRM | Stock, quote and order tracking in dealer and wholesale sales; a structure designed for the automotive supply industry. - Field Sales Software | Dealer visits, route planning and performance reports for the field team. - Customer Tracking Software | Customer tracking independent of industry: how record discipline, the sales pipeline and reporting are set up. ##### Go into the season peak with a system that is ready In a 30-minute demo, let us show you the customer and vehicle record, the tire hotel record, the seasonal reminder lists and appointment tracking on your own scenario. Request a demo The scope of the setup and any fee are worked out in the discovery call and shared in writing. ### [WhatsApp CRM: One Business Number, Shared Inbox | Rapitek](https://rapitek.com/en/whatsapp-crm) Your team writes from one WhatsApp business number, every message lands on the customer record, and the history stays with the company when a rep leaves. WhatsApp + CRM #### WhatsApp CRM: one number, history stays Every incoming message lands in a shared inbox and is written onto the customer record. Even if a rep changes, goes on leave or leaves the company, the message history stays with you. This page is about how the inbox works across a team; how the line itself is connected on Meta's side is on the WhatsApp integration page. Request a demo Get in touch ##### When WhatsApp conversations stay on personal phones, customer history never accumulates in the company If your business correspondence has moved to WhatsApp, we do not need to tell you that; the customer is waiting for the green bubble, not for an email. That is not the problem. The problem is that the conversation runs on employees' personal phones. This is the picture we saw again and again in our own CRM projects: - Every rep writes from their own number; the customer becomes the rep's customer rather than the company's. - When the rep goes on leave the conversation stops — nobody else can see it or take it over. - Prices, deadlines and promises given on WhatsApp are recorded nowhere; in a dispute there is no document in hand. - A manager can only find out what was discussed with which customer by asking. - When an employee leaves, their number, their contacts and years of accumulated message history go with them. None of this is solved by banning WhatsApp — your customer is there. The solution is to take the conversation off the personal phone and connect it to the company's system. That is exactly what WhatsApp CRM does. A concrete scenario ##### Wednesday, 16:40 — a customer writes to your business number. - The message lands in a shared inbox, not on a personal phone | A message sent to the company's single WhatsApp business number appears in the team inbox on web and mobile. Whose desk it is on does not matter; whoever sees it first can take the conversation. - The number is matched to the customer record | If the sender is a registered customer, the conversation is written straight onto their record. If the number is unknown, a new lead record is opened with its source logged — no manual data entry. - The conversation is assigned to a rep | Everyone can see who is handling it; when needed it is handed to another rep with an internal note. The customer never notices the handover — they are always writing to the same number. - The reply goes out from the same business number | Photos, documents, location and voice messages are sent and received in the same window; all of it is kept on the customer record. The price and the deadline you quoted are now on file. - The conversation is linked to the opportunity | If it turns into a sale, the conversation is attached to the opportunity record; the quote, tasks and reminders all move on the same card. Where work that came in from WhatsApp stands is visible in the sales report. - Even when a rep leaves, the history stays with the company | The user account is closed and their open conversations are handed to another rep. The customer keeps writing to the same number; years of message history stay on the customer record. Department routing #### Customers reach the right department. An incoming message is met by an automatic menu; the customer picks the relevant department and the conversation is routed to whoever owns it. The conversation runs on one business number and its history stays on the customer record — even when the rep changes. ##### The building blocks that connect WhatsApp to the CRM - One business number, one shared inbox | The whole team writes from the company's single WhatsApp business number; incoming messages land in the shared inbox on web and mobile. Conversations are assigned to a rep and handed over with internal notes. The customer never sees how many people are working behind it. - Written to the customer record automatically | Every message is written onto the customer record that matches the sender's number; for unknown numbers a new lead record is opened with its source logged. Text, images, documents, audio and location are kept together. - On the same screen as the pipeline | The conversation is linked to the related opportunity record; the quote, tasks and reminders move on the same card. Where work that came in from WhatsApp is waiting shows up in the sales reports. - Template messages and the approval flow | Texts such as an appointment reminder or an order notification are managed as templates from inside the CRM. Templates are submitted for Meta approval through your own WhatsApp Business account; the decision and how long it takes sit with Meta. The team only uses approved texts. - İYS sync covers SMS, calls and e-mail | For customers who connect their own İYS account through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM. WhatsApp is outside this sync; WhatsApp campaigns are sent with Meta-approved templates. - Permissions and audit | Who sees which conversation is set by role; a manager can see the team's correspondence. When an employee leaves, their access is closed and their conversations are handed over — the records stay with the company. ##### The connection is built with the official Cloud API — the detail is on a separate page This page describes the inbox; how the line is connected is a separate subject and we wrote it up end to end on the WhatsApp integration page. Briefly, even so: The route we recommend and build is Meta's official WhatsApp Business Cloud API. We connect your own Meta WhatsApp Business account; the app, the WhatsApp Business account and the number stay in your name, and Meta invoices you directly. We do not sell message bundles or credits in between. On Meta's side there are business verification, number registration and template approval steps; we run that process as part of the implementation. We give no commitment for Meta's decision time — the approval decision, and how long it takes, sit with Meta, not with us. We do not offer pairing a phone by QR code as a product promise. The same inbox can be connected that way too, but the method is not Meta's official API and it carries the risk of the number being restricted by Meta; if that risk materialises your business line goes down. If you still prefer that route we share the risk in writing and take the decision together. ##### The same inbox on the phone; connecting your other software ###### Replying from mobile Our iOS and Android apps are live and come with a Turkish interface; the shared inbox works the same way on the phone. A rep in the field sees the message, replies, and updates the customer record and the follow-up task. Rapi, the voice assistant in the app, does not only read the CRM by speaking Turkish — it creates and updates records too. The call is yours: Rapi is off by default; unless you turn it on, your CRM data is never sent to any AI provider. Where the request goes once you enable the assistant is written on our security page. This matters more than it sounds: if an inbox can in practice only be used on the desktop, telling a rep who is out in the field to “just log in on the web” means telling them not to use it. ###### ERP, accounting and your other systems WhatsApp is not your only channel. If you use accounting software, an ERP or another business system, the connection is built like this: over the REST API, OAuth2, webhooks and import/export, by the team that builds and develops the product. For the general framework, see the integrations page. Let us be reachable too: you can write your questions to our WhatsApp line — +90 212 963 22 84. What we can say ##### What we have verified about the inbox - Core | The messaging inbox is in the product's core, not an add-on - Live | SLA engine in messaging: first-response target, business-hours calendar - iOS + Android | The shared inbox also opens in the mobile apps on the stores - Two-way | İYS sync when you connect your own İYS account via Verimor; not WhatsApp - EU | Data location: database Helsinki, files Frankfurt, backups Falkenstein Implementation ##### How is WhatsApp CRM brought live? - Discovery and the number decision | Which teams will write, whether an existing number is used or a new business number taken, which legal entity the verification runs through — we take these decisions together. The business verification and number registration on Meta's side we run as part of the implementation. - Configuration | The inbox, rep permissions, customer-record fields and template messages are set up around your process; templates are submitted for Meta approval through your own WhatsApp Business account. No code is needed — but setting it up well takes expertise, and that part we do. - Data migration | Your customer list, from a spreadsheet or your current system, is imported; phone numbers are matched to customer records and duplicates are weeded out. From day one, conversations land on the right record. - Training and go-live | Rep and manager training, close follow-up in the first week. There is no call centre on our support line; the team that builds the product answers. We do not commit to a duration before discovery; after it we give you a date, not a range. Meta's approval timing depends on Meta. From our CRM implementation projects ##### What the teams who moved into one system say - As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations. | Şemun Alp Biber | General Manager | Anatolia Tile | Read the customer story - With Rapitek's solution-oriented approach, we started the necessary work to quickly complete improvements in our Salesforce customizations and integrations. With these improvements, we prevented data duplication and increased system efficiency. | Ögetay Can | Sales Director | Petroyağ | Read the customer story - As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient. | Utku Aydın | Business Development Director | Iyzico The references above relate to CRM implementation and integration projects carried out by Rapitek; they do not mean that those organizations use the Rapitek CRM product today. Brand names, logos and titles belong to their owners. ##### A WhatsApp conversation is personal data — data location and KVKK, as they are WhatsApp conversations contain names, phone numbers, addresses, sometimes prices and contract detail; that makes them personal data, and they should be managed as such. So we are plain here. - Your data is kept in the European Union. The database is in Helsinki, uploaded files and media in Frankfurt, database backups in Falkenstein. We have no component in Turkey and we do not offer region selection; we do not say the data is kept in Turkey, because it is not. - Seen from Turkey this is an international transfer under Article 9 of KVKK. The message itself also passes through Meta's infrastructure; that is true of every enterprise WhatsApp deployment. We establish the basis for the transfer together during the contract process. - TLS is used in transit. Passwords are hashed one-way; two-factor authentication secrets and the credentials for email, WhatsApp Business API, Instagram/Meta, payment and İYS connections are encrypted at the application level. Your CRM data is kept in a separate database that belongs to you. - For marketing messages there is commercial-message consent management; campaigns are only sent to consented lists. WhatsApp is outside İYS sync: when you connect your own İYS account through Verimor, only SMS, call and e-mail consent and opt-out records are sent to İYS. - Who sees which conversation is set by role-based permissions; when an employee leaves their access is closed and the records stay with the company. We do not hold an information security certificate such as ISO 27001 or SOC 2, and we do not claim to. Every technical detail we state has a counterpart in the system; we answer your security questions in writing before implementation. For detail, see our security and KVKK privacy notice pages. ##### We put the figure on the pricing page, not on this one The implementation scope of the WhatsApp line is worked out in the discovery call and shared in writing. Plan prices we keep in one place — so you never read two different figures for the same thing. See pricing Three plans, a scope table and separately priced items on one page. FAQ ##### Frequently asked questions about WhatsApp CRM - What is WhatsApp CRM? | WhatsApp CRM means connecting WhatsApp conversations to customer relationship management software: the team writes from one business number, every message is written onto the relevant customer record, and sales and support run on that same record. In Rapitek CRM the connection is built over Meta's official WhatsApp Business Cloud API; we connect your own Meta WhatsApp Business account. The step-by-step account of the connection is on our WhatsApp integration page. - Why do we need WhatsApp CRM when we already have the WhatsApp Business app? | The WhatsApp Business app is designed for one person: it is limited to a few linked devices, the conversations stay on the phone, and they are not related to a customer record. In WhatsApp CRM the whole team writes from the same number, conversations are assigned to reps, the history is kept on the customer record, and a manager sees the team's message traffic in reports. - Can several reps use the same WhatsApp number? | Yes — that is exactly what this page is about. Incoming messages land in the shared inbox on web and mobile; conversations are assigned to reps and handed over with internal notes. The customer always deals with a single company number and never sees how many people are working behind it. - What happens to WhatsApp conversations when an employee leaves? | Because the conversations sit in the company's CRM rather than on the rep's phone, they stay with the company. The user account is closed, their open conversations are handed to another rep, and the customer keeps writing to the same number. In a setup that runs on personal numbers there is no equivalent to this; that is the concrete return of a shared inbox. - Can we use our existing WhatsApp number? | Yes, with one condition. If the number is currently used in personal WhatsApp or in the WhatsApp Business app, it has to be removed from there before it can be registered on the Cloud API; it does not work in two places at once. Old conversations on the phone are not carried into the CRM; the history starts accumulating from the day of connection. Taking a new business number is also possible — the decision is made together in the discovery call. - Is it possible to connect by pairing the phone with a QR code? | Technically possible, but we do not offer it as a product promise. The method is not Meta's official API and it carries the risk of the number being restricted by Meta; if that happens your business line goes down. The route we recommend and build is the official Meta Cloud API. If you still prefer that route, we share the risk in writing and take the decision together. - Can we send bulk messages or campaigns from WhatsApp? | Sending is done only with Meta-approved templates and only to lists that hold commercial-message consent. WhatsApp is outside İYS sync; when you connect your own İYS account through Verimor, SMS, call and e-mail consent and opt-out records are sent to İYS. How many messages you can send is set by the ceiling Meta grants your account; because that ceiling does not come back to us as a readable value from the API, we do not put a figure on this page. You see your current limit in your Meta Business account. Meta invoices the conversation cost directly to you; we work that cost out with you when planning a campaign. - How long does the WhatsApp CRM integration take to set up? | We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The WhatsApp connection is built inside that schedule. The timing of business verification and template approvals on Meta's side depends on Meta; we run the process, but we give no commitment for Meta's decision time. The scope of the implementation, and any fee for it, are worked out at discovery and shared in writing. - What does the WhatsApp integration cost? | We apply no separate module fee on the Rapitek side for the WhatsApp connection; current plan information and the items priced outside the plan price are listed one by one on our pricing page. On Meta's side the conversation cost is invoiced directly to you: we do not sell message bundles or credits, and we add nothing on top of that cost. We work the total cost out in writing in the discovery call. - How are WhatsApp conversations kept under KVKK? | The database is in Helsinki, uploaded files and media in Frankfurt, database backups in Falkenstein; we have no component in Turkey. Seen from Turkey this means an international transfer under Article 9 of KVKK; the message itself also passes through Meta's infrastructure, and we establish the basis for the transfer together during the contract process. TLS is used in transit and your CRM data is kept in a separate database that belongs to you. - Can we see the product before buying? | There is no trial you start on your own. We begin with a 30-minute live demo; afterwards, if you want to explore at your own pace, we open a time-limited demo account. In the demo we show the product live on your own scenario and answer your questions in the same call. The WhatsApp connection and the configuration specific to your process are done after purchase, during implementation. - Can we reply from the phone? | Yes. Our iOS and Android apps are live and come with a Turkish interface; the shared inbox works on the phone too, so a rep in the field sees the message and replies. Instagram direct messages land in the same inbox; replying to them from the mobile app has not yet been measured in a customer deployment. Rapi, the voice assistant in the app, creates and updates records in the CRM by speaking Turkish. ##### Related solutions - WhatsApp integration | The connection itself: your own Meta account, number registration, template approval and billing. - Instagram CRM | The 24-hour reply window and Instagram's limits, written plainly. Instagram direct messages land in the same shared inbox. - Mobile app | The inbox is inside the app — the field team replies without going back to the office. ##### Connect your WhatsApp traffic to the company's memory In a 30-minute demo let us show the shared inbox, the automatic writing to the customer record and the template message flow — on your own scenario. Request a demo The implementation scope, and any fee for it, are worked out at discovery and shared in writing. ### [WhatsApp Integration: Meta Cloud API | Rapitek CRM](https://rapitek.com/en/whatsapp-integration) We connect your WhatsApp Business account to Rapitek CRM through our Meta-approved app: messages land in a shared inbox, attach to the customer record, and Meta invoices you. Integration · WhatsApp Business Cloud API #### Your CRM messages from your own WhatsApp Business number. We connect your own Meta WhatsApp Business account to the CRM; messages land in the team inbox, attach to the customer record, and Meta invoices you directly. This connection runs in production today — setting it up does not require a provider-specific development project. Request a demo Talk through the scope of your connection ##### Whose name are the number, the account and the invoice in? From the outside, connecting WhatsApp to a CRM looks like a technical job; there is also an ownership side to it. The mechanism is this: whichever Meta account the connection is built through, the number, the approved templates and the invoice stay tied to that account. These are the outcomes we have run into in our own installations: - If the number is registered to an intermediary's Meta account, the number coming with you when you want to change providers does not happen by itself. - If the messaging cost is sold to you as “credits” or a “bundle”, you cannot see Meta's actual price and your own usage directly. - If your templates are approved under someone else's WhatsApp Business account, the account holding the approved texts is not yours either. - As long as the conversations stay on personal phones, nothing is recorded about who promised what; when a rep leaves, the history leaves with them. - If business verification has never been done, the work waits on Meta's side when installation day arrives. That is why we build the connection through our Meta-approved app, into your own account: the WhatsApp Business account and the number stay in your name, and Meta invoices you directly. We do not sell messages in between; what we do is connect that account to the CRM and set up how your team works. ##### This connection runs in production today In Rapitek CRM the WhatsApp connection is built on Meta's official WhatsApp Business Cloud API and runs in production today; version v21.0 of the Meta Graph API is used. So this is not a “we could do it” page: the connection exists in the product and is configured during setup. The connection runs through our Meta-approved WhatsApp and Instagram apps; no separate development work or intermediary is needed: - The WhatsApp Business Account (WABA) is yours. You authorise our Meta-approved app on your account, and you can withdraw that authorisation from your Meta Business account at any moment. - The number is registered in your name. You can port it, close it or connect it to another system independently of us. - Meta invoices you directly. We do not collect the conversation charge and we do not add anything on top of it. Incoming messages land in the CRM through a webhook, the sending number is matched to a customer record and the conversation is assigned to a rep. What comes after the connection — the shared inbox, conversation handovers, response-time tracking and team routines — we covered on a separate page: WhatsApp CRM. This page deals with the connection itself. If a question comes up while you read, you can message us on our own WhatsApp line: +90 212 963 22 84. Connection day ##### Tuesday 11:00 — we connect your line. Here is what happens, in order: - Your business is verified on Meta's side | Your Meta Business account is opened and business verification is started. Documents such as registry details, legal company name and contact address are submitted to Meta on your behalf; we run the process as part of the setup. - The WhatsApp Business account and the number are registered | Your business number is registered to your WhatsApp Business Account (WABA) and verified by SMS or voice call. If the number is in use in personal WhatsApp or in the WhatsApp Business app today, it has to be removed from there first. - The CRM connects through our Meta-approved app | You authorise your WhatsApp Business account on our Meta-approved app and messages start flowing into the CRM. The account stays in your name; you can withdraw the authorisation at any moment. - The inbox and the matching rules are set up | Which team a message lands with, how an unrecognised number opens a record and who the conversation is assigned to are configured. For number matching, your existing customer list is imported and duplicate records are weeded out. - Your templates are submitted for Meta approval | Texts such as appointment reminders or order notifications are prepared as templates and submitted for Meta approval through your own WhatsApp Business account. The approval decision and how long it takes rest with Meta; we prepare the text in line with the rules and follow the process. - It is verified with a test message, then the line is opened to the team | We verify together on screen that the test message lands on the right record, that media is stored and that the reply goes out from the same business number. The line is then opened for the team to use. ##### What you need to have in hand before the connection - A verifiable business | Meta ties the WhatsApp Business account to a business. Documents such as the legal company name, registry details and contact address need to be available for submission to Meta's verification. - A usable business number | It can be a landline or a mobile; what matters is that it can be verified by SMS or voice call. We recommend using a number registered to the company, one that will not leave with an employee. - The number having been removed from WhatsApp | If the number is in use in personal WhatsApp or in the WhatsApp Business app today, it has to be deleted from there before it is registered to the Cloud API. Old conversations on the phone are not carried over to the CRM. - A payment method on Meta's side | The conversation charge is billed to you directly by Meta; that requires a payment method set up in your Meta Business account. We do not sell credits or message bundles in between. - A counterpart who can make decisions | Someone who can decide about the number, the team setup and the template texts. Working with someone who can reach the documents Meta asks for in verification shortens the process noticeably. - Your consent and İYS setup | If you are going to send marketing content, commercial message consent is required. In the product the İYS connection works in both directions through the authorised integrator Verimor: consent lookup and notification to İYS. Scope ##### What syncs and what does not? This table describes the scope of the connection. Using the inbox inside a team is on the WhatsApp CRM page; the canonical limits are on the integrations page. Topic | How it works today | The limit - Incoming message | A message arriving at your connected business number lands in the CRM through a webhook; the sending number is matched to a customer record, and for an unrecognised number a new record is opened together with its source | Only the business number connected to the CRM is in scope; reps' personal numbers are not connected - Outgoing message | Replies are sent from inside the CRM, from the same business number | Outside the 24-hour window following the customer's last message, only a Meta-approved template can be sent — this is Meta's rule, not our choice - Media and files | Images, documents, audio and location are stored in the conversation along with the message | Uploaded files are held in object storage in Frankfurt, in a separate area for each customer - Template messages | Templates are defined in your own WhatsApp Business account and go through Meta approval | The approval decision and how long it takes rest with Meta; a rejected text is corrected and resubmitted, we do not commit to a timeframe - Past conversations | Conversations that accumulate from the moment the connection is made stay on the customer card | Conversations that accumulated on the phone before the connection are not carried over to the Cloud API; history starts accumulating from scratch - Commercial message consent | The İYS connection works in both directions: consent lookup and notification to İYS, through the authorised integrator Verimor | Sending marketing content is limited to consented lists; we do not make sending without consent easy through the product - Instagram DMs and comments | Instagram direct messages land in the same shared inbox over a separate connection | Instagram is not in the scope of this connection What we are able to say ##### What we have verified - Live | The Meta WhatsApp Business Cloud API connection runs in production today - v21.0 | The Meta Graph API version used in the connection - Meta-approved | Connected via our Meta-approved app; account, number and invoice stay yours - Verimor / İYS | Commercial message consents both ways: consent lookup and notification to İYS Implementation ##### How is the WhatsApp connection rolled out? - Discovery and the number decision | Which teams will be messaging, whether the existing number will be used or a new business number obtained, which legal entity the verification will run through — we make these decisions together. - Setting up the Meta side | Meta Business account, business verification, WhatsApp Business account and number registration. The account is opened in your name; we run the process as part of the setup and ask you for documents and approvals. - CRM configuration and testing | Your account is authorised on our app; the inbox, permissions, customer card fields and templates are set up. Your customer list is imported and number matches are verified with test messages. - Training and go-live | Rep and manager training, close follow-up in the first week. We do not commit to a timeframe before discovery; after the discovery call we give you a date, not a range. The scope of the setup, and any fee for it, is worked out in the discovery call and shared in writing before the work starts. ##### Our limits: what we do not promise on this page These headings come up whenever WhatsApp integration is discussed. We promise none of them, and we write down why. - We do not sell message bundles or credits. Meta invoices you for the conversation charge directly; we do not add anything on top of that charge. - We do not say “this many messages a day” or “unlimited sending”. Meta sets your sending limit, and that limit does not come back to us as a readable value from the API; we do not promise a figure we do not know. You can see your current limit in your Meta Business account. - We do not present pairing a phone with a QR code as a product promise. The same inbox can be connected this way too, but the method is not Meta's official API and it carries the risk of the number being restricted by Meta. The route we recommend is the official Cloud API; if you still prefer this route, we share the risk in writing and make the decision together. - Instagram is not part of this connection. Its direct messages land in the same shared inbox over a separate connection. The detail is on the Instagram CRM page. Data location: Your data is hosted in the European Union — the database in Helsinki, files in Frankfurt, backups in Falkenstein. We wrote out one by one which component sits in which country, and what we do not offer in Türkiye, on the Security page. The message itself also passes through Meta's infrastructure; this holds for every enterprise setup that uses WhatsApp. Seen from Türkiye, both are transfers abroad under KVKK art. 9; we establish the basis for the transfer together during the contract process. The detail is in the KVKK privacy notice. Certification: We do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. The canonical limits that apply to all of the integrations — stock sync, the order-invoice-collection chain and production automation — sit in one place: the three things we do not promise. ##### We write the figure on the pricing page, not on this one Meta's conversation charge is billed to you directly; the plan prices on our side we keep in one place — so that you never read a different figure in two places. See pricing Three plans, the scope table and separately priced items, all on one page. FAQ ##### Frequently asked questions about WhatsApp integration - Can we connect WhatsApp to Rapitek CRM? | Yes, this connection runs in production today. We connect your own Meta WhatsApp Business account to the CRM through Meta's official Cloud API; incoming messages land in the team inbox, the sending number is matched to a customer record and the conversation is assigned to a rep. Setting it up does not require a provider-specific development project; the connection exists in the product and is configured during setup. - Whose name are the number and the Meta account in? | In your name. The WhatsApp Business Account (WABA) and the business number are opened under your own account; the connection is made by authorising our Meta-approved app. This means you can withdraw the authorisation at any moment and the number stays with you. We run the verification and registration steps as part of the setup, but we are not the owner of the account. - Does the fee we pay Meta appear on your invoice? | No. Meta invoices you for the conversation charge directly; it is collected from the payment method set up in your Meta Business account. We do not sell message bundles or credits and we do not add anything on top of that charge. The plan scopes on the Rapitek side, and the items priced outside the plan price, are written on our pricing page. - Can we use our existing WhatsApp number? | Yes, you can — on one condition. If the number is in use in personal WhatsApp or in the WhatsApp Business app today, it has to be deleted from there before it is registered to the Cloud API; it does not work in two places at once. Old conversations that accumulated on the phone are not carried over to the CRM; history starts accumulating from the day of the connection. Getting a new business number is also possible — the decision is made together in the discovery call. - How long does the setup take? | We do not commit to a timeframe before discovery; after the discovery call we give you a date, not a range. The whole setup — discovery, configuration, data migration and training — is planned against that schedule, and the WhatsApp connection is built within it. How long business verification and template approvals take on Meta's side depends on Meta; we run the process but we do not give a commitment for Meta's decision time. - Can we message a customer whenever we want? | For 24 hours after the customer messages you, replies can be sent as free text. Outside that window, only a Meta-approved template message can be sent. This is Meta's own platform rule; it is not a restriction the product imposes. That is why we prepare your templates together during setup. - How does template approval work? | Templates are defined in your own WhatsApp Business account and submitted for Meta approval. We prepare the text in line with Meta's content rules, submit it and follow the process; a rejected text is corrected and resubmitted. The approval decision and how long it takes rest with Meta, not with us. - Can we send bulk notifications or campaigns? | Sending is done only with Meta-approved templates and to lists that have commercial message consent; consents are managed in both directions through the İYS connection. How many messages you can send is set by the upper limit Meta grants your account; because that limit does not come back to us as a readable value from the API, we do not give a figure on this page. You can see your current limit in your Meta Business account. - Is it possible to connect by pairing the phone with a QR code? | Technically possible, but we do not present this as a product promise. This method is not Meta's official API and it carries the risk of the number being restricted by Meta; if that risk materialises, your business number goes down. The route we recommend is the official Cloud API. If you still prefer this route, we share the risk in writing and make the decision together. - Can everyone on the team message from the same business number? | Yes. Incoming messages land in a shared inbox, conversations are assigned to reps and handed over when needed. The mechanism is this: because the messaging runs from a single company number rather than personal lines, the number the customer sees stays the same even when the rep changes. How the inbox is organised inside a team — handovers, internal notes, response-time tracking — we covered in detail on the WhatsApp CRM page. - Do Instagram messages land in the same inbox too? | Yes. Instagram direct messages land in the same shared inbox as WhatsApp; the conversation is assigned and handed over the same way. We connect Instagram separately during setup; the detail is on the Instagram CRM page. - Where are our messages stored? | On the CRM side, in the European Union: the database in Helsinki, uploaded files and media in Frankfurt, database backups in Falkenstein. We do not have a single component in Türkiye and we do not offer a region choice. The message itself also passes through Meta's infrastructure. Seen from Türkiye, both are transfers abroad under KVKK art. 9; we establish the basis for them together during the contract process. - What happens if we want to end the connection? | You can remove our app's authorisation unilaterally from your Meta Business account; the number and the WhatsApp Business account are already in your name. The conversations and customer records that accumulate in the CRM are yours and can be exported. We do not build an arrangement that creates lock-in. ##### Related pages - WhatsApp CRM | What comes after the connection is made: the shared inbox, conversation handovers, team routines and response-time tracking. - Integrations | The connections that work in the product today, the ones we build on request, and the three things we do not promise — all in one list. - Instagram CRM | The 24-hour window and Instagram's limits are written down as they are. Instagram direct messages land in the same shared inbox. - Security | Which country the data sits in, the sub-processor list, authorisation, and what we do not offer yet. ##### Let's plan your WhatsApp line in 30 minutes In the demo call, let's go through the number decision, the verification steps on Meta's side and how the inbox will be set up in your team, using your own scenario. Request a demo The scope of the setup, and any fee for it, is worked out in the discovery call and shared in writing. ### [WooCommerce Integration: CRM Connection | Rapitek CRM](https://rapitek.com/en/woocommerce-integration) WooCommerce customer, order and form data moves to the CRM; quote requests land in a record, wholesale splits off. We build it with REST API and webhooks. Integration · WooCommerce store #### Every buyer who comes from your WooCommerce store finds a matching record in the CRM. Orders, payments and delivery run in WooCommerce; the buyer, the quote request and the wholesale customer are recorded in the CRM. We build the connection ourselves, with the REST API, OAuth2, signed webhooks and import. Request a demo Schedule a discovery call ##### A store on your own server: flexible, but nobody owns it If your WooCommerce installation was set up by an agency, grew over the years through plugins and no longer has a single owner inside the company, that flexibility looks like this on the sales side: - Customer data sits in the store database, quote requests in a form plugin, correspondence in a mailbox. None of the three knows the others. - A “price for a bulk order” request from the site lands in a shared mailbox; who will handle it is unclear, and the ones left unanswered are never seen. - The same company both buys retail from the site and negotiates wholesale; that the two belong to the same customer comes together on no screen at all. - Store reports describe the order, not the customer: who bought a second time, who returned an item, who complained — none of it sits together. - When the agency changes, or when a plugin goes un-updated, historical data is put at risk; nobody holds a copy that has been taken outside. This picture is not a store-software problem, it is an ownership problem. What the CRM does is not to replace the store; it is to move the customer side somewhere independent of the store, somewhere you own. ##### How is the connection built — and why is it not a WordPress plugin? There is no out-of-the-box module for WooCommerce, and we will not say there is. The connection is built as an integration project whose scope is determined in the discovery call, using the REST API, OAuth2, webhooks and import/export. We have no plugin published in the WordPress plugin directory either; we cannot say “install it from the plugin store”. Rapitek is not an e-commerce platform. Products, prices, stock, cart, payment and shipping stay on the WooCommerce side. What the CRM adds is the customer side: the buyer's record, the quote request, the communication history, repeat sales and the wholesale line. The connection is built with three tools: - REST API — the product ships out of the box with 183 business objects, and each one is published in the REST API with its own data and schema endpoint; you can read the field structure from outside with describe. Access is authorised with OAuth2, no user password is shared; multiple operations and bulk writes are supported. - Outgoing webhook — events in the CRM are delivered to your system signed; a failed call is retried and the target address is verified. - Import — a four-step wizard: upload, map fields, preview, run. 100,000 rows per job, 25 MB per file, more than 75 objects. Export is done in the same module; because we have not measured its limits, we do not put a figure here. We will not overstate field mapping: of the 34 import jobs we measured across the 8 tenants we could access, 16 failed, and the hyphenated “E-posta” header in Turkish exports does not map automatically. We do not make a statement such as “zero data loss guaranteed”. That is why we run the first migration ourselves during setup and confirm the mapping together on the preview screen. The proof that this connection is not a bluff is in the product's own use: today, in one live customer installation, a third-party ERP integrator reads and writes records over this same REST API. We give no names, because we do not have permission to publish the customer's or the integrator's name; what we are saying is a measured fact. This is a single installation, not a list of case studies. We set out our general approach on the integrations page, and how the same framework looks on a hosted store on the Shopify integration page. A concrete scenario ##### Thursday 10:20 — a “price for a bulk order” request came in from the site. Once the connection is in place: - The request lands in a record, not in a mailbox | The form on your site is connected to the CRM's REST API or to a signed webhook; the incoming record lands on the list as a lead with its source tagged. It does not get lost in a shared mailbox. - The owner is clear, and what went unanswered is visible | The record is assigned to a person and open requests stay on the list. The question “who answered this?” is answered on the screen, not around the team. - The same company's retail history is visible | If the requester has bought from the site before, the matching key links them to the existing card. You go into the wholesale negotiation knowing the history. - The quote process runs tied to the record | An opportunity is opened, a price list is chosen, the quote comes out as a PDF and the approval process runs. Quote → order conversion is a ready-made action in the product. - Outgoing mail leaves the individual's inbox | If your Gmail account is connected with OAuth, outgoing mail is sent from inside the CRM and tied to the same record; the connection covers sending and calendar sync, and inbox reading is switched off. Outlook and Microsoft 365 connections are not live. Generic IMAP/SMTP is not supported either. - Historical data stays with you | Customer data sits in a separate database of your own, independent of the store, and is exported whenever you want. When the agency changes, the customer memory does not go with it. ##### Flows that can be built between WooCommerce and Rapitek CRM - Migrating the customer and order export | A CSV/Excel export taken from WooCommerce is imported into the CRM with the four-step wizard; you confirm the mapping on the preview screen. We run the first migration ourselves as part of the setup. - Connecting the site forms to the CRM | Quote, dealership and contact forms are connected via the REST API or a signed webhook; the incoming record lands as a lead with its source tagged. This is a flow we configure during setup. - Retail and wholesale merging on the same card | If the company buying from the site and the one negotiating wholesale are the same, the records are merged with a matching key; duplicate cards are cleaned up during setup. - Quote, approval and price list | A wholesale request runs as an opportunity: price list, quote PDF template (ready in Turkish and English) and approval process. The administrator edits the template themselves. - Signed and verified outgoing notification | An event in the CRM goes to your server as a signed webhook; the receiving side verifies the signature and filters out fake notifications, the target address is verified and a failed call is retried. - Data ownership and export | Your CRM data is held in a separate database that belongs to you and is exported as Excel/CSV whenever you want. Field-level change history is recorded. Choosing a method ##### Which method, and when? The method is chosen during discovery, according to how open your server is to the outside and who manages the store. Method | What it is for | When it is preferred - Import (Data Hub) | The CSV/Excel export is imported in four steps; a suggestion is offered for header matching — 19/19 and 13/17 on the headers of the two exports we measured — and you confirm the mapping on screen | When there is no external access to the server, or when periodic freshness is enough - REST API (183 business objects, each with its own endpoint) | An event on the store side is written into the CRM as a record; each object has its own data and schema endpoint, access is authorised with OAuth2 and no user password is shared | When a continuous flow is wanted; the layer that does the writing is written within the project scope - Outgoing webhook | Events in the CRM are delivered to your server signed; the target address is verified and a failed call is retried | When something that happens in the CRM needs to trigger the store side - Your agency or your own developer | They can write the connection themselves using the same REST API; we provide the schema, OAuth2 access and the field mapping table | When there is already a team managing the site and you want to keep working with that team What we can say ##### What we have verified — the good news and the bad - 16 / 34 | Import jobs that failed, of those measured across the 8 tenants we could access - 183 | Business objects in the REST API - A single installation | In a live setup a third-party integrator reads and writes records on this API - Plain text | The shipment tracking number is held as a field; no shipping API is called Implementation ##### How is the WooCommerce connection put live? - Discovery | Who manages your store, how open is the server to the outside, which form plugin is in use, and in what format can historical data be exported? We recommend that your agency is in this call. - Scope, field mapping and method | The matching key, the direction of the flow, its frequency and the duplicate-record rule are put in writing. The field mapping table, the scope and the fee, if there is one, are shared in writing before work starts. - Configuration and test migration | Fields, channel lists, the form connection and permissions are set up; a test migration is run with a sample export. Header matching is verified one by one at the preview step. - Team training and go-live | Team training and close follow-up in the first week. The date of this step is set during discovery; we do not commit to a duration before discovery. ##### Our limits: what we do not promise on this page Some of the first things that come to mind in an e-commerce context are not our job. We turn six of them down by name: - We do not promise stock synchronisation. We do not say “your stock will be in sync with the store”; authority over the stock record stays in WooCommerce and in your warehouse system. - We do not say that the order → invoice → collection chain will flow on its own. The chain is built into the product, but we do not think it is right for it to be sold as an automated accounting flow. - We do not promise production and MRP automation. The bill of materials and the production line definition exist in the product; we cannot describe work order execution with a reference today. - We do not do shipment tracking. The tracking number is a plain text field in the product; no shipping service is called and shipment status is not read by the CRM. - We are not a solution installed from the plugin directory. We have no plugin published in the WordPress plugin directory; the connection is work that we build. - Rapitek is not an e-commerce platform. The storefront, product management, payment and returns stay in WooCommerce; the CRM takes the customer side. We wrote the reason for the first three, and “what can be done instead”, line by line in one place: the three things we do not promise. We do not repeat it here, so that we do not end up making two different statements in two places. We do not overstate data migration either: of the 34 import jobs we measured across the 8 tenants we could access, 16 failed. We do not make a statement such as “zero data loss guaranteed”; instead we go through the preview step together and run the first migration ourselves as part of the setup. Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no region selection feature. Under KVKK art. 9 this is a transfer abroad; we establish your legal basis for the transfer together during the contract process. The details are on the security page and in the KVKK information notice. Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your corporate security assessment forms and describe the architecture in writing. ##### We write the figure on the pricing page, not on this one The scope of the WooCommerce connection, and its fee if there is one, are worked out in the discovery call and shared in writing. Plan prices we keep in a single place — so that you do not read a different figure in two places. See the pricing Three plans, the scope table and separately priced items on a single page. FAQ ##### Frequently asked questions about the WooCommerce integration - Is a WooCommerce and CRM integration possible? | Yes — not with an out-of-the-box module, but as an integration project with a defined scope. The connection is built with the REST API, OAuth2, signed outgoing webhooks and import/export. Which of the customer, order and form data flows in which direction and how often is worked out during discovery and shared as a written scope. - Do you have a ready-made plugin in the WordPress plugin directory? | No. We have no plugin published in the WordPress plugin directory and we will not write as if we did. What we have is a documented interface: the product ships out of the box with 183 business objects, and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there are OAuth2, signed outgoing webhooks and a four-step import/export wizard. The connection is written on top of these, specific to your installation. - Our site is on our own server and closed to the outside. Is integration still possible? | Yes, only the method changes. On an installation closed to the outside, the flow runs through import/export: customer and order exports taken from the store are imported into the CRM periodically with a template. Because it does not require external access to your server, this is the route we recommend at the start; if access conditions change later, the same scope is moved to an API-based flow. - Can we migrate our customer and order export with CSV? | Yes. A four-step wizard runs: upload, map fields, preview, run. We measured header matching: in one Salesforce lead export 19 of 19 headers matched correctly; in one HubSpot contact export 13 of 17 — two matched incorrectly and “City” did not match at all. The hyphenated “E-posta” header in Turkish exports does not match either. That is why you confirm the mapping one by one on the preview screen. 100,000 rows per job, 25 MB per file; the accepted formats are .csv, .xls and .xlsx. - Will the quote form on our site land in the CRM? | Yes. Your form is connected to the CRM's REST API or to a signed webhook; the incoming record lands on the list as a lead with its source tagged and is assigned to an owner. We write this not as an out-of-the-box module but as a flow we configure during setup. Which form fields go to which CRM fields is set out in a table during discovery. - Our webhook address is on an internal network. What happens in terms of security? | Outgoing webhook calls are signed; the receiving side verifies the signature and filters out fake notifications. The target address is also verified, so a call to an arbitrary internal network address is prevented. A failed call is retried. Which event goes to which endpoint is defined during setup. - Our agency manages the site. Can they write the connection themselves? | Yes, this is a route we support. Your agency or your own developer can write the connection themselves using Rapitek CRM's REST API; we provide the API documentation, OAuth2 access, the object definitions and the field mapping table. As a separate fact: in one live customer installation a third-party ERP integrator reads and writes records over this same API. This is a single installation, not a list of case studies. - Our retail and wholesale customer is the same company. Do the two lines of business merge on one card? | They do merge. Records are linked to the same company card with a matching key — tax number, email or phone; duplicate cards are cleaned up during setup and the rule stays in the written scope. The wholesale side is read as opportunities and quotes and the retail side as order history, under the same card. - Will our stock work in sync with WooCommerce? | We do not promise real-time stock synchronisation. Authority over the stock record stays in your store and in your warehouse system; a stock mirror fed from the CRM produces two numbers that do not agree in two places. We wrote the reason, and what can be done instead, line by line in the limits section of the integrations page. - Does an order turn into an invoice in the CRM, can we issue e-invoices? | No. The order → invoice → collection chain is built into the product, but we do not think it is right for it to be sold as an automated accounting flow. Rapitek CRM does not issue e-Fatura or e-Arşiv documents and is not a GİB private integrator; fields such as ETTN or GİB status do not exist in the product. Your invoices continue to be issued at your current integrator; the invoice number, date and amount can be carried into the CRM as fields. - What happens to our customer data when the agency changes? | Your CRM data is held in a separate database that belongs to you and is independent of the store; you can export it as Excel/CSV and take it with you whenever you want. Field-level change history is recorded, so it can be seen who changed a field and when. Even if the site technology changes, the customer memory stays with the company. - What does the WooCommerce integration cost? | We do not write a figure on this page, because the fee depends on the scope: the number of records to be migrated, the direction of the flow, its frequency and whether your server can be accessed. After the discovery call we share the scope and the fee in writing. A project-specific integration is a separate line of work outside the plan price; the plan details are on the pricing page. - How long does it take for the WooCommerce connection to go live? | We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The setup consists of these steps: discovery, configuration, data migration, training and go-live. An import-based store flow is built within this plan; the scope of API-based flows is also clarified in the same discovery. - Where is the customer data migrated from the store held? | Wherever your WooCommerce server is, the CRM side stays in the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. Under KVKK art. 9 this is a transfer abroad; we establish the legal basis for it together during the contract process. Your CRM data is held in a separate database that belongs to you. The legal assessment here is information, not legal advice. ##### Related pages - Integrations | An overview of integration: which connection is live today, which ones we build on request, and the reason for the three things we do not promise. - Shopify integration | How the same framework looks on a hosted store: customer data, consent records and the wholesale line. - Netsis integration | The ERP side behind the store: account, balance, order and invoice information appearing on the sales screen. ##### Let's clarify your WooCommerce flow in 30 minutes In the demo call, let's talk through how your customer export and your site forms will connect to the CRM, over your own installation; let's choose the method and the scope together. Request a demo The scope of the setup, and its fee if there is one, are worked out in the discovery call and shared in writing. ### [Moving from Zoho to Rapitek CRM | Setup Included](https://rapitek.com/en/zoho-crm-alternative) Moving from Zoho to Rapitek CRM: setup, migration and training run by the team that builds the product. Compare quotes on setup, not licence alone. For teams coming from Zoho #### When you evaluate quotes, write the setup next to the licence. A CRM costs more than its licence: configuration, data migration, integration and training. Until it is written down who takes on those four items, two quotes are not being weighed on the same scale. We write down our own side: those four items are ours. Request a demo See pricing ##### The short answer We do not compare ourselves with another product on this page. We write down what we do and what we don't. What sets Rapitek apart is not the licence price but the delivery model. Here, the team that builds the product does the setup, the data migration and the training; the scope is worked out in discovery and put in writing. Buying a product you will set up yourselves and taking delivery of a system that has been set up are two separate line items; the calculation has to be made by writing down both. If the fields have not been fitted to the process, the data has not been migrated and the team has not been trained, the product goes unused — and the licence being paid for produces nothing in return. We have seen this in our own projects. Write that line into your calculation too. Our own side ##### What Rapitek CRM has, and what it doesn't Area Rapitek CRM - Licence price | Plan prices are public: from 39 USD - Who does the setup | The team that builds the product - Time to go live | We don't commit to a timeline before discovery; after it we give a written date, not a range - WhatsApp | Inside the product - Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery - Support and training language | Turkish - Data separation | A separate database per customer - Ecosystem breadth | Narrow. We have no app marketplace and no trained partner network — we say so plainly - Usability | We try to keep it simple, and we simplify further during setup How to evaluate ##### Put these three lines in your evaluation too - Licence | Monthly per-user price × users × 12. This is the easiest line to calculate; write it out separately on every quote you receive. - Setup and configuration | Fields, stages, roles, reports, data migration and integration. If you'll do it yourself: who, and how many weeks of their time? If a partner will: get their quote and write it on this line. - The risk of it going unused | In a CRM nobody uses, the licence being paid returns nothing — we have seen this in our own projects. Whether the team gets trained, and whether anyone stays close through the first month, belongs on this line. ##### When we are not the right product - If you want accounting, HR, projects and support under one roof. We have no app marketplace and no product family that wide; we can't meet that need. - If you have the capacity to do the setup yourselves. If someone in-house will configure the system and train the team, our biggest contribution disappears. - If your team is under 5 people. Our Sales and Platform tiers require at least 5 users. - If you need a local implementation partner abroad. We have no such network; setup and support come from our own team. - If your budget only stretches to a licence. If you can't fund setup, data migration and training on top of it, we understand that and won't push. FAQ ##### About moving from Zoho to Rapitek CRM - Can our Zoho data be migrated? | Yes. Leads, contacts, accounts, opportunities and your custom fields are migrated and duplicates cleaned out. The scope is decided in discovery and put in writing. - How much does Rapitek CRM cost? | Our plan prices are public: they start from 39 USD, and we publish the current tiers on our pricing page. What that price buys is that the setup is ours — configuration, data migration, integration and Turkish-language training. When you weigh up any quote you receive, put setup, customisation and training on the line next to the licence. If you can do that work yourselves, that line closes in your favour, and we say so honestly. - Do you connect to Turkish ERPs? | We connect to systems like Logo, Netsis, Mikro and Paraşüt over REST API, OAuth2, webhooks and import/export, through the team that builds and develops the product. It is not an off-the-shelf connector — access and field structure differ from one installation to the next, so we build the connection per project; the scope and cost are defined in discovery. - How long does the migration take? | We don't commit to a timeline before discovery. After the discovery call we give you a date, not a range: once the configuration, data migration and training plan is settled, the schedule comes to you in writing. ##### Let's work out the total cost together. Put the licence, the setup and the risk of it going unused side by side and look at them. We'll also tell you where we are not the right product. Get a demo and quote 30 minutes · No obligation · The call is held in Turkish ### [Zoom Integration: Meeting Transcript and Summary | Rapitek CRM](https://rapitek.com/en/zoom-integration) Upload the meeting audio recording to the CRM; get a transcript, a summary and action items. An automatic Zoom connection is built per project over the Zoom API. Integration · Zoom #### Zoom's audio recording turns into a transcript, a summary and action items inside the CRM. You upload the recording to a customer or opportunity record; the audio is transcribed, a summary and action items are extracted, and the items can be turned into tasks. Pulling the meeting from Zoom automatically, on the other hand, is built over Zoom's API as a separate piece of work whose scope is determined in discovery. Request a demo Schedule a discovery call ##### Forty minutes of talking, three lines of notes left behind Forty minutes are spent talking and three lines of notes are left behind — and the person writing those three lines is trying to take part in the conversation at the same time. This is where the mechanism sits: speech is immediate, while a note is a summary written afterwards; when both are done at once, the trace that remains is not the conversation itself but that summary. Here is the picture we see in our own calls and in customer projects: - The rep tries to listen and to write at the same time. They cannot do both well; the side that gets sacrificed is the notes. - The question “What did we talk about last time?” eats the first five minutes of the next call. The customer explains the same thing a second time. - The commitments made in the conversation — price, delivery date, scope — never make it anywhere in writing. When a disagreement comes up, the two sides' memories are set against each other. - Action items are not assigned to anyone. Because the sentence “We'll send the quote” never becomes a task, it waits three days. - Someone who has just joined the team cannot read the history; they only know what has been told to them. When the rep changes, the customer starts from scratch. - If a recording is to be made, the consent question is left hanging: who asks, when do they ask, where is the answer kept? If these questions have no written answer, the decision to record is left hanging too. This page describes two jobs separately: leaving a trace from the call that becomes a record, and doing it in a way whose consent is documented. We put the second one up front as well. ##### What we measured: 22 recordings, 19 completed, a single tenant — ours There is no out-of-the-box module for Zoom on our side, and we will not say that there is. The connection is built as an integration project — with REST API, OAuth2, webhooks and import/export — whose scope is determined in the discovery call. Pulling the meeting from Zoom automatically falls into exactly this class. But the chain that processes the content of the meeting does exist in the product: the audio recording is uploaded to the CRM, transcribed, a summary and action items are extracted; the items can be turned into tasks and assigned to an owner. Audio recording in the mobile app exists as well. Now the measured state of this chain — without overstating it. To date this flow has run only in our own tenant: a total of 22 recordings were processed, 19 of them completed the transcript and summary stage, and the last recording was taken on 23 July. We cannot say that it works in a customer installation, so we do not say it. You will not read the sentence "Our customers run their meetings from the CRM" on this page; the number we measured does not support it. Why do we write it this way? Because this feature gets tested very quickly after it is bought: it either works in the first meeting or it does not. Having said "fully automatic" before the sale turns into a support ticket opened in the first week. Stating the scope narrowly and accurately from the start serves both of us. When an automatic connection on the Zoom side is asked for, the surface it rests on is the REST API and OAuth2. We can say that this surface really is usable from the outside on the basis of a measured fact: in one live customer installation a third-party ERP integrator reads and writes records over that same REST API. We do not give a name because we do not have permission to publish it; this is a single installation, not a case list. We described the same framework as it applies to an ERP on the Netsis integration page, and our general approach on the integrations page. A concrete scenario ##### Tuesday, 16:45 — a forty-minute remote call has just ended. If this flow is switched on, here is what changes: - The recording is uploaded where the work sits | The audio file is attached to the customer or opportunity record. The meeting sits next to the deal it is about, not in an e-mail attachment or on someone's computer. - The audio is transcribed and the conversation becomes readable | A transcript is produced. Commitments such as price, delivery date and scope are tied to text rather than to memory; you do not have to interrupt the conversation in order to take notes. - A summary and action items are extracted | A summary and a to-do list are produced from the forty-minute recording. The sentence "We'll send the quote" remains as a line; it can be read and work can be built on it. - The action item becomes a task and is assigned to an owner | Items are opened as tasks and handed to an owner together with a date. The quote that waited three days stops being a reminder problem, and stops being a record-keeping problem as well. - Consent is taken at the start of the call and documented | You tell the participants at the outset that the call will be recorded. If a biometric voiceprint is to be processed, separate explicit consent is required for it; the consent text, its version and its time are kept in the data model. - The next call starts from the transcript, not from scratch | Someone who has just joined the team opens the record and reads the history. The customer does not explain the same thing a second time; when the rep changes, the relationship does not go back to the beginning. ##### The surface you rely on on the meeting side - The audio → text → summary chain | The uploaded audio recording is transcribed and a summary and action items are extracted. The chain is built into the product; the usage measured to date is only in our own tenant. - From action item to task | The items that come out of the summary are opened as tasks, given a date and assigned to an owner. The output of the meeting does not stay as a text file. - Audio recording in the mobile app | Recording can be started from the mobile app. Recording stops when the screen is locked and nothing is recorded in the background — this is a deliberate choice made to comply with an app store rule. - The recording file sits in Frankfurt | Uploaded audio recordings are kept in the file storage in Germany, in a partition set aside per tenant. They are not thrown into a shared pool. - Consent evidence chain | The consent text, its version, the time it was taken, the IP address and the source address are kept in the data model. A separate explicit consent is required for a biometric voiceprint. - REST API and OAuth2 for the Zoom API | This is the surface relied on when automatic pulling of the meeting is asked for: the product ships out of the box with 183 business objects, and each one is published in the REST API with its own data and schema endpoint; access is authorised with OAuth2, and the field structure is read from outside with describe. What is what ##### What exists and what does not on the meeting side The only measured usage on this page is in our own tenant: 19 of 22 recordings completed the transcript and summary stage. We do not say that it works in a customer installation. Topic | What exists today | How it is set up - Transcript and summary from an audio recording | The chain exists in the product: audio is transcribed, a summary and action items are extracted | Switched on within the scope of implementation; you upload the recording and see the output on the record - Pulling the meeting from Zoom automatically | We have no module that connects to Zoom | Written over the Zoom API as a separate piece of work whose scope is determined in discovery - Audio recording in the mobile app | Exists; recording stops when the screen is locked, nothing is recorded in the background | Started from the app. We describe this behaviour as it is, not as a shortcoming - Matching the meeting to a calendar | Calendar sync works only with Google Calendar | You connect your Google account; Outlook calendar is out of scope - Processing a biometric voiceprint | It is not a default processing activity; it requires separate explicit consent | The consent text, its version, time and source are kept in the consent evidence chain - Live transcription during the meeting | Not available; processing starts after the recording is finished | We do not offer it. If what you need is live captioning, say so at the start of discovery What we can say ##### What we have verified - 22 recordings | Total recordings measured in the audio→text→summary chain; in a single tenant - 19 completed | Recordings that completed the transcript and summary stage without trouble - 0 customers | Number of customer tenants that have used this flow to date - Frankfurt | Where the uploaded audio recording sits; a separate partition per tenant - Separate consent | If a biometric voiceprint is processed, explicit consent is taken separately Implementation ##### How is the meeting flow rolled out? - Discovery | We map out how your calls are run, who will make the recording and how your consent process works today. If you have a counterpart on the legal or compliance side, we recommend that they join this call. - Scope and consent text | Which calls will be recorded, how long the recording will be kept and how consent will be taken are put in writing. If a biometric voiceprint is to be processed, a separate explicit consent text is prepared at this stage. - Configuration and a sample recording | The flow is switched on and tested with your own recording: you see the quality of the transcript, how useful the summary is and the items that turn into tasks before you accept it. - Training and go-live | The subject we dwell on separately in team training is not a technical one: how to ask for consent at the start of a call. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. ##### Our limits: what we do not promise on this page Meeting AI is a heading that is easily overstated. We name the things we do not promise. - We do not say “Your Zoom meetings land in the CRM automatically”. We have no module that pulls the meeting from Zoom; the recording is processed by being uploaded to the CRM. Automatic pulling is a separate piece of work written over the Zoom API. - We do not say “Our customers use it”. We measured it: to date this flow has run only in our own tenant — 22 recordings, 19 of them completed, the last recording on 23 July. - We do not say “Record the meeting in the background”. Background recording was removed from the mobile app, and recording stops when the screen is locked. Presenting this as a feature would leave the user to notice the loss afterwards. - We do not recommend recording without the participants' knowledge. Recording is a matter of consent; if a biometric voiceprint is to be processed, separate explicit consent is required. This is not a limit of the product but a limit of the law, and it needs to be written on a sales page. - We do not offer live transcription during the meeting. Processing starts after the recording is finished. - We do not promise that your stock will be in sync, that the order → invoice → collection chain will flow on its own, or production/MRP automation. We wrote the reason for all three, and what can be done instead, in one place: the three things we do not promise. AI processing and sub-processors: transcribing and summarising an audio recording is an AI processing activity. We give you in writing, during the contract process, which sub-processors are involved and in which country the recording is processed; the list we can name today is in the sub-processor section of our security page. Rapi, the assistant inside the product, is a separate matter and is switched off by default; we wrote its scope on the Claude integration page. Data location: your data is kept in the European Union — the database in Helsinki (Finland), files including the audio recordings you upload in Frankfurt, and backups in Falkenstein (Germany). We have no component in Türkiye and we have no region selection feature. Under KVKK art. 9 this is a transfer abroad; we establish its legal basis together during the contract process. The detail is on the security page and in the KVKK disclosure notice. Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment forms and describe the architecture in writing. ##### Plan prices are out in the open; scope comes out in discovery The scope of the pulling flow on the Zoom side, and its cost if there is one, comes out in the discovery call. We publish plan prices and separately priced items such as Rapi AI credit on a single page. See the pricing Three plans, a scope table and separately priced items on one page. FAQ ##### Frequently asked questions about the Zoom integration - Does Rapitek CRM integrate with Zoom? | Partly, and we write the limit openly. What exists in the product is this: you upload the meeting's audio recording to the CRM and get its transcript, its summary and its action items; the items are turned into tasks. An automatic connection on the Zoom side — the meeting being pulled in on its own — is a separate piece of work written over the Zoom API whose scope is determined in discovery. - Do our Zoom meetings land in the CRM automatically? | No, they do not land on their own. We have no module that connects to Zoom; the recording is processed by being uploaded to the CRM. It is enough to download your Zoom cloud recording and attach it to the customer or opportunity record. If you want automatic pulling, that is a piece of work written over the Zoom API and scoped separately. - Do a transcript and a summary really come out of a meeting recording? | They do, and we write the measured version as it is: 22 recordings have been processed in this flow to date and 19 of them completed the transcript and summary stage. All 22 of these recordings were taken in our own tenant, the last one on 23 July. So the chain works; but we cannot tell it through a customer installation. - How many of your customers use this flow? | As far as we know, none. All 22 of the measured recordings are in Rapitek's own tenant. We write this instead of hiding it, because the sentence "our customers use it" is one that changes a purchasing decision and should not be built without grounds. The day it works in a customer installation, we will write it here. - Can we record the meeting in the background, with the phone locked? | No. Background recording was removed from the mobile app, and recording stops when the screen is locked. This is not a fault but a deliberate change made to comply with an app store rule. We also make a point of saying in team training that the app has to stay open and the screen unlocked while recording. - Is consent required to record a meeting? | Yes. You need to tell the participants at the start of the call that it will be recorded. If a biometric voiceprint is to be extracted from the audio, separate explicit consent is required for that — a general disclosure notice is not enough. In the product, the consent text, its version, the time it was taken, the IP address and the source address are kept in the data model; that is how the evidence chain is built. - Where are the audio recordings stored? | Uploaded audio recordings sit in the file storage in Frankfurt (Germany), in a partition set aside per tenant; they are not thrown into a shared pool. Your CRM database is kept in Helsinki (Finland) and the backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. - Which provider processes the recording? | Transcribing and summarising the recording is an AI processing activity; we give in writing, during the contract process, which sub-processors are involved and in which country the processing is done. The list we can name on the site is in the sub-processor section of our security page. If you have a question specific to this item, ask it in discovery; we answer in writing. - Which languages does the transcript work in? | We do not give a published list for the language coverage of the transcript, because we cannot support it with our own measurement. The right path is this: bring a sample from your own recordings to the demo call, let us run it together, and see the output before you buy. That is the fastest answer for us too. - Do Zoom meeting invitations land in the CRM calendar? | Calendar sync works only with Google Calendar, and it is two-way: pull, create, update and delete. Outlook calendar is out of scope — Outlook and Microsoft 365 connections are not live. However your Zoom invitations sit in your calendar is how they are reflected into the CRM; we have no direct calendar connection with Zoom itself. - Can the items from the summary be turned into tasks? | Yes, and this is the genuinely valuable part. The items that come out of the summary are opened as tasks, given a date and assigned to an owner. That way the output of the meeting stops being a text that is read and forgotten and turns into work that is followed up. Whether the task is closed can also be tracked from the report. - How long does implementation take, and is it included in the plan price? | Switching on recording upload and the summary flow is within the scope of implementation. Project-specific development such as automatic pulling over the Zoom API is scoped and priced separately. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. - Where is our data kept? | In the European Union: the database in Helsinki (Finland), the files you upload — including meeting audio recordings — in Frankfurt, and the database backups in Falkenstein (Germany). We have no component in Türkiye and we do not offer region selection. Under KVKK art. 9 this is a transfer abroad; we establish its legal basis together during the contract process. - Can we see it before buying? | There is no trial you start on your own. First we run a 30-minute live demo — and for the subject of this page, the best demo is a sample from your own meeting recording. We run it together and you see the transcript and the summary before you buy. After that we open a time-limited demo account. ##### Related pages - Integrations | Which connection works in the product today, which ones we build on request, and the reason for the three things we do not promise. - Mobile app | Where the audio recording is started: recording, business card scanning and offline behaviour for teams working in the field. - Security | Which country the data and the files sit in, the sub-processor list, the audit trail, and what we do not offer yet. ##### Let's test it with your own recording in 30 minutes Instead of describing the quality of the transcript and whether the summary is useful, we prefer to show it. Let's set up the consent process together in the same call. Request a demo Bring a sample from your own meeting recording to the demo; let's look at the output together. ## Industries ### [Accessories CRM: Sample Cases and Fair Cards | Rapitek CRM](https://rapitek.com/en/accessories-crm) The display sample case is booked out to the dealer record and stays an open task once its return date passes; region, payment term and discount sit on the same card, so the quote uses those values. ##### What we set up, and how - Book the sample case that goes out on display out to the rep; when the delivery and return dates pass, the case stays on the list as an open task - Collect the cards coming back from a fair in a single pool, distribute them by region and open a follow-up task for the contacts that respond - Close the dealer visit from the mobile app with location verification and see from the record where the visit was marked - Keep region, payment term and discount rate on the dealer card so the quote comes out with those values - Sample Case Assignment | The case that goes out on display is an assignment task; the delivery and return dates are its fields, and a case that does not come back stays on the rep's open task list. - Fair Card Pool | Every card collected at a fair is a lead record; the fair attended stays in the source field, and the assignment rule defined during setup distributes the cards to the regional rep. - Showroom Visit Verification | The dealer visit is closed from the mobile app; location verification records where the visit was marked, and fake location detection is part of that check. - Dealer Discount and Payment Term Card | Region, payment term and discount rate are fields on the dealer record; the quote and the order take those values from the card. ##### Frequently asked questions - Can I track the samples on display at a dealer through the system? | Yes. Sample delivery is a task with delivery and return date fields; the ones not returned stay as open tasks and are visible from the dealer's card. - How do I process the hundreds of business cards that come back from a fair? | The cards are imported as lead records with the fair name written in the source field; the assignment rule defined during setup distributes them by region and a follow-up task is opened for each lead. - Can I see from the record that the rep actually visited the dealer? | The visit is closed from the mobile app; location verification writes into the record that the visit took place at the dealer's address, and the fake location flag is part of that check. When the dealer was last visited stays on its card. - Which is the best CRM software for accessories? | When choosing a CRM for the accessories sector you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your process in the accessories sector, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an accessories CRM system cost? | On the accessories side, a sample case that does not come back stays on the rep's task list; it is this field team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the accessories sector? | 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the accessories sector? | We start with a discovery call: we work out together your process in the accessories sector, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for accessories? | In accessories the dealer visit is closed from the mobile app; location verification records where the visit was marked. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Accounting Firm CRM: File Fees and Workload | Rapitek CRM](https://rapitek.com/en/accounting-firm-crm) The monthly fee and the last update date are fields on the client record, so files left behind drop onto a list. Time spent on a file accumulates on that same record. ##### What we set up, and how - Give every client file an owner, a contract date and a monthly fee field, and gather the files whose fee has not been updated for a long time into a single list - Accumulate the task time spent on a file on the client record and see how much workload each client creates side by side with its fee - Run the onboarding checklist for a new client step by step and keep any missing step on the list as an unclosed task - Record the handover steps and the returned documents of a departing client and track who is holding the file - File Ownership | Every client is an account record; the responsible member of staff is in the assignment field, who is holding the file is read from that field, and no separate list is kept. - Fee Update Tracking | The monthly fee and the last update date are fields on the client record; the ones whose date has fallen behind drop onto a list and are opened as a quote opportunity. - Workload Measurement | Time spent on a file sits in the task records; when it is totalled per client, the fee and the effort come side by side in the same report. - Client Onboarding and Offboarding | Onboarding and handover are each a checklist; every step is its own task, and a step that does not close keeps the file's closure waiting on the list. ##### Frequently asked questions - Can I see how many hours a client actually costs the firm? | Yes. Time spent on the tasks attached to a file accumulates on the client record; when it is reported side by side with the monthly fee, it becomes visible which file is not returning the effort put into it. - Can I record the handover process when a client leaves the firm? | Yes. Handover is a checklist whose steps are tasks; the documents returned, the person handing over and the person receiving are recorded in those steps. - How do we catch files whose fee has not been updated for years? | The monthly fee and the last update date are fields on the client record; the ones whose date has fallen behind drop onto a list and are opened as a quote opportunity. The increase conversation is thereby tied to a calendar rather than to an argument. - Which is the best CRM software for an accounting firm? | When choosing a CRM for an accounting firm you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your firm's process, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an accounting firm CRM system cost? | On the accounting firm side, the member of staff responsible for each file is written into the assignment field; the users of the system are this office team. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the accounting firm sector? | 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the accounting firm sector? | We start with a discovery call: we work out together your firm's process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for an accounting firm? | Yes. The field and branch team can update the customer card, the note and the follow-up task from a phone. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Advertising CRM: Campaign Period and Load | Rapitek CRM](https://rapitek.com/en/advertising-crm) A campaign is a record with start and end date fields; production, print and broadcast are tasks that sit under it, each with its own delivery date. ##### What we set up, and how - Turn the campaign into a single record with a start and an end date and track the broadcast period from that record - Plan the production, print and broadcast steps as separate tasks under the campaign, each with its own delivery date - See the jobs falling in the same period in the calendar and read how full that period is before accepting a new job - Keep the advertiser and the supplier in separate account records and attach the sold and the bought side to the same campaign - Campaign Period | A campaign is a record with start and end date fields; which job belongs to which range is read from those fields. - Chain Steps | Production, print and broadcast are each a task; each sits under the campaign record with its own delivery date and owner. - Period Load | Tasks are gathered in the calendar by their date field; the number of jobs falling in a range is visible from the list, and the decision to accept is made by looking at it. - Advertiser and Supplier | Both are account records; because they are attached to the same campaign, the sold side and the bought side of the work are tracked from a single record. ##### Frequently asked questions - Do the agency, the media owner and the production company use the same setup? | The shared backbone is the same: the advertiser account, the campaign record and dated tasks. The stage names and the fields are defined during setup according to your company's role in the chain; on the media side the load of the period comes to the fore, on the production side the shoot and delivery steps do. - Can we see in advance that we have promised the same period to two customers? | Campaigns and tasks are gathered in the calendar by their date fields; the jobs falling in a range are listed side by side. The clash is visible before the job is accepted, and the threshold of the warning rule is also defined during setup according to the load level you set. - Can we see a one-day slip in the chain before the broadcast day? | Yes. Production, print and broadcast are separate tasks that sit under the campaign record with their own delivery date and owner. When a task's date passes without it closing, it stays on the list and appears side by side with the later steps of the same campaign; the slip is read without waiting for the day the campaign is due to start. - Which is the best CRM software for advertising? | When choosing a CRM for the advertising sector you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your advertising process, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an advertising CRM system cost? | In advertising, because the production, print and broadcast steps each sit with their own owner, more than one owner is defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the advertising sector? | 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the advertising sector? | We start with a discovery call: we work out together your advertising process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for advertising? | Yes. The field and branch team can update the customer card, the note and the follow-up task from a phone. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Aesthetic Clinics CRM: Post-Op Follow-Up | Rapitek CRM](https://rapitek.com/en/aesthetic-clinic-crm) The first contact channel of a patient still deciding, the procedure of interest and the last contact date are fields on one record; post-op checks are tasks tied to that date. ##### What we set up, and how - Send a patient still deciding a planned flow of educational content, patient reviews and frequently asked questions spread over six months - Attach the enquiry arriving from the web form, WhatsApp or Instagram direct messages to a lead record; for an Instagram sender with no record yet, opening a new lead with Instagram as the source is a setting switched on during setup - Tie the 1 week, 1 month, 3 month, 6 month and 1 year post-operative check-ups to reminders and skip no patient - While satisfaction is at its highest, send the permission form for before/after photos and the Google review request as steps tied to the check-up date, and keep the consent in a consent record - Answer as a team from a single number with the WhatsApp Business account connected during setup; have conversations assigned by the rule you define, and keep the history even when staff change - Six-Month Follow-Up Sequence | A patient still deciding can be attached to a follow-up sequence; every step of the sequence is a record with day interval, channel and template fields. The step whose turn has come is sent as educational content, a patient review or a frequently asked questions message; the sequence stops when the patient comes back for an appointment. - A Single Record for the Incoming Enquiry | An enquiry arriving from the web form or WhatsApp becomes a lead record; the channel of the first contact, the procedure of interest and the last contact date are fields on that record. Instagram direct messages land in the same shared inbox and are linked to an existing record by the Instagram username; opening a new lead for a sender with no record is a setting switched on during setup. - Post-Operative Check-Up | Check-up steps are opened as tasks tied to the operation date (1 week, 1 month, 3 months, 6 months, 1 year); a check-up that does not close stays on the list. - Before/After Consent Record | Photo permission is a consent record attached to the patient record; the date the form was sent, the scope of the consent and whether it has been withdrawn are fields on that record. The permission form and the Google review request go out as steps tied to the check-up date; the image of a patient without consent does not enter the consented list. - Multi-Session Procedure Protocol | Procedures spread over sessions are a protocol record attached to the patient record; which session it is, the physician performing it, the area treated and the number of days that must be left between sessions are fields on that record; the appointment for the next session is opened according to that interval and the post-session check-up is attached to the same protocol. ##### Frequently asked questions - Why is CRM critical for aesthetic clinics? | In aesthetic surgery the decision process takes 3-12 months. If you do not follow the patient up during that time, they go to a competitor. A CRM lets you avoid losing the patient while they are thinking it over. - How are Instagram leads managed? | Instagram direct messages land in the same shared inbox as WhatsApp; the conversation is assigned and handed over there, and the sender is linked to an existing record by their Instagram username. Opening a new lead with Instagram as the source for a sender with no record is a setting switched on during setup. Not today: in no deployment does AI reply to customers on Instagram on its own. You can also point the link in the profile to the web form or to WhatsApp — a message arriving at your WhatsApp Business account connected during setup appears in the team inbox and is written into the patient record. - How is consent for before/after photos obtained? | The permission form is sent to the patient as a step tied to the post-operative check-up date. The consent the patient gives sits in a consent record attached to the patient record; the date the form was sent, the scope of the consent and whether it has been withdrawn are fields on that record. Only images of patients whose consent stands are used in the gallery; a patient whose consent has not arrived or has been withdrawn does not appear on the consented list. - Can more than one person use the same WhatsApp number for aesthetic clinics? | Yes. We connect your own Meta WhatsApp Business account to the CRM during setup; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Agency CRM: Agent Hours and Retainers | Rapitek CRM](https://rapitek.com/en/agency-crm) Retainer, project and performance contracts are a field on the customer card; agent hours attach to a customer and a project, and the month-end report comes out of those records. ##### What we set up, and how - Keep the contract type, the monthly budget, the contacts and the payment terms for every brand on a single card - Run the customer, project and task queue in a Kanban or Gantt view - Enter agent hours per customer and per project and see the remaining hours on a retainer at any moment - Submit design, video and content files for approval through the limited-permission account you open for the customer, and attach revision requests to the record - At the end of the month gather the work done, the hours spent and the campaign results into a single PDF report - Customer and Brand Record | Every agency customer is an account record; the contract type (retainer, project, performance), the monthly budget and the payment terms sit in its fields, and contacts are attached to that record. - Project and Task | A project is a record attached to the customer and a task is a record attached to the project; the assigned agent and the time estimate are in the task fields, and the queue is read in the Kanban or the calendar view. - Agent Hour Entry | An hour spent is a record carrying a customer and a project field; on a retainer it is deducted from the contract hours, and the remaining hours appear in that customer's report. - File and Revision | Design, video and content files are attached to the project; a revision request is written onto the project and which round it is is counted from the record. - Monthly Activity Report | The report is produced from the task and hour records within the month; campaign result figures (CTR, followers, KPI) do not arrive from the ad accounts by themselves, they are entered into the record by hand or by import. ##### Frequently asked questions - Is there a difference between an advertising agency, a digital agency and a PR agency? | The sector name differs but the flow is similar: customer portfolio, project management, hour tracking, invoicing. Rapitek CRM suits all three. On the PR side the media list, and on the digital side campaign and KPI tracking, are defined during setup with your own fields. A module that pulls the figures from social media and ad platforms by itself does not come out of the box; the figures are entered into the record by hand or by import. - How are retainer and project invoicing managed separately? | Every customer is tagged with a contract type: on a retainer the invoice is issued on a fixed monthly amount and the remaining hours are reported. On a project it is invoiced by milestone, on performance according to the result. Mixed contracts can also be defined in the same structure. - Can we offer a portal to customers? | We open a user account with limited permissions for the customer in the CRM: which projects, files and reports they will see is determined by the profile. File approval and revision requests run through that account on the same record, and the monthly report can also be sent as a PDF. We do not have a separate branded portal product — what they see is the CRM itself, as much of it as their permissions allow. - Is hour tracking done automatically? | Hours are entered in two ways: the agent enters them by hand during the day, or they are kept with a timer attached to the start of a task. If you use tools such as Toggl or Clockify, we build the connection ourselves; there is no out-of-the-box module. You can bring in the report you export from those tools by import; if a live connection is needed, our professional services team builds it specifically for the project over the REST API, OAuth2 and webhooks, and the scope and the cost are shared in writing in the discovery call. When no connection is built, hours continue to be entered by hand or by file transfer. ### [Agriculture CRM: Grower Network and Periods | Rapitek CRM](https://rapitek.com/en/agriculture-crm) Contract growers and buyers are both account records; the crop, quantity and delivery period committed sit in attached rows, and purchase and sale meet in one period report. ##### What we set up, and how - Keep contract growers in an account record and write the crop planted, the quantity committed and the advance given into fields - Manage the wholesale market, retail, industrial and export channels in separate accounts and apply each channel's own price list from its record - Compare purchase and sale commitments in the same list by delivery period and see the shortfall before the period starts - Attach the production unit to the record, report which channel the produce from which region went to, and separate permissions by that field as well - Grower Network | A contract grower is an account record; the crop planted, the committed quantity and the advance given sit in its fields, and deliveries accumulate under the card. - Channel Account | The wholesale market broker, the retail chain, the industrial buyer and the exporter are separate account records; each channel's price list is attached to its own account. - Period Commitment | The delivery period is a date field on the record; purchase and sale commitments are listed with the same period filter and compared in a single report. - Production Unit | The facility, the region or the farm is a field on the record; which channel the produce from which unit went to is read from the report on that field. ##### Frequently asked questions - Can I see the quantity coming from a contract grower and the promise given to a buyer in the same place? | Yes. Both the grower and the buyer are account records, and the commitment is a record attached to those accounts; because the delivery period is a date field, purchase and sale commitments listed with the same period filter are compared in a single report. - How do I separate permissions in a business with more than one production unit and more than one sales channel? | The production unit is a field on the record and user permissions are set up around that field; the regional manager sees the records of their own unit, head office sees them all in a single list. Because channel price lists are also attached to accounts, every team works with the price of its own channel. - Can I see the advance given to a grower and the quantity they delivered on the same card? | Yes. A contract grower is an account record; the crop planted, the committed quantity and the advance given are its fields. Deliveries accumulate row by row under that card, and the remaining commitment is read from the same place. - Which is the best CRM software for agriculture? | When choosing a CRM for the agriculture sector you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your agricultural process, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an agriculture CRM system cost? | In agriculture, because the production unit is attached to the record and permissions are separated by that field, users are defined unit by unit. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the agriculture sector? | 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the agriculture sector? | We start with a discovery call: we work out together your agricultural process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for agriculture? | Yes. The field and branch team can update the customer card, the note and the follow-up task from a phone. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [AgriTech CRM: Plot Records and Pilot Tracking | Rapitek CRM](https://rapitek.com/en/agritech-crm) The device installed on the pilot plot, the field visit and the subscription end date sit on the same farmer record; the time left to expiry drops a renewal task onto the list. ##### What we set up, and how - Keep farmer, cooperative and dealer records separate and see each plot's hardware, subscription start and end date on its card - Track the pilot installation as a separate stage; write the trial result and the measurement note onto the record the quote is attached to - Turn installation and maintenance visits into field tasks and close them from the mobile app with location verification - Plan renewal and preliminary contact tasks ahead according to the season calendar and get in touch before the planting window closes - Farmer and Plot Record | A farm is an account record; the plot, the area and the crop pattern sit in its fields, and the installed device is attached to that record. - Pilot and Trial Tracking | A pilot is an opportunity stage; the installation date, the measurement note and the trial result accumulate on the same opportunity. - Field Installation Visit | An installation is a task; the technician and the date are in its fields, it is closed from the mobile app and location verification is written into the record. - Subscription Renewal | A subscription is a record with a start and an end date; a task tied to the time left to expiry drops the renewal contact onto the list. ##### Frequently asked questions - Can I track separately the farmers who moved from a pilot installation to a contract? | Yes. The pilot is a separate opportunity stage; how many trial installations turned into contracts, and under which crop pattern they did, is read from a report with a date range. - How do I separate the enquiries coming through dealers and agricultural engineers? | The channel the enquiry came from is a field on the lead record; the dealer and the engineer each sit as an account record, every incoming enquiry drops into the queue with its channel information, and the assignment rule defined during setup routes it to the relevant rep. - Will the system remind me of farmers whose subscription end date is approaching? | A subscription is a record with a start and an end date; depending on the time left to expiry, a renewal task drops onto your list, so the conversation happens before the planting window closes. - Which is the best CRM software for AgriTech? | When choosing a CRM for the AgriTech sector you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your process in the AgriTech sector, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an AgriTech CRM system cost? | On the AgriTech side a field installation is a task carrying a technician and a date field; it is this field team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the AgriTech sector? | 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the AgriTech sector? | We start with a discovery call: we work out together your process in the AgriTech sector, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for AgriTech? | In AgriTech a field installation is a task; it is closed from the mobile app and location verification is written into the record. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [AI Services CRM: Proof of Concept Tracking | Rapitek CRM](https://rapitek.com/en/ai-services-crm) Data access permission, the non-disclosure agreement and the pilot's success threshold are fields on the opportunity record; until approval is complete the opportunity does not move on. ##### What we set up, and how - Run the proof of concept with its own stages; keep data access permission and the status of the non-disclosure agreement in fields on the opportunity record - Tie the pilot's success threshold to a written field so that when the result arrives both sides look at the same criterion - Keep the legal, information security and business unit stakeholders in separate contact records and see from the list which approval is waiting with whom - Manage the long evaluation period with a contact sequence; keep usage volume in an account field and tie the renewal conversation to it - Proof of Concept Opportunity | The pilot is an opportunity record with its own stages; the start date, the scope and the success threshold are in its fields, and the result stays on the same card. - Data Access and Confidentiality | The non-disclosure agreement and data access permission are each a field; the signature date and the scope sit in the record, and a missing approval does not let the opportunity move to the next stage. - Stakeholders and the Approval Queue | Legal, information security and the business unit are separate contact records under the account; a pending approval is a task and its owner is written in its field. - Usage and Renewal | Usage volume is a field on the account; as the contract end approaches, the renewal task drops onto the list and the expansion opportunity is opened from the same account. ##### Frequently asked questions - How do we track the customer's data access permission and the status of the non-disclosure agreement during the proof of concept stage? | The non-disclosure agreement and data access permission are fields on the opportunity record; the signature date and the scope sit there. A stage rule is defined so that the opportunity does not move to the next stage before approval is complete; a pending approval appears on the list as a task with a definite owner. - Whether the pilot counts as successful becomes a subject of argument afterwards; how do you prevent that? | The success threshold is a written field on the pilot opportunity and it is filled in before the pilot starts. When the result arrives it is written onto the same record; if the criterion is changed afterwards, that leaves a trace as an update. So in the evaluation meeting both sides look at the same line. - Can we see in advance the accounts whose contract renewal is approaching? | Yes. Usage volume and the contract end date are fields on the account; accounts whose end is approaching drop onto the list, and the renewal task and the expansion opportunity are opened from the same account. - Which is the best CRM software for artificial intelligence? | When choosing a CRM for the artificial intelligence sector you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your process, we migrate your data, and we give your team training in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does an artificial intelligence CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the artificial intelligence sector? | In artificial intelligence projects the counterpart the CRM will talk to is the billing or the infrastructure 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the transition to a CRM system work in the artificial intelligence sector? | We start with a discovery call: we work out together your sales process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for artificial intelligence? | Yes. The field and branch team can update the customer card, the note and the follow-up task from a phone. The app is published on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Aquaculture CRM: Harvest Batches and Commitments | Rapitek](https://rapitek.com/en/aquaculture-crm) The size range, quantity and delivery week promised to a buyer are a record linked to the account; the harvest batch stands separately, and the two are read side by side by delivery week. ##### What we set up, and how - Write the size range, quantity and delivery week agreed with the buyer onto the account record and track approaching commitments from the list - Link the harvest batch to a record with production unit, size class and harvest date fields, and see which batch is set aside for whom - Collect dispatch documents as attachments on the record and keep their validity dates as fields, listing missing paperwork before loading - Plan cold chain delivery as a task, record the vehicle and delivery time, and inform the buyer by SMS or WhatsApp - Harvest Batch | A batch is a record; the production unit, the size class and the harvest date are its fields, and the quantities set aside accumulate under that record. - Buyer Commitment | The agreed size, quantity and delivery week are a record linked to the buyer's account; commitments whose week is approaching are filtered from the date field. - Document Set | The documents accompanying a dispatch sit as attachments on the record; the validity date is a field, and a dispatch with a missing document stays flagged on the list. - Cold Chain Delivery | A delivery is a task; the vehicle, the delivery time and the temperature note are its fields, and a closed task leaves a trace on the buyer's record. ##### Frequently asked questions - How do I compare the size and quantity promised to a buyer against the harvest plan? | A commitment is a record linked to the buyer's account; the size range, quantity and delivery week are its fields. Because the harvest batch is also a separate record, the total of commitments filtered by delivery week and the batch that will be ready that week are read side by side in the same report. - Can I see a missing dispatch document before the day of loading? | Yes. Documents are collected as attachments on the dispatch record and the validity date is kept as a field; dispatches with a missing or expired document are flagged on the list. There is no out-of-the-box module for connecting to public systems; document records and date tracking run inside the CRM. - Can we track cold chain delivery through the record? | A delivery is a task; the vehicle, the delivery time and the temperature note are its fields. When the task is closed it leaves a trace on the buyer's record, so which batch was delivered with which vehicle and at what time is read afterwards from the same place. - Which is the best CRM software for aquaculture? | When choosing a CRM for the aquaculture sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your aquaculture process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a aquaculture CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the aquaculture sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the aquaculture sector? | We start with a discovery call: together we work out your aquaculture process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for aquaculture? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phones. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Architecture Office CRM: Permits and Revisions | Rapitek CRM](https://rapitek.com/en/architecture-office-crm) Preliminary, final, construction, permit and supervision are stages of one project record; the architect in charge and the delivery date sit in fields, and every revision keeps its own date. ##### What we set up, and how - Run the preliminary design, final design, construction, permit and site supervision stages with the architect in charge and the delivery date; tie the opening of the next stage to a rule during setup - Track the permit application, missing files and the municipality's responses, and store the version of every revision - Keep structural, mechanical, electrical and landscape contractors in a pool with their past projects and quality scores - Track stage-based progress payment deductions, the client payment plan and subcontractor payments from a single place - Record the approval at stages that need client approval; let who approved what and when leave a trace, and report approval times and the number of revision rounds - Project Stage Management | Preliminary design, final design, construction drawings, permit and site supervision are stages of the same project record; the architect in charge and the delivery date sit in fields, and the opening of the next stage is defined during setup. - Permit and Municipality Tracking | The permit process is a record attached to the project; the application date, missing files and the municipality's response are kept in its fields, and every revision is stored with its own date. - Subcontractor Pool | A contractor is an account record; the discipline and past projects accumulate under the card, and the suitable ones for a new project are filtered by those fields. - Progress Payments and Payment Processes | Progress payment lines are attached to the project's stages; client and subcontractor payments are compared on the same project. - Room Schedule and Material Selection | The material to be used in each room is a list attached to the project record; the product chosen, its alternative and the client's selection date sit in fields, and rooms awaiting a selection stay open on the list without falling into the construction stage. - Contract and Design Approval Tracking | Every stage requiring approval is marked on the record; who approved what and when stays as a trace, and approval time and revision rounds are reported from those traces. ##### Frequently asked questions - How are AutoCAD or Revit files managed in the CRM? | The file itself is uploaded as an attachment to the record, or the link to it on your cloud drive is added to the record; the CRM does not open drawing software. Which version is current, who changed it and when, and which revision round it belongs to sit in the fields of the project record. - What about several architects working on the same project? | More than one architect can be assigned to each stage; the owner field and the hour record are kept separately per person. The hour-cost report is taken from the total of those fields. - How do you model permit processes? | The permit type (new build, alteration, amendment) is a field on the record and each type uses its own stage flow. Municipality feedback, revision requests and missing files are kept in the fields of the same record; which file is waiting with whom is read from the list. - How is the progress payment process managed? | The stage-based payment plan in the contract is defined in the CRM. When a stage is completed, the progress payment item is opened on the record and the invoice record is created from that item; the client notification and the late payment reminder are defined attached to the same record. Official e-document generation is not done in the CRM. ### [Art Studio CRM: Capacity and Lesson Balance | Rapitek CRM](https://rapitek.com/en/art-studio-crm) A studio programme is a record and the capacity is its field; once full, an incoming application is attached to the same record with a waiting list status and reached when a place opens. ##### What we set up, and how - Take online enrolments for different studio programmes and manage the capacity and the waiting list - Keep the participant's level, preferences and past attendance in a single profile - Plan the weekly, monthly and term programme by instructor and by room - Track the payments for one-off workshops and term course packages separately - Send new workshop announcements and lesson reminders over WhatsApp - Workshop Enrolment Management | A studio programme is a record; the capacity is in a field, and once it is full an incoming application is attached to the same record with a waiting list status. - Participant Profiles | A participant is a contact record; the level and preferences sit in its fields, and past attendance accumulates under the card. - Programme Planning | A lesson is a record with instructor, room and time fields; the weekly and term programme is the calendar view of those records. - Payment and Package Management | A one-off workshop and a term package are separate item types; payments are kept row by row under the participant's card. - Studio Material Consumption | Each programme's material list consists of the item lines of the studio record; the consumption quantity that comes out of the capacity is deducted from stock, and the material cost per workshop is read from the total of those lines. ##### Frequently asked questions - Can I create separate programmes for different age groups? | Yes, you can create separate studio programmes for children, youth and adult groups, and price them by age. - Can I sell workshops online? | Yes. You can take online enrolment and payment from your website. The capacity is a field on the studio programme; when it is full, an incoming application is attached to the same record with a waiting list status, and when a place opens you reach the next person from that list. - Is there material and stock tracking? | Yes, you can track the stock of studio materials and produce a material cost analysis per workshop. - How long does setup take for an art studio? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your art studio process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Athletic Club CRM: Dues and Court Booking | Rapitek CRM](https://rapitek.com/en/athletic-club-crm) A membership is a record: start, end and package type are its fields. A booking carries a facility and a time field, and a setup rule blocks a second booking at the same hour. ##### What we set up, and how - Run the collection, renewal reminder and suspension of monthly, annual and package memberships from a single screen - Let members book courts, the pool, the fitness studio and the sauna from the mobile app, with clashes blocked by the rule set up during setup - Attach each group lesson's participant list, coach assignment and capacity to the record; tie the notification to the member on a change to a rule - Run registration, payment and team formation for tournaments, competitions and social events from a single place - Track members' attendance frequency and lesson preferences with a monthly report and see the risk of leaving early - Membership and Dues Management | A membership is a record; the start, the end and the package type sit in its fields, and the renewal reminder is set up with a task tied to the end date. - Facility and Court Booking | A booking is a record with a facility and a time field; the rule that blocks a second booking being opened at the same hour is defined during setup. - Group Lesson and Coach Schedule | A lesson is a record; the coach and the participants are attached to it. The coach sees their own calendar, and a change made leaves a trace on the member's card. - Event and Tournament Management | The event record keeps attendance, payment and team information together; the application coming from the registration form dropping directly under that record is defined during setup. - Member Attendance Report | Because attendance and lesson preference accumulate on the member card, the question "who has thinned out" is answered with a date-range report; your own measure sets the risk threshold. ##### Frequently asked questions - What can I do with a CRM for an athletic club? | Membership collection, facility booking, group lesson management, coach assignments, event registration and member attendance analytics — on a single platform. When you connect your own Meta WhatsApp Business account, you tie to a rule during setup on which event and how many hours ahead the reminders to members go out. - How does tennis court and swimming pool booking work? | Members book particular time slots from the mobile app. A booking is a record carrying a facility and a time field; the rule that blocks a second booking being opened at the same hour is defined during setup. How many hours before the booking the reminder goes out is also something you set in the same setup. - Can coaches manage their own schedules? | Yes. There is a dedicated profile and calendar for each coach. Availability is marked and upcoming lessons appear as a list. Coaches can see their own performance reports. - What kinds of features are there for club events? | For tournaments, races and social events, the registration form, payment collection, team formation and result sharing flows are defined during setup. After the event, the results and photos are sent from the same record. ### [Auto Body and Paint CRM: Parts and Assessor Approval](https://rapitek.com/en/auto-body-shop-crm) A job card is a record; the damage assessment, the work to be done, the delivery date and the cost sit on the same card. Before and after photos land on that record with their dates. ##### What we set up, and how - Gather the damage assessment, the paint and body work to be done, the delivery date and the cost on a single job card - Track comprehensive and third-party insurance files, assessor reports and approval steps file by file - List the parts required and attach the supplier order and its delivery status to the job card - Document the damage and the repair carried out with before and after photos - Let the whole team reply to the customer from a single WhatsApp number - Job Card Management | A job card is a record; the damage assessment, the work to be done, the delivery date and the cost fields sit on the same card. - Insurance File Tracking | The insurance file is attached to the job card; the assessor's report is an attachment, the approval step advances as a stage, and pending files gather in a list. - Parts Order Management | Parts lines sit under the job card; because the supplier order and the delivery status are held on those lines, a missing part is visible on the vehicle card. - Photographed Damage Record | Before and after photos are attachments to the job card; because they carry dates, the basis for any dispute comes out of the same record. - Additional Work Approval Record | Additional work found during strip-down is an approval record attached to the job card; the item, the extra charge and the time the customer approved sit in fields, and until the approval arrives that item is not added to the labour list. ##### Frequently asked questions - How do we get the customer to approve additional work found during strip-down? | Additional work is an approval record attached to the job card; the item, the extra charge and the time the customer approved sit in fields. Until the approval arrives that item is not added to the labour list, so no argument comes up at delivery. - Can I see whether the delay came from the part or from the assessor's approval? | The insurance file and the parts lines sit under the same job card; the approval step advances as a stage, and the delivery status of the supplier order sits on the line. How many days each step waited is read from the record dates. - How long does setup take for Auto Body and Paint? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your workshop process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for Auto Body and Paint? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for Auto Body and Paint? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Auto Repair CRM: Work Orders and Reminders | Rapitek CRM](https://rapitek.com/en/auto-repair-crm) A vehicle is a record opened by its number plate; service history, mileage and parts lines accumulate on the same card. Vehicles whose interval is due drop onto a list from those fields. ##### What we set up, and how - Open the vehicle from its number plate; keep past work, the last mileage and service notes on the same card - Turn an appointment that comes in online into a work order and see from a single screen which mechanic it is assigned to - Track the spare parts issue, the order and the cost attached to the work order before the job closes - Drop the vehicles whose interval is due for an oil change, an inspection or a periodic service onto a list; tie the SMS reminder going out to that list to a rule - Run the correspondence with vehicle owners as a team from a single WhatsApp number and get off personal phones - Vehicle and Customer Cards | A vehicle is a record opened by its number plate and attached to the customer; service history, mileage and notes accumulate under the card. - Appointment and Work Order | The appointment is turned into a work order on the same record; the mechanic assignment is in a field, and the day's jobs appear in the calendar and the list. - Spare Parts Management | Parts lines sit under the work order; stock issue and cost are calculated from those lines, and a missing part is visible before the job closes. - Service Reminders | The last service date and the mileage are fields on the vehicle record; the ones whose interval is due drop onto a list, and the reminder is tied to that condition. - Courtesy Car Assignment Record | The courtesy car given for the duration of the service is an assignment record attached to the work order; the mileage at handover, the fuel and the expected return date sit in fields, and the ones not returned stay on the open assignment list. ##### Frequently asked questions - Can I see separately the jobs held up waiting for a part? | Parts lines sit under the work order; stock issue and cost are calculated from those lines. Jobs held up waiting for a part appear as a separate list, and the missing part stays on the card until the job closes. - How do we track the courtesy car given for the duration of the service? | The courtesy car is an assignment record attached to the work order; the mileage at handover, the fuel and the expected return date sit in fields. The ones not returned stay on the open assignment list. - How does the periodic service reminder come out? | The last service date and the mileage are fields on the vehicle record; vehicles whose interval is due are filtered by those fields and drop onto a list. You tie the reminder going out to that list as an SMS or a WhatsApp message to a rule during setup; the send leaves a trace on the vehicle record. - How long does setup take for an auto repair shop? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your service process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Will it integrate with my existing systems for an auto repair shop? | In an auto repair shop the parts lines sit under the work order; stock issue and cost are calculated from those lines. 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 access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for an auto repair shop? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Automotive CRM: Dealer Network and Vehicles | Rapitek CRM](https://rapitek.com/en/automotive-crm) The sale, the handover, the servicing and the complaint for the same vehicle are written onto one vehicle record; because the service interval is calculated from it, no reminder list is made by hand. ##### What we set up, and how - Compare the sales and service performance of your dealer network by dealership and against regional targets - Take service appointments online; drop the vehicles whose service interval is due onto a list and tie the reminder going out to that list to a rule - Open the entire history of every vehicle, from the moment of sale to the last service record, on a single screen - Run the points system and campaigns by customer segment - Gather the WhatsApp messages arriving at a single business number in the team inbox and assign conversations by the rule you define - Dealer Network | Every dealership is a separate user group; the regional target and the sales achieved sit in that group's fields, and a dealership can be given permissions so that it sees only its own customer records. - Service Appointment | An appointment is an activity attached to the vehicle record; the date, the service type and the owner sit in fields, and past appointments are listed under the same vehicle. - Vehicle Life Cycle | The vehicle is its own record; the chassis number, the sale date, the service interval and the service history are fields on that record, and which dealership it came from is read from the same record. - Loyalty Points | Points are a field on the customer record; the campaign target audience is drawn out by filtering on that field and the segment field. - Test Drive Record | A test drive request is an appointment record attached to the model of interest; the vehicle, the time and the advisor sit in fields, and the evaluation survey sent after the drive is attached to the same record. ##### Frequently asked questions - How can I manage my dealer network? | You can define each of your dealerships as a separate user group, set regional targets and compare performance. Dealerships can be given permissions so that they see only their own customer records. - Are service reminders automatic? | The service interval and the last service date are fields on the vehicle record; vehicles whose interval is due are filtered by those fields and drop onto a list. You tie the reminder going out to that list as an SMS, an email or a WhatsApp message to a rule during setup; which channel is used is read from the customer's preference field, and the send leaves a trace on the vehicle record. - Will it integrate with my existing DMS? | We build the connection to DMS and ERP software ourselves; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; the scope and the cost are shared in writing in the discovery call. As long as no connection is built, vehicle, customer and service data are entered with an import file or by hand; the chassis number, the service interval and the service history are still kept on the vehicle record and the service reminders are produced from there. - Can more than one person use the same WhatsApp number for automotive? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Automotive Dealer CRM: Showroom and Test Drives | Rapitek](https://rapitek.com/en/automotive-dealer-crm) The showroom visit, the test drive, the trade-in valuation and the service date sit in the fields of the same customer record; when service is due, the appointment is planned from it. ##### What we set up, and how - Record the visitor who comes into the showroom together with the model they are interested in, their budget and their purchase timing - Attach the follow-up after the test drive, the presentation of financing options and the closing step to their owner - Keep the annual service, tyre change and inspection date in a field on the vehicle record; let the vehicles whose date is approaching drop onto a list and take the reminder from that list - Open the trade-in request together with the vehicle valuation and track the used vehicle on the resale line - Set up a WhatsApp inbox on a single business number that the whole team answers, and assign conversations by the rule you define - Showroom Visitor | A person who comes into the showroom is a prospect record; the model they are interested in, their budget and their purchase timing sit in the fields of that record, and on their second visit the same record is opened. - Test Drive | A test drive is an activity attached to the prospect; its date and its vehicle sit in fields, and the follow-up after the drive drops onto its owner's list as a task. - Service Reminder | The warranty start and the service interval of the vehicle sold are fields on the sale record; as the date approaches, the service appointment task is produced from those fields. - Trade-In Vehicle | A trade-in request is an item attached to the customer's record; the make, model, mileage and valuation amount sit in fields, and vehicles that have not sold are filtered and listed from those same fields. - Vehicle Handover Preparation List | Registration, number plates, accessory fitting and the handover appointment are checklist items attached to the sale record; each item is a task with its owner, and the handover date is not confirmed until they have all closed. ##### Frequently asked questions - Why is a CRM necessary for automotive dealerships? | Vehicle sales have a long sales cycle. With a CRM the showroom visitor is followed up, the follow-up after the test drive is done, and the after-sales service relationship is maintained. - How is after-sales service managed? | When the vehicle is sold, the warranty start and the service intervals are written into the fields of the sale record. As the date approaches, the vehicle drops onto a list, the reminder comes out of that list, and the service appointment is planned from the same record. - How is used vehicle tracking done? | The customer making a trade-in request is recorded and the vehicle is valued. For vehicles that have not sold, a campaign and matching with prospective buyers are done. - Can more than one person use the same WhatsApp number for an automotive dealership? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Aviation CRM: Parts and Maintenance Slots | Rapitek CRM](https://rapitek.com/en/aviation-crm) Part number, serial number, certificate details and the requested delivery date are fields on the request itself. Urgency is a field too; the request keeping an aircraft on the ground stands out. ##### What we set up, and how - Collect part and maintenance requests in a single record with part number, serial number and certificate details - Route urgent requests straight to the person responsible through the queue and the assignment rules defined during setup, and measure the time to first response - Keep the price quoted and the delivery date promised on the record, and let late deliveries drop into a list - Plan maintenance slots on the account record and see upcoming visits and contract renewals in advance - Part Request | Every request is a record; part number, serial number, certificate details and the requested delivery date sit in the fields of that record. - Urgency and Queue | Urgency is a field; requests that keep an aircraft on the ground reach the person responsible through the queue and the assignment rules defined during setup, and the waiting time is measured on the record. - Quote Record | A quote is a record with price and delivery time fields; what was promised to which customer is read from the line items. - Maintenance Slot | The slot is a date field; the customer's next maintenance visit sits on the account record, and upcoming dates drop into a list. ##### Frequently asked questions - How do I separate urgent requests that keep an aircraft on the ground from routine work? | Urgency is a field on the request record; the queue and the assignment rules defined during setup look at that field and drop the request straight to the person responsible. The time to first response is measured on the record, and late requests stand out in the list. - Can part serial numbers and certificate details be kept in the CRM? | Yes; part number, serial number and certificate details are fields on the request and the quote record, and the document file is attached to the same record. That way, which part was quoted with which document can be read from the record afterwards. - Where do I see what delivery time we promised to which customer? | A quote is a record with price and delivery time fields; what was promised to which customer is read from the line items, and deliveries past the promised date drop into a list. - Which is the best CRM software for aviation? | When choosing a CRM for the aviation sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your aviation process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does an aviation CRM system cost? | On the aviation side, an incoming request enters the queue and reaches the person responsible through an assignment rule; it is this request team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the aviation sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the aviation sector? | We start with a discovery meeting: we work out your aviation process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for aviation? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [B2B SaaS CRM: Trial Conversion and Churn Risk | Rapitek CRM](https://rapitek.com/en/b2b-saas-crm) A trial account is a record; its start, end date and activation metrics sit in its fields. In Rapitek CRM a task opens for the account owner when the quota and usage threshold is passed. ##### What we set up, and how - Track activation metrics on your own product's trial accounts and start contact with low-usage accounts - Tie the drop in usage and the rise in support tickets to a threshold you set yourself, and pull the risk list daily - Define your own threshold for quota usage and trigger the upgrade suggestion for accounts that cross it, and open cross-sell based on feature usage - Combine NPS, usage intensity and support history in a single customer health score - Answer as a team from a single WhatsApp number, assign conversations by the rule you define, and track response times - Trial→Paid Conversion Tracking | Trial accounts of your own product are records in the CRM; the start of the trial, its end date and its activation metrics are fields on that record. Your own product decides the length of the trial; accounts whose usage stays low before the period runs out are listed by these fields and a contact task is opened. - Churn Risk Estimation | A drop in usage and a rise in support tickets are fields on the account record; you set the threshold, and when it is passed the account drops into the risk list and a task opens for its owner. Your team decides which action to take. - Expansion Revenue Automation | Quota and feature usage rates are fields on the account record; these fields are fed from your product over the REST API or webhooks, and you set the threshold that triggers the upgrade suggestion. - Customer Health Score | NPS, usage and support satisfaction are brought together in a single combined score; you define the components of the score and its thresholds, and accounts that fall below the threshold move to the top of the list. - Onboarding Step List | The setup steps for a new customer are tasks tied to the subscription record; which step is waiting with whom and the completion date sit in fields, and before the renewal meeting the status of these steps is seen from the same record. ##### Frequently asked questions - Why is CRM critical for SaaS companies? | In SaaS, customer acquisition cost (CAC) is high and lifetime value (LTV) is critical. With a CRM, trial conversion, customer retention and expansion revenue are optimised. - How is churn risk estimated? | We carry the product usage data into the CRM; there is no out-of-the-box module. Login frequency, feature usage and the number of support tickets are fields on the account record; for these fields to be fed from your own product, the connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; the scope and the cost are shared in writing in the discovery meeting. You define the threshold for risk: when the threshold is passed, the account drops into the risk list and a task is opened for its owner, and the last contact and the open support tickets appear on the same card. Your team decides which action to take; the CRM produces the record, not the decision. As long as the connection is not built, these fields are updated with an import file or by hand. - How are upsell opportunities identified? | Quota usage, feature usage and account size are kept in fields on the account record; these fields are fed from your own product over the REST API or webhooks. You define the threshold; when it is passed, the upgrade campaign is triggered. - Can several people use the same WhatsApp number for B2B SaaS? | Yes. We connect your own Meta WhatsApp Business account to the CRM; the shared inbox is a capability of the product itself. Connecting the account is done during setup, and after that your team answers from a single business number. Incoming messages drop into the team inbox and are recorded on the customer card; conversations are assigned to a representative by the rule you define, and managers see the conversations and the response times. The Meta invoice is issued directly to you — we do not sell message bundles or credits. The history recorded on the card stays in the CRM even if staff change. ### [Bakery and Patisserie CRM: Custom Orders | Rapitek CRM](https://rapitek.com/en/bakery-crm) An order is a record with delivery date and time fields, and the day's work gathers in a calendar. The hotel's agreed price sits in a field on the account and reaches the order from there. ##### What we set up, and how - Track cake and custom design orders on a visual calendar by delivery date - Record the price agreements of your hotel, restaurant and shop customers per customer - Plan daily delivery routes and make driver assignments from a single screen - Plan holiday, New Year and special-day campaigns in advance and follow their results - Keep order messages off personal phones; let the whole team answer on WhatsApp from a single business number - Custom Order Tracking | An order is a record with delivery date and time fields; the day's work gathers in a calendar view, and the design note and the photo are attached to the same card. - Wholesale Customer Management | Hotels and restaurants are each an account record; the agreed price sits in a field on the account and reaches the order from there. - Delivery Planning | A delivery is a task; the driver and the address are in its fields, and the day's route is read from the list of these tasks. - Seasonal Campaigns | A campaign is a record; which customer it went to and when, and the order that came back, are tied to the same record, and the result is compared in a report. - Stale Return Line | Unsold bread coming back from the shop is a return line tied to that day's delivery record; the quantity and the reason sit in fields, which customer produces regular returns is filtered from these lines, and the next day's order quantity is corrected accordingly. ##### Frequently asked questions - Can we see how much work falls on which day while we are taking the order? | An order is a record with delivery date and time fields; the day's work gathers in a calendar view, and while a new order is being taken that day's load appears on the same screen. - Can we see which customer regularly returns stale bread from the shop? | Unsold bread coming back is a return line tied to that day's delivery record; the quantity and the reason sit in fields, and customers with regular returns are filtered from these lines. - How long does setup take for a bakery and patisserie? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your bakery process needs becomes clear in that meeting. We migrate your data; the scope of the migration and any fee for it are worked out in the same meeting and shared in writing. - Will it integrate with my existing systems for a bakery and patisserie? | In a bakery and patisserie, unsold bread coming back from the shop is a return line tied to that day's delivery record. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the other side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - Can several people use the same WhatsApp number for a bakery and patisserie? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned by the rule you define. Managers can follow the conversations and the response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Banking CRM: Loan Files and Missing Documents | Rapitek CRM](https://rapitek.com/en/banking-crm) An application is a record with stage and missing-document fields, and which document is awaited from whom sits on the card. In Rapitek CRM an objection enters the queue as its own case record. ##### What we set up, and how - Follow loan and product applications through their stages, write the missing document into a field on the record, and send the reminder from there - Plan visits to corporate customers in the portfolio as tasks, and enter the visit note from the field with the mobile application - Open customer objections and complaints as case records, put them in the queue and drop them to their owner through the assignment rule you defined during setup - Segment consented communication lists and run SMS and WhatsApp notifications from a shared inbox - Application File | An application is a record with stage and missing-document fields; which document is awaited from whom sits on the card. - Portfolio Visit | A visit is a task; the account and the date are in its fields, the visit note is written on the same record, and the location is confirmed in the mobile application. There is no built-in portfolio manager field; the manager is held in the task's owner field. - Objection and Case | A customer objection is a case record; it enters the queue, reaches its owner through the assignment rule defined during setup, and at closing the survey is tied to the same record. - Communication Consent | Consent status is a field on the customer card; the campaign list is filtered by that field, and a record without consent does not enter the list. ##### Frequently asked questions - How does tracking missing documents on a loan application work in the CRM? | On the application record, a missing document is a field; it is ticked off as each document arrives, a dated follow-up task is opened for those that do not, and the reminder to the customer is sent from the same record over SMS or WhatsApp. - Can a connection be built to our core banking system? | We build the connection to your core banking system; there is no out-of-the-box module. The connection is built specifically for the project over the REST API covering 183 business objects, OAuth2 and webhooks; we work out its scope in the discovery meeting and share it in writing. - Can I stop a campaign message going to a customer without consent? | Consent status is a field on the customer card; the campaign list is filtered by that field, and a record without consent does not enter the list. If you connect your own İYS account through Verimor, Rapitek CRM sends SMS, call and e-mail consent and opt-out records to İYS every 30 minutes; opt-outs and consents that recipients make directly in İYS are checked every 6 hours and can take up to a day to reach the CRM. - Which is the best CRM software for banking? | When choosing a CRM for the banking sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your process in the banking sector, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a banking CRM system cost? | On the banking side, a visit task carries the account and date fields, while the portfolio manager is held in the task's owner field; it is this team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the banking sector? | In banking, the counterpart the CRM will talk to is the core banking system. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the other side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the banking sector? | We start with a discovery meeting: we work out your process in the banking sector together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for banking? | In banking a portfolio visit is a task; the visit note is entered onto the record from the field with the mobile application. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Beauty Centre CRM: Session Balance and Bookings | Rapitek](https://rapitek.com/en/beauty-center-crm) The package sold is a membership record; total sessions, remaining sessions and the expiry date are its fields. Every appointment deducts one session, and the session photo sits on the same card. ##### What we set up, and how - Define skincare, laser, filler and mesotherapy packages separately and see the remaining session balance on the client card - Add the photo of each session to the card with the client's explicit consent and compare it with 1, 6 and 12 months later - Tie bookings coming in from the web and the Instagram bio to the therapist calendar and the room assignment - Run the loyalty score and the list of clients with upcoming birthdays from fields on the client record - Track consumables such as hydrafacial solution and filler material together with an expiry date warning - Package and Session Balance | The package sold is a membership record tied to the client record; total sessions, remaining sessions and the expiry date are its fields, and every appointment deducts one session from that record. - Before/After Photo Archive | The photo uploaded during a session is an attachment on the client card; the explicit consent taken before the upload is kept in a field on the same record, and the 1, 6 and 12 month comparison is made from the date order of these attachments. - Appointment and Therapist Calendar | An appointment is a record; the therapist, the room and the service duration are its fields, and appointments clashing on the same therapist appear in the calendar. - Loyalty and Birthday | The loyalty score and the date of birth are fields on the client record; clients whose birthday is approaching come out of the list on that date field, and the campaign task is opened from there. - Consumable and Cosmetic Stock | The product consumed in a session is tied to the record; the stock quantity drops on the product card, and products past the threshold or nearing their expiry date are gathered in a single list. ##### Frequently asked questions - What is the difference between a beauty centre and an aesthetic clinic from a CRM point of view? | A beauty centre offers non-medical services (skincare, manicure, permanent make-up, laser hair removal). An aesthetic clinic performs medical procedures (botox, fillers, thread lifts). The CRM supports both — the difference lies in authorisation (in aesthetics a doctor's approval is required) and in KVKK classification. - Is there a separate page for laser hair removal packages? | Yes, our laser hair removal centre CRM page covers the flow specific to laser hair removal centres (package balance, body area tracking, machines). The beauty centre page is broader — it covers skincare, manicure, laser and fillers all together. - What does the product cover for KVKK in the client photo archive, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. Before a photo is uploaded, the client signs their explicit consent on the signature screen in the mobile application, and that consent is kept in a field on the record. Each customer's data is kept in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256 and two-step verification secrets are encrypted at rest; access is limited by role-based permissions, meaning only authorised staff see the photos. Photo files are kept in the media store in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. For the client data you enter into your CRM, you are the data controller and Rapitek is the processor; the disclosure and consent processes toward your clients are yours as well. A client can request deletion whenever they want; however, deleting the photos from the card or deleting the client's record does not remove the photo files from the media store, and today the product does not delete these files by itself. The deleted record moves to the recycle bin; an authorised user can restore it from there or delete it permanently. To have the photo files deleted, you need to write to our support team. - Which booking channels does it support? | Website widget, Instagram bio link, WhatsApp Business, Linktree, Google Business Profile booking. They all come together in a single CRM, and double booking is prevented. ### [Beauty Salon CRM: Chair Occupancy and Stock | Rapitek CRM](https://rapitek.com/en/beauty-salon-crm) A booking lands on the calendar of the stylist doing the treatment; when one runs long the ones behind shift and the gap that opens shows in the list. The allergy note is a field on the card. ##### What we set up, and how - Gather bookings, including requests coming in over WhatsApp, in a single calendar; tie how many hours in advance and over which channel the reminder goes out to a rule - Keep each client's past treatments, allergies and preferred products on their card - Tie the products consumed during a treatment to the record and get a warning when stock runs low - Keep the remaining uses and the expiry date of package memberships on the record, and follow which room and which member of staff each use was with from the same line - Chair Occupancy by Stylist | A booking lands on the calendar of the stylist who will do the treatment; when a treatment runs long, the bookings behind that stylist shift, the gap that opens appears in the list during the day and can be given to another client. - Client Preferences | Past treatments, allergies and preferred products are fields on the client card; they are seen from the same card at the next booking. - Product and Stock Tracking | The product consumed during a treatment is tied to the record; the stock quantity drops on the product card, and products past the threshold are gathered in a single list. - Package Membership and Room Use | The care package sold is a membership record tied to the client record; the number of uses the package includes, the uses remaining and the expiry date are its fields; every booking deducts one use from that membership, and which room and which member of staff the booking was done with is written on the same line; memberships about to expire drop into a list by date. ##### Frequently asked questions - Can bookings be taken over WhatsApp? | Yes, with the WhatsApp integration your clients can create a booking by sending a message. - Can more than one branch be managed? | Yes, you can manage all your branches from a single panel and report per branch. - How is the booking reminder sent? | The date and time of the booking are fields on the record; you tie how many hours before that date and over which channel the reminder goes out to a rule during setup. The send is recorded on the same booking record; the client's confirmation or postponement drops onto that record too. - What happens to the bookings behind when a treatment runs long? | The booking lands on the calendar of the stylist who will do the treatment; when the treatment runs long, the bookings behind that stylist shift, and the gap that opens appears in the list during the day and can be given to another client. - Which is the best CRM software for a beauty salon? | When choosing a CRM for the beauty salon sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your beauty salon process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a beauty salon CRM system cost? | In a beauty salon, the booking lands on the calendar of the stylist who will do the treatment. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the beauty salon sector? | In a beauty salon the product consumed during a treatment is tied to the record; the stock quantity drops on the product card, and those past the threshold are gathered in a single list. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the beauty salon sector? | We start with a discovery meeting: we work out your beauty salon process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a beauty salon? | Yes — the beauty salon stylist in the treatment room can update the past treatment and allergy fields on the client card from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Biotech CRM: Sample and Validation Tracking | Rapitek CRM](https://rapitek.com/en/biotech-crm) The institution is an account record; the researcher, the project lead and purchasing are separate people tied to it. In Rapitek CRM a sample sent to the lab is a dated task. ##### What we set up, and how - Keep the institution as an account and the researcher and the purchasing unit as separate contact records under the same account - Tie the sample sent to the laboratory to a task with its lot and expected return date, and write the validation result into a field on the opportunity - Tie tender and framework agreement dates to the record and gather approaching files in a single list - Report the application specialist's institution visit from the mobile application, and let the technical note build up on the same card as the sales history - Laboratory Account | The institution is an account record; the researcher, the project lead and the purchasing unit are separate contact records tied to that account. - Protocol Sample | The sample sent to the laboratory is a dated task; the lot sent and the return date expected from the laboratory's own protocol sit in the fields of that task, and when the date passes a follow-up task drops into the list. - Validation Stage | The opportunity moves through stages that include the trial and validation steps; files waiting at a stage are filtered by that field. - Tender Calendar | The tender and framework agreement date is a field on the account; records whose date is approaching drop into a list, and the preparation task is opened from there. ##### Frequently asked questions - How do we follow the result from the laboratory we sent a sample to? | The sample despatch is opened as a dated task; the batch sent and the expected return date sit on the record, when the date passes a follow-up task drops into the list, and the result is written into the validation field on the opportunity. - We work with several research groups at the same university — will the records get mixed up? | The institution is a single account record, but each group and researcher is a separate contact record tied to that account; the opportunity is tied to the relevant group, so work running in parallel at the same institution does not bury the history of the other. - What do we do so as not to miss a tender or framework agreement date? | The tender and framework agreement date is a field on the account; records whose date is approaching drop into a list, and the preparation task is opened straight from that record. - Which is the best CRM software for biotech? | When choosing a CRM for the biotech sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your process in the biotech sector, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a biotech CRM system cost? | In biotech, because the application specialist reports the institution visit from the mobile application, roles outside sales enter the system as well. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the biotech sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the biotech sector? | We start with a discovery meeting: we work out your process in the biotech sector together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for biotech? | In biotech the application specialist's institution visit is reported from the mobile application, and the technical note builds up on the same card. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Blockchain CRM: Consortium and Pilot Stages | Rapitek CRM](https://rapitek.com/en/blockchain-crm) Every institution joining the network is its own account record and the project links them under a single opportunity; in Rapitek CRM the opportunity does not move while an exit condition is empty. ##### What we set up, and how - Keep every institution joining the network in its own account record and tie the project to those accounts under a single opportunity - Define the proof of concept, pilot and production stages separately and write the exit condition of each stage onto the record - Record the legal, IT and business unit counterparts with their roles, and see who is waiting on which question - Drop recurring technical questions into the queue as case records; let the resolution note stay on the case and be read from the same record at the next institution - Consortium Accounts | Every institution joining the network is a separate account record; the project opportunity links those accounts, and progress per institution is visible on its own card. - Stage Gates | Proof of concept, pilot and production are stages of the opportunity; the condition for moving to the next stage is written in a field on the record, and when it is left empty the rule defined during setup stops the stage from progressing. - Stakeholder Roles | The legal, IT and business unit counterparts are contact records; the role is a field, and open questions sit as tasks tied to the person. - Technical Question History | Recurring integration questions are opened as case records; the resolution note is written onto the case, and later cases opened with the same question are read from these records. ##### Frequently asked questions - How do we track several institutions joining the same network in a single project? | Each institution is a separate account record, while the project is a single opportunity relating those accounts; which institution is waiting at which stage is read from the records under that opportunity. - Can we make the CRM talk to our own chain application or our nodes? | We build the connection to your own chain application or your nodes; there is no out-of-the-box module. The connection is written specifically for the project over the REST API covering 183 business objects, OAuth2 and webhooks; we work out its scope in the discovery meeting and share it in writing. - Can we stop a move to the next stage before the exit condition is complete? | Proof of concept, pilot and production are stages of the opportunity; the condition for moving to the next stage is written in a field on the record, and when that field is left empty the rule defined during setup stops the stage from progressing. - Which is the best CRM software for blockchain? | When choosing a CRM for the blockchain sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your process in the blockchain sector, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a blockchain CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the blockchain sector? | In a blockchain project, each of the institutions joining the network asks its own IT department about integration. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the blockchain sector? | We start with a discovery meeting: we work out your process in the blockchain sector together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for blockchain? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Building Materials CRM: Quote Revisions | Rapitek CRM](https://rapitek.com/en/building-materials-crm) The material list of a renovation project is the line items of the quote; each revision is kept with its own date under the same quote, and the discount comes from the account's price list. ##### What we set up, and how - Break the material list of a renovation project into quote line items, and keep every revision version with its own date on the quote - Define price lists specific to corporate customers; let the discount reach the quote line from that list - Track supplier performance by comparing their order and delivery times - Keep the stock quantity and the critical threshold in fields per product; let items falling below the threshold gather in a single list - Material List Revision | The material list of a renovation project is the line items of the quote; when the customer removes and adds items, each version is kept with its own date under the same quote, and which version applies at delivery is read from the record. - Customer-Specific Pricing | The corporate customer's price list is tied to the account record; the discount reaches the quote line from that list. - Supplier Relationship Management | A supplier is an account record; order and delivery dates build up under the card, and the comparison of lead times is made in a report. - Stock and Order Tracking | The stock quantity and the critical threshold are fields on the product record; items falling below the threshold are gathered in a single list. ##### Frequently asked questions - Can bulk orders and project quotes be managed? | Yes, with Rapitek CRM you can create project-based bulk quotes, follow customer approval processes and keep the revision history. - Is supplier management inside the CRM? | Yes, you can record your suppliers, follow the order history and report supplier performance. - Is the discount we give tradespeople and renovation companies applied the same way on every quote? | The corporate customer's price list is tied to the account record and the discount on the quote line comes from that list; it does not depend on who remembers what. When the list is updated, new quotes open with the current rate. - Which is the best CRM software for a building materials store? | When choosing a CRM for the building materials sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your building materials process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a building materials CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the building materials sector? | In a building materials store the stock quantity and the critical threshold are fields on the product record; items falling below the threshold are gathered in a single list. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the building materials sector? | We start with a discovery meeting: we work out your building materials process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a building materials store? | Yes — the building materials team can open the stock quantity and critical threshold fields on the product record from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Butcher CRM: Trade Prices and Weight Differences | Rapitek](https://rapitek.com/en/butcher-crm) Restaurants and hotels are each an account record, and the agreed price per kilo sits in a field on the account. Fat ratio, thickness and packaging are fields on the order line. ##### What we set up, and how - Open the daily order of regular customers such as restaurants and hotels from a template, and apply the agreed price per kilo from the account - Write preparation instructions such as mince fat ratio, cut thickness and packaging onto the order line - Record the actual weight after weighing, and see the difference between order and delivery without waiting for the end of the month - Tie holiday period slaughter requests to an appointment record and plan the delivery order in advance - Trade Account Price | Restaurants and hotels are each an account record; the agreed price per kilo sits in a field on the account and reaches the order line from there. - Preparation Instruction | Fat ratio, thickness and packaging are fields on the order line; the butcher preparing it and the person who took the order look at the same line. - Weight Difference | The weight ordered and the weight delivered are two separate fields on the record; the difference is calculated from those fields and stays on the delivery record. - Slaughter Appointment | A holiday period slaughter is an appointment record with date and time fields; the day's delivery order is read from the list of those records. ##### Frequently asked questions - Can mincing and cut preparation instructions be kept on the order record? | Yes. Fat ratio, number of passes, cut thickness and packaging preference are fields on the order line; the butcher preparing it reads that same line rather than a recipe described over the phone. Because a regular customer's standard recipe sits on the account record, it is not asked again with every order. - What happens when the kilos ordered and the kilos delivered do not match? | The weight ordered and the weight off the scale sit in two separate fields on the record; the difference between them and its effect on the price are read from the delivery record. When the account is settled at the end of the month, which delivery produced how much difference comes out of the records rather than out of memory. - How do we plan the delivery order for slaughter requests during the holiday period? | A slaughter request is an appointment record with date and time fields; the day's delivery order is read from the list of those records. That way the order is known in advance rather than at the door. - Which is the best CRM software for a butcher? | When choosing a CRM for the butchery sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your butchery process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a butcher CRM system cost? | In a butcher's, because the person taking the order and the butcher look at the same order line, people on both sides become users of the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the butchery sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the butchery sector? | We start with a discovery meeting: we work out your butchery process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a butcher? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Cafe CRM: Customer Preferences and Table Booking | Rapitek](https://rapitek.com/en/cafe-crm) A regular customer is a record; the preference note, the visit frequency and the last visit date are its fields. The campaign goes to the list filtered out of those fields. ##### What we set up, and how - Record regular customers with their preferences and visit history, so the information stays in place even when staff change - Send the loyalty status and the campaign to a filtered list, and write a separate message to those who have not been in for a long time - Tie group bookings for meetings and celebrations to the calendar, and keep the table and time on the record - Follow office and company orders as repeating orders under the account, and turn the delivery day into a task - Customer Card | A regular customer is a record; the preference note, the visit frequency and the last visit date sit in its fields. - Loyalty and Campaign | A campaign is sent to a list of records pulled out with a filter; who received which message is visible on the customer card. - Table Booking | A booking is a record with date and time fields; the number of people, the table and the celebration note sit on the same card, and the day's reserved tables are read from a single list. - Corporate Order | Offices and companies are each an account record; the repeating order sits under the account, and the delivery day is opened as a task. ##### Frequently asked questions - Is it realistic to record a customer on a day when the counter is moving fast? | The record is opened once; on later visits it is found by name or phone number and the preference note is written onto it. Because loyalty and campaign lists come out of these records, every customer entering the system is automatically targeted in the next announcement. - We have several branches; can we see what a customer bought at which branch? | Yes. The customer is a single record, and their visits build up under that record together with the branch information; with branch-based permissions each team sees its own list, while management follows all branches from one place. - Where does the request of a customer booking a table for a meeting sit? | A booking is a record with date and time fields; the number of people, the table and the celebration note sit on the same card. The day's reserved tables are read from the list of those records rather than from the shift notebook. - Which is the best CRM software for a cafe? | When choosing a CRM for the cafe sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your cafe process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a cafe CRM system cost? | In a cafe, because the customer preference sits on the customer card rather than in the barista's memory, the staff behind the counter enter the system too. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the cafe sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the cafe sector? | We start with a discovery meeting: we work out your cafe process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a cafe? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Call Centre CRM: Screen Pop and Queues | Rapitek CRM](https://rapitek.com/en/call-center-crm) A call is a record tied to a contact, account or lead — direction, duration and outcome code are its fields. In Rapitek CRM the shift report comes out of these records; no spreadsheets are merged. ##### What we set up, and how - Open the customer card on the agent screen on an incoming call; the record matched from the number is reached over the adapter - Tie every call to a contact, account or lead record; keep its direction, its outcome and its duration in the same place - Gather incoming WhatsApp conversations in the team inbox and distribute them with queue and assignment rules - Record the case opened during a conversation and run the resolution process from the same customer card until it closes - Report the number of calls, the average duration, the resolution rate and the survey result per shift - CTI Adapter Panel | Rapitek does not make a softphone; the PBX vendor's adapter is embedded in the right-hand panel of the CRM. The bridge is documented: matching a record from a number, writing the call onto the record, click-to-dial from the phone field and agent status are all defined in that protocol. - Screen Pop | The adapter sends the incoming number; on a single match it goes straight to that record, on more than one a selection window opens, and when there is none a new lead record filled in with the number can be opened. - Call Record | A call is a record tied to a contact, an account or a lead. Direction, status, date, duration and note sit in their own fields; if the adapter is installed, this record is written from there when the conversation ends. - WhatsApp Team Inbox | The business's own Meta WhatsApp Business account is connected to the inbox; the conversation is recorded on the customer card, and canned responses and keyword rules run from the same record. Even if a member of staff leaves, the history stays with the business. - Queues and Assignment Rules | An incoming record drops into a queue; who it goes to is defined in the assignment rule (customer type, language, subject). The rule is built around your flow during setup. - Shifts and Reporting | The shift and working-hours calendar is defined; the number of calls, the average duration and the resolution rate come out of a shift-broken-down report on these records, and no spreadsheets are merged at the end of the day. ##### Frequently asked questions - Which telephone systems does it work with? | Rapitek CRM offers a CTI adapter panel in the pattern of Salesforce Open CTI: your PBX vendor's adapter is embedded in the right-hand panel of the CRM and works over a documented bridge. We build the connection to particular PBX systems; there is no out-of-the-box module. The adapter is written to this protocol either by the PBX vendor or specifically for the project; its scope and cost are worked out in the discovery meeting and shared in writing. - Does the customer card open automatically on an incoming call? | Once the adapter is installed, yes. The adapter sends the incoming number to the bridge; on a single match it goes straight to that record, on more than one match a selection window opens, and when there is no match a new lead record filled in with the number can be opened. Without the adapter installed, this flow does not work. - Can we make calls from the browser? | Rapitek does not make a softphone. Your PBX vendor's softphone adapter is embedded in the right-hand panel of the CRM; click-to-dial on the phone fields depends on that adapter and becomes active when the adapter enables it. - How do we run an outbound calling campaign? | A call list can be defined as a stepped sequence: the target list, the steps, the number of attempts and the outcome code (no answer, appointment, sale, refusal) are defined during setup. The agent sees their turn from the list, dials by clicking on the phone field, and closes every call as a Call Record. We do not offer an automatic dialer; if you have such a system on the PBX side, it is connected over the adapter. - What does the product cover for KVKK with call records and voice recordings, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. The voice recording is taken on the PBX side — we do not offer call recording out of the box. The adapter can pass the recording link to the call record. On the CRM side, the call itself and the customer's consent status are kept as fields, and access is limited by role-based permissions. You define the retention period and the deletion step; there is no deletion engine that runs by itself. Deleted records are moved to the recycle bin; an authorised user can restore them from there or delete them permanently; evidence and consent records are protected from permanent deletion. Data is hosted in the EU (Finland). For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. For the personal data in your call records, your business is the data controller and Rapitek is the data processor; disclosure to the people you speak with, and any consent processes, are also your business's responsibility. ### [Camping CRM: Pitch Bookings and Group Requests | Rapitek CRM](https://rapitek.com/en/camping-crm) Every pitch, caravan space and cabin is its own record; a booking is tied to that unit with its arrival and departure dates, and a clash shows as the second booking is opened. ##### What we set up, and how - Keep pitches, caravan spaces and cabins as separate unit records, and tie the booking directly to the unit by date range - See seasonal and nightly stays in the same calendar, and catch clashing dates while the record is being opened - Move school, club and company group requests through quote stages, and write the number of people and the extra services onto the record - Send a message to last season's campers when the season opens, and record their replies and the departure survey - Pitch and Unit Record | Every pitch, caravan space and cabin is a separate record; capacity, electricity and water connection and price class sit in its fields. - Booking | A booking is a record with an arrival and a departure date; it is tied to the unit, and a clash on the same dates shows while the second record is being opened. - Group Request | A school or club request is an opportunity record; the number of people, the accommodation type and the extra services are fields, and the card moves on as the stage changes. - Camper History | A returning camper is a record; their past stays and their preferred pitch build up under it, and the pre-season list comes out of there. ##### Frequently asked questions - How do we stop the same pitch being promised twice, for the season and for a weekend? | Every pitch is a separate unit record, and the booking is tied to that unit with its arrival and departure dates; when a second record is opened for the same date range, the clash shows on the record, and seasonal use takes up space in the same calendar. - Can we manage a thirty-person school group's request separately from an accommodation booking? | Yes. The group request moves through quote stages as a separate record with fields for the number of people, the accommodation type and the extra services; once agreement is reached, the relevant pitch and cabin bookings are opened under that record. - How do we reach last season's campers when the season opens? | A returning camper is a record; their past stays and their preferred pitch build up under that record. The pre-season message list is pulled out by filtering on those fields, and the replies that come back are recorded on the same record. - Which is the best CRM software for a campsite? | When choosing a CRM for the camping sector, you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, stages and reports around your camping process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we carry out the setup with that experience. - How much does a camping CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out in the camping sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in the camping sector? | We start with a discovery meeting: we work out your camping process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a campsite? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Car Rental CRM: Fleet Availability and Reports | Rapitek CRM](https://rapitek.com/en/car-rental-crm) Every vehicle is a record; status, location and rental dates are its fields. In Rapitek CRM the difference between the check-out and check-in report gives the extra charge. ##### What we set up, and how - Follow the location, status and availability of all vehicles live from a single screen - Drop booking requests coming in from the web form straight onto a record, and send the confirmation message from that same record - Record the check-out and check-in mileage, the fuel level and the damage photos on the report; let the person taking delivery sign on the signature screen in the mobile application - Track damage records, insurance processes and their cost per vehicle - Let the whole team answer from a single business number, with conversations assigned by the rule you define and followed by managers - Fleet and Availability Management | Every vehicle is a record; status, location and rental dates are kept in its fields, and availability is read from the list and calendar view of those records. - Online Booking | A request coming in from the web form can be set to drop straight in as a record; the confirmation message and the follow-up task are tied to that form during setup. - Vehicle Check-out and Check-in Report | At check-out and at check-in, the mileage, the fuel level and the existing scratches are written into the fields of the report record; photos sit as attachments, and the person taking delivery signs on the signature screen in the mobile application. The extra charge after the rental comes out of the difference between those two reports, rather than staying on a separate piece of paper. - Damage and Insurance Tracking | A damage record is tied both to the vehicle and to the rental; thanks to the cost field, total damage expense per vehicle appears in the report. - Rental Extension Request | An extension asked for before the return day is a request tied to the rental record; the new return date, the extra day charge and the approval status sit in fields, and a clash with that vehicle's next booking is seen from the same record. ##### Frequently asked questions - If a rental extension request clashes with the next booking, will I see it? | Yes. An extension is a request tied to the rental record; the new return date, the extra day charge and the approval status sit in its fields. A clash with that same vehicle's next booking is seen from this record, and the calendar does not change until approval is given. - How do we document the difference between handover and return? | At check-out and at check-in, the mileage, the fuel level and the existing scratches are written into the fields of the report record, and the photos sit as attachments; the person taking delivery signs on the signature screen in the mobile application. The extra charge after the rental comes out of the difference between those two reports. - How long does setup take for car rental? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your car rental process needs becomes clear in that meeting. We migrate your data; the scope of the migration and any fee for it are worked out in the same meeting and shared in writing. - Will it integrate with my existing systems for car rental? | In car rental, a request coming in from the web form dropping straight in as a record can be set up during setup. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - Can several people use the same WhatsApp number for car rental? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned by the rule you define. Managers can follow the conversations and the response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Car Wash CRM: Plate, Allowance Balance and Fleet](https://rapitek.com/en/car-wash-crm) A package is a record; the number bought and the allowance left sit in its fields, and each wash lands as a line. Search the plate and the remaining allowance and fleet agreement appear together. ##### What we set up, and how - Call the vehicle up by its plate; see the remaining package allowance, the last wash date and the price applied on the same card - Decrement the allowance of a customer who bought a wash package at every transaction and remind them by SMS before it runs out - Gather all transactions of fleet and corporate customers within the period under the account and produce their summary - Record the member of staff who did each wash and read the count per person and the bonus earned from the report - Package and Allowance Balance | A package is a record; the number bought and the allowance remaining sit in its fields, and every wash lands as a line attached to that record. - Vehicle Card by Plate | A vehicle is a unique record opened by its plate and attached to the customer; the model, the colour and the special instruction note are fields on the card. - Fleet Account and Period Summary | A fleet customer is an account record; the transactions within the period are attached to that account, and the summary is a list of those same lines by date range. - Staff Count and Bonus | Every transaction record has a field for the member of staff who did the work; the number of washes per person is read from the report grouped by that field. ##### Frequently asked questions - How do we see a customer's remaining wash allowance at the till? | The package is a record attached to the customer card; when the plate is searched, the number bought, the number used and the allowance remaining appear together. Because every wash lands on that record as a line, the balance is not updated by hand. - Can we produce a single summary for a fleet customer at the end of the period? | Because transactions are attached to the fleet account, at the end of the period how many times each plate was washed gathers in a single list and the summary comes out of it. Issuing the invoice stays on the accounting side; we build the connection to your pre-accounting program, there is no out-of-the-box module, and the transfer is built specifically for each project over a REST API or export. - Where do we get the number of washes a member of staff has done for the bonus? | Every transaction record has a field for the member of staff who did the work; the number of washes per person is read from the report grouped by that field. The bonus calculation is not rebuilt at the end of the month, it comes out of the same records. - Which is the best CRM software for a car wash? | When choosing a CRM for a car wash you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your wash process, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a car wash CRM system cost? | In a car wash every transaction record has a field for the member of staff who did the work, so the people at the bay are defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the car wash sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in the car wash sector? | We start with a discovery call: together we work out your wash process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a car wash? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Haulage and Transport CRM: Crew and Vehicle | Rapitek CRM](https://rapitek.com/en/cargo-shipping-crm) The distance, volume, floor and extra services entered at the survey are fields on the quote line; when the quote changes, the job's plan changes too. Crew and vehicle sit on the same record. ##### What we set up, and how - Enter the distance, goods volume, floor situation and extra services onto the quote line after the survey; have the total calculated from the price list - Record the incoming request and produce the quote from the same record; run home removals, office moves and intercity jobs separately - Assign the right crew and vehicle to each moving job, and see clashes falling on the same day in advance - Record moving-day status updates and keep the customer informed as they happen - Send quote, date confirmation and moving-day notifications over WhatsApp - Request and Quote Management | An incoming request is opened as a record; the job type (home removal, office, intercity) is a field, and the quote is produced under the same record. - Crew and Vehicle Assignment | A job is a record with crew and vehicle fields; because jobs falling on the same day appear side by side in the calendar, a clash is noticed in advance. - Operations Tracking | Moving-day updates are written onto the same job record; the information going to the customer goes from that record, and who told them what and when leaves a trace. - Price Calculation | Distance, volume, floor and extra services are fields on the quote line; unit prices come from the price list, and the total comes out on the quote card. - Goods Inventory and Delivery Report | The list of goods drawn up at the survey is the line items of the job; the person taking delivery signs on the signature screen in the mobile application, the damage photo is attached to the same record, and a damage claim raised later is compared against those lines. ##### Frequently asked questions - Is the price calculation automatic? | Distance, goods volume, floor situation and extra services are fields on the quote line; unit prices come from the list you defined in advance, and the total is calculated from those fields. Your team enters the values at the survey; once they are entered, the calculation does not have to be repeated and two different figures do not come out for the same job. - Can I manage intercity and home removals separately? | Yes. The service type (home removal, office move, intercity) is a field on the job record; each type uses its own stage flow and its own price list, and reports are taken separately by that field. - Is customer referral tracking done? | Yes, which customer came from whom is a field on the record; the share of work coming in by referral is reported from that field. - How long does setup take for haulage and transport? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your haulage process needs becomes clear in that meeting. We migrate your data; the scope of the migration and any fee for it are worked out in the same meeting and shared in writing. ### [Catering CRM: Headcount, Equipment and Capacity | Rapitek](https://rapitek.com/en/catering-crm) An event is a single record with date, time, address, headcount and menu fields. In Rapitek CRM, when the headcount changes the quote lines are recalculated from that same record. ##### What we set up, and how - Run every event in a single record with its date, headcount, menu and delivery time - Produce the quote line by line according to the menu and the headcount, and follow the revisions - Tie equipment and staff assignments to the event record - See events falling on the same day in the calendar and catch capacity clashes in advance - Keep corporate customers' repeat events together with their history - Event Record | An event is a single record with date, time, address, headcount and menu fields. When the headcount changes, the quote lines are updated from that same record. - Quote and Revision | The quote is produced with its line items under the event; each revision is kept with its own date, and which version was approved sits on the record. - Equipment and Staff | Equipment and assigned staff are each a field; the same piece of equipment falling on two events appears in the list, and the rule is defined during setup. - Daily Capacity | Events are gathered in the calendar by their date field; the total headcount falling on one day comes out in a report, and the decision to accept is made by looking at it. - Corporate Customer History | A company is an account record; its past events, the menus it chose and its agreed price build up under the card, and reach the new quote from there. ##### Frequently asked questions - What happens to the quote if the headcount changes on the last day? | The headcount is a field on the event record; when you change it, the quote lines are recalculated from that same record and the previous version is kept with its date, so which version was approved is not lost. - How do I see that two events have fallen on the same day? | Events are gathered in the calendar by their date field; the total headcount falling on that day and the equipment assigned come out side by side in a report, and the capacity decision is made by looking at that. - How much does a catering CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery meeting and shared in writing. Rapi artificial intelligence credit and ERP integration are items priced separately. - How are CRM integrations carried out on the catering side? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from installation to installation, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery meeting and share them in writing. - How does the move to a CRM system work in catering? | We start with a discovery meeting: we work out your catering process together, and which fields and which stages are needed. After the meeting, we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for catering? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The application is live on both the App Store and Google Play. The web interface also works on tablets and phones. The application 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. ### [Ceramics CRM: Batch, Calibre and Project Records | Rapitek](https://rapitek.com/en/ceramics-crm) An order carries batch and calibre fields alongside the product code; which batch went to which project is read from the record, and a later shortfall request attaches to the same record. ##### What we set up, and how - Record the order with batch and calibre fields, and read from the record which batch went to which project - Link the project to the dealer who entered it first, so that the existing record appears in the list when the same site is entered a second time - Attach the shade sample sent to the architect to a task together with the batch it came from, and drop the ones with no answer into a list - Produce the quote with both the square metre and the box equivalent, and track the quantity sent to site and the quantity invoiced from the same line - Batch and Calibre | An order is a record that carries batch and calibre fields alongside the product code; a later shortfall request attaches to the same record. - Project Record and Dealer | A project is a record and it is linked to the dealer who entered it first; when the same site is entered again the existing record appears in the list. - Shade Batch Sample | A shade sample sent to an architect or a dealer is a task; the batch it came from and its reply date sit in its fields, and the ones with no answer drop into a list by date. - Square Metres and Boxes | A quote line carries both the square metre and the box equivalent; the quantity shipped and the quantity invoiced are read from the same line. ##### Frequently asked questions - Can we find the batch that went to the site later on? | Yes. Batch and calibre are fields on the order, and the order is linked to the project record; how many square metres went to which project from which batch is read from the record. Because a shortfall request that arrives months later is opened on the same record, which batch is being looked for is not guessed. - How do we see that two dealers are tracking the same project? | A project is a record and it is linked to the dealer who entered it first. When the same site is about to be entered a second time, the existing record appears in the list; which dealer recorded it and when, and what stage the conversation is at, are read from the record, and the decision is made before the price is discussed. - Can we see that no answer has come back on a shade sample we sent? | Yes. A shade sample sent to an architect or a dealer is a task; the batch it came from and the expected reply date are in that task's fields. Samples that are past their date and have not been closed stay in a list sorted by date; which project, to whom and from which batch they were sent are read from the same record. - Which is the best CRM software for ceramics? | When choosing a CRM for the ceramics industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your ceramics process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a ceramics CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the ceramics industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the ceramics industry? | We start with a discovery call: we map out your ceramics process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for ceramics? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Chemical CRM: Sample Trials and Batch Tracking | Rapitek](https://rapitek.com/en/chemical-crm) The lot number is a field on the order line; when a complaint comes in about a batch, every customer shipped from that lot is gathered in a list filtered on that field. ##### What we set up, and how - Move the sample request, the trial conditions and the approval decision forward on a single opportunity record - Link the shipped batch number to the customer order, and filter the affected customers from that field when a complaint comes in - Attach the technical data sheet and the safety data sheet to the record and track which version went to whom - See the number of returnable drums and IBCs held at the customer on the account record, and open the collection task from there - Sample and Trial | A sample request is a stage on the opportunity record; the trial condition and its result are in the card's fields, and the approval decision stays on the same record. - Batch Tracking | The lot number is a field on the order line; every customer shipped from that batch is gathered in a list filtered on that field. - Product Documents | The technical data sheet and the safety data sheet are attachments linked to the record; because sending leaves a trace in the record history, versions do not get mixed up. - Returnable Packaging | The number of drums and IBCs held at the customer is a field on the account record; collection is opened as a task linked to that field. ##### Frequently asked questions - Can we find from the CRM which customer a shipped batch went to? | Yes. The lot number is a field on the order line; when a complaint comes in about a batch, every customer shipped from that lot is listed with a single filter. Because a notification task can be opened from the same list, who was contacted also stays on the record. - How are the safety data sheet and the technical data sheet sent to the customer? | The documents are attached to the product and customer record; because sending is written into the record history, which version went to whom and on what date can be read afterwards. When a document is updated, the list of customers it has to be sent to again comes out of the same records. - Where do we track the returnable drums and IBCs held at the customer? | The number of drums and IBCs at the customer is a field on the account record; collection is opened as a task linked to that field, and how many containers are left at which customer is read from the list on the same field. - Which is the best CRM software for the chemical industry? | When choosing a CRM for the chemical industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your chemical process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a chemicals CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the chemical industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the chemical industry? | We start with a discovery call: we map out your chemical process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for chemicals? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Cinema CRM: Group Tickets and Corporate Quotas | Rapitek](https://rapitek.com/en/cinema-crm) A corporate screening is an opportunity record; the film, session date, screen and headcount are its fields. The run-end date is a field too, so expired quotes gather in a separate list. ##### What we set up, and how - Track private screening, group ticket and corporate requests through stages from first contact to contract - Track the ticket quota assigned to a company and the number used on the account record, and open the renewal task when the quota runs out - Build up each company's past screenings, contacts and the terms discussed on a single card - Report which type of request came in during which period and at which stage the quotes have stalled - Group Ticket Booking | A school or company group booking is its own record; the group size, the requested session and the deposit status sit in its fields; bookings that are not confirmed are listed by the time left until the session day. - Corporate Ticket Quota | The ticket quota assigned to a company and the number used are fields on the account record; when the remaining quota runs out, a renewal meeting task is opened under the same account. - Private Screening Session | A corporate screening is an opportunity record; the film, the session date, the screen and the headcount are in its fields; because the date the film comes off release is a field too, expired quotes gather in a separate list. - Pre-Show Advertising Sales | An advert to run in the auditorium is a contract record; the advertiser, the broadcast period and which screens it will run on are in its fields, and taking delivery of the advertising material is a task under the same record. - Distributor Release Record | Each film is a release record linked to the distributor account; the release start, the print delivery status and which screens it was given to sit in its fields, and a task for the screen plan is opened before the run ends. ##### Frequently asked questions - Can we see in advance the quotes that rest on a film about to come off release? | Yes. A corporate screening is an opportunity record; the film, the session date and the date the film comes off release are its fields. Quotes whose run end is approaching and that are still waiting for an answer are gathered in a separate list with a filter on that field; that way the conversation is renewed before the ground the quote stands on drops off the box office. - How long does setup take for a cinema? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your cinema operation process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Will it integrate with my existing systems for cinema? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person on the cinema team use the same WhatsApp number? | On the cinema side, private screening and group ticket requests land with different people through different channels, so a shared place is needed. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Cleaning Services CRM: Scope and Site Sign-Off | Rapitek](https://rapitek.com/en/cleaning-services-crm) Every customer site is an account record; the scope, the frequency, the monthly fee and the renewal date are its fields. Extra work outside the scope is a separate record, listed at month end. ##### What we set up, and how - Keep each site's contract scope, frequency and monthly fee on the account record, and drop recurring work onto the calendar as tasks - Define team shifts and working hours, and take site check-in from the mobile app with location verification - Have the customer's representative sign the completion form on the signature screen in the mobile app, and write the consumables used onto the same task - Collect out-of-scope requests in separate records and produce the breakdown of work done outside the contract at month end - Site and Contract Scope | Every customer site is an account record; the scope, the frequency, the monthly fee and the renewal date sit in its fields. - Recurring Work | Recurring cleaning is a task; it falls onto the calendar according to its frequency, and a task that is not done stays open in the list. - Site Confirmation | Team check-in is taken from the mobile app and the location is verified; the customer's representative signs the completion form on the signature screen in the mobile app. - Out-of-Scope Request | Work that is not in the contract is a separate request record; it is linked to the site, and whether or not it was charged sits in its field. ##### Frequently asked questions - How do I record extra work that is not in the contract? | An out-of-scope request is a separate record and is linked to the site; who asked for it, when it was done and whether or not it was charged sit in its fields. Because a list of these records is produced at the end of the month, the renewal meeting is entered with a breakdown of the work done outside the contract. - How do I verify that the team actually went to the site? | Site check-in is taken from the mobile app, the location is verified, and fake location reporting is detected. At the end of the job the customer's representative signs the form on the signature screen in the mobile app; the signed form and the check-in record sit under the same task. - Does recurring work that was not done at a site show up in the list? | Yes. Recurring cleaning is a task and falls onto the calendar according to its frequency; a task that is not closed stays open in the list, and which job is missing at which site is seen during the day. - Which is the best CRM software for cleaning services? | When choosing a CRM for the cleaning industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your cleaning process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a cleaning services CRM system cost? | In cleaning, because the check-in of the team going to the site is taken from the mobile app, the people in the field are defined in the system as well. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the cleaning industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the cleaning industry? | We start with a discovery call: we map out your cleaning process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for cleaning services? | In cleaning, team check-in is taken from the mobile app and the location is verified; the customer's representative signs the completion form. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Clinic CRM: No-Show and Follow-Up Tracking | Rapitek](https://rapitek.com/en/clinic-crm) The follow-up date is derived from the treatment protocol; the appointment, the WhatsApp thread and the balance due sit on the same patient card. A due follow-up reserves a calendar slot. ##### What we set up, and how - Gather allergies, medication in use, past visits and uploaded test results on a single patient card, and limit access by role - Combine online booking, the doctor's calendar and room assignment; set a rule for a reminder to go out 24 hours before the appointment - Let WhatsApp conversations be linked to the patient record and template messages be managed centrally - Run package sales, instalment payments and collection tracking on a single record; we build the connection to the e-invoice side, there is no out-of-the-box module - Set up the 1-week, 1-month and 3-month follow-ups as tasks tied to the treatment date, according to the treatment protocol - Patient Card and Medical History | A patient is a single card; personal details, allergies, medication in use, past visits, payment lines and uploaded test results are the fields and attachments of that card, and which role sees which field is defined in the permission set. - Appointment Management and No-Show Tracking | An appointment is a record; the doctor's calendar, the room and the time sit in its fields. You set a rule at setup for a WhatsApp or SMS reminder to go out 24 hours before the appointment; confirmation and rescheduling are written onto the same appointment record, and a missed appointment stays open in the list. - WhatsApp Conversation | The WhatsApp conversation with the patient sits in the team inbox and is linked to the patient record; template messages, voice notes and images build up under the same record, and even if staff change the history stays on the card. - Payment and Invoicing | Package sales, instalments and invoice records are lines linked to the patient card; the outstanding balance sits in a field and an overdue line drops into a list. The connection to the e-invoice side is built for each project; there is no out-of-the-box module. - Follow-Up Appointment Calendar | Follow-up steps (1 week, 1 month, 3 months) are tasks tied to the date of the treatment record; the steps are defined at setup according to your own protocol, a step that falls due reserves a slot in the calendar and a notification is sent to the patient. ##### Frequently asked questions - What is a clinic CRM and why should I use one? | A clinic CRM is a system that brings patient records, appointments, WhatsApp communication, invoicing and follow-up processes together on a single platform. Instead of moving between Excel, a diary and the phone, you manage the whole patient journey from one place. Missed appointments, follow-up steps and collections sit on the same patient card; you see how much each of them has improved from your own report. - What does the product cover for KVKK with health data, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. Rapitek CRM stores your data in a separate database of your own; up-to-date TLS encryption is used in transit, and passwords are hashed one-way with PBKDF2-SHA256 and 2FA secrets are encrypted at rest. For health data, role-based access comes ready, and field changes users make to existing records are stored in the record's history. Deleted records are moved to the recycle bin; an authorised user can restore them from there or delete them permanently, and evidence and consent records are protected from permanent deletion. Clearing the personal fields on a patient card by hand or with a bulk update does not delete files attached to the record or the old values kept in the field change history; files attached to a record are not deleted from storage whether you delete the file from the card or delete the record. To have the attached files and the old values in the change history deleted, you need to write to our support team. For the patient data you enter into your CRM, you are the data controller and Rapitek is the processor; you add and manage your own privacy notice. Hosting is in the European Union: the database is in Finland and media files are in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. - Is it suitable for specific clinics such as dermatology, dental, ophthalmology or obstetrics? | Yes. Customisation is done for each speciality on top of the general clinic template: a photo archive in dermatology, a treatment plan diagram in a dental clinic, dioptre tracking in an eye centre, gestational week tracking in an obstetrics clinic. We also have separate sector pages. - How do you migrate our existing patient data? | We carry out the one-off data migration from Excel, from older clinic software (Medisoft, Hekim Bilişim, Mediport and the like) or from paper forms. After the discovery call we give you a date, not a range — how many fields and how many stages your patient history, your appointment calendar and your invoice records need becomes clear in that call. The scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Cloud Services CRM: Renewals and Health Score | Rapitek](https://rapitek.com/en/cloud-crm) A subscription is a record with start, renewal date and monthly amount fields. In Rapitek CRM, MRR and ARR come out of those fields, and the health score out of the threshold you define. ##### What we set up, and how - Calculate MRR, ARR and churn metrics from the amount and date fields on the subscription records - Define the components of the health score and its threshold yourself, and move accounts that fall below the threshold to the top of the list - Send the task tied to the time left until the renewal date to the account owner, and produce the quote from the same record - Open an upgrade opportunity for accounts whose quota and module usage rates cross the threshold - Subscription Record | A subscription is a record with start, renewal date and monthly amount fields. MRR and ARR are calculated from the sum of those fields, and churn from the proportion of cancelled records. - Customer Health Score | You define the components of the score and its threshold; login frequency, the modules used and open support tickets are fields on the account record, and an account that falls below the threshold moves to the top of the list. - Renewal Task | The renewal date is a field on the subscription record; a task tied to the time left until that date goes to the account owner, and the quote is produced from the same record. - Expansion Opportunity | Quota and module usage rates are fields on the account record; an upgrade opportunity is opened for an account that crosses the threshold, and feeding those fields from your product is set up over the REST API or webhooks. ##### Frequently asked questions - Can MRR/ARR be tracked? | Yes. MRR, ARR and churn are calculated from the amount and date fields on the subscription records, and the period comparison comes out of the report on those records. - Does it integrate with billing systems? | We build the connection to Stripe, iyzico or your bank; there is no out-of-the-box module, and collections do not land in the CRM by themselves. The connection is built for each project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost in writing in the discovery call. When this connection is not built, subscription, collection and usage information is entered into the CRM manually or by file import; MRR, ARR, the renewal date and the health score run on those records. - How do we see the accounts whose renewal date is approaching? | The renewal date is a field on the subscription record; a task tied to the time left until that date goes to the account owner, the renewal quote is produced from the same record, and accounts with a low health score stand out in that list. ### [Construction CRM: Tender Files and Site Reports | Rapitek](https://rapitek.com/en/construction-crm) Every project is a record; the client, subcontractor, contract and site report build up under it. A subcontractor's past performance is seen from the same card when a new assignment is made. ##### What we set up, and how - Open every project as a separate record and link clients, subcontractors and contracts under it - Prepare tender and quote files quickly with standard templates - Enter photos and progress reports from the site instantly with the mobile app (the app is live on both the App Store and Google Play) - Build the connection to accounting software such as Logo, Netsis and SAP for your own project with the REST API and webhooks - Run site and office messaging as a team from a single WhatsApp number, and let the history stay on the project - Project Record | Every project is a record; the client, the subcontractor, the contract and the site report build up under this record, and a subcontractor's performance on earlier projects is seen from the same card when a new assignment is made. - Quote and Tender | The quote is produced with its line items linked to the project; because the standard template is fed from the fields on the record, the tender file is not compiled from scratch. - Site Entry | Photos, progress notes and reports entered from the site are written from the mobile app onto the same project record; the app is live on both the App Store and Google Play. - ERP Connection | We build the Logo, Netsis and SAP connection; there is no out-of-the-box module, the connection is built for each project over the REST API, OAuth2 and webhooks, and the scope is shared in writing in the discovery call. - Site Material Request | A material request coming from the field is a request linked to the site record; the item, the quantity, the date requested and the approver sit in its fields, and that the request was opened from the site is confirmed with location verification in the mobile app. ##### Frequently asked questions - How can I track construction projects in the CRM? | In Rapitek CRM you can create each project as a separate record and link the relevant clients, subcontractors and documents to the project. The project timeline and its stages move forward on the same record. - How is subcontractor management done? | You can manage subcontractors as a separate account type, track their performance and assign them to projects. Communication history and contracts are kept in a single place. - How long does setup take for construction? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your construction process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Can more than one person on the construction team use the same WhatsApp number? | On the construction side, site and office messaging is run as a team from a single number and the history stays on the project record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Consulting CRM: Proposal Replies and Man-Days | Rapitek](https://rapitek.com/en/consulting-crm) The stage and close probability are fields on the opportunity record and the weighted value comes from those two; in Rapitek CRM each visit writes a line drawing down the contracted man-days. ##### What we set up, and how - Weight each opportunity by the probability tied to its stage and read the monthly close forecast on a single screen - Keep the proposal's send date and expected reply date in fields; let proposals whose reply is overdue drop into a list and make the call from that list - Set up the 3rd, 6th and 12th month contacts after a project closes as tasks tied to the closing date - See how full each consultant is and assign the new project accordingly - Set up a shared WhatsApp inbox on a single business number and assign conversations to consultants - Weighted Pipeline | The opportunity's stage and close probability are fields on the record; the weighted value is calculated from those two fields, and the monthly close forecast is the sum of that value across open opportunities. - Proposal Reply Date | A proposal is a record linked to the opportunity; the send date and the expected reply date sit in its fields, proposals whose reply is overdue drop into a list, and the follow-up task is opened from that list. - Recurring Client Contact | The project closing date is a field on the record; the 3rd, 6th and 12th month contacts are opened as tasks tied to that date and drop into the owner's list. - Consultant Capacity Map | The projects a consultant is assigned to and the number of days build up under the person record; who is full in which week is read from the calendar and report views of those records. - Man-Day Usage Record | The number of days defined in the contract is a field on the project record; each consultant visit writes a line drawn down from that field, and when the remaining days run low a task goes to the project owner. ##### Frequently asked questions - What makes a CRM different for consulting firms? | A long sales cycle, high project value, relationship-driven selling. The CRM tracks every opportunity with its stage, keeps the proposal's reply date in a field, and opens recurring contact points as tasks. - How does proposal tracking work for consulting? | A proposal is a record sitting under the opportunity; the send date and the expected reply date are kept in fields, proposals whose reply is overdue drop into a list, and the follow-up task is opened from that list. There is no read receipt tracking whether the client opened the document or how long they looked at it, and we do not say there is. - How accurate is pipeline forecasting? | A probability is defined for each opportunity (e.g. proposal stage 30%, negotiation 70%). The weighted pipeline value is the sum of the opportunity amounts multiplied by those probabilities, and the monthly forecast is read from there. - Can I see how much of the man-days in the contract has been used? | The number of days defined in the contract is a field on the project record; each consultant visit writes a line drawn down from that field, and when the remaining days run low a task goes to the project owner. - Can more than one person use the same WhatsApp number for consulting? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Cosmetics CRM: Shelf Checks and Shade Variants | Rapitek](https://rapitek.com/en/cosmetics-crm) A point of sale is an account and every visit a task linked to it; location is verified on the task, the shelf photo and note written onto it. Shade and batch sit on the order line. ##### What we set up, and how - Plan point-of-sale visits as tasks, close them with location verification and write the shelf observation onto the same record - Keep shade, size and packaging variants on separate product records and build the dealer order from those records - Filter which product is left at which point by batch number and expiry date - Define dealer and chain store campaigns as records, and verify the points where they were applied from the visits - Point of Sale Visit | A visit is a task linked to the account; the location is verified on the task, and the shelf photo and the observation note are added to the same task. - Variant Management | Shade, size and packaging are fields on the product record; the order line is fed from that card, and which variant went where stays on the record. - Batch and Expiry Date | The lot number and the expiry date are fields on the order line; shipments whose date is approaching are filtered from that field. - Dealer Campaign | A campaign is a record; the products and the points it covers are linked to it, and whether it was applied is read from the visit tasks. ##### Frequently asked questions - Is this page for a cosmetics brand or for a beauty salon? | This page is for the side that manufactures, imports or distributes the product; the dealer network, point-of-sale visits and variant management run from here. If you work on the service side, the appointment and session flow on our beauty salon CRM and beauty centre CRM pages is closer to your business. - How are the field team's store visits verified? | A visit is a task linked to the point-of-sale account; when the field representative closes the task from their phone the location is verified and fake location reporting is detected. Because the shelf photo and the observation note are added to the same task, head office reads the outcome of the visit from the record and not from a message group. - Can I see which point is holding a product whose expiry date is approaching? | Yes. The lot number and the expiry date are fields on the order line; shipments whose date is approaching are filtered from that field, and which point of sale they went to is read from the same line. The same filter also gives which variant is left at which dealer. - Which is the best CRM software for cosmetics? | When choosing a CRM for the cosmetics industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your cosmetics process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a cosmetics CRM system cost? | In cosmetics, because the state of a point as seen by the field team is written onto the record the head office team reads, the people in the field and at head office enter the system together. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the cosmetics industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the cosmetics industry? | We start with a discovery call: we map out your cosmetics process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for cosmetics? | In cosmetics a point-of-sale visit is a task; it is closed with location verification and the shelf observation is written onto the same record. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Courier CRM: Proof of Delivery and Assignment | Rapitek](https://rapitek.com/en/courier-crm) A shipment is a record; recipient, address, attempt count and failed-delivery reason are its fields. The second attempt opens under the same record, where the proof of delivery sits too. ##### What we set up, and how - Keep every shipment on a single record with recipient, address, attempt count and failed-delivery reason fields - Take the proof of delivery from the mobile app; let the person receiving it sign on the signature screen, and let the photo and location verification be written onto the same record - Drop the shipment into the queue of an available courier in the area with the shift and the assignment rule defined at setup - Open sending companies' complaints and queries as request records and track their closure - Shipment Record | A shipment is a record; the recipient, the address, the attempt count and the failed-delivery reason are in its fields, and the second attempt is opened under the same record. - Proof of Delivery | Delivery is a task with signature and photo fields; the person receiving it signs on the signature screen in the mobile app, the location verification is written onto the record, and fake location detection is part of that verification. - Courier Shift and Assignment | A shift is a record; the assignment rule defined at setup drops the shipment into the queue of an available courier according to the area and shift fields. - Sender Account | The sending company is an account record; the agreed unit price sits in a field on the account, and complaints and queries are opened as request records linked to that account. ##### Frequently asked questions - How do we track undelivered shipments? | The failed-delivery reason and the attempt count are fields on the shipment record. The second attempt is opened as a new task under the same record; the list filtered by reason shows in which area and in which time window the returns are concentrated. - Can signature and location be kept as proof of delivery? | Yes. The person receiving it signs on the signature screen in the mobile app, the photo stays as an attachment, and the location verification at the moment of delivery is written onto the same record; the verification also covers fake location detection. The amount collected at the door also sits in a field on that record. - Where is the sending company's question "what happened to that shipment" tracked? | The sending company is an account record; the agreed unit price sits in a field on the account, and complaints and queries are opened as request records linked to that account. Which shipment the request relates to is linked on the record; its closure leaves a trace, and when the same question is asked a second time the history is on the same screen. - Which is the best CRM software for couriers? | When choosing a CRM for the courier industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your courier process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a courier CRM system cost? | On the courier side the assignment rule defined at setup drops the shipment into the queue of an available courier according to the area and shift fields; it is this courier workforce that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the courier industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the courier industry? | We start with a discovery call: we map out your courier process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for couriers? | In courier work the person receiving the delivery signs on the signature screen in the mobile app, and the location verification is written onto the same record. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Coworking Space CRM: Member Risk and Occupancy | Rapitek](https://rapitek.com/en/coworking-crm) Check-in records are dated lines under the membership record; you define which drop counts as a risk, and a member crossing the threshold falls into the risk list where the contact task opens. ##### What we set up, and how - Flag members as at risk according to the drop threshold you set yourself (for example, members whose check-ins have fallen over the last two weeks) and reach out before the cancellation - Define your hot desk day threshold (for example 20 days); let members crossing it drop into a list and open the dedicated desk suggestion task from there - Tie the hours your meeting rooms are left empty to corporate campaigns open to the outside - Produce introduction and event invitation lists from the industry and area of interest fields on the member record - Set up a shared WhatsApp inbox on a single business number that the whole team answers from - Cancellation Risk Threshold | Check-in records are dated lines under the membership record; you define which drop counts as a risk, members crossing the threshold fall into the risk list, and the contact task is opened from that list. - Upsell Threshold | The number of days a member spends at a hot desk is a field on the membership record; you set the day threshold that triggers the dedicated desk suggestion (for example 20 days), members crossing the threshold drop into a list and the suggestion task is opened. - Meeting Room Occupancy | A meeting room booking is a record with room, date and time fields. The hours left empty are read from the calendar view of those records, and the corporate campaign list to be opened up outside is built around those gaps. - Member Profile and Matching | Industry and area of interest are fields on the member record; members in the same industry are filtered on those fields and produced as a list, the event invitation is sent from that list, and the contact is written onto the member's record. - Virtual Office Mail Record | Official notices and parcels arriving for a virtual office member are mail lines linked to the member record; the arrival date, the sender and the delivery status sit in fields, informing the member is opened as a task, and it closes once the item is collected. ##### Frequently asked questions - Why does a CRM matter for coworking spaces? | In a coworking space the occupancy signal sits in operations and the membership conversation in sales; when the two do not come side by side, the cancellation is noticed after the fact. Rapitek CRM gathers check-in frequency, membership history and conversations on the same membership record; you define the risk threshold, the upsell suggestion and the empty meeting room campaign, and the system produces tasks and notifications according to those rules. - How is cancellation risk predicted? | Check-in records sit as dated lines under the membership record; you define which drop counts as a risk (for example, members whose usage has fallen by 50% over the last two weeks). Members crossing the threshold fall into the risk list; sending the satisfaction survey and the contact task are produced from that list. - How is community interaction supported? | Industry and area of interest are fields on the member record; existing members in the same industry as a new arrival are filtered on those fields and produced as a list. The introduction or the event invitation is sent from that list and the contact is written onto the member's record. There is no community notification that goes out to a member by itself; you define which list gets a message and when. - Can more than one person use the same WhatsApp number for a coworking space? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Customs CRM: Declaration Files and Missing Docs | Rapitek](https://rapitek.com/en/customs-crm) The declaration number, the GTİP code and the bonded warehouse entry date are the file's own fields; a missing document is a task, and who it was asked from and when sits on the same file. ##### What we set up, and how - Gather every shipment on a single file record with the declaration number, the GTİP code and the bonded warehouse dates, and see which stage the file is waiting at - Open a missing document as a task, record who it was requested from and on what date, and send the reminder by WhatsApp or SMS from the same screen - List the open files of importing and exporting companies under a single account, and report pending work by client - Write the per-file fee and the costs to be passed on onto the record, and produce the month-end invoicing list from the files - Customs File | Every shipment is a record; the declaration number, the GTİP code, the bonded warehouse entry date and the delivery date are the fields of that record. - Missing Document | Every document requested is a task; the document name, the person it was requested from and the date sit in its fields, and documents that do not arrive stay in the open task list. - Client Account | The importing company is an account record; the power of attorney validity date and the agreed per-file fee are kept in fields on the account. - Bonded Warehouse Period | The bonded warehouse entry date is a date field on the file record; files whose period, calculated from that date, is close to running out drop into a list and a notification goes to the person responsible. ##### Frequently asked questions - Can I track documents that have not come from the client in the CRM? | Yes. Every document requested is a separate task under the file; the name of the document, who it was requested from and the request date sit in fields, the ones that do not arrive stay in the open task list, and the reminder is sent by WhatsApp or SMS from the same screen. - Where do the declaration and bonded warehouse details sit in the CRM? | The declaration number, the GTİP code and the bonded warehouse entry date are fields on the file record; this information is not pulled automatically from customs systems — the person following the file enters it, or it is loaded by import. Once it has been entered, files whose period is approaching drop into a list based on the date field. - Where do I see the clients whose power of attorney is about to expire? | The importing company is an account record; the power of attorney validity date and the agreed per-file fee are kept in fields on that account, and powers of attorney approaching the end of their validity come out of the list on that date field. - Which is the best CRM software for customs brokerage? | When choosing a CRM for the customs industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your customs process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a customs CRM system cost? | On the customs side the notification for a file that drops into the list goes to the person responsible; the users of the system are this brokerage team. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the customs industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the customs industry? | We start with a discovery call: we map out your customs process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for customs? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Cybersecurity CRM: Authorisation and Reports | Rapitek](https://rapitek.com/en/cybersecurity-crm) The date the written authorisation was received is a field on the project record; while that field is empty, the rule defined at setup stops the record moving to the testing stage. ##### What we set up, and how - Keep the test scope, the environment and the test window dates in fields on the project record, and set a rule so the stage does not move on before the written authorisation arrives - Track report delivery and the retest date as fields, drop the ones whose deadline is approaching into a list and open a task for the person responsible - Limit access to the report and its attachments with role-based authorisation, and determine from the role definition which user can see the record - Keep monitoring and subscription renewal dates under the account, and queue the request opened on an incident notification and route it with the assignment rule defined at setup - Test Project | A test is a project record; the number of assets in scope, the environment and the start and end dates of the test window sit in its fields. - Written Authorisation | The client's written authorisation is a date field; while the field is empty, the record moving to the testing stage is blocked by the rule defined at setup. - Retest Date | Report delivery and the retest are each date fields; files whose deadline is approaching drop into a list and a task is opened for the person responsible. - Report Access | The record and its attachments are subject to role-based authorisation; which user sees the report is read from the role definition. ##### Frequently asked questions - Can the system stop a test from starting before written authorisation arrives? | The date the client's written authorisation was received is a field on the project record; while that field is empty, the rule that stops the record moving to the testing stage is defined at setup. You decide at which stage it becomes mandatory, and the record does not move on until that condition is met. - How do we avoid missing the retest period for the findings? | The report delivery date and the period given for the retest are each date fields. Files whose deadline is approaching drop into a list by date and a task is opened for the person responsible; the reminder to go to the client is also planned from the same record. - Can we limit who inside the company can see the vulnerability report? | Yes. The report is an attachment on the test project record, and the record is subject to role-based authorisation; which user sees the record and its attachments is determined by the role definition. Who changed which field and when also sits field by field in the change history. - Which is the best CRM software for cyber security? | When choosing a CRM for the cyber security industry you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your cyber security process, we migrate your data, and we train your team in Turkish. Before we built our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a cyber security CRM system cost? | In cyber security, because which user sees the report is read from the role definition, people are defined in the system with their roles. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the cyber security industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the cyber security industry? | We start with a discovery call: we map out your cyber security process, which fields and which stages are needed, together. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for cyber security? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Defense Industry CRM: RFQs and Access Control | Rapitek](https://rapitek.com/en/defense-crm) A request for quotation is an opportunity record; the deadline, the specification items and which unit will prepare the reply are its fields, and a task opens as the date approaches. ##### What we set up, and how - Track opportunities in the long procurement cycle stage by stage, and do your forecasting over those stages - Gather the communication history and notes of organisation and supply chain contacts on a single customer record - Keep the end date of the non-disclosure agreement on the organisation record and limit the user group that can see the file from the record itself - Connect a single WhatsApp business number to the team inbox, and let conversations be assigned to the person responsible by the rule you define - Measure sales performance and team productivity through reports - Request for Quotation File | A request for quotation coming from the prime contractor is an opportunity record; the deadline, the specification items requested and which unit will prepare the reply sit in its fields, and a task opens as the date approaches. - Program and Platform Field | Every job carries which program and platform it belongs to in its own field; jobs on different programs of the same organisation are separated by that field, and when the file passes to another engineer the technical correspondence stays on the same record with its attachments. - Non-Disclosure Agreement and Access | The parties to the non-disclosure agreement signed with the organisation and its end date are fields on the organisation record; which user group can see a job sits in the record's access setting, and agreements that have expired drop into a list by date. - Qualification Process | Every job that goes to the prime contractor is a record; sample submission, qualification approval and the quote are separate stages of that record, and when the stage changes its date and owner are updated on the same record. - Approved Supplier Card | Each of the sub-suppliers that make part of the work is its own record; which part family they are approved in, the expiry date of their approval certificates and the note left at the site audit are fields on that record; a supplier whose certificate has expired drops into a list by date, and which supplier is linked to the request for quotation file is read from the same record. ##### Frequently asked questions - Can we see the organisations whose non-disclosure agreement has expired? | Yes. The parties to the non-disclosure agreement and its end date are fields on the organisation record; agreements that have expired or are about to expire are gathered in a list sorted by date. Because which user group can see a job also sits in the record's access setting, permission is managed from the same place as the agreement itself. - How long does setup take for the defense industry? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your defense industry process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Will it integrate with my existing systems for the defense industry? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for the defense industry? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Dental Clinic CRM: Check-Ups and Treatment Plans | Rapitek](https://rapitek.com/en/dental-clinic-crm) The last treatment date is a field on the patient record; patients reaching six months drop into a list, and the 48, 24 and 1 hour reminders tie to the same appointment record. ##### What we set up, and how - Drop patients who reach six months from their last treatment date into a list, and tie the check-up reminder steps to that list - Track treatment plans left half-finished and send reminders for the remaining sessions - Reduce missed appointments with 48, 24 and 1 hour pre-appointment reminder steps - Keep the satisfaction score on the patient record; send a Google review link to the list of those who gave a high score - Gather correspondence with patients on a single WhatsApp business number so the whole team sees the same history - 6-Month Check-Up Reminder | The last treatment date is a field on the patient record; patients who reach six months drop into a list and the reminder is sent to that list. - Treatment Plan Tracking | A treatment plan is a record linked to the patient record; sessions that have not been completed stay open as tasks linked to the plan, and the session reminder is sent to that list. - Missed Appointment Prevention | Reminder tasks at 48, 24 and 1 hour before are tied to the appointment date; confirmation and rescheduling are written onto the same appointment record, and a patient who does not turn up stays open in the list. - Google Review Request | The post-treatment satisfaction score is a field on the patient record; those who give 4 and 5 are sent a review link, and those who give a low score an in-clinic feedback form. - Prosthetics Laboratory Dispatch Record | An impression or prosthetic job sent to the laboratory is a dispatch record linked to the patient record; the dispatch date, the laboratory name and the expected return sit in fields, and if the return is late a task goes to the person responsible for the appointment. ##### Frequently asked questions - Why does a CRM matter for dental clinics? | In the dental sector patient loyalty is critical: the six-month check-up cycle, treatment continuity and referral management. The CRM takes these out of memory and ties them to fields on the record; which patient is to be called and when is read from a list. Because the number of patients a reminder was sent to and the number who came back sit on the same records, you report its effect from your own data. - How does the 6-month reminder work? | The last treatment date is a field on the patient record; patients who reach six months are filtered on that field and drop into a list. You set a rule at setup for when and how many times the message goes to that list (for example at 6 months, 6 months 1 week, 6 months 2 weeks); when the patient books an appointment their record comes off the list and the steps stop. - How are Google reviews increased? | The post-treatment satisfaction score is a field on the patient record. A Google review link is sent to the list of those who gave 4 and 5, and an in-clinic feedback form to the list of those who gave 1 to 3; you define at setup which message goes to which score, and the send is written onto the patient record. - Can more than one person on the dental clinic team use the same WhatsApp number? | On the dental clinic side, correspondence with patients is gathered on a single business number and the whole team sees the same history. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Dental Implant Clinic CRM: Staged Treatment Plans | Rapitek](https://rapitek.com/en/dental-implant-clinic-crm) Each stage of implant treatment — extraction, placement, temporary and permanent prosthesis — is a separate appointment on the plan; instalment dates and insurance approval are fields on the card. ##### What we set up, and how - Schedule the extraction, implant placement, temporary and permanent prosthesis stages separately according to healing time - Upload panoramic X-ray, DICOM and 3D model files to the patient card and open them chairside - Run the consultation, travel, accommodation and check-up steps of a patient coming from abroad on a single roadmap - Track treatment instalments, private insurance payments and SGK approvals with their due dates over the records entered in the CRM - Open the 6-month and annual check-ups as tasks tied to the treatment end date; set the reminder as a rule together with the panoramic X-ray renewal - Multi-Stage Treatment Plan | All-on-4, All-on-6, sinus lifting and bone augmentation are each treatment plan records; every stage sits on the plan with its own appointment, X-ray and approval step, and a stage that is not completed stays open in the list. - Panoramic X-Ray and Model Archive | X-ray images and 3D model files (DICOM, JPG) are uploaded to the patient card as files; the dentist opens each file from the same record. There is no out-of-the-box module for the imaging device — files are added manually or by bulk upload. - Overseas Patient Roadmap | Consultation, travel plan, treatment, accommodation and check-up steps are tasks linked to the patient record; the patient's language and time zone are fields on the record, and reminders are produced according to those fields. - Instalment and Insurance Tracking | Treatment instalments, private insurance payments and SGK approval are lines linked to the patient record; a line that falls due drops into a list and the reminder task is opened from that list. There is no out-of-the-box module for SGK MEDULA and insurance companies — this information is entered by import file or by hand. - 6-Month and Annual Check-Up | The treatment end date is a field; the 6-month and annual check-up appointments and the panoramic X-ray renewal task are tied to that date. ##### Frequently asked questions - How are long treatment processes such as All-on-4 or All-on-6 managed? | Rapitek CRM supports multi-stage treatment plans. Every stage (extraction, implant placement, temporary prosthesis, permanent prosthesis) is a separate appointment tied to the plan; the next appointment is suggested according to the patient's healing time, and a stage that is not completed stays open in the list. - What features are there for implant patients coming from abroad? | Along with multilingual lead management (Turkish, English, German, Russian), the airport transfer, accommodation, interpreter coordination and consultation video call steps are opened as a 'travel package' task list linked to the patient record; the clinic team carries out the steps. There is no out-of-the-box module for airlines, hotels or transfer providers — booking details are written onto the record by hand. - Is there SGK and private insurance integration? | We build the connection to SGK MEDULA or to private insurance companies; there is no out-of-the-box module, and we have no product called a "compatible module" either. The connection is built for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. As long as the connection is not built, authorisation and approval details are entered by import file or by hand; the approval status, the amount paid and the patient's contribution are still kept in the CRM, and reminders for instalments falling due are produced from there. - How do post-implant check-up reminders work? | The date of the implant placement is a field; the 1st week, 1st month, 3rd month, 6th month and annual check-up tasks are opened on the card tied to that date, and the ones approaching their date drop into a list. You set a rule at setup for how many days in advance and through which channel the patient is reminded. At each check-up the patient note, the X-ray and the dentist's comment are written onto the same record. ### [Dermatology Clinic CRM: Lesion Photo Archive | Rapitek](https://rapitek.com/en/dermatology-clinic-crm) Lesion photos, pathology reports and prescription history sit in one patient record in date order; for chronic diagnoses the 1, 3 and 6-month follow-ups open in the calendar. ##### What we set up, and how - Store the lesion and rash photographs taken during examinations in date order and compare before and after - Keep chronic diagnoses such as acne, psoriasis, eczema and vitiligo in a field on the patient record; open the 1, 3 and 6-month follow-ups in the calendar as dated tasks tied to that field - Attach laboratory and pathology result reports to the patient card as files and review them together with the examination history in suspicious lesions - Keep prescription history on the patient card and run repeat prescription reminders and side effect notifications - For follow-up consultations paste the Zoom or Google Meet link you opened yourself into the link field on the appointment record, and review the photographs the patient sent in advance before the consultation - Dermatology Photo Archive | Every lesion, mole and rash photograph taken during an examination is added to the patient record with its date; before and after are read side by side on the same card. - Chronic Disease Follow-up | The acne, psoriasis, eczema and vitiligo diagnosis is a field on the patient record; the 1, 3 and 6-month follow-ups fall into the calendar as dated tasks tied to that field. - Biopsy and Pathology Result Archive | The laboratory result report is attached to the patient record as a file; in suspicious lesion diagnoses the pathology report is read next to the lesion record. We build the connection to the laboratory system ourselves; there is no out-of-the-box module — it is set up specifically for the project over REST API, OAuth2, webhooks and import/export, and where it is not built the clinic staff upload the report themselves. - Prescription and Medication Follow-up | Prescription history sits on the patient card as a list; the repeat prescription reminder is a dated task and the side effect note is written under the same record. - Telemedicine Meeting Link | There is a meeting link field on the appointment record; you open the Zoom or Google Meet meeting in your own account and paste the link into this field, and the reminder message carries this link. There is no out-of-the-box Zoom/Meet module. ##### Frequently asked questions - How is skin lesion follow-up done? | A separate record is opened for each lesion. Size, colour and border pattern are fields on that record and are updated at every examination. You define which change counts as suspicious; lesions that pass the threshold fall into a list, and you set the alert going to the dermatologist as a rule during setup. - How is acne treatment followed? | There is a standard follow-up template for acne patients. The active lesions on a face map, the products used and the treatment duration are recorded. The treatment start date is a field; the 1st, 3rd and 6th month follow-ups open as tasks tied to that date, and the ones whose date is approaching fall into a list. - Can pathology results be seen on the patient card? | Yes, once the report is attached to the patient record as a file; the doctor reviews the result on the card together with the examination history and sends the patient a message. We build the connection to the laboratory system ourselves; there is no out-of-the-box module. The connection is set up specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost in writing at the discovery meeting. Where this connection is not built, the clinic staff who receive the result from the laboratory upload the report to the patient record themselves; the person who uploaded it and the date are written into the record, and a result that has not been uploaded does not appear on the card. - How are telemedicine appointments arranged? | We build the Zoom and Google Meet connection on request; there is no out-of-the-box module. The connection is set up specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost in writing at the discovery meeting. Without this being built you use the meeting link field on the appointment record: you open the meeting in your own account, you paste the link into this field, and the reminder that goes to the patient carries this link. The patient sends the photographs 24 hours before the appointment and the doctor reviews them before the consultation. ### [Dietitian CRM: Measurement History and Packages | Rapitek](https://rapitek.com/en/dietitian-crm) 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. ##### What we set up, and how - 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 Records | Every 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 Revision | The 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 Sessions | The 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 Diary | The 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 Break | The last session date is a field; clients who pass the threshold are gathered with a filter. You set the threshold during setup. ##### 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? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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. ### [Digital Agency CRM: Scope Creep and Quotes | Rapitek](https://rapitek.com/en/digital-agency-crm) Every out-of-scope extra request is a separate record tied to the project record; its added time and cost sit in their own fields, and approval is recorded as a stage change. ##### What we set up, and how - Produce a monthly revenue projection with weighted deal value and stage-based forecasting - Keep the quote's sent date and expected reply date in a field; let quotes whose reply is overdue fall into a list and make your calls from that list - Record every extra request separately, keep the change cost in its own field and record the client's approval as a stage change - Set up annual maintenance, server renewal and update reminders as tasks tied to the date field of delivered jobs - Reply as a team from a single WhatsApp business number, assign conversations by the rule you define and monitor response times - Weighted Sales Forecast | The amount and the stage of the opportunity are fields; the monthly projection comes out of a weighted report on those two fields, and no separate spreadsheet is kept. - Quote Tracking | The quote sits under the opportunity; the sent and reply dates are held in fields, and a follow-up task is opened for quotes whose reply is overdue. - Scope Creep Control | Every extra request is a separate record tied to the project record; its amount sits in its own field, and approval is recorded as a stage change. - Post-Delivery Revenue | A finished job is a closed record but it is not deleted; the maintenance and renewal reminder is set up as a task tied to the date field of that record. - Account Authorisation Line | The permissions opened to the agency on the client's control panel, server and ad account are lines tied to the project record; which account, who was authorised and on what date sit in fields, and when the job ends, revoking the permission is opened as a task. ##### Frequently asked questions - Why does a web agency need a CRM? | Agency sales have a long cycle; the decision spreads over several weeks and regular follow-up is essential in that time. A CRM also makes it possible to create maintenance revenue from existing clients. - How does quote tracking work for digital agencies? | The quote is a record that sits under the opportunity; the sent and reply dates are held in fields, quotes whose reply is overdue fall into a list, and the follow-up task is opened from that list. - Can I see that the client opened the quote? | No — there is no read receipt tracking whether the quote PDF was opened, and we do not say there is. Follow-up is built on the sent date and expected reply date fields: quotes whose reply is overdue fall into a list, and you make the call from that list. - How is scope creep managed? | Every change request is a separate record tied to the project record; the extra cost and time sit in their own fields, the client's approval is recorded as a stage change, and project profitability stays visible while the work is still running. - Will we remember to revoke our permissions on the client's panels when the job is finished? | The permissions opened to the agency on the control panel, server and ad account are lines tied to the project record; which account, who was authorised and on what date sit in fields, and when the job closes, revoking the permission is opened as a task. - Can more than one person use the same WhatsApp number at a digital agency? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Digital Marketing Agency CRM: Campaign Budgets | Rapitek](https://rapitek.com/en/digital-marketing-agency-crm) A campaign is a record tied to the client account; budget and metrics sit in fields. No publishing task opens before the content approval round is complete; workload is read from a task report. ##### What we set up, and how - Keep every client's active campaigns, budget and performance metrics on a single screen - Track prospects through the First Meeting, Analysis, Quote and Contract stages - Produce monthly revenue and campaign performance reports per client from the platform - Track who is working on which client, the workload distribution and the delivery dates - Let the whole team reply from a single WhatsApp number and keep the correspondence with the agency - Client and Campaign Management | A campaign is a record tied to the client account; budget and metrics sit in its fields, and the same client's campaigns accumulate under the card. - Quote Pipeline | The stages (First Meeting, Analysis, Quote, Contract) are defined in the sales pipeline; every opportunity follows this pipeline and those waiting in a stage appear in the report. - Monthly Reporting | Because revenue and performance fields sit inside the records, the monthly report is taken by selecting a date range, with no manual compilation needed. - Team and Task Management | A job is a task; its owner, its client and its delivery date are in fields, and the workload distribution is read from the per-person task report. - Content Approval Round | The visual and text going live is an approval round tied to the campaign record; which round it is, who approved it and the planned publication date sit in fields, and the publishing task does not open until the approval arrives. ##### Frequently asked questions - Can we stop the publishing task from opening before the content approval arrives? | The visual and text going live is an approval round tied to the campaign record; which round it is, who approved it and the planned publication date sit in fields, and the publishing task does not open until the approval field is filled. This condition is defined during setup. - Can I see whose week is full when I hand out new work? | A job is a task; its owner, its client and its delivery date are in its fields. The workload distribution is read from the per-person task report, and when three clients' delivery dates fall into the same week, it shows in that report. - How long does setup take for a digital marketing agency? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your agency process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Will it integrate with my existing systems at a digital marketing agency? | On the digital marketing agency side, campaign budgets sit in ad panels and quotes sit in e-mail. 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 ERP 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. - Can more than one person use the same WhatsApp number at a digital marketing agency? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Driving School CRM: Lessons and Exam Tracking | Rapitek](https://rapitek.com/en/driving-school-crm) A driving lesson appointment is one record carrying the instructor, vehicle and student fields. Exam result and attendance sit on the student's record, and stalled candidates fall into a list. ##### What we set up, and how - Track the student's whole life cycle, from prospective student to active enrolment, in a single record - Keep the instructor, the vehicle and the student in the fields of the same appointment record; define the rule that blocks a second record for the same hour during setup - Track theory and practical exam results and attendance status as they happen - Report each instructor's number of students, pass rate and schedule - Send appointment reminders and exam notifications over WhatsApp - Student Record Management | From prospective student to active enrolment, the same record moves through the stages; how many candidates are waiting at which step is read from the stage report. - Driving Lesson Appointment System | The appointment is a record with instructor, vehicle and student fields. The rule that prevents a second record being opened for the same hour is defined during setup. - Exam and Attendance Tracking | The exam result and attendance status are fields on the student record; those with missing attendance are gathered in a single list. - Instructor Performance Tracking | Lesson and exam records carry an instructor field; the number of students and the pass rate come out of a breakdown report on that field. - Trainee File Documents | The medical report, the criminal record certificate and the education certificate are separate fields on the trainee record; those with missing documents are gathered in a single list, and the task to complete them is opened from that list before the exam application. ##### Frequently asked questions - Are there modules specific to a driving school? | There is no out-of-the-box driving school module; what there is, is configuration, and we do it ourselves. The driving lesson appointment is set up as a record with instructor, vehicle and student fields; the exam result and attendance status are defined as fields on the student record, and the rule that prevents a second appointment being opened for the same hour is written during setup. - Can I migrate my existing student data? | Yes, we migrate all your student data from Excel or from your existing system ourselves; the scope of the migration and its cost, if any, are worked out at the discovery meeting and shared in writing. - How long does setup take for a driving school? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your driving school process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Can I see a trainee's missing documents before the exam application? | Yes. The medical report, the criminal record certificate and the education certificate are separate fields on the trainee record; trainees whose field is empty are gathered in a single list, and the completion task is opened from that list. - Can I manage more than one branch for a driving school? | Yes, with multi-branch support you can manage all your locations from a single panel. ### [Drone Services CRM: Flight Plans and Permits | Rapitek](https://rapitek.com/en/drone-services-crm) A flight is a task record; the site coordinates, the permit expiry date and the assigned pilot are fields on the same card. Postponing changes the record's date; the previous one leaves a trace. ##### What we set up, and how - Keep the flight task in a single record together with the site coordinates, the planned date and the assigned pilot - Track the validity dates of flight permits and pilot certificates and open a warning task before they expire - Update a flight date changed by the weather on the record and notify the client from the same place - Have the team out in the field mark the flight record from the mobile app with location verification - Flight Task | A flight is a task record; the site coordinates, the planned date and the pilot are in its fields, postponing changes the date of the same record, and the previous date leaves a trace on the card. - Permit and Certificate Validity | The permit document and the pilot certificate are fields with an expiry date; those whose date is approaching fall into a list, and the warning task is opened for that list. - Field Verification | The team marks the job from the mobile app; the location verification is written into the record, and fake location detection can be switched on during setup. - Delivered Output | The orthophoto, the video and the survey report are attachments on the flight record; what was delivered to the client and the delivery date are read from the same card. ##### Frequently asked questions - How do I track flights postponed because of the weather? | A flight is a task record; postponing changes the date of the record, and the previous date stays on the card as a trace. Because the notification to the client is sent from the same record, both sides see the same day. - Does the system remind me when flight permits and pilot certificates expire? | The document expiry date is a field; records whose date is approaching fall into a list, and a warning task is opened for that list. How many days in advance each document warns is defined during setup. - Can I see from the record that the flight really was carried out in the field? | The team marks the job from the mobile app and the location verification is written into the flight record; the orthophoto, video or survey report delivered sits as an attachment on the same record. - Which is the best CRM software for drone services? | When choosing a CRM for the drone sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your flight and field process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does a drone CRM system cost? | On the drone side the flight task carries the site coordinates, the planned date and the pilot fields; it is this flight team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the drone sector? | 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 ERP 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 in the drone sector? | We start with a discovery meeting: we work out your flight and field 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 mobile CRM be used for drone work? | In drone work the team out in the field marks the flight record from the mobile app; the location verification is written into the record. 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. ### [Dry Cleaning CRM: Item Barcodes and Pick-up | Rapitek](https://rapitek.com/en/dry-cleaning-crm) Each item is tracked by its own barcode label; whose it is and which process it is waiting in sit in the record. An item not scanned at handover is marked missing and opens a task. ##### What we set up, and how - Print a unique barcode label for every item and see at once which customer it belongs to and which process it is in - Tie door-to-door pick-up and delivery requests to the courier's daily pick-up and delivery list and write the payment taken at handover into the same record - Set the threshold on the digital loyalty card yourself; let customers who pass the threshold fall into a list and tie the discount to that list as a rule - Create a purchase request when consumables such as solution, hangers and covers reach the critical level - Compare daily turnover, customer and item numbers by branch and track item transfers between branches - Item Tracking (Label + Barcode) | Every item gets a unique barcode label. Which customer it belongs to, on which date and which process it went through (dry cleaning, pressing, stain removal, tailoring) is visible in the record. The number of items is a field on the delivery record; an item not scanned at handover is marked missing and opens a task. - Door-to-Door Pick-up and Delivery Management | The customer opens a pick-up request over WhatsApp or the web; the request is tied to the courier's pick-up and delivery list for that day, and you arrange the order yourself. As the steps are completed the status moves on in the record and a message goes to the customer from the same card. The amount collected at handover and the payment method are written onto the line. - Loyalty Card and Campaigns | The loyalty card is tied to the customer record; total spend and number of items are its fields. You set the threshold: customers who pass the threshold fall into a list, and the discount and the birthday and seasonal campaign message are tied to that list as a rule. - Stock and Consumables | Stock tracking for consumables such as dry cleaning solution, stain remover, hangers, plastic covers and steam water. Opening a purchase request when the critical level is reached can be defined during setup. - Multi-Branch and Consolidated Reporting | If you have more than one branch, each branch's daily and monthly turnover, customer and item report and their comparison. Tracking of item transfers between branches. ##### Frequently asked questions - Why is dry cleaning CRM software needed? | In dry cleaning the biggest problems are mixed-up items, losses and losing customers. In the CRM every item is recorded with its own barcode; whose it is and which process it is waiting in sit in the record, and an item not scanned at handover is marked missing and opens a task. The history and favourite services are kept on the customer card, you set the loyalty card thresholds yourself, and door-to-door pick-up requests are tied to the courier list. Because visit frequency and spend accumulate on the customer card, you measure the effect of a campaign from your own data. - Is it compatible with a barcode label printer? | The label is produced in the CRM as printable output and sent to the printer defined on your computer or your network through the operating system's own printer driver; this flow is tried out together with the printer you use during setup. There is no out-of-the-box module for particular printer brands. If a connection beyond that is needed, our professional services team sets it up specifically for the project over REST API, OAuth2, webhooks and import/export, and its scope and cost are shared in writing at the discovery meeting. At handover the barcode is scanned, the item is marked as delivered and the invoice record is created from the same screen. - Is there a courier app for the door-to-door service? | Couriers use the mobile app made for field teams: the day's pick-up and delivery list, addresses, customer contact, item confirmation photo and a delivery record with location verification. The app is live on both the App Store and Google Play; the web interface also works on a 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. There is no optimisation engine that orders the route by itself — you arrange the order yourself. The amount taken at handover and the payment method are written into the record; there is no out-of-the-box module for taking payment by card or POS device, and if it is needed the connection is set up specifically for the project over REST API and webhooks. There is no live map tracking opened to the customer either; the customer is informed by the message that goes out from the record as the status changes. - Does it support multiple branches? | Yes. Each branch has its own staff, prices, stock and reports. A customer can bring an item to one branch and collect it from another; the transfer between branches is written onto the item's record as a line, and which branch the item is in is visible from the record when the barcode is scanned. The head office team manages all the branches with a consolidated report. ### [E-commerce CRM: Cart Recovery and RFM | Rapitek](https://rapitek.com/en/ecommerce-crm) Web, app and marketplace records merge on the same customer card through e-mail and phone; the last purchase date, the frequency and the amount are fields on that card. ##### What we set up, and how - Merge website, app and marketplace data into a single customer record - Let an abandoned cart fall in as a record; set as a rule how long afterwards the e-mail, SMS and push notification goes out - Measure customer value on the recency, frequency and monetary (RFM) axis - Compare the performance of marketplace, web and mobile channels side by side - Connect a single WhatsApp number to the team inbox and have conversations assigned by the rule you define - Single Customer Record | Web, app and marketplace records are merged on the same customer card through e-mail and phone; duplicate records are reduced to a single card with a merge operation. - Abandoned Cart Recovery Flow | An abandoned cart falls in as a record and opens a follow-up task; how long afterwards the e-mail and WhatsApp message goes out is set as a rule during setup. The store connection is built specifically for the project over the API. - RFM Segmentation | The last purchase date, the frequency and the amount are fields on the customer card; the segment comes out of lists filtered on these fields. - Channel Performance Analysis | The channel is a field on the order; the comparison of turnover and conversion by channel is taken from the report on that field. - Returns and Exchange File | A return request is a file tied to the order's own record; the reason, the shipping tracking number and the decision sit in fields, and the notification going to the customer and the confirmation coming from the warehouse accumulate under the same file. ##### Frequently asked questions - How do we reduce the same person's records from the site and the marketplace to a single record? | Web, app and marketplace records are merged on the same customer card through e-mail and phone; duplicate records are reduced to a single card with a merge operation, and the order history is gathered under that card. - Can a message go to a customer who abandoned their cart? | When the abandoned cart falls into the CRM as a record, a follow-up task is opened; you set as a rule during setup how long afterwards the e-mail or WhatsApp message goes out. The connection that carries the cart data from your store platform into the CRM does not come out of the box; it is built specifically for the project over REST API and webhooks, and its scope is determined at the discovery meeting. - Can we tell the customer which stage their return request is at? | The return request is a file tied to the order's record; the reason, the shipping tracking number and the decision sit in fields. Because the notification going to the customer and the confirmation coming from the warehouse accumulate under the same file, the latest status is read from one place. - How long does setup take for e-commerce? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your e-commerce process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Will it integrate with my existing systems for e-commerce? | In e-commerce, web, app and marketplace records are merged on the same customer card through e-mail and phone. 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 same applies to your store platform and your marketplace accounts. 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. - Can more than one person use the same WhatsApp number for e-commerce? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [EdTech CRM: Pilot Classes and Licences | Rapitek](https://rapitek.com/en/edtech-crm) The teacher, the administration and the IT officer are separate contact records tied to the same school record; the end of the pilot class and the licence renewal day are fields on that record. ##### What we set up, and how - Split school and institution opportunities into stages and follow which one is nearing a decision in a visual pipeline - Keep the end of the pilot class and the licence renewal day on the institution record and see the schools to call back before the term closes in a single list - Gather the meetings and notes with all the contacts at the same institution in a single customer record - Report how many opportunities are waiting at which stage and the progress per team member - Run the correspondence with institution contacts from a single business number; let the conversation history stay in the record even when staff change - School Contact Cards | The teacher, the administration and the IT officer are separate contact records tied to the same school record; which promise was given to whom sits in a note on their own contact card, and the whole situation of the school is read from the institution record. - School Year and Licence Renewal | The end of the pilot class deployment and the licence renewal day are fields on the institution record; the schools that need to be called back before the term closes are gathered in a single list by these dates. - School Support Request | A usage problem coming from a school is a request record; which school it came from and which module it concerns sit in its fields. The resolution note is written onto the request, and when the same question comes again, it is read from the records of the earlier requests. - Budget Line and Approval Step | Which budget line the school will pay from and which approval step the quote is waiting at are fields on the opportunity record; the quote, the management approval and the order are separate stages, and which institution is stuck at which step is read from a single list. - Teacher Training Session Record | The usage training given to an institution is a session tied to the institution record; the teachers who attended, the date and the trainer sit in fields, the post-session survey is tied to the same record, and which subject department has not had the training is seen from a list. ##### Frequently asked questions - Can we see what we answered before to the same usage question from a school? | Every support request is a record; which school it came from and which module it concerns sit in its fields. Because the resolution note is written onto the request, when the same question comes again the answer is read from the records of the earlier requests. - How do we see which schools we need to go back to before the pilot period ends? | The end of the pilot class deployment and the licence renewal day are fields on the institution record; the list filtered by these dates gathers in one place the schools that need to be called back before the term closes. - How long does setup take for education technology? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your sales process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Will it integrate with my existing systems in education technology? | 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. - Can more than one person on an education technology team use the same WhatsApp number? | On the education technology side, correspondence with institution contacts runs from a single business number; even when staff change, the history stays in the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Electricity Distribution CRM: Fault & Outage | Rapitek CRM](https://rapitek.com/en/electrical-crm) Requests and fault records meet under the same subscriber; class, opening time and outage duration are fields, and quality indicators come from their periodic report. ##### What we set up, and how - Run new connection, capacity increase, tariff and complaint requests from a single panel and track response times - Classify fault notifications by the rule you define, assign them to field crews and monitor resolution time - Set up the task plan for meter reading, maintenance and repair crews and measure their performance - Use the report and dashboard builder to prepare, from fields defined during setup, the service quality indicators and outage statistics that underpin your regulatory reporting, and export them as Excel, CSV or PDF; no ready-made report template in the official filing format is provided - Subscriber Request Management | A request is opened as a record; its type and opening time are among its fields, and the response time is calculated from those dates and appears in the report. - Fault and Outage Management | A fault record carries a class field; the assignment rule is bound to that field during setup, and the resolution time follows from the record's dates. - Field Operations Coordination | Meter reading, maintenance and repair jobs are tasks assigned to a person; how much work each crew closed is read from the task report. - Regulatory Reporting | Outage duration and customer count are fields defined on the fault record during setup; the quality indicators that underpin your regulatory reporting are produced from the periodic report of those fields. No ready-made report template in the official filing format is provided. ##### Frequently asked questions - Can subscriber management be done for electricity distribution companies? | Yes. Subscriber records, tariff management and request tracking are held in a structure that does not require keeping a separate table as the number of subscribers grows. - Is there integration with the outage notification system? | We build the connection to SCADA and outage management systems ourselves; there is no out-of-the-box module. The connection is set up specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing during the discovery call. Until that connection is built, outage information is entered with an import file or by hand; subscriber requests, fault records, field tasks and outage duration fields are still held in the CRM, and quality indicators are produced from those records. - Can I see an overdue subscriber request in time? | The request's type and opening time are fields on the record; the response time is calculated from those dates, and requests that pass the threshold collect in their own list. The threshold is defined during setup. - Which is the best CRM software for electricity distribution? | When choosing a CRM for the electricity distribution sector, you should look at sector-specific workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up yourself, we do: we configure the fields, stages and reports around your distribution process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does an electricity distribution CRM system cost? | In electricity distribution, meter reading, maintenance and repair are tasks assigned to a person; the whole field crew is in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together during the discovery call and shared in writing. Rapi AI credit and ERP integration are separately priced items. - How does the move to a CRM system work in the electricity distribution sector? | We start with a discovery call: we work out your distribution process together, and which fields and which stages are needed. After that call we give you a date, not a range. We migrate your data, and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for electricity distribution? | Yes — the electricity distribution crew in the field can update the meter reading, maintenance and repair tasks assigned to them from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you wrote is kept on the device for 24 hours. ### [Electronics CRM: Dealer Prices and Warranty | Rapitek](https://rapitek.com/en/electronics-crm) Dealers and distributors are account records; the price list they are tied to is a field on the account. A sold device is a record with its own serial number and the warranty dates are its fields. ##### What we set up, and how - Keep the dealer, the distributor and the corporate buyer in separate accounts and tie each one to its own price list - Record the device sold with its serial number; follow the warranty start and end from the device record - Run faulty product return and service requests stage by stage on the record and see recurring faults - Keep the status of discontinued models and replacement products on the product record and prevent an old model being selected on a quote - Channel and Price List | The dealer and the distributor are each an account record; the price list they are tied to is a field on the account, and the quote line takes its price from that list. - Serial Number and Warranty | A device sold is a record with its own serial number; the warranty start and end dates are fields on that record, and its owner is tied to the account. - Fault and Return Process | A fault report is a request record; because it is tied to the device record, how many times the same device has come in is read from the history of the card. - Product Range Status | Active, discontinued and replacement product are values of the status field on the same product record; which products can be selected on a quote is tied to that field. ##### Frequently asked questions - Can I keep the dealer price and the corporate buyer price separate in the same system? | Yes. Every account is tied to a price list and the quote line takes its price from the list the account is tied to; the lists, and who can see which one, are defined during setup. - Can I track the warranty through the serial number? | Yes. A device sold is a separate record with its serial number; the warranty dates sit on that record, and when a fault report comes in, the device's sales and service history is seen from the same card. - Can we prevent a discontinued model being selected on a quote? | Active, discontinued and replacement product are values of the status field on the same product record; which products can be selected on a quote is tied to that field, and the condition is defined during setup. - Which is the best CRM software for electronics? | When choosing a CRM for the electronics sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your electronics sales process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does an electronics CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the electronics sector? | 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 ERP 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 in the electronics sector? | We start with a discovery meeting: we work out your electronics sales 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 mobile CRM be used for electronics? | 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. ### [Elevator CRM: Maintenance and Fault Requests | Rapitek](https://rapitek.com/en/elevator-crm) Every elevator car is a separate record: the building, the capacity and the contract end date are its fields. Maintenance tasks, fault requests and annual inspections accumulate under the same card. ##### What we set up, and how - Keep every elevator as a separate record; let the building, the capacity, the year of installation and the contract status sit on its card - Tie monthly maintenance visits to a periodic task and let the technician close the form from the mobile app with location verification - Turn fault calls into request records and read from the history which elevator they recur on - Write the non-conformities found at the annual inspection and the re-inspection date into the record, and let the task fall in before the time runs out - Elevator Asset Record | Every car is a separate record; the building, the capacity, the year of installation and the contract status are its fields, and its history accumulates on that card. - Periodic Maintenance Task | Maintenance is a task; the date and the technician are its fields, the field team closes it from the mobile app and the location verification is written into the record. - Fault Request | A fault call is a request record; it falls into the queue, the assignment rule defined during setup routes it to the technician in that area, and its closure stays in the elevator's history. - Annual Inspection and Non-Conformity | The inspection result and the label issued are fields on the elevator record; the task tied to the re-inspection date falls into the list before the time runs out. ##### Frequently asked questions - Can I see in advance which buildings' maintenance contracts are about to end? | Yes. The contract end date is a field on the elevator record; a task tied to the time left before it ends falls into the list, and you go to the renewal meeting with that building's maintenance and fault history. - Can I verify that the technician really carried out the maintenance at the building? | When the maintenance task is closed from the mobile app, location verification is carried out and fake location reporting is detected; the building manager also signs on the signature screen in the same app. - How do I track that a non-conformity found at the annual inspection has been closed? | The inspection result and the label issued are fields on the elevator record; the task tied to the re-inspection date falls into the list before the time runs out, and the closure of the non-conformity stays in the history of the same car. - Which is the best CRM software for the elevator sector? | When choosing a CRM for the elevator sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your process in the elevator sector, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does an elevator CRM system cost? | On the elevator side the maintenance task carries the date and technician fields and is closed by the field team; it is this crew that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the elevator sector? | 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 ERP 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 in the elevator sector? | We start with a discovery meeting: we work out your process in the elevator sector, 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 mobile CRM be used in the elevator sector? | In the elevator sector periodic maintenance is a task; the field team closes it from the mobile app and the location verification is written into the record. 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. ### [Energy CRM: Plant Maintenance and Field Records | Rapitek](https://rapitek.com/en/energy-crm) A record entered from the field is written into the same database at head office; the plant is a record, and periodic maintenance recurs through a task tied to its date field. ##### What we set up, and how - Gather the record entered by the field team in the same database at head office, with no separate transfer step - Track plants, projects and periodic maintenance calendars in a single list - Let technicians enter updates, photos and reports from the mobile app - Follow maintenance history, fault records and the periodic maintenance calendar with tables and summary reports; periodic maintenance recurs by itself through a task tied to the date field - Turn a single WhatsApp number into a team inbox and have conversations assigned by the rule you define - Field-to-Head-Office Flow | A record entered from the field is written directly into the same database at head office; because there is no intermediate file and no manual transfer, data is not lost on the way. - Project and Plant Tracking | The plant is a record; projects and maintenance jobs are tied to it, and periodic maintenance recurs through a task tied to its date field. - Mobile Field Use | The technician enters the update, the photo and the note into the same record from a phone; the app is live on both the App Store and Google Play, and the web interface works on tablet and phone. - Reports and Dashboards | Because measurement and maintenance data sit in record fields, deviations show up in a date-range report and on a dashboard; the thresholds are set by your own measure. - Connection Point and Site Survey Record | The facility's connection point, its current consumption and the obstacles on site are fields on the site survey record; that the surveying team is on site is confirmed by location verification in the mobile app, and the quote lines are produced from these fields. ##### Frequently asked questions - How does field-to-head-office integration work in the energy sector? | We build the connection to external systems such as SCADA, meter reading systems and other measurement software ourselves; there is no out-of-the-box module. Such a connection is set up specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing at the discovery meeting. The field-to-head-office flow, however, is not an external system matter: your field team enters the record from Rapitek CRM's own mobile app and that record is written into the same database at head office, with no separate transfer step in between. As long as the connection to external systems is not built, the measurement values there are entered with an import file or by hand; the plant, the maintenance date and the fault record are still kept in their own fields in the CRM and the reminders are produced from there. - Is it suitable for renewable energy projects? | Yes, you can track all your energy projects, including solar and wind power plants. You can create per-plant performance analyses and maintenance calendars. - How long does setup take for energy? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your energy process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Can more than one person on an energy team use the same WhatsApp number? | On the energy side, correspondence between the field and head office is gathered in the team inbox and conversations are assigned by rule. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits. ### [Engineering CRM: Man-Hours and Win Rate | Rapitek](https://rapitek.com/en/engineering-crm) The task time written against quote preparation accumulates on the opportunity record; reported together with the quote's outcome field, the hour cost of lost quotes comes out separately. ##### What we set up, and how - Accumulate the engineer hours spent on quote preparation on the opportunity record and measure how many orders each customer gives against how many quotes - Keep the compliance answers given to specification clauses and the assumptions on the quote record and compare them between revisions - Follow the hours spent on a fixed-price project side by side with the contract budget and set a warning for projects nearing a budget overrun - Keep warranty end and maintenance contract renewal dates on the project record and gather those that are due in a list - Quote File | Every request for a quote is an opportunity record; the specification attachment, the assumptions and the compliance answers sit on the same card, and the revisions are lined up in the record history. - Man-Hour Record | The time spent is written against the task; because tasks are tied to the opportunity and to the project, the quote cost and the project cost are added up from the same place. - Win Rate | The outcome of the quote is a field on the opportunity record; how many quotes were given per customer and how many of them were won is reported from that field. - Maintenance Contract Renewal | The warranty and contract end date is a field on the project record; those whose date is approaching fall into a list and are opened as a new opportunity. ##### Frequently asked questions - Can I see how many engineer hours we spent on quotes we did not win? | Yes. The time written against the tasks in quote preparation accumulates on the opportunity record; when it is reported together with the quote's outcome field, the hour cost of the lost quotes comes out separately. - Can I notice a budget overrun on a fixed-price project before the work is finished? | Yes. The contract budget is a field on the project record; when the total hours coming from the tasks approach that field, the project is flagged in the list and a notification goes to the person responsible. - Who gives the reminder for warranty and maintenance contract renewal? | The warranty and contract end date is a field on the project record; those whose date is approaching fall into a list and are opened as a new opportunity. Because the project's history sits on the same record, the renewal meeting does not start from scratch. - Which is the best CRM software for engineering? | When choosing a CRM for the engineering sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your engineering process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does an engineering CRM system cost? | On the engineering side the work of more than one engineer goes into a single quote file; it is this office team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the engineering sector? | 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 ERP 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 in the engineering sector? | We start with a discovery meeting: we work out your engineering 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 mobile CRM be used for engineering? | 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. ### [Enterprise Banking CRM: Limits and Collateral | Rapitek](https://rapitek.com/en/enterprise-banking-crm) A company is an account record; its subsidiaries hang on the same tree, and limit allocation end and collateral type are its fields. Renewals coming due fall into a list from the date field. ##### What we set up, and how - Tie the parent company and its subsidiaries in a parent-child account relationship and see the group's total relationship with the bank in a single list - Keep limit allocation end and collateral renewal dates as fields and tie renewals coming due to a task - Write the company visit, the person met and the product discussed into the visit record; let the history stay with the organisation when a portfolio is handed over - Mark products such as cash management, foreign trade and payroll in an account field and open a contact task for companies missing a product - Group and Subsidiary Structure | A company is an account record; the parent company and its subsidiaries are tied together in a parent-child account relationship, and the group total is read from the report on that tree. - Relationship Manager Assignment | There is no built-in relationship manager field; the manager is held in the account's owner field. The assignment rule defined during setup drops a new company to the relevant manager by segment and region; on handover the owner is changed one by one or on the bulk reassignment screen, and the visit and meeting history stays under the account. - Limit and Collateral Calendar | The allocation end and the collateral type are fields on the account; dates coming due fall into a list, and missing documents are tracked as a request record. - Product Ownership and Visit Record | The products owned are a field on the account; a company visit is a task, and the person met and the product discussed are written into the same record. ##### Frequently asked questions - How do we link different companies of the same holding in the CRM? | The parent company and its subsidiaries are tied together in a parent-child account relationship; each company keeps its own record, and the group total and group-level product ownership are reported from that tree. Because the owner field sits on the company's own account record, the relationship manager can be assigned separately per company. - Does the system remind me about limit allocation and collateral renewals? | The allocation end date and the collateral type are fields on the account. Dates coming due fall into a list according to the day threshold you define, and the renewal task is opened for the owner of the account; missing documents are tracked as a separate request record. - When the relationship manager changes, do past meetings stay with the organisation? | Yes. The owner of the account is a field; on handover only that field changes, and the visit and meeting notes go on sitting under the account. Because the products owned are also marked in a field on the account, the new manager reads the company's total relationship with the bank from the same record on day one. - Which is the best CRM software for enterprise banking? | When choosing a CRM for the enterprise banking sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your corporate banking process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does an enterprise banking CRM system cost? | On the enterprise banking side the owner of the account is a field; the assignment rule defined during setup drops a new company to the relevant manager by segment and region, and it is this portfolio team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the enterprise banking sector? | 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 ERP 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 in the enterprise banking sector? | We start with a discovery meeting: we work out your corporate banking 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 mobile CRM be used for enterprise banking? | 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. ### [Cooperative CRM: Dues and General Assembly | Rapitek](https://rapitek.com/en/enterprise-cooperative-crm) A member is a person record; share count, dues lines and custom transfer records sit on one card. Who the general assembly notice reached and who attended by proxy is read from the event record. ##### What we set up, and how - Keep member records on a single card together with the share information, the payment history and the communication consent - Process dues and instalment movements per member and see overdue payments in a single list - Send the general assembly notice to members by SMS and WhatsApp and follow attendance and proxy status on the same record - Record membership transfers together with their date and read from the history who held the share in which period - Member Record | A member is a person record; the number of shares, the membership status and the date of joining are its fields, and the payment lines accumulate under the card. - Share and Dues Movement | Accrual and payment are lines tied to the member record; the balance is calculated from those lines and overdue ones fall into a list. - General Assembly | The general assembly is an event record; the sending of the notice, attendance and proxy status are held in fields tied to it. - Membership Transfer | The transfer record and its transfer date, transferring member and receiving member fields do not come ready-made; they are built with custom fields defined during setup. The record is tied to the cards of the transferring and the receiving member, and the history of the share is read from these records. ##### Frequently asked questions - How are membership transfers and share history kept in the CRM? | The transfer record and its transfer date, transferring member and receiving member fields do not come ready-made in the product; they are built with custom fields and flows defined during setup. In that setup a transfer is a dated record linking the transferring and the receiving member; the number of shares on the member card is updated with that record. Who held the share in which period is read afterwards from the list of transfer records, and you are not left dependent on the former board's folder. - Can the general assembly notice and the attendance list be prepared? | The general assembly is opened as an event record; the notice is sent to the member list over SMS and WhatsApp, and who the sending reached stays in the record. Because attendance and proxy status are marked on the same record, the attendance list is formed during the meeting. - Can I see overdue dues per member in a single list? | Yes. Accrual and payment are lines tied to the member record; the balance is calculated from those lines and overdue amounts fall into a single list. When you open a member's card, their share, payment history and communication consent sit on the same screen. - Which is the best CRM software for cooperatives? | When choosing a CRM for the cooperative sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your cooperative process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does a cooperative CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the cooperative sector? | In a cooperative, payment movements are entered by hand or by import; a connection to the bank side is built if it is requested. 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 ERP 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 in the cooperative sector? | We start with a discovery meeting: we work out your cooperative 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 mobile CRM be used for a cooperative? | 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. ### [Enterprise Manufacturing CRM: Plants and Samples | Rapitek](https://rapitek.com/en/enterprise-manufacturing-crm) The plant, channel and price list are fields on the account record; a quote line's unit price is not typed by hand but comes from these fields. Sample and framework contract have their own records. ##### What we set up, and how - Define dealer, distributor and direct corporate buyer as separate channels and tie each channel to its own price list - Gather the requests of several plants in a single pool and track from the record which job is tied to which plant - Run the sample request through its own stages; keep the approval or the reason for rejection on the customer record - Keep the annual commitment and the end date of framework contracts as fields and tie renewals coming due to a task - Multi-Channel Customer Structure | Dealer, distributor and direct buyer are different channel values of the same account object; the price list is tied to that field and comes onto the quote from there. - Multi-Plant Request Distribution | An incoming request is a record; the plant field and the assignment rule defined during setup drop the request to the team of the relevant plant, and the jobs waiting in the queue are read from a list. - Sample and Approval Process | A sample request is a record with its own stages; the dispatch date, the result and the reason for rejection are its fields, and the history stays on the customer card. - Framework Contract Tracking | A contract is a record tied to the account; the annual commitment, the price validity and the end date are fields, and endings coming due fall into a list. ##### Frequently asked questions - We sell the same product to the dealer and to a direct buyer at different prices — how is this set up in the CRM? | The channel is a field on the account record and a separate price list is tied to each channel. The unit price on the quote line comes from the list according to the customer's channel; deviation from the list is tied to a permission, and discount approval is defined as a separate step. - We have more than one production plant; can we separate requests by plant? | Yes. The plant is a field on request and opportunity records; the assignment rule defined during setup drops an incoming request into the queue of the relevant team by plant and product group. Reports are taken separately per plant, and the head office total is read from the same records. - Can I be notified when the end date of a framework contract approaches? | Yes. A contract is a record tied to the account; the annual commitment, the price validity and the end date are its fields. Endings coming due fall into a list from the date field and the renewal task is opened for the owner of the account; how much of the commitment has been fulfilled is read from the same record. - Which is the best CRM software for enterprise manufacturing? | When choosing a CRM for the enterprise manufacturing sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your production process, we migrate your data, and we train your team in Turkish ourselves. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce period; we carry out the setup with that experience. - How much does an enterprise manufacturing CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the enterprise manufacturing sector? | 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 ERP 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 in the enterprise manufacturing sector? | We start with a discovery meeting: we work out your production 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 mobile CRM be used for enterprise manufacturing? | 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. ### [Event Management CRM: Date Options and Site Surveys | Rapitek](https://rapitek.com/en/event-management-crm) The requested event day, the option expiry date and the scope discussed are fields on the same record; sponsorship packages and guest confirmations are rows linked to that record. ##### What we set up, and how - Track the brief, proposal, date confirmation and contract stages in a visual flow - Keep sponsorship packages as line items and see in one list who is late with logos and materials - Plan the venue survey as a task and record measurements and constraints on site, with arrival shown by location verification - Report which type of enquiry was won and at which stage the others were lost - Handle incoming enquiries as a team from a single business number, with conversations assigned by the rule you define - Site Survey Visit | The venue survey is a task closed from the mobile app; the visit date, the measurements taken and constraints such as the goods lift sit in the same task, and the team's arrival on site is recorded with location verification. - Date Option Record | Every enquiry is a record; the requested event day, the date the option expires and the scope discussed sit in its fields; when the date is confirmed the same record moves to the contract stage. - Sponsorship Package Line | The event's sponsorship packages are line items linked to the record; which brand took which package, the stand area and the logo delivery day sit in the line's fields, and sponsors whose material has not arrived are gathered into a single list. - Guest List and Attendance Confirmation | The event's guests are contact rows linked to the record; the date the invitation was sent, the confirmation received and the attendance scanned at the door sit in the row's own fields, and the post-event survey is sent to the same list. - Supplier Engagement Record | Sound, lighting, stage and catering suppliers are engagements linked to the event record; the site entry time, the set-up duration and the person responsible sit in fields, and the rehearsal and the strike are each separate tasks. ##### Frequently asked questions - Can we be notified before the date option we granted expires? | The date the option expires is a field on the enquiry record; records whose date is approaching drop into a list, and the contact task is opened from that list. How many days in advance it warns you is defined during setup. - Can we see sponsors whose material has not arrived in a single list? | Sponsorship packages are line items linked to the event record; the logo delivery day is a field on the line, and sponsors whose date has passed without material arriving are gathered into a single list based on that field. - How long does setup take for Event Management? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your event process requires becomes clear in that call. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same call and shared with you in writing. - Does Event Management integrate with my existing systems? | 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 access and field structure on the other side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - Can more than one person use the same WhatsApp number for Event Management? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Eye Center CRM: Refraction and LASIK Tracking | Rapitek](https://rapitek.com/en/eye-center-crm) Sphere, cylinder and axis for each eye are written to the same patient card at every visit; the dioptre's direction over the years is read from those rows. Lens renewal dates sit on the same card. ##### What we set up, and how - Record sphere, cylinder and axis for the right and left eye at every examination and track the change over the years on a chart - List LASIK candidates with their pre-assessment result based on corneal thickness, pupil width and the dry eye test - Run LASIK, PRK, LASEK, cataract and implantation processes in the same flow, from pre-preparation through to post-operative care - Track the lens brand, diameter, base curve and renewal date on the patient card, and drop those whose renewal date is approaching into the call list - Plan the post-operative day 1, week 1, month 1, month 3 and year 1 check-ups as tasks tied to the surgery date - Refraction History | The dioptre, cylinder and axis values for the right and left eye are dated rows written to the patient record at every examination; because the rows sit on the same card, the rate of change is read from a chart. - LASIK Pre-Assessment | Corneal thickness, pupil width and the dry eye test are fields on the patient record; the eligibility result is written from those fields according to the rule defined during setup, and eligible candidates come out of that field's list. - Surgery Process | LASIK, PRK, LASEK, cataract and implantation are each a surgery record; pre-preparation, the day before, the day of surgery and the steps that follow are tasks tied to that record's date, and a step that is not completed stays open on the list. - Contact Lens and Spectacle Prescription | The lens brand, diameter, base curve and renewal date are fields on the patient record; patients whose renewal date is approaching are filtered by that field and drop into the call list. A spectacle order is a separate row linked to the same card; which optician the patient was referred to sits in its field. - Post-Operative Check-Up Schedule | The day 1, week 1, month 1, month 3 and year 1 check-ups are tasks tied to the surgery date; the steps are defined during setup according to your own protocol, and at every check-up visual acuity is written to the same patient record. ##### Frequently asked questions - How is LASIK eligibility assessed in the CRM? | Corneal thickness, pupil width, dioptre and the dry eye test are fields on the patient record; the eligibility result is calculated from those fields according to the rule defined during setup and marked as 'eligible', 'conditionally eligible' or 'not eligible', and the physician makes the final decision. - How are refraction values tracked? | At every examination the sphere, cylinder, axis and near addition values for the right and left eye are written to the patient record as dated rows. Because the rows sit on the same card, the change in dioptre is tracked on a chart over the years. - Is there contact lens sales and follow-up? | Yes. The lens brand in use, its measurements and the renewal date are fields on the patient record; patients whose renewal date is approaching are filtered by that field and drop into the call list. If you want the reminder message to go out based on that date, you tie it to a rule during setup. Lens stock counts can be kept on the product record. - How does the post-LASIK schedule work? | The check-ups 1 day, 1 week, 1 month, 3 months and 1 year after the day of surgery are opened as tasks tied to the surgery date; you define the steps during setup according to your own protocol. At every check-up visual acuity and the state of recovery are written to the same patient record. ### [Facility Management CRM: Charges & Maintenance | Rapitek](https://rapitek.com/en/facility-management-crm) A unit is a record; service-charge lines sit under it period by period, an overdue line drops into a list, and the resident's fault report links to that same unit. ##### What we set up, and how - Create service-charge accruals unit by unit; let overdue lines drop into a list and tie the late-payment reminder to that list with a rule - Receive residents' faults, complaints and suggestions digitally and follow the resolution through until it is closed - Set up the periodic maintenance calendar and manage technical staff assignments job by job - Produce monthly and annual income-expense reports and share them transparently with residents - Service Charge Management | A unit is a record; service-charge lines are kept under it period by period, and an overdue line drops into a list. - Resident Request Management | A request is opened as a record and linked to the unit; it stays in the list until it is closed, the resolution time comes out of the record dates, and earlier requests from the same unit are listed under the card. - Maintenance and Repair Planning | Periodic maintenance is a recurring task tied to a date field; the technical staff assignment sits on that same task. - Income and Expense Reporting | Because income and expense lines sit inside the records, monthly and annual reports are taken by selecting a period, and the same output is shared with residents. ##### Frequently asked questions - Can residents pay their service charges online? | Payment records are matched with the unit and the resident record; transactions arrive either through an import or through a connection built for the specific project over the API. We build the connection to the bank side ourselves; there is no out-of-the-box module. Payment statuses are updated either way. - How is a resident reminded about an overdue service charge? | Service-charge lines are kept under the unit record period by period, and each line's due date is a field; the overdue ones drop into a list. During setup you tie to a rule how many days after the due date the reminder message goes out and through which channel; the send is recorded on the unit record. - Can we manage more than one residential complex or block from the same panel? | Yes, you can manage different complexes and blocks from a single CRM panel and report separately for each of them. - Can we see that the same fault has been reported a second time? | Yes. A request is a record and is linked to the unit; earlier requests opened from the same unit are listed with their dates under the card. Because an open request stays in the list until it is closed, the second report sits on top of the first; requests opened under the same subject heading are also counted in a single list. - Which is the best CRM software for facility management? | When choosing a CRM for the facility management sector, you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your facility management process, we migrate your data, and we deliver the training to your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a facility management CRM system cost? | In facility management, the technical staff assignment sits on the periodic maintenance task; that team is who uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the facility management sector? | In facility management, payment transactions are matched to unit records; transactions are entered by hand or through an import. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built for the specific project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and cost in the discovery call and share them in writing. - How does the move to a CRM system work in the facility management sector? | We start with a discovery call: we work out your facility management process together, along with which fields and which stages are needed. After the call, we give you a date, not a range. We migrate your data, and we deliver the training to your team in Turkish. On our support line there is no call centre. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for facility management? | In facility management, periodic maintenance is a recurring task tied to a date field; the technical staff member assigned to it sees that task in the field from a phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is held on the device for 24 hours. ### [Farming CRM: Harvest Commitments and Parcel Records | Rapitek](https://rapitek.com/en/farming-crm) A buyer is an account record; the quantity, price and delivery period discussed sit on the record linked to it. In Rapitek CRM commitments whose period is approaching drop into a list. ##### What we set up, and how - Keep buyers on an account record and write down the quantity, price and delivery period discussed before the harvest - Link the parcel and the crop variety to the record and trace which field's produce went where - Define the seasonal crew's shifts and take field check-in from the mobile app with location verification - Send delivery and dispatch information to the buyer by SMS or WhatsApp from the same record - Buyer Account | The broker, the supermarket and the wholesaler are each an account record; the agreed price and quantity sit in the account's fields, and deliveries accumulate under the card. - Harvest Period Commitment | The delivery period is the record's date field; commitments whose period is approaching drop into a list, and the preparation task is opened from that list. - Parcel and Crop | The parcel and the crop variety are fields on the record; which field's produce went to which buyer is read from the report on those fields. - Seasonal Crew Shift | Shifts and working hours are defined in the system; field check-in is taken from the mobile app, the location is verified and mock location detection is active. ##### Frequently asked questions - How do we track the quantities discussed with buyers before the harvest? | Every buyer is an account record; the quantity, price and delivery period discussed are written to the record linked to that account. As the period approaches the commitments drop into a list, and the total promised is compared against the crop in hand in the same report. - Can we record which parcel the seasonal crew worked on? | Yes. Shifts and working hours are defined, field check-in is done from the mobile app, and mock location detection works through location verification; at the end of the day which crew was on which parcel is read from the record. - Can I trace which buyer received the produce from which field? | The parcel and the crop variety are fields on the record; because the delivery is linked to that record, which field's produce went to which buyer is read from the report on those fields. - Which is the best CRM software for farming? | When choosing a CRM for the farming sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your farming process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a farming CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the farming sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the farming sector? | We start with a discovery call: together we work out your farming process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for farming? | On a farm the seasonal crew's field check-in is taken from the mobile app with location verification. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Fashion CRM: Season Calendar and Channel Split | Rapitek](https://rapitek.com/en/fashion-crm) A season is a record; the showing, order-taking and delivery dates are its fields. A return record carries a style and a channel field, and the breakdown is read from those two. ##### What we set up, and how - Set the collection season up with calendar steps, so that a task drops to the person responsible as the showing, order-taking and delivery dates approach - Send the lookbook and collection showing to the buyer from the shared inbox and read the WhatsApp and SMS correspondence on the same card - Keep store and online channels separate on the account record and see which channel a style is working in during the season - Total return records by style and channel field and base the next collection's decisions on that difference - Season Calendar | Every collection season is a record; the showing, order-taking and delivery dates are its fields, and a step whose date is approaching drops into the task list of the person responsible. - Collection Showing Despatch | The lookbook link that goes to the buyer goes out from the shared inbox; the WhatsApp and SMS correspondence sits in the same flow on the buyer's card. - Channel Separation | Store and online sales are separated by the channel field on the account record; the same style's sales in the two channels are totalled separately according to that field. - Return Difference by Style | A return record carries a style and a channel field; which style comes back more often through the online channel is read from the breakdown of those two fields. ##### Frequently asked questions - Can I track the showing and delivery dates of a collection season from the system? | Yes. A season is a record; the showing, order-taking and delivery dates are its fields, and a step whose date is approaching drops into the task list of the person responsible. - Can I see the return difference between the store and the online channel for the same style? | Yes. A return record carries a style and a channel field; the breakdown of the two fields lists which channel a style comes back from more often. - Where do we see which showing went to a buyer and when? | The lookbook link that goes to the buyer goes out from the shared inbox; the WhatsApp and SMS correspondence sits in the same flow on the buyer's card. Who was sent what and when is read on a single screen together with the season record's dates. - Which is the best CRM software for fashion? | When choosing a CRM for the fashion sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your fashion process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a fashion CRM system cost? | On the fashion side, a step in the season calendar whose date is approaching drops into the task list of the person responsible; it is that team who uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the fashion sector? | On the fashion side, store and online sales are separated by the channel field on the account record, and the same style's sales are totalled channel by channel. 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the fashion sector? | We start with a discovery call: together we work out your fashion process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for fashion? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phones. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Finance CRM: Loan Applications and Missing Documents | Rapitek](https://rapitek.com/en/finance-crm) The application moves through its own stages; the documents requested are rows linked to it, and the file does not move to the next approval step until the missing ones are closed. ##### What we set up, and how - Bring each customer's financial profile, product holdings and transaction history together on a single screen - Run the loan application through its stages and block the move to the next step until the missing document line is closed, with a rule defined during setup - Use the report and dashboard builder to prepare the tables that underpin your BDDK and SPK reporting and export them as Excel, CSV or PDF; no ready-made BDDK/SPK report template in the official filing format is provided - Drop cross-sell and upsell opportunities into a list based on the products-held field - Connect a single WhatsApp number to the team inbox and have conversations assigned according to the rule you define - Suitability Form Validity Record | The suitability form the customer fills in is a form linked to the customer record; the answers, the date it was completed and the validity period sit in fields, and before the period expires a renewal task drops to the portfolio manager. - Application and Collection Tracking | The application moves through its own stages; the approval step and who will approve it are tied to permissions during setup, and collection lines are kept under the record. - Compliance and Reporting | The fields you specify for your filings are defined during setup and made mandatory on the records; periodic listings are taken from the reports. No ready-made report template in the official filing format is provided. Institutional connections are built specifically for the project; there is no out-of-the-box module. - Cross-Sell Opportunities | The products held are a field; customers missing a product are gathered in a list filtered by that field and a contact task is opened. - Missing Document Line on a File | The documents requested for an application are rows linked to the application record; which document is missing, who it was requested from and the date it arrived sit in fields, and the file does not move to the next approval step until the missing ones are closed. ##### Frequently asked questions - Is financial data secure? | Each customer's data is kept in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256, two-step verification secrets are encrypted at rest, and access is limited by role-based permissions. - Can regulatory reports be produced? | With the report and dashboard builder you can prepare the tables that underpin your BDDK and SPK reporting from the data in the system yourself, and export them as Excel, CSV or PDF; you can also tie compliance tracking to your records with custom fields, validation rules and approval processes. No ready-made BDDK/SPK report template in the official filing format is provided. - How do the approval steps of a loan application work? | The application moves through its own stages; who approves which step is tied to permissions during setup. The documents requested are rows linked to the application record, and the file's move to the next step until the missing line is closed is blocked by a rule defined during setup. There is no engine that runs the steps by itself; you define the rule, and the system makes what is missing and what is late visible. - Does it integrate with existing banking systems? | We build the connection to core banking systems and ERP software ourselves; there is no out-of-the-box module. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared with you in writing in the discovery call. As long as the connection is not built, customer, product holding and collection data are entered from an import file or by hand; the application stages, missing document lines and suitability form validity period are still kept in the CRM and the reminders are produced from there. - Can more than one person use the same WhatsApp number for Finance? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Fintech CRM: Integration Process and Volume | Rapitek](https://rapitek.com/en/fintech-crm) Integration is a record linked to the account with its own stages; the test environment, key handover and go-live are stages, and a customer who is waiting shows up on the list. ##### What we set up, and how - Track the enterprise customer's integration process through its own stages and see which step it is waiting at on a single list - Attach the signed version of contracts and privacy notices to the customer record - Accumulate the go-live date and the periodic transaction volume that follows it under the same account - Record applications coming through business and solution partners together with their source and run commission tracking - Integration Process | Integration is a record linked to the account with its own stages; the test environment, key handover and go-live are each a stage, and the person responsible for each stage is a field. - Document and Signature | The contract and the privacy notice are attachments on the customer record; the signature date sits in a field, and accounts with an unsigned file drop into a list. - Volume and Revenue Tracking | The go-live date is a field; periodic volume lines accumulate under the account and the customer-by-customer trend is read from the report. - Partner Channel | A partner is an account record; the applications they bring in point to that account in their source field, and the commission calculation comes out of those records. ##### Frequently asked questions - Can I track customers whose contract is signed but whose integration is not finished separately? | Yes. Integration is a separate record linked to the account and moves through its own stages; customers who have not gone live are gathered in a list filtered by that stage. - Do you build connections to banking and payment infrastructures? | Yes, we build the connection ourselves; there is no out-of-the-box module. The CRM tracks your customer's integration process as a record; the connection to your own systems is built specifically for the project via REST API, OAuth2 and webhooks, and its scope is set out in writing in the discovery call. - Can I see accounts with an unsigned contract in a single list? | The contract and the privacy notice are attachments on the customer record; the signature date is a field, and accounts where that field stays empty are gathered in their own list. - Which is the best CRM software for fintech? | When choosing a CRM for the fintech sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your fintech process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a fintech CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the fintech sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the fintech sector? | We start with a discovery call: together we work out your fintech process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for fintech? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phones. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Fitness and Gym CRM: Absence and Renewals | Rapitek](https://rapitek.com/en/fitness-gym-crm) The membership end date and the last entry date are fields on the same member record; a member who comes less often drops into a list at the threshold, and the renewal task opens before the date. ##### What we set up, and how - Keep the membership end date in a field and tie reminder and loyalty offer tasks to it at 60, 30 and 15 days out - Send a motivational message to a member who has not come in for two weeks and a special offer to one who has been away a month - Suggest a PT package and supplement campaign based on the member's fitness goal - Track the campaign you define for members who bring a friend, together with the referral chain - Have the whole team reply from a single WhatsApp number, with conversations assigned by the rule you define - Membership Renewal Tracking | The membership end date is a field; the 60-30-15 day steps are opened as tasks tied to that date, and the loyalty offer is linked to the same record. - Early Intervention on Absence | The last entry date is a field on the member card; those who pass the two-week and one-month thresholds drop into separate lists, and the message goes to those lists. - PT and Supplement Sales | The fitness goal is a field on the member record; suitable packages are filtered by that field and the offer is opened from the member's card. - Bring a Friend Campaign | The new member's source field points to the member who brought them; the referral chain is followed through that link and the campaign reward is recorded on the record. - Group Class Capacity Record | Every group class session is its own record; the instructor, the time and the capacity sit in fields, the member's booking is linked to that record, and a member who does not turn up is marked on the same class record. ##### Frequently asked questions - Why does a CRM matter for gyms? | In a gym the revenue breaks on the member's renewal decision, and the sign of that decision shows weeks earlier in how often they come. When the membership end date and the last entry date are fields on the same member record, a member who is coming less often drops into a list and the win-back task is opened before the renewal day. - How is absence tracked? | We build the connection to the turnstile and access control system ourselves; there is no out-of-the-box module, and the entry record at the turnstile does not reach the CRM by itself. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost with you in writing in the discovery call. When that connection is not built, the last entry date is a field on the member card and is updated by importing the turnstile report or by hand at reception; as the field is updated, a member who has not come for 2 weeks drops into the 'we missed you' message list, one who has not come for 1 month into the win-back offer list, and one who has not come for 3 months into the to-be-called list. - How can PT sales be increased? | The fitness goal is a field on the member record; members with weight-loss and muscle-building goals drop into separate lists, and the PT introductory offer is opened from those lists through the member's card. If you want to take an offer to a new member at the end of their first week, a task tied to the registration date is defined. - Can more than one person in the gym team use the same WhatsApp number? | On the gym side, the whole team replies to member correspondence from a single number; conversations are assigned according to the rule. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Fleet Management CRM: Contract Expiry and Handover | Rapitek](https://rapitek.com/en/fleet-management-crm) A contract is a record linked to the customer account; the start and end dates are its fields, and the renewal task opens off the end date. The vehicle is linked to the same contract. ##### What we set up, and how - Keep the lease contract's end date in a field, have those approaching expiry drop into a list, and tie the renewal task and the reminder to a rule from that list - See which customer has each vehicle, its maintenance history and the contract detail on a single screen - Track corporate fleet quotes by negotiation stage and close rate - Write the number of vehicles, the term and the service package onto the quote line and have the total calculated from the price list - Have the whole team reply from a single WhatsApp number and keep conversations under manager oversight - Customer Contract Management | A contract is a record linked to the customer account; the start and end dates are its fields, and the renewal task is opened off the end date. - Vehicle-Level Customer Tracking | A vehicle is a record and is linked to the contract; who has which vehicle and when it is due for service is answered from the vehicle card in a single step. - Sales Pipeline Management | Corporate quotes move along the pipeline as opportunity records; the waiting time at a stage and the close rate come out of the report on those records. - Quote Preparation | The number of vehicles, the term and the service package are fields on the quote line; the total is calculated on the quote card from the values coming out of the price list. - Driver Assignment and Handover Report | Which driver has the vehicle is a field on the vehicle record; at handover the mileage, the damage note and the equipment list are opened as a report, and the person taking delivery signs on the signature screen in the mobile app. ##### Frequently asked questions - How can we track fleet leasing contracts? | In Rapitek CRM you can define every contract at customer and vehicle level. The start and end dates are fields on the contract record; contracts approaching expiry drop into a list based on that field and the renewal task is opened for the person responsible. You tie how many days in advance the reminder goes out to a rule during setup, and you create the renewal quote from the same screen. - How can we manage the vehicle-customer relationship? | You can relate each vehicle record to the relevant customer, contract and maintenance history. You can see all of a customer's vehicles, or a vehicle's whole history, on a single screen. - How long does setup take for Fleet Management? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your fleet process requires becomes clear in that call. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same call and shared with you in writing. - Can more than one person use the same WhatsApp number for Fleet Management? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Florist CRM: Sender, Recipient and Card Message | Rapitek](https://rapitek.com/en/florist-crm) The sender is a customer record and the recipient's name and address are fields on the order; in Rapitek CRM the delivery time window and the second attempt run from that same order record. ##### What we set up, and how - Keep the sending customer and the delivery recipient apart; write the card message into the order's field and, for anonymous sending, leave the sender's name out of the card text - Write the delivery time window onto the order; have the courier close the delivery from the mobile app with location verification, have the person taking delivery sign on the signature screen, and open a second attempt task when the recipient cannot be found - Put work that must close the same day, such as funeral wreaths and ceremony orders, into a separate queue, set its owner with the assignment rule you define during setup, and notify the team as the status changes - Run the pre-order window before a special day with stepped follow-up tasks; turn the lists from hotel, office and agency accounts into quotes at their own agreed prices - Separating Sender and Recipient | The sender is a customer record; the recipient's name, address and phone number sit in the order's own fields. When the recipient later places an order of their own they become a separate customer record, so the two histories do not get mixed up. - Card Message and Anonymous Sending | The card text is a field on the order and passes to the delivery task along with the address; when the sender wants to stay anonymous their name is not written into the card text and stays only on the order record. - Narrow Delivery Window and Second Attempt | An order carries a time window, not just a day; the courier closes the delivery with location verification and the person taking delivery signs on the signature screen in the mobile app. If the recipient is not at the door the outcome is recorded on the task, and the time for the second attempt is agreed with the recipient from the shared WhatsApp or SMS inbox. - Corporate Pre-Order Window | Hotels, offices and agencies give their lists weeks before a special day; that list is opened as a pre-order under the account, turns into a quote at the price defined for that account, and is split into individual tasks on the delivery day. ##### Frequently asked questions - Can I track the sender and the recipient separately on a flower order? | Yes. The sender stays as a customer record, while the recipient's name and delivery address are in the order's own fields. That way orders the same customer sends to different people accumulate in a single history, and next year's reminder is set up for the right person. - How do I plan deliveries on busy days like Valentine's Day? | Deliveries are opened as tasks; because the delivery time and the address sit in fields, the day's list is sorted by time, distributed to the couriers, and the delivered confirmation is marked from the mobile app. - How do we handle corporate lists before a special day? | The list given by hotels, offices and agencies is opened as a pre-order under the account; it turns into a quote at the price defined for that account and is split into individual tasks on the delivery day. - Which is the best CRM software for a florist? | When choosing a CRM for the florist sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your florist process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a florist CRM system cost? | On the florist side the courier who closes the delivery also works on the same record; the system is used by the shop and the distribution staff. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the florist sector? | On the florist side, the list that hotels, offices and agencies give before a special day is opened as a pre-order under the account. 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the florist sector? | We start with a discovery call: together we work out your florist process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for a florist? | At a florist the courier closes the delivery with location verification, and the person taking delivery signs on the signature screen in the mobile app. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Food CRM: Channel Pricing and Shelf Visits | Rapitek](https://rapitek.com/en/food-beverage-crm) The price for a chain supermarket, a wholesaler and a hotel kitchen sits in the account record's own field; the order takes it from there. A field visit is a task, closed on site from the app. ##### What we set up, and how - Manage chain supermarket, wholesaler, HORECA and export customers as separate account types and apply each its own price and discount terms - Plan field sales visits, see that the representative reached the point with GPS verification, and have shelf and stock notes written onto the visit record - Track the listing negotiation and sample despatch as a staged opportunity and see which product is at which step with which chain - Link a product complaint to a case record by batch number and gather complaints for the same batch into a single list - Channel-Based Pricing | Chains, wholesalers and HORECA are separate account types; the agreed price and discount sit in the account's field and pass from there to the order. - Point of Sale Visit | A visit is a task; the date, the representative and the point of sale are its fields; the representative closes it at the supermarket from the mobile app, the location is verified by GPS, and shelf and stock notes are written to the same record. - Listing Process | Getting a product into a chain is an opportunity record; the negotiation, the sample and the paperwork are each a stage, and every stage has its own date. - Batch and Complaint | A complaint is a case record; the batch number is carried in its field, and cases belonging to the same batch appear in a single list. ##### Frequently asked questions - We sell the same product to different channels at different prices — how does the CRM hold that? | The price and discount terms are in a field on the account record; because chain supermarket, wholesaler and HORECA customers are separate account types, when an order is opened the price comes from that account's terms rather than being entered by hand. - How do I verify that the field team really visited the supermarket? | A visit is planned as a task and the representative closes it on site from the mobile app; the location is verified by GPS, mock location reporting is detected, and shelf and stock notes are written to the same visit record. - Can I see complaints about the same batch in a single list? | A complaint is a case record and the batch number is carried in that record's field; cases belonging to the same batch appear in a single list, and which channel the product went to is read from the account record. - Which is the best CRM software for food? | When choosing a CRM for the food sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your food process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a food CRM system cost? | On the food side the visit task carries the date, representative and point of sale fields; it is that field staff who uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the food sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the food sector? | We start with a discovery call: together we work out your food process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for food? | In food a field visit is a task; the representative closes it at the supermarket from the mobile app, and shelf and stock notes are written to the same record. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Footwear CRM: Size Runs and Pre-Orders | Rapitek](https://rapitek.com/en/footwear-crm) An order line carries a model and a size field; a model's size spread is read from those lines. In Rapitek CRM a warranty case opens with a defect type and recurring defects gather in a list. ##### What we set up, and how - Record dealer pre-orders with a model and size run breakdown and look at the production plan from the same list - Record in-season demand as a separate type from the pre-order and see in the report which size sells out early - Open warranty and return cases with a defect type; have the resolution note written on the case, so later cases opened with the same defect type are read from those records - Tie subcontracting workshop work to a task with its deadline date, and have the person taking delivery sign on the signature screen in the mobile app - Size Run | An order line carries a model and a size field; a model's size distribution and the difference from dealer to dealer are read from those lines. - Pre-Order and In-Season Demand | Both are order records linked to the same account; the type is separated in a field, and the season report is split in two by that field. - Warranty Case and Defect Type | A warranty case is a record; the model, the defect type and the decision given are its fields. The resolution note is written on the case, and later cases opened with the same defect type are read from those records. - Subcontracting Workshop Deadline | Work given to a workshop is a task; the deadline date and the quantity are its fields, and as the deadline approaches the task moves up the list. ##### Frequently asked questions - Can I keep the size run on the order? | Yes. An order line carries a model and a size field; the size distribution of the same model is read from the lines, and the dealer-level size run report comes out of that breakdown. - Can I see a defect recurring on the same model across warranty cases? | On the case record the model and the defect type are each a field; the model-level list shows how many times a defect has recurred. The resolution note is written on the case, and later cases opened with the same defect type are read from those records. - Will I know when the deadline for work given to a subcontracting workshop is approaching? | Work given to a workshop is a task; the deadline date and the quantity are its fields, and as the deadline approaches the task moves up the list. A handover record is opened at delivery and the person taking delivery signs on the signature screen in the mobile app. - Which is the best CRM software for footwear? | When choosing a CRM for the footwear sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your process in the footwear sector, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a footwear CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the footwear sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the footwear sector? | We start with a discovery call: together we work out your process in the footwear sector, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for footwear? | In footwear, subcontracting workshop work is a task with a deadline date; the person taking delivery signs on the signature screen in the mobile app. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Franchise CRM: Franchisee Audits and Turnover | Rapitek](https://rapitek.com/en/franchise-crm) Every item on the audit form becomes an action with an owner and a date; an item left open comes up open at the next visit, and the turnover declaration is linked to the franchisee account. ##### What we set up, and how - Score franchise applications against your own assessment criteria and move them through the approval steps - Compare each franchisee's sales and target achievement on the same screen - Plan field visits and fill in the audit form on mobile with photos, tying each item to an action - Send campaign, announcement and training information to the whole network in one go - Reply as a team from a single WhatsApp number, so correspondence does not stay on personal phones - Franchise Application | A candidate application is a record; the assessment criteria and the score awarded are its fields, the approval steps move along as stages, and which candidate is waiting where is read from the list. - Franchisee Performance | Every franchisee is an account record; sales, target and actual sit in that account's fields, and the franchisee-level comparison is taken from the report. - Brand Standards Audit | A field visit is an audit form filled in from the mobile app; every item on the form becomes an action with an owner and a date, and an item left open comes up open at the next visit. - Central Communication | Announcements, campaigns and training information are sent to the franchisee list; who was sent what and when leaves a trace on the despatch record. - Royalty and Turnover Declaration | A franchisee's periodic turnover declaration is a declaration record linked to the franchisee account; the period, the amount declared and the royalty calculated sit in fields, and when the declaration does not arrive on time a task is opened for the regional manager. ##### Frequently asked questions - How are franchisee applications assessed? | You can define customisable assessment criteria for every application, score candidates, and tie the approval steps to the flow defined during setup. - How are field audits carried out? | You can fill in field audit forms from the mobile app, attach photos, and open an action with an owner and a date for every item. An item left open comes up open at the next visit. - Can franchisee performance reports be produced? | Yes. Because sales, target and actual sit in the fields of the franchisee account, the franchisee-level performance and brand compliance report is produced from those fields. - Can more than one person in the franchise team use the same WhatsApp number? | On the franchise side, franchisee correspondence does not stay on personal phones but is run by the team from a single number. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Funeral Services CRM: Transfer and Burial Files | Rapitek](https://rapitek.com/en/funeral-services-crm) Every funeral service is a single record: transfer, washing and burial are its stages. In Rapitek CRM, while the burial permit field is empty the file does not move to the next step. ##### What we set up, and how - Run the transfer, washing and burial arrangements step by step on a single process - Record every conversation with the family on the same record, so it is clear who has taken over the process - Track municipal, hospital and institutional contracts together with their scope and service breakdown - Send process updates to the family over WhatsApp in measured language - Service File | Every funeral service is a single record; the transfer, washing and burial steps are its stages, a completed step is recorded onto the same record, and whoever takes over the shift reads from the record where the process stands. - Family Communication History | Every conversation with the family is an activity written onto the service file; who said what and when sits on the record, so the information does not change from person to person. - Corporate Contract | A municipality or a hospital is an account record; the contract scope and the agreed price are its fields, every service given is linked to that record, and the monthly breakdown comes out of it. - Burial Permit and Transfer Document | The death certificate, the burial permit and the out-of-city transfer permit are separate fields on the service file; a file with a missing document does not move to the next step, and which document is waiting with whom sits there as a task. ##### Frequently asked questions - Can municipal and institutional contracts be managed? | Yes, you can manage corporate contracts, special pricing and monthly service reports through the CRM. - How is data privacy ensured? | Each customer's CRM data is kept in a separate database allocated to them, and access authorisation is granted on a role basis. Hosting is in the European Union: the database in Finland, the media files in Frankfurt. Under KVKK Article 9 this counts as a transfer abroad; that is why we run the disclosure and explicit consent processes. - Can we stop a file progressing because of a missing document? | The death certificate, the burial permit and the out-of-city transfer permit are separate fields on the service file; the rule defined during setup stops a file with a missing document from moving to the next step, and which document is waiting with whom sits there as a task. - How long does setup take for Funeral Services? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your funeral services process requires becomes clear in that call. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same call and shared with you in writing. ### [Furniture CRM: Fabric Choice and Installation | Rapitek](https://rapitek.com/en/furniture-crm) Fabric, colour and dimensions are fields on the order line; the choice is entered at the point of sale and production reads it from the same record. Installation is a task tied to the order. ##### What we set up, and how - Record a made-to-measure order together with the fabric, colour and dimension choices - Track the production, dispatch and installation stages on the order record - Plan the installation appointment around team availability and notify the customer - Keep the price agreements of dealers and project customers on the account card - Link post-delivery warranty and service requests to the same order - Order Configuration | Fabric, colour and dimensions are fields on the order line; the choice is entered onto the record at the point of sale and production reads it from the same record, without asking a second time. - Production and Delivery Stages | Production, dispatch and installation are stages of the same order; which order is waiting where is read from the stage report. - Installation Team Calendar | Installation is a task tied to the order; the team, the date and the address are its fields. Because installations falling on the same day sit side by side in the calendar, giving a second job to the same team is visible on the record, and the notification to the customer goes out from that task's date. - Dealer and Project Pricing | Dealers and project customers are each an account record; the agreed price list is linked to the account and comes from there onto the quote. - Warranty and Service | A service request is linked to the relevant order; which product, which fabric and when the problem arose are tracked from the order record. ##### Frequently asked questions - How does the fabric and colour the customer chose show up in production? | Fabric, colour and dimensions are fields on the order line. Because they are entered at the point of sale, production reads them from the same record; no scrap of paper and no asking a second time. - How do I plan the installation appointment? | Installation is a task with team and date fields, and it is tied to the order. Installations falling on the same day appear side by side in the calendar, and the notification to the customer goes out from the same record. - How much does a furniture CRM system cost? | On the furniture side the installation task carries the team, date and address fields; it is that installation staff who uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the furniture sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in furniture? | We start with a discovery call: together we work out your furniture process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for furniture? | In furniture, installation is a task tied to the order; the team, the date and the address are its fields, and the installation team sees the task on their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Gaming CRM: Support Cases and Release Calendar | Rapitek](https://rapitek.com/en/gaming-crm) A support case is opened with version, platform and region fields; reports carrying the same symptom gather into one list, and how many players are affected is read from its count. ##### What we set up, and how - Open player support cases with version, platform and region fields and gather records reporting the same bug into a single list - Write the answer to frequently raised problems into the case's resolution note, so later cases opened with the same symptom are read from those records - Keep publisher, store and localisation partners on an account record, and leave the contract date and conversation history with the company - Run content creator and sponsorship conversations as a contact sequence tied to the launch calendar - Support Case Record | A case is a record with version, platform and region fields; it is linked to the player record, and reports with the same symptom are filtered by those fields. - Resolution Note | A recurring answer is written into the case's resolution note field; later cases opened with the same symptom are read from those records, so the text is not written from scratch every time. - Partner Account | The publisher, the store and the localisation company are each an account record; the contract start and end dates sit in fields, and the renewal task is tied to that date. - Release and Launch Calendar | A release is a dated record; the tasks linked to it are opened as content creator outreach and support preparation, and that week's load is visible from this list. ##### Frequently asked questions - Can we gather players reporting the same bug in one place? | Yes. Because version, platform and region are each a field on the case record, reports carrying the same symptom are gathered into a single list with a filter; how many players are affected is read from that list's count, and the order of the fix is discussed on that basis. - Does in-game purchase and store data flow into the CRM by itself? | We build the connection to the store and purchase side ourselves; there is no out-of-the-box module. Purchase and player data are connected via the REST API covering 183 business objects, webhooks and import; the scope is worked out in the discovery call. Once connected, the player's spending history appears alongside the support case. - Can I be notified when the publisher contract's end date arrives? | Yes. The publisher, the store and the localisation company are each an account record; the contract start and end dates sit in that record's fields. Because the end date is a field, contracts approaching expiry drop into a list, and it is defined during setup so that the renewal task is opened for the person responsible. - Which is the best CRM software for gaming? | When choosing a CRM for the gaming sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your game studio process, we migrate your data, and we deliver the training for your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a gaming CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together in the discovery call and shared with you in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the gaming sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project via our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does the move to a CRM system work in the gaming sector? | We start with a discovery call: together we work out your game studio process, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we deliver the training for your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for gaming? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from their phones. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Glass CRM: Measurement Card, Tempering, Breakage | Rapitek](https://rapitek.com/en/glass-crm) A job is a single record holding the measurement, thickness and edgework fields. In Rapitek CRM a broken pane becomes a separate record under that job, and breakage is reported by job and crew. ##### What we set up, and how - Write the measurement taken at the survey, with thickness and edgework detail, to the job record from the mobile app and attach the photo - Follow the cutting, tempering and fitting stages on the job record and see which job is waiting where - Plan the fitting appointment as a task with crew and time fields, and close it from the field with location verification - Record panes broken in transport and fitting under the job, and report breakage broken down by job and by crew - Measurement and Processing Card | A job is a record on which the measurement sits together with thickness, edgework and hole detail as fields; the survey photo is attached to the same card. - Production Stage | Cutting, tempering and packing are stages of the job record; jobs waiting at a stage are gathered in a list filtered on that field. - Glass Fitting Appointment | The day the glass is to be fitted is a task tied to the job record; crew, address and time are in its fields, and it is closed from the mobile app with location verification. - Breakage and Waste Record | A broken pane is a separate record under the job; the cause and stage fields are filled in, and the total is read from a report broken down by job and by crew. ##### Frequently asked questions - How does the glass measurement taken at the survey reach the workshop? | The measurement, thickness and edgework are written from the mobile app into the fields of the job record; the workshop looks at the same record, and because the survey photo is attached to the card, the measurement is not passed on by word of mouth a second time. - Can we track glass broken during fitting? | Yes. The broken pane is opened as a separate record under the job concerned, with cause and stage fields; the remake task is started from there, and the breakage total is reported broken down by job, crew and period. - Can I see which job is waiting at cutting and which at tempering? | Cutting, tempering and packing are stages of the job record; jobs waiting at a stage are gathered in a list filtered on that field, and jobs with an approaching fitting appointment stand out in the same list. - Which is the best CRM software for Glass? | When choosing a CRM for the glass sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your process in the Glass sector, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Glass CRM system prices cost? | In glass, the fitter who takes the measurement and the workshop that does the cutting look at the same job record, so people in the field and people in the workshop become users together. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the Glass sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the Glass sector? | We start with a discovery call: we work out your process in the Glass sector together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Glass? | In glass, the measurement taken at the survey and the edgework detail are written to the job record from the mobile app, and the photo stays attached. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Government CRM: Application Record, Unit Routing | Rapitek](https://rapitek.com/en/government-crm) An application is a record; its channel, subject and responsible unit are fields. Manual and workflow handovers are timestamped in the record's history; overdue applications gather in one list. ##### What we set up, and how - Gather applications arriving by letter, web form, e-mail and WhatsApp into a single record structure - Route an application to the right unit with assignment rules defined during setup, and see waiting and overdue work in one list - Send notifications to citizens over SMS and WhatsApp, and leave a trace of the sending on the record - Keep a dated history of the field changes users make on a record, for audit purposes - Application Record | An application is a record; the channel it came in on, its subject and the unit responsible are in its fields; when the owner is changed by hand, by bulk reassignment, over the API or by a workflow, the handover, with its date and the previous and new owner, is written to the record's history; routing done by the assignment rules defined during setup is not currently written to this history. - Unit Routing | Routing is an assignment rule defined during setup; based on the subject field the record drops into the queue of the relevant unit, and work with no owner assigned stays on a list. - Response Time | The target date by which an application must be answered is a field on the record; applications approaching and past their deadline gather in lists filtered on that field. - Audit Trail | Field changes users make on the record are kept in its history, while the record's initial creation and some bulk updates the system makes in the background are not; which user changed what and when is read from the record itself, although for record deletions, user and permission settings, automations and background processes the user shown in the history may not be the person who actually made the change. ##### Frequently asked questions - How are citizen applications arriving from different channels distributed to units? | The subject of the application and the channel it came in on are each fields on the record; the assignment rules defined during setup look at those fields and drop the record into the queue of the relevant unit. Because applications with no owner assigned stay on a separate list, no request ever becomes invisible on a single desk. - Where is institutional data stored? | Data is kept within the European Union: the CRM database is on servers in Finland, and files and media are hosted in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. A separate database is used for each tenant, and TLS is applied in transit. - Can I see how many days an application has been waiting in which unit? | Partly. When the application's owner is changed by hand, by bulk reassignment, over the API or by a workflow, the handover, with its date and the previous and new owner, is written to the record's History tab; routing done by the assignment rules defined during setup is not currently written to this history. The target date by which the application must be answered is also a field on the record. Applications approaching and past their deadline gather in lists filtered on that field. - Which is the best CRM software for Government? | When choosing a CRM for the public sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your public sector process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Government CRM system prices cost? | In the public sector an application drops into the queue of the relevant unit according to its subject and is assigned to an owner, so how many units will use the system varies from institution to institution. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the public sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the public sector? | We start with a discovery call: we work out your public sector process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Government? | Yes. Field and branch staff can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Graphic Design CRM: Briefs and Revision Rounds | Rapitek](https://rapitek.com/en/graphic-design-crm) Every amendment request drops under the project with its version, and which round of revisions you are on is counted. The hours the designer logs sit beside the quote amount on the same card. ##### What we set up, and how - Keep the brief, the delivery date and the approval status of every job on a single project record - Record amendment requests, keep the version history, and follow how much of the agreed revision allowance has been used - Prepare the quote per project; record client approval as a stage change and transfer it to an invoice with a ready-made conversion action - Keep client correspondence, meeting notes and design files in the same place - Communicate quickly and share files over WhatsApp, with the whole exchange staying in the CRM - Project and Brief Management | A job is a project record; the brief, the delivery date and the approval status sit in its fields, and files are attached to the same card. - Revision Tracking | Every revision request is a separate record tied to the project; which round of revisions it is gets counted, and going over the agreed number shows up on a list. - Quoting and Invoicing | The quote is produced under the project with its line items; approval is recorded as a stage change, and the transfer to an invoice is done with a ready-made record action. - Client Communication History | Correspondence, meeting notes and files accumulate under the client card; the question of who promised what is answered from a single record. - Designer Hours Breakdown | The hours a designer logs against a job sit line by line under the project; because the quote amount and the total of those lines come side by side on the same card, the profit on the job is visible before the project closes. ##### Frequently asked questions - Is there a file sharing feature? | Yes, you can create client-specific file areas, share design files and manage approval processes. - Can freelancers use it too? | Rapitek CRM is an enterprise solution aimed at teams of 5 or more users. It suits agency and studio structures. - Can I get profitability reports per project? | Yes, you can produce detailed profitability reports for each project on the basis of time spent, cost and revenue. - Does an invoice get created on its own once the quote is approved? | The quote is produced under the project with its line items; client approval is recorded as a stage change. To turn an approved quote into an invoice you run the ready-made conversion action on the record; the line items and totals carry over as they stand on the quote. There is no flow that issues an invoice by itself at the moment of approval — your team starts that step. - How long does setup take for Graphic Design? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your graphic design process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Greenhouse and Nursery CRM: Production Plan | Rapitek](https://rapitek.com/en/greenhouse-crm) A supermarket chain, a landscaping firm and a dealer are each an account record; species preference and order history accumulate there, and next season's production plan comes out of those records. ##### What we set up, and how - Keep the order history and species preferences of supermarket chains, landscaping firms and dealers per customer - Follow the balance between orders and stock on the same screen and update your production plan accordingly - Keep plant species, price and stock information up to date and share it with your customers - Send campaigns and offers to the target customer group during planting and sowing seasons - Send new product announcements and order confirmations over WhatsApp - B2B Customer Management | A supermarket chain, a landscaping firm and a dealer are each an account record; species preference is in a field, and order history accumulates under the card. - Order and Production Planning | Orders and stock are tied to the same product record; open orders and the quantity on hand appear side by side in a single list. - Product Catalogue Management | Species, price and stock are fields on the product record; the list shared with the customer is produced from that card, and no separate catalogue is kept. - Seasonal Campaigns | A campaign is a record; the target group is filtered on customer fields, and because orders coming back are tied to the campaign, the result is measured. - Plant Passport Tracking | For every batch that goes out for dispatch, the plant passport number and its date of issue are fields on the batch record; a batch whose paperwork is not complete does not close the dispatch task, and which batch went to which customer is read backwards from the same record. ##### Frequently asked questions - Can I manage wholesale and retail sales separately? | Yes, you can use different price lists, payment terms and order modules for B2B and B2C customers. - Is there a seasonal planning module? | Yes, you can forecast seasonal demand from previous years' data and adjust your production plan accordingly. - Is logistics tracked? | Yes, you can follow order picking, packing and dispatch processes through the CRM. - How long does setup take for Greenhouse and Nursery? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your greenhouse and nursery process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Grocery and Corner Shop CRM: Store Credit | Rapitek](https://rapitek.com/en/grocery-store-crm) Store credit lines sit under the customer record; the balance drops the moment a payment is entered, and the reminder comes from that balance. The same card carries points and purchases. ##### What we set up, and how - Keep the store credit balance per customer, see the payment history and send a reminder notification - Reward customers who collect points and gather frequent shoppers in a separate group - Track product stock, get an alert for items that fall to a critical level and start the order from the same screen - Compare the best-selling products and profitability in daily, weekly and monthly sales - Let the whole team reply from a single WhatsApp number, with the messaging staying on the customer record - Store Credit Tracking | Store credit lines are kept under the customer record; the balance is calculated from those lines, and the payment history stays on the same card. - Home Order Delivery | An order that comes in by phone or WhatsApp is a record; the delivery address, the person taking the order out and the delivered flag are fields on that record; if it was put on store credit, the line falls to the same customer card. - Supplier Rep Visit Day | Which supplier's sales rep comes on which day is a field on the supplier record; the missing items to be ordered that day are filtered from the product records and tied to the same visit task. - Sales Reports | Because sales records sit with their date and their product, daily, weekly and monthly comparisons are taken by changing the report range. - Expiry Date Tracking | The expiry date is a field on the product record; items whose date is approaching are filtered by that field, and the shelf check is a task produced from that list. ##### Frequently asked questions - Can I see an order sent to a home and its store credit in the same place? | An order that comes in by phone or WhatsApp is a record; the delivery address, the person taking the order out and the delivered flag are fields on that same record. If it was put on store credit, the line falls to the same customer card and the balance is calculated from there. - How do we catch products whose expiry date is approaching? | The expiry date is a field on the product record; items whose date is approaching are filtered by that field, and the shelf check is opened as a task produced from that list. - How long does setup take for a grocery or corner shop? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your shop's process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for a grocery or corner shop? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person on a grocery or corner shop team use the same WhatsApp number? | On the grocery and corner shop side the whole team replies to order messages from a single number, and the messaging stays on the customer record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even when staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Hair Transplant Centre CRM: Graft Plan and Transfers](https://rapitek.com/en/hair-transplant-center-crm) The patient journey is six stages on a single record: first enquiry, hair analysis, quote, preparation, the operation and follow-up spread over twelve months; each stage opens its own task. ##### What we set up, and how - Route patient enquiries arriving in different languages by language, and answer them with the reply templates defined during setup for each language - Keep consultation and hair analysis photos, the follicular graft count and the placement plan together on the patient card - Plan the international patient's hotel booking, airport transfer and travel to the clinic from the same record - Open the week 1, month 1, 3, 6 and 12 follow-ups as tasks tied to the procedure date, and tie the WhatsApp or e-mail reminder to those tasks as a rule - Direct satisfied patients to a Google review and follow the new patients coming in through the referral programme - Multilingual Lead Management | Language is a field on the prospective patient record; routing and reply templates are matched on that field. The interface is fully translated in Turkish and English; in other languages, untranslated text appears in English. - Hair Analysis Photo Archive | Photos are attachments on the patient record; the graft count and the placement plan are fields on the same card, and comparison is done on a single screen. - Accommodation and Transfer Coordination | Hotel, transfer and travel to the clinic are tasks tied to the patient file; who took on which step is visible on the record. - Post-Operative Follow-Up | Follow-up steps are opened as tasks tied to the procedure date; whether the reminder goes out over WhatsApp or e-mail is tied to a rule, and the sending is recorded on the card. - Review and Referral Management | The satisfaction marker is a field on the patient card; the review invitation and referral tracking run on tasks tied to that field, and an incoming patient shows the referral in their source. ##### Frequently asked questions - How is the patient journey managed with a CRM in hair transplant centres? | The patient journey is six stages on a single record: first enquiry, hair analysis, quote, pre-operative preparation, the day of surgery and post-operative follow-up. The stage is a field on the record; when the stage changes, which checklist and which WhatsApp template come into play is tied to a rule during setup. How many patients are waiting at which stage is read from the stage report. - Is there language support for patients coming from abroad? | Yes. The prospective patient's language is a field on the record; requests arriving in Turkish, English, Arabic, German and Russian are routed on that field. A separate reply template, consultation form and follow-up message sequence is defined for each language during setup. The interface is fully translated in Turkish and English; in other languages, untranslated text appears in English. - Are leads from Instagram, Google Ads and WhatsApp recorded automatically? | The Meta Lead Ads connection that would cover Instagram lead forms is not live, so it cannot be set up today. On the Google Ads or the WhatsApp side we build the connection; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export, and its scope and cost are shared in writing in the discovery call. As long as the connection is not built, prospects coming from advert forms are entered with an import file or by hand; the source, the campaign and the first message are still fields on the prospective patient record, and which channel turned into an operation is counted from those fields. On the WhatsApp side the shared inbox is a capability of the product itself: your own Meta WhatsApp Business account is connected during setup, incoming messages drop into the team inbox and are recorded on the patient card. - How do post-operative photo follow-up and Google reviews work? | The procedure date is a field on the patient record; the day 1, week 1, month 1, month 3, month 6 and month 12 follow-ups are opened on the card as tasks tied to that date, and photos are uploaded as attachments to the same record. Which month's reminder goes out through which channel is tied to a rule during setup. Once the satisfaction marker has been recorded on the card, the Google review invitation is sent from a task tied to that field; there is no survey that goes out by itself. ### [Healthcare CRM: Appointment Reminders and Consent](https://rapitek.com/en/healthcare-crm) The appointment is tied to the patient's own file; the timing and channel of the reminder are set per patient, and referral and follow-up are opened as tasks in the same chain. ##### What we set up, and how - Gather the patient's treatment history, appointments and notes on a single record - Tie how many hours before an appointment the SMS, e-mail or WhatsApp reminder goes out to a rule, and bring down your no-show rate - Open the follow-up appointment of a referred patient as a task tied to the referral record; let those left unclosed stay on a list - Keep patient data on infrastructure where access is limited by role and the data sits in a separate database that belongs to you - Let the whole team answer from the clinic's single WhatsApp number; have conversations assigned by the rule you define and response times visible to managers - Patient Management System | Treatment history, appointments and notes accumulate under the patient card; the question of who called and when is answered from the same record. - Appointments and Reminders | The reminder is sent tied to the appointment date; confirmation and cancellation are recorded on the same record, and no-shows stay on a list. - Data Security and KVKK | Access is limited by role-based permissions, each tenant's data sits in a separate database, and transfer is done over TLS. Hosting is in the EU (Finland); for transfer abroad, explicit consent is obtained under KVKK art. 9. - Referral and Follow-Up Management | A referral is a record and is tied to the patient card; the follow-up appointment is opened as a task tied to that record, and those left unclosed stay on a list. - Consent Form Signature Record | The informed consent taken before a procedure is a form tied to the patient record; which procedure it is for, who signed it and when sit in fields, and the person giving consent signs on the signature screen in the mobile app. ##### Frequently asked questions - Is health data safe? | Each customer's data is kept in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256, two-step verification secrets are encrypted at rest, and access is limited by role-based permissions. Hosting is in the European Union (Finland); for transfer abroad, the disclosure and explicit consent process under KVKK art. 9 is carried out. - Does it integrate with our existing patient information system? | We build the connection to HBYS products; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. As long as the connection is not built, patient information is entered with an import file or by hand; treatment history, appointment and follow-up tracking are still kept in the CRM and reminders are produced from there. - How do appointment reminders work? | The date and time of the appointment are fields on the record; how many hours before that date the reminder goes out, through which channel (SMS, e-mail or WhatsApp) and how many times, is tied to a rule during setup. The sending is recorded on the same appointment record; the patient's confirmation or cancellation drops onto that record too, and no-shows stay on a list. - Can more than one person use the same WhatsApp number for Healthcare? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [HealthTech CRM: Pilot Installs and Tender Tracking](https://rapitek.com/en/healthtech-crm) A hospital is an account record; the clinician, IT and procurement are separate contacts tied to that same account. Who raised which objection sits in the notes on the opportunity record. ##### What we set up, and how - Follow the clinician, IT and procurement as separate contacts under the same opportunity, and tie each one's objection to the record - Run the pilot installation as a chain of tasks with dates and exit criteria, and see which institution is at which stage - Follow the tender and quote calendar with submission deadlines, and attach specification and technical document versions to the opportunity - Record integration requests with their scope and areas of responsibility, and move the go-live process forward under the same account - Multi-Stakeholder Selling | A hospital is an account record; the clinician, IT and procurement are contacts tied to that account, and objections sit in the opportunity's notes. - Pilot Installation Tracking | The pilot is a chain of tasks with a start and end date; the exit criterion is written in a field, and its outcome is tied to the opportunity. - Tenders and Specifications | A tender is an opportunity record; the submission deadline is in a field, and versions of the specification and technical documents are kept as attachments. - Permissions and Visibility | Fields relating to patient data are tied to permission level; which role sees which field is defined on the record type. ##### Frequently asked questions - Can we exchange data with our hospital information management system? | We set up the data exchange with your hospital information management system — we build the connection. There is no out-of-the-box module: because every hospital's system and field structure is different, the connection is built specifically for the project over the REST API covering 183 business objects, OAuth2 and webhooks; which fields flow in which direction is defined in the discovery call and shared in writing. - In a hospital sale that runs for months, how do we track who objected to what? | The clinician, IT and the procurement department are separate contacts tied to the same account; the note from every meeting and whether the objection has been met sit on the opportunity record, and even if the representative changes, the history stays on the record. - Where do we keep tender submission deadlines and specification versions? | A tender is an opportunity record; the submission deadline is a field on that record, and tenders whose date is approaching drop onto a list. Every version of the specification and the technical document is kept as an attachment on the same record. - Which is the best CRM software for HealthTech? | When choosing a CRM for the HealthTech sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your healthtech process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do HealthTech CRM system prices cost? | In HealthTech, because which role sees which field is defined on the record type, users are set up individually with their roles. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the HealthTech sector? | In HealthTech the counterpart the CRM will talk to is the hospital's information system. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the HealthTech sector? | We start with a discovery call: we work out your healthtech process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for HealthTech? | Yes. Field and branch staff can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Holding Company CRM: Consolidated Group Reporting](https://rapitek.com/en/holding-company-crm) Each subsidiary is a separate unit; a record carries in a field which company it belongs to. When the same customer is opened at two subsidiaries the records match and the histories sit side by side. ##### What we set up, and how - Define each subsidiary as a separate unit and run it with its own sales process and pipeline stages - Consolidate the sales, pipeline and customer data of the group companies on a single dashboard - Let users see only their own company's data while opening all of the data to holding management - Route a customer won at one subsidiary to the other group companies as an opportunity - Have the whole team answer from a single WhatsApp business number and assign conversations in the team inbox - Multi-Company Management | Each subsidiary is defined as a separate unit; records carry in a field which company they belong to, and sharing between companies is set up over that field. - Consolidated Holding Reporting | Because the data sits in one place, the group report is taken by grouping on the company field; there is no need to collect files from the subsidiaries. - Subsidiary-Based Access Permissions | Visibility is set up with role-based permissions; a user sees the records of their own company, while the holding role sees all of them. - Cross-Selling Opportunities | An account won at one subsidiary can be opened as a new opportunity at another company; because the source record stays linked, which company it came from is tracked. - Intra-Group Request Handover | A request one subsidiary cannot meet is handed over to another company's queue with its source preserved; the handover date, the transferring unit and the person taking it on sit in fields defined during setup, and the response after the handover is followed from the same record. ##### Frequently asked questions - Can we manage the different companies within a holding in a single CRM? | Yes. With its multi-company architecture, Rapitek CRM defines each subsidiary as a separate unit. Data isolation, a shared customer pool and consolidated reporting at holding level are offered on a single platform. - Can the same CRM be used for subsidiaries in different sectors? | Absolutely. You can define different sales processes, pipeline stages and custom fields for each subsidiary. Companies in different sectors such as textiles, energy and logistics use their own workflows. - How long does setup take for Holding Companies? | After the discovery call we give you a date, not a range — how many units, how many fields, how many stages and how many reports your holding structure needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Can more than one person use the same WhatsApp number for Holding Companies? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Home Healthcare CRM: Verified Visits and Care Plans](https://rapitek.com/en/home-healthcare-crm) A visit is a record with carer, patient and time fields — its start is recorded with time and location verification. A care plan item that is skipped stays open on the visit. ##### What we set up, and how - Match the most suitable carer to the patient's needs - Plan the daily visit schedule and verify the time and location of the visit at the moment it is recorded - Record the detail of every visit and produce a periodic progress report - Send the daily care report and visit notification to the patient's family over WhatsApp - Follow visit timing and care quality scores per carer - Patient-Carer Matching | Needs and competencies are fields on the patient and carer records; a suitable carer is chosen from a list filtered on those fields, and the assignment is recorded. - Visit Planning and Tracking | A visit is a record with carer, patient and time fields; the start and end are kept together with their times, and the plan is visible on the calendar. - Family Communication Centre | A patient's relative is a contact record tied to the patient card; who was told what and when leaves a trace on the same card. - Care Quality Reporting | Because the note from every visit sits on its own record, the periodic progress report is compiled from those records and no separate logbook is kept. - Medication Times and Care Plan | The patient's medication times and care plan items are sub-lines on the patient record; each item is ticked off one by one during the visit, and an item that is skipped stays open on the visit record and drops onto the office's list. ##### Frequently asked questions - Is carer performance tracked? | Yes, each carer's visit timing, patient satisfaction and care quality scores are tracked. - Is patient data safe for Home Healthcare Services? | Each customer's data is kept in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256, two-step verification secrets are encrypted at rest, and access is limited by role-based permissions. Hosting is in the European Union: the database in Finland, media files in Frankfurt. This counts as a transfer abroad under KVKK art. 9; that is why we run disclosure and explicit consent processes. A small number of sub-processors operate outside the EU; we list each of them and where they process the data one by one in our privacy policy. - Is there SGK and insurance integration? | We build the connection to SGK or private insurance companies; there is no out-of-the-box module, and we have no product called a “compliant module” either. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. As long as the connection is not built, authorisation and entitlement information is entered with an import file or by hand; visit records, medication times and care plan items are still kept in the CRM, and invoicing, payment tracking and reminders are produced from there. - How long does setup take for Home Healthcare Services? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your home healthcare process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Hosting & Domain CRM: Domain and SSL Expiry | Rapitek CRM](https://rapitek.com/en/hosting-crm) Package, domain and SSL certificate are each a record; the expiry date sits in a field on them, upcoming expiries fall into a list, and the reminder task is opened from that list. ##### What we set up, and how - Keep hosting package, domain and SSL renewal dates in a record field; let upcoming expiries fall into a list and tie the reminder to that list as a rule - Follow a customer's history from the first record to today and see the risk of losing them early - Split support tickets into categories and run them by priority and committed response times - List customers eligible for a higher package by the package field and open the opportunity record from that list - Subscription and Renewal Tracking | The package, the domain and the certificate are each a record; the expiry date sits in a field on them, upcoming expiries fall into a list and a reminder task is opened. - Customer Lifecycle Management | Every transaction from the first record to today accumulates under the customer card; thinning contact and a downgraded package show up in the report on that history. - Technical Support Ticket Management | A ticket is a record; category, priority and opening time are its fields, and the ones that exceed the response time you have committed to are collected in a report. - Upsell and Cross-sell Opportunities | The package owned is a field; customers eligible for a higher package are gathered in a list filtered on that field and opened as opportunities. ##### Frequently asked questions - Is there a WHMCS or Plesk integration? | If you use WHMCS, cPanel or Plesk, your CRM talks to it — we build the connection. There is no out-of-the-box module: the connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export, and its scope and cost are shared in writing during the discovery call. Where it is not built, customer and subscription data is entered from the import file you take out of your panel or by hand; the package, domain and expiry date fields are held in the CRM either way, and reminders are generated from those fields. - Can we send bulk domain renewal reminders? | The expiry date is a field on the record of the package, the domain and the certificate; upcoming expiries fall into a list based on that field and the renewal task is opened from that list. How many days ahead and through which channel (email or SMS) the reminder goes out is set as a rule during setup; you can also send in bulk to that same list, and the send is written onto the customer record. - How do I find the customers who could move up to a higher package? | The package owned is a field on the customer record; customers eligible for a higher package are gathered in a list filtered on that field and the opportunity record is opened from that list. Because the support history sits on the same card, you can also see there which customer to take the offer to and when. - Which is the best CRM software for hosting and domain businesses? | When choosing a CRM for the hosting and domain sector, pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up, we do: we configure the fields, the stages and the reports around your hosting and domain process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a hosting and domain CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery call and shared in writing. Rapi AI credit and ERP integration are separately priced items. - How does the move to a CRM system work in the hosting and domain sector? | We start with a discovery call: we work out your hosting and domain process together, which fields and which stages are needed. After that call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for hosting and domain businesses? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. 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. ### [Hotel CRM: Corporate Contracts and Guest Preferences](https://rapitek.com/en/hotel-crm) A corporate agreement is a contract tied to the account record; the term, the room allocation and the negotiated nightly rate sit in fields. A renewal task drops before the contract ends. ##### What we set up, and how - Gather corporate agreements, group reservations and meeting package sales on a single dashboard - Record room preferences and stay notes on the guest card, and have the team alerted when a VIP guest arrives - Keep the date of the last stay in a field; set up the post-checkout thank-you message and the win-back campaign months later as tasks tied to that date - Follow wedding, conference and launch enquiries from the first meeting through to the contract - Corporate Room Allocation and Contract | An agreement made with a company is a contract tied to the account record; the term, the room allocation and the negotiated nightly rate sit in fields, and a renewal task drops to the sales manager before the contract ends. - Guest Preference Tracking | Room preference and stay notes are fields on the guest card; the VIP marker is a field too, and the team sees it on the same card when a reservation is opened. - Loyalty and Repeat Stays | The date of the last stay is a field; the thank-you message is set up as a task tied to check-out and the win-back campaign as a task tied to that date. - MICE and Event Sales | An event enquiry is an opportunity record; it moves through its stages from the first meeting to the contract, and the quote is produced under it. - In-Room Fault Request | A fault reported by a guest is a request tied to the reservation; with the queue rule defined during setup it drops to technical services or housekeeping, and the resolution time and closing note sit on the same request. ##### Frequently asked questions - What does a CRM do in the hotel sector? | The PMS manages the operation: it knows who is staying in which room that night. The CRM, on the other hand, manages corporate sales, guest preferences and the loyalty relationship. The two complement each other; the agreement, the contact person and the renewal date sit on the CRM record. - How are guest preferences used? | Room preference, dietary notes and special requests are fields on the guest card; when a reservation is opened the team sees them on the same card, and the room is prepared from the record rather than by asking the guest. The VIP marker is a field too; at check-in a task drops to the relevant team. - How are the post-checkout thank-you and win-back messages set up? | The date of the last stay is a field on the guest record. You set up the thank-you message tied to check-out and the win-back campaign that comes into play months later as tasks tied to that field; you define during setup which message goes out how many days later and through which channel, and the sending is recorded on the guest card. - How is corporate sales managed? | The agreement per company, the room allocation, the negotiated nightly rate and the contact people are kept in a contract tied to the account record. Because the contract end date is a field, the annual review and renewal task is produced from that date. - Can more than one person use the same WhatsApp number for Hotel? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [HR and Recruitment CRM: Talent Pool and Interviews](https://rapitek.com/en/hr-recruitment-crm) Every candidate is a record; the CV, the position applied for and the interview score sit on one card. A rejected candidate is not deleted — mark the pool field and they return for the next opening. ##### What we set up, and how - Gather CVs arriving from careers sites and e-mail into a single candidate database, by hand or with a bulk import - See the candidate flow of every open position step by step, and measure how many candidates were rejected at which point - Digitise the interview calendar and the assessment forms, and tie the scoring to the candidate card - Take rejected but qualified candidates into the talent pool, and look there first for a new position - Run correspondence with candidates over a single business number and the team inbox, so the history stays on the record even when staff change - Candidate Record | Every candidate is a record; the position applied for and the application source sit in its fields, and the CV file is attached to the same record; past applications accumulate under the same card. - Recruitment Stages | A position is a record and candidates are tied to it; the stage is a field, and how many candidates were rejected at which step is read from the report on that field. - Interviews and Assessment | An interview is an activity tied to the candidate record; the date, the interviewer and the score are in its fields, and the assessment form is recorded on the same record. - Talent Pool | A rejected candidate is not deleted; once the pool field is marked, they appear on a list filtered on that field when a new position opens. - Offer Letter and Acceptance Record | The job offer made to a candidate is an offer tied to the candidate record; salary, start date and validity period sit in fields, the candidate who accepts signs on the signature screen in the mobile app, and the reasons for rejected offers accumulate on the same record. ##### Frequently asked questions - Can it pull CVs in automatically? | We connect your careers site and your e-mail inbox to the CRM — we build the connection. There is no out-of-the-box module: because the access and field structure of every careers site is different, the connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. Even without this connection, the candidate record and the CV file are added to the candidate card by hand or with a bulk import; after that, the position stages, the interview form, the scoring and the talent pool all run on the same card. - How are interview assessments done? | You can create customisable assessment forms and gather interviewer notes and scores digitally. - What does the product cover for KVKK with Human Resources data, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. Because the application date is a field on the candidate record, candidates whose retention period has expired drop onto a list on that field; you move those candidates to the recycle bin with a bulk deletion step; the product has no separate anonymisation function — you can clear the personal fields by hand or with a bulk update, but that does not delete files attached to the record or the old values kept in the field change history; to have these deleted, you need to write to our support team. Bulk deletion moves candidate records to the recycle bin; because the bin's automatic clean-up is not running today, they stay there; an authorised user can restore them from the bin or delete them permanently. Copies remain in backups until those backups are deleted. Files attached to a record (for example, candidates' CV files) are not deleted from storage whether you delete the file from the candidate card or delete the candidate record; today the product does not delete these files by itself. To have these files deleted, you need to write to our support team. There is no deletion engine that runs by itself; you define the period and the step, and the operation leaves a trace in the change history. Hosting is in the European Union: the database in Finland, media files in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. For candidate data, your organisation is the data controller and Rapitek is the data processor; disclosure to candidates and any consent processes are also your organisation's responsibility. - Can more than one person in the Human Resources team use the same WhatsApp number? | On the Human Resources side, correspondence with candidates runs from a single business number; even when staff change, the history stays on the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [HVAC / Ventilation CRM: Duct Take-off and Installation](https://rapitek.com/en/hvac-crm) The duct take-off and equipment list from the survey go into the quote lines; a change on site is kept dated on the same project record. The maintenance period is a field on the account. ##### What we set up, and how - Set out the duct take-off and equipment list measured at the survey as quote lines, and keep the revision on the same project record - Set up the installation calendar and make crew assignments, and follow site progress from the record - Keep the maintenance period in a field on the customer record; let those whose period has run out drop onto a list, and tie the filter change and duct cleaning reminder to that list as a rule - Add up the material, labour and overhead lines of every project and measure profitability - Duct Take-off and Survey Record | The duct take-off, the suspended ceiling height and the equipment list measured at the survey go into the project's quote lines; when the take-off changes on site, the revision is kept under the same project record with its own date. - Installation Crew Coordination | Installation jobs are tasks tied to the project; crew and date are in their fields, and site progress is read from the task list. - Maintenance Contract Management | A maintenance contract is a record tied to the customer account; filter changes and cleaning tasks are opened again and again according to the period field. - Project Profitability Analysis | Materials, labour and overheads are line items on the project; profitability is visible on the project card over the total of those lines. ##### Frequently asked questions - Can the quoting process for ventilation projects be managed from the CRM? | Yes, you can run the whole process through Rapitek CRM, from the customer enquiry to the technical survey, and from preparing the quote to signing the contract. - Are periodic maintenance reminders sent automatically? | The maintenance period and the last maintenance date are fields on the customer account; customers whose period has run out drop onto a list on those fields, and the filter change, duct cleaning and general inspection tasks are opened from that list. How many days in advance the reminder goes to the customer, and through which channel, is tied to a rule during setup. - What happens to the quote and the cost if the take-off changes on site? | The duct take-off, the suspended ceiling height and the equipment list measured at the survey go into the project's quote lines; when the take-off changes on site, the revision is kept under the same project record with its own date, and because the material and labour lines change, profitability is updated on the project card. - Which is the best CRM software for Ventilation? | When choosing a CRM for the ventilation sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your ventilation process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Ventilation CRM system prices cost? | On the ventilation side, installation jobs are tasks carrying crew and date fields; it is this field workforce that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the Ventilation sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the Ventilation sector? | We start with a discovery call: we work out your ventilation process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Ventilation? | Yes. Field and branch staff can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [AC and Boiler Service CRM: Device History, Maintenance](https://rapitek.com/en/hvac-service-crm) Air conditioners and boilers are each a record with their serial number; brand, model and warranty expiry are their fields, and every service done accumulates under the same record. ##### What we set up, and how - Keep every device in its own record with brand, model, serial number and warranty expiry, and accumulate the service history beneath it - Distribute incoming fault requests to technicians with the queue and the assignment rules defined during setup, and drop the day's job list onto the field team's phones - Have the service form signed on the spot from the signature screen in the mobile app, and write the spare part used and the location verification of the visit onto the record - Draw up a renewal list from the end dates of annual maintenance contracts and send the reminder by SMS and WhatsApp - Device Record | Air conditioners and boilers are each a record; brand, model, serial number and warranty expiry are in fields, and services accumulate under that record. - Request Distribution | A fault report is a request record; the queue and the assignment rules defined during setup drop it to a technician, and jobs that have not been closed stay on a single list. - Service Appointment | An appointment is a task; the technician, the address and the time sit in fields; when the job is done the customer signs the service form on the signature screen in the mobile app, the technician's location is verified, and the spare part fitted is written onto the same task. - Device Maintenance Agreement | The agreement is a record attached to the device record; the maintenance interval, the parts left out of scope and the end date are in its fields; devices whose end date is approaching collect in the renewal list. ##### Frequently asked questions - Is the service history attached to the address or to the device? | To the device. Air conditioners and boilers are each a separate record with their serial number; when the owner of the home or the workplace changes, the device's history stays where it is. Before going out to site, the technician sees from the record which part was fitted to that same device before. - How is it verified that the technician actually did the job on site? | The visit is a task record; when the technician closes the job from their phone, location verification is carried out and spoofed location reports are detected. The customer signs the service form on the spot, on the signature screen in the mobile app; the spare part used is written onto the same task. - Where do I see the devices whose maintenance contract is about to end? | The agreement is a record attached to the device record; the maintenance interval, the parts left out of scope and the end date are its fields. Devices whose end date is approaching collect in the renewal list, and the reminder is sent from that list. - Which is the best CRM software for air conditioning and boiler service? | When choosing a CRM for the air conditioning and boiler service sector, you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your air conditioning and boiler service process, we migrate your data ourselves, and we train your team ourselves in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does an air conditioning and boiler service CRM system cost? | In air conditioning and boiler service the fault request drops to the technician through assignment rules, so the technicians in the field are defined in the system too. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the air conditioning and boiler service sector? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does moving to a CRM system work in the air conditioning and boiler service sector? | We start with a discovery call: we work out your air conditioning and boiler service process together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we train your team ourselves in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product - this is a choice, not a matter of capacity. - Can mobile CRM be used for air conditioning and boiler service? | In air conditioning and boiler service the service form is signed on the spot from the signature screen in the mobile app, and the location verification is written onto the record. 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 wrote is kept on the device for 24 hours. ### [Import Export CRM: Freight Costs and Batch Allocation](https://rapitek.com/en/import-export-crm) A shipment batch is a record with its own line items; freight, customs duty and demurrage invoices are added to those lines as they arrive, and the batch's cost is read from the total. ##### What we set up, and how - Keep the samples and quotes coming in from several overseas suppliers for the same product on a single comparison - Run every shipment batch on its own record, and add the freight, duty and demurrage items to the batch's lines as they arrive - Follow which customer the arriving goods were allocated to from the batch record, and match them with waiting orders - Gather the correspondence, the documents and the payment schedule on both the supplier and the buyer side under the same accounts - Supplier Comparison | Every overseas supplier is an account record; the sample result, the lead time and the minimum order quantity sit in its fields. - Shipment Batch | A batch is a record with its own line items; freight, customs duty and demurrage are added to those lines, and the cost is read from the total. - Allocation | Arriving goods are tied to customer orders under the batch record; which quantity was set aside for whom is seen from that link. - Document File | The invoice, the packing list and the bill of lading are attachments on the batch; a missing document is visible from the record's checklist. ##### Frequently asked questions - Import costs are only settled later; how do we track that? | Every shipment batch carries its own line items; freight, customs duty and demurrage invoices are added to those lines as they arrive, and the batch's current cost is totalled on the record, with the comparison against the sale price made from the same card. - Can we compare quotes from different suppliers for the same product? | Yes. Every supplier is a separate account record; because the sample result, the unit price, the lead time and the minimum order quantity are kept in fields, the quotes are seen side by side on the same list, and the chosen quote is tied directly to the order record. - Where do I see which customer the arriving goods were set aside for? | Arriving goods are tied to customer orders under the batch record; which quantity was set aside for whom is seen from that link, and matching against waiting orders is done on the same record. - Which is the best CRM software for Import Export? | When choosing a CRM for the import export sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your import export process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Import Export CRM system prices cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the Import Export sector? | In the import export business the counterpart the CRM will talk to is your customs broker's or your freight forwarder's system. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the Import Export sector? | We start with a discovery call: we work out your import export process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Import Export? | Yes. Field and branch staff can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Independent Accountant CRM: Tax Return Calendar](https://rapitek.com/en/independent-accountant-crm) The tax regime is a field on the taxpayer record; VAT, withholding, corporate and provisional tax dates are opened as tasks on that field, and work left unclosed stays on the list. ##### What we set up, and how - Set up each client's VAT, withholding, corporate, tax-at-source and provisional tax calendar according to their tax regime, and get an alert seven days before the date - Open the month-end document expectation as a task per client, keep the incomplete ones on a list, and tie the reminder to that task - Keep the monthly fee and additional service lines under the client card, and follow overdue ones from a list - Archive the e-Beyanname, e-Defter and e-Fatura submission confirmation on the client record with its date and time - Follow your clients' KOSGEB support and incentive entitlement dates and put a quote together when the time comes - Tax Return Calendar | The tax regime is a field on the taxpayer record; the VAT, withholding, corporate, tax-at-source and provisional tax dates are opened as tasks on that field, and the alert period is defined during setup. - Document Collection Process | The monthly document expectation is a task tied to the taxpayer; because a task left incomplete does not close, it stays on the list, and the reminder is tied to that task. - Client Collections Tracking | The retainer and additional service lines sit under the taxpayer card; a line past its due date drops onto a list. Bank reconciliation is built specifically for the project; there is no out-of-the-box module. - Trainee and Staff Management | A trainee is a user record; which taxpayer's file they look after sits in the assignment field, and working hours are totalled from the task records. - KOSGEB and Incentive Tracking | The entitlement date is a field on the taxpayer record; those falling due drop onto a list and are opened as a quoting opportunity. - Submission Archive | The e-Beyanname, e-Defter and e-Fatura submission confirmation is added to the taxpayer record with its date and time. The GİB connection is built specifically for the project; there is no out-of-the-box module. ##### Frequently asked questions - Do I have to set up the tax return calendar separately for every client? | No. The tax regime is a field on the taxpayer record; the VAT, withholding, corporate, tax-at-source and provisional tax tasks are opened on that field. You define the alert periods once during setup, and when a new taxpayer is added the calendar builds itself. - Does it work with accounting software such as Logo, Mikro and Luca? | We build the connection; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export. The same applies on the GİB side: the submission confirmation is recorded on the record by hand, and there is no automatic connection that returns it. We work out the scope and the cost in the discovery call and share them in writing. - Can I see which trainee looks after how many taxpayers? | Yes. A trainee is a user record, and which taxpayer's file they look after sits in the assignment field. When taxpayers are grouped on that field, the number of files per person is read from a report; because the number of open tasks appears in the same breakdown, it is clear where the load is building up during tax return week. - Which is the best CRM software for Independent Accountants? | When choosing a CRM for the independent accountancy sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your accountancy process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Independent Accountant CRM system prices cost? | On the independent accountancy side a trainee is a user record; which file they look after is written into the assignment field. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the independent accountancy sector? | On the independent accountancy side the e-Beyanname, e-Defter and e-Fatura submission confirmation is added to the taxpayer record. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the independent accountancy sector? | We start with a discovery call: we work out your accountancy process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Independent Accountants? | Yes. Field and branch staff can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Insurance Agency CRM: Policy Renewal Tracking | Rapitek CRM](https://rapitek.com/en/insurance-agency-crm) The policy expiry date is a field; the 60-30-15-7 day steps open as tasks tied to that date, and all of a customer's lines sit on a single card. ##### What we set up, and how - Keep the policy expiry date in a field; let policies 60-30-15-7 days from expiry drop into a list, and tie the renewal message to that list with a rule - See a customer's existing policies on a single card and report the missing coverages; do not miss the moment to quote, with a task tied to the renewal date - Track every quote you give with its stage; tie the follow-up task to the time waiting in that stage - Tie a rule so that the customer is notified when a claim file changes stage; keep who was told what and when on the record - Connect your single WhatsApp business number to a team inbox and monitor response times under manager oversight - Policy Renewal Tracking | The policy expiry date is a field; the 60-30-15-7 day steps open as tasks tied to that date, and the steps are defined during setup. - Cross-Sell Lists | The lines a customer holds are a field on the customer card; customers with a missing line collect in a list filtered on that field and a quote opportunity is opened. - Quote Pipeline Management | Every quote is an opportunity record; time waiting in a stage is calculated from the record dates, and the follow-up task is tied to the stage. - Claim Process Tracking | A claim file is a record attached to the policy; as the stage changes the customer is informed, and who was told what and when stays on the record. - Endorsements and Coverage Changes | An endorsement made on a policy is a change line attached to the policy record; the changed coverage, the effective date and the premium difference sit in fields, and the notice sent to the customer is attached to the same line. ##### Frequently asked questions - What does a CRM give an insurance agency? | Policy renewal tracking, cross-sell opportunities, quote management and customer communication on one platform. Contact steps tied to the renewal date open as tasks; which step renewed how many policies is reported from your own data. - How do renewal reminders work? | Every policy's expiry date is a field on the record; policies 60, 30, 15, 7 and 1 day from expiry drop into a list based on that field. During setup you tie to a rule which step sends a message through which channel (WhatsApp, SMS or e-mail); the template takes the customer name, the policy type and the new premium from the record, and the send is written onto the same policy. - We work with more than one insurer, is that a problem? | No. It works in a multi-insurer structure. Each insurer's policies are tracked separately but the customer card is single. You see all of a customer's policies on one screen. - Can more than one person use the same WhatsApp number for an insurance agency? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [InsurTech CRM: Pilot Tracking, Compliance Review | Rapitek](https://rapitek.com/en/insurtech-crm) Evaluation, compliance review, pilot and contract are stages of the same opportunity record; how long each stage waited is calculated from the record dates and shows in the report. ##### What we set up, and how - Track insurer and agency opportunities in their own long sales pipeline - Tie the technical evaluation, compliance review and pilot steps to the opportunity - Keep the different decision makers at the same organisation on a single account card - Follow the scope and delivery steps of integration projects - See contract renewal and usage growth opportunities in time - Long-Cycle Sales Pipeline | Evaluation, compliance, pilot and contract are stages of the same opportunity record; the time waiting in a stage is calculated from the record dates and shows in the report. - Multi-Stakeholder Account | The people on the technical, compliance and business side are contact records attached to the same account; who said what stays in the account's history even when the representative changes. - Pilot Tracking | The pilot is a stage and carries its own tasks; the start and end dates sit in fields, and pilots that drag on collect in a list. - Integration Scope | An integration project is a record attached to the opportunity; the scope items and delivery steps are kept there. The connection is built specific to the project; there is no out-of-the-box module, it is built over the API. - Renewal and Growth | The contract end date is a field on the account record; the ones coming up drop into a list and the contact task is tied to that date. ##### Frequently asked questions - How do I track a long sales cycle? | Evaluation, compliance review, pilot and contract are stages of the same opportunity record. How long each stage waited is calculated from the record dates, so where the opportunity is really stuck shows in the report. - How do I manage different people at the same organisation? | The people on the technical, compliance and business side are separate contact records attached to the same account. Whoever a meeting note comes from, it stays in the organisation's history; when the representative changes, the information stays with the organisation. - How much does an InsurTech CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done on the InsurTech 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does moving to a CRM system work on the InsurTech side? | We start with a discovery call: we work out your insurtech process together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we train your team ourselves in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product - this is a choice, not a matter of capacity. - Can mobile CRM be used for InsurTech? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks 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 wrote is kept on the device for 24 hours. ### [Interior Design CRM: Concept Versions and Product Selection](https://rapitek.com/en/interior-design-crm) Every revision is a dated record under the project record; the approved version shows in the current-version field. In Rapitek CRM, an item whose supplier delivery date slips drops into a list. ##### What we set up, and how - Keep concept revisions version by version under the project record; take the customer's approval on the signature screen in the mobile app and mark the signed version as current - Attach the chosen products to the record item by item and track the supplier delivery date in the item's field - Plan the installation and delivery appointment as a task and send the customer's reminder from the same record - Report the site visit from the mobile app and add the photos of the space and the measurements to the project - Concept Versions | Every revision is a dated record under the project record; when the customer approves on the signature screen in the mobile app, that version shows in the current-version field, and the next change opens a new version. - Product Selection List | The chosen products are items attached to the project; brand, code and quantity sit in fields, and a changed selection is added as a new line without deleting the old item. - Supply Tracking | The supplier delivery date is a field on the item; items whose date has passed drop into a list, and the task to inform the customer is opened from there. - Curtain and Accessory Installation | The day the curtains, lighting and furniture are fitted is a task attached to the project record; the team, address and time are in fields, the item list under the task carries the products to be fitted that day, and the reminder sent to the customer is generated from that date. ##### Frequently asked questions - How do we prove which design the customer approved? | Every revision is stored under the project record with its own date; the customer gives approval on the signature screen in the mobile app and the signed version is marked on the record as the current version, while later changes open a new version. - Do we hear about it if a chosen product is delayed at the supplier? | Every product is an item attached to the project and the supplier delivery date sits in a field on the item; when the date passes, the item drops into a list, and the task to inform the customer and the alternative product line are opened from the same record. - Where does the team see which products are to be fitted on installation day? | Installation day is a task attached to the project record; the team, address and time are in fields and the item list under the task carries the products to be fitted that day. The reminder sent to the customer is also generated from that date. - Which is the best CRM software for interior design? | When choosing a CRM for the interior design sector, you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your process in interior design, we migrate your data ourselves, and we train your team ourselves in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does an interior design CRM system cost? | In interior design the person who goes out on the site visit writes the measurements and the photos into the project from the mobile app, so the field side is a user of the system too. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the interior design sector? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does moving to a CRM system work in the interior design sector? | We start with a discovery call: we work out your process in the interior design sector together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we train your team ourselves in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product - this is a choice, not a matter of capacity. - Can mobile CRM be used for interior design? | In interior design the site visit is reported from the mobile app; photos of the space and measurements are added to the project. 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 wrote is kept on the device for 24 hours. ### [IT Services CRM: Support Requests and Contracts | Rapitek](https://rapitek.com/en/it-services-crm) Every incoming support request is a record; its category, priority and the promised response time are its fields. The support hours the customer bought come down with every request closed. ##### What we set up, and how - Keep project stages, team assignments and the hours spent on the project in one place - Sort incoming support requests by category and priority and track them against the response time you promised - Follow maintenance contract and licence renewal dates together with the revenue forecast - Have the solution note written onto the request so that later requests opened with the same type are read from those records - Let the whole team reply over a single business number, with conversations assigned according to the rule you define and visible to the manager - Project and Resource Management | A project is a record; the stage and team assignment sit in its fields and the hours spent sit in the lines beneath it; which job an engineer booked how many hours to is read from those lines. - Support Request System | Every incoming support request is a record; its category, its priority and the response time target you promised your customer are fields on that record; requests past their target time collect in a single list by date and drop to the person responsible as a task. - Contract and Licence Tracking | The maintenance contract and the licence are records attached to the customer account; the renewal date and the amount are in fields, the ones with a date approaching drop into a list, and the revenue forecast comes out of that list. - Solution Note | The solution note is written onto the request and later requests opened with the same fault type are read from those records; technical notes specific to a customer sit on that customer's account record. - Support Hour Package Counter | The support hours the customer bought are a field on the contract record; the time booked to each closed request comes off that field, and a renewal task is opened for the person responsible before the package runs out. ##### Frequently asked questions - Where do we find the solution when the same problem comes in a second time? | The solution note is written onto the request; later requests opened with the same fault type are read from those records. Because the request's category and priority are fields too, similar requests collect in a single list. - How long does setup take for IT Services? | After the discovery call we give you a date, not a range - how many fields, how many stages and how many reports your IT services process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for IT Services? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for IT Services? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [IVF Clinic CRM: Cycle and Embryo Records | Rapitek CRM](https://rapitek.com/en/ivf-clinic-crm) Every day of the stimulation cycle is a line attached to the patient card; hormone values, ultrasound appointments and embryo records move in order in the same file. ##### What we set up, and how - Write the daily FSH, LH, estradiol and progesterone values onto the record in every cycle; let values outside the thresholds you define be flagged in the list - Record the embryos' quality score, cell count and day progression, and attach the transferred and frozen ones to the patient card - Run requests from patients coming from abroad on the same screen as accommodation, transfer and interpreter planning - Plan psychologist sessions according to the phases of the process, and start the support steps after a negative result through the rule you define - Open the beta hCG check as an appointment on day 12, and move onto the 40-week pregnancy schedule on a positive result - Stimulation and Hormone Tracking | Every cycle is a record; the daily FSH, LH, estradiol and progesterone values are entered into its fields, and values that fall outside the thresholds you define are flagged in the list. - Embryo and Laboratory Tracking | Every fertilised embryo is its own record; the quality score, the cell count and the day progression (day 3, day 5 blastocyst) sit in its fields, and transferred and frozen embryos are attached to the patient card. - International Patient Record | The patient's language of communication is a field on the record and the correspondence template is chosen according to that field; accommodation, transfer and interpreter planning are tasks attached to the same record. The interface is fully translated into Turkish and English; in other languages, untranslated text appears in English. - Psychological Support Plan | A psychologist session is an appointment attached to the patient record; cycle records with a negative result drop into a list and the support steps are opened according to the rule you define. - Pregnancy Confirmation and Follow-up | The beta hCG check opens on day 12 as an appointment tied to the transfer date; when the result field is marked positive, the patient moves onto the 40-week pregnancy schedule. ##### Frequently asked questions - How many days does an IVF cycle take and how does the CRM manage it? | It takes 28-45 days from the start of stimulation to the embryo transfer. Rapitek CRM attaches every day to the patient card: hormone injection reminders, ultrasound appointments and laboratory tests are dated lines on the cycle record; lines whose date has come drop into a list. During setup you tie to a rule which step sends the patient a notification through which channel. - Are there special features for patients coming from abroad? | The patient's language of communication is a field on the record and the correspondence template is chosen according to that field; accommodation, flight coordination and interpreter planning are tasks attached to the same record. Follow-up messages during the 12-day wait after the transfer also go out from this record. The interface is fully translated into Turkish and English; in other languages, untranslated text appears in English. - What happens after unsuccessful IVF attempts? | Cycle records whose result field is marked negative drop into a separate list; the suggestion of a psychologist appointment, the rest-period reminders and the preparation calendar for the next cycle are opened from that list according to the rule you define. - Is there embryo freezing and storage tracking? | Yes. For every frozen embryo, the quality, the freezing date, the storage tube number and the annual payment date are recorded. Embryos with an approaching payment date drop into a list based on that field; during setup you tie to a rule how many days in advance and through which channel the annual renewal notice goes out. ### [Jewelry CRM: Custom Orders and Gram Weight Lines | Rapitek](https://rapitek.com/en/jewelry-crm) On every quote line the carat, the gram weight and the workmanship charge are separate fields; when the customer returns days later, which figure was given on which weight is read from the line. ##### What we set up, and how - Collect the customer's contact history, meeting notes and records on a single card - Keep the quote's validity date in a field; let quotes nearing expiry drop into a list, and open the follow-up task from that list - Track open opportunities stage by stage and see which amount is waiting where - Measure sales performance, customer behaviour and team productivity with reports - Let the whole team reply on WhatsApp from a single business number; have conversations assigned according to the rule you define, with manager oversight kept - Reports and Dashboards | Because sales, contact and opportunity data sit in record fields, the performance report is taken directly with a breakdown by date and by person. - Carat and Gram Weight Line | On every line of the quote the item's carat, its gram weight and the workmanship charge are separate fields; when the customer consults their family and comes back days later, which figure was given on which gram weight is read from the line. - Tasks and Reminders | A follow-up is a task; its date and its owner are in fields, and the reminder tied to the quote validity date is defined during setup. - Sales Pipeline Tracking | An opportunity moves through its stages; which amount is waiting at which stage is read from the Kanban and the stage report. - Custom Manufacturing Order Slip | Wedding bands and sets made to order are their own manufacturing record; the ring size, the carat, the stone type and count, and the dates the piece went to the workshop and is due back are fields on that record; until the piece returning from the workshop is written onto the record, the order stays in an open stage and drops to the person responsible as a task. ##### Frequently asked questions - Where do I see a wedding band made to order while it is at the workshop? | Custom manufacturing is its own record; the ring size, the carat, the stone type and count, and the dates the piece went to the workshop and is due back are fields on that record. Until the piece returning from the workshop is written onto the record, the order stays in an open stage and drops to the person responsible as a task. - When the customer comes back days later, where do we see which price we discussed? | On every line of the quote the item's carat, its gram weight and the workmanship charge are separate fields; which figure was given on which gram weight is read from the line. Because the quote's validity date is a field, quotes nearing expiry drop into a list and the follow-up task is opened from that list - it does not stay in anyone's memory. - How long does setup take for jewelry? | After the discovery call we give you a date, not a range - how many fields, how many stages and how many reports your jewelry process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for jewelry? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - Can more than one person on a jewelry team use the same WhatsApp number? | On the jewelry side, correspondence with the buyer is collected on a single business number; conversations are assigned according to the rule, and manager oversight is kept. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [Jewelry Store CRM: Special Dates, Certified Stock | Rapitek](https://rapitek.com/en/jewelry-store-crm) Every piece is tied to one record by its certificate number; which supplier it came from and which customer it went to come out of one search. Special dates are fields on the customer card. ##### What we set up, and how - Keep the customer's birthday, wedding anniversary and their family's special days in a date field; let the approaching ones drop into a list, and tie the campaign contact 7-14 days ahead to that list with a rule - Match every product in stock together with its certificate number, gram weight, carat and stone properties - Write the customer's style, carat, stone and brand preference onto the profile; when a suitable product arrives, tie the notification with a rule to the list filtered on those fields - Stage the custom design order from draft to delivery and track the time with the designer and craftsman assignment - Enter the current gold gram price into the rate record and compare profit/loss against past sales' own price field - Important Date Reminder | The customer's birthday, wedding anniversary and the special days of their spouse and children are date fields on the customer record; the ones with a date approaching drop into a list, and the campaign task is opened from that list. - Certified Stock Management | Every product is a unique record with its certificate number; the gram weight, the carat (24K/22K/18K) and the stone's carat and cut are fields on that record, and the stock-certificate match is read on a single screen. - Customer Preference Profile | Style, carat, stone and brand preference are fields on the customer record; when a new product arrives, a list filtered on those fields is drawn up and the notification is tied to that list. - Model and Casting Stages | A custom design order carries the draft, wax model, casting, stone setting and delivery stages in its own field; the designer and craftsman assignment are fields on the record, and how many jobs are waiting at which stage is read from the list. - Loyalty and Referral Programme | Family connections (mother, daughter, daughter-in-law) are kept as relationships between customer records; because the spending total accumulates in a field, the special card and the referral bonus are given by filtering on that field. - Gold Gram Price Field | The current gram price is a rate record that you update; every sale stores that day's gram price in its own field, and the profit/loss comparison is read across those two fields. ##### Frequently asked questions - Does it provide traceability for every certified product? | Yes. Every certificate number is found with a single search: which supplier it was bought from, which customer it was sold to, and the carat/stone/gram weight details. Critical for warranty claims. - Can I do stock valuation against the live gold price? | The current gram price sits in the CRM in a rate record that you update; there is no out-of-the-box price feed module. We set up the feeding of that field from your own price source: the connection is built specific to the project over REST API, OAuth2, webhooks and import/export, and its scope is shared in writing in the discovery call. Stock valuation and the historical profit/loss comparison are done over that field. - How do we make contact without missing the customer's special day? | Birthdays, wedding anniversaries and the family's special days are date fields on the customer record; customers with an approaching date drop into a list based on those fields and the campaign task is opened from that list. During setup you tie to a rule how many days ahead (7 or 14) and through which channel the reminder goes out; the contact made is written under the same card. - How do you model family connections? | Customer-to-customer relationships (spouse, mother-daughter, daughter-in-law and mother-in-law) are managed as a tree. One family member's purchase turns into suggestions on the others' profiles. - What about KVKK and the confidentiality of certificate numbers? | Every customer's data is held in a separate database of your own, hosted in the European Union (Finland); it is encrypted in transit with current TLS, and passwords are hashed one-way with PBKDF2-SHA256 and 2FA secrets are stored encrypted at rest. Because the hosting is outside Turkey, this counts as a transfer abroad under KVKK art. 9; that is why we run disclosure and explicit consent processes. Certificate numbers are protected with role-based access - only authorised employees see them. ### [Label and Sticker Manufacturer CRM: Revisions | Rapitek](https://rapitek.com/en/label-company-crm) Which revision was approved sits on the order record; the material card and work order attach to the same order, and a purchase request for out-of-stock material opens from there. ##### What we set up, and how - Collect the order, the designer assignment, the customer approval and the revision history in a single flow; let a notification go out at every step - Keep thermal, vinyl, coated, opaque, transparent and holographic materials on separate cards; tie the opening of a purchase request for material not in stock to a rule during setup - Sort orders by priority and assign machine and staff, and get a warning for jobs running late - Enter the carrier and the tracking code onto the dispatch record on shipping day and inform the customer from the same record - Keep the customer's previous design and order history under their account, and open the new order by copying from the same card - Order and Design Approval Flow | An order is a record coming in from the web form or from WhatsApp; designer assignment, design upload, customer approval and revision are stages of the same record. Which version the approved revision is sits on the record, and a notification drops at every stage transition. - Print Type and Material Management | Thermal, vinyl, coated, opaque, transparent and holographic labels are each a material record; each card's price schedule and production time are in its fields. The order is attached to that card, and a purchase request for material not in stock is opened from the same order. - Production Planning and Work Order | A work order is a record with priority, machine, staff and estimated production time fields. The daily and weekly plan is a list of these records, and jobs past their delivery date stay open on the list. - Shipping and Logistics | The carrier, the dispatch date and the tracking code are fields on the order record; the day's bulk dispatch list and the customer notification come out of here. We build the connection to the courier companies ourselves; there is no out-of-the-box module. - Re-ordering | The customer's previous design and order history sit under their account; a new order is opened by copying from the same card, and the price comes from the price list the customer is attached to. ##### Frequently asked questions - Why is a label company CRM better than Excel? | In Excel the design revision history cannot be kept, material stock is not connected to production, and customer approval cannot be tracked. With a CRM the order, the design, the approval, the production and the dispatch are connected in a single flow. Because which version the approved design is sits on the record, an argument over a wrong print does not stay without evidence; you track the number of errors and delays from your own records. - Does it support different label types such as thermal, vinyl and coated? | Yes. For every label type a separate material card, price schedule, production time and machine assignment is set. When an order is taken it is assigned to the right production line according to the rule you define. - How do we manage orders coming in from WhatsApp? | On the label and sticker manufacturer side, an order coming in from WhatsApp is a record; approval and revision are stages of the same record. We connect your own Meta WhatsApp Business account to the CRM ourselves; there is no out-of-the-box module, the account linking is done during setup. Incoming messages drop into the team inbox and are written onto the customer card. The order form, the design PDF and the payment receipt are added to the same card as attachments, and the record is converted into a CRM order from a single screen. Meta bills you directly - we do not sell message packages or credits. If a connection beyond this is needed, it is built specific to the project over our REST API, OAuth2, webhooks and import/export; its scope and fee are shared in writing in the discovery call. - Is it integrated with courier companies? | We build the connection to Yurtiçi, Aras, MNG, UPS, DHL or Sürat Kargo ourselves; there is no out-of-the-box module. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export, and its scope and fee are shared in writing in the discovery call. As long as the connection is not built, the tracking code is taken from the courier company's own screen and entered onto the dispatch record by hand, or uploaded in bulk with an import file; the carrier, the dispatch date and the tracking code are fields on the order record, and customer notification and the tracking of undelivered items are generated from those fields. ### [Laboratory CRM: Sample Tracking and Calibration | Rapitek](https://rapitek.com/en/laboratory-crm) A sample is a record with its unique code; intake, analysis and approval stages are written onto the same record with their owner and time. The time from intake to result is calculated from it. ##### What we set up, and how - Take every sample onto a record with a unique code and see which stage it is at at any moment - Define a different process flow by test type, and attach the analyst responsible and the estimated time to the record - Tie to a rule that a notification goes to the customer when the result stage is reached; keep who was informed when on the record - Keep the contracts and agreed prices of hospital, clinic and industrial customers on the customer card - Send the sample collection confirmation and the result notification over WhatsApp - Sample Intake and Tracking | A sample is a record with its unique code; which stage it is at sits in a field, and the time elapsed from the intake hour to the result is calculated from the record. - Test Process Management | Every test type uses its own stage flow; the analyst responsible and the estimated time are kept as fields on the record. - Result Notification System | A notification is sent when the result stage is reached; who was informed when leaves a trace on the sample record. The trigger is defined during setup. - Retained Sample Storage and Disposal | The retained sample left over from the analysis is a separate line attached to the main sample record; the cabinet and shelf position where it is stored, the end day of the storage period and the person who carried out the disposal are fields on that line; retained samples whose period has expired drop into a list by date and the disposal task is opened for the person responsible. - Instrument Calibration Calendar | Every instrument is a record; the last calibration date and the interval sit in its fields, the maintenance task is opened before the period expires, and which test was done on which instrument is read from the sample record. ##### Frequently asked questions - Can I manage different test types? | Yes. Medical, food, environmental and industrial tests are defined as separate record types; different fields and different stage flows are configured for each during setup. - Is accreditation document tracking done? | Yes. The documents and periodic processes you keep for accreditation are defined as records, fields and tasks; which fields are made mandatory is determined during setup according to your own accreditation scope. - Does the customer get word when the result is ready? | Which stage the sample is at is a field on its record; during setup you tie to a rule that a notification is sent when the result stage is reached. You define which channel (e-mail or WhatsApp) and which template it goes out with; who was informed when leaves a trace on the sample record. - Is laboratory data safe? | Your CRM data is held in a separate database of your own, and access is limited on a role and permission basis. The hosting is in the European Union: the database in Finland, the media files in Frankfurt. This counts as a transfer abroad under KVKK art. 9; that is why we run disclosure and explicit consent processes. - How long does setup take for a laboratory? | After the discovery call we give you a date, not a range - how many fields, how many stages and how many reports your laboratory process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. ### [Landscaping CRM: Maintenance Visits, Site Verification](https://rapitek.com/en/landscaping-crm) The visits in the maintenance contract open at the start of the season as dated tasks; the field team closes the task from the mobile app, and location check and photo sit on the same record. ##### What we set up, and how - Run the installation job with its stages on a single record, from the site survey to the quote and from the design to the handover - Open the periodic visits in the maintenance contract as tasks up front, according to the seasonal calendar - Let the field team close the visit with a location check; have the photo of the work done and the signature of the person receiving it added to the same record - Keep plant warranty periods and contract end dates on the record and start the renewal conversation in time - Installation Project | The site survey, the quote, the installation and the handover are stages of a single project record; the plant list and the irrigation plan sit as attachments to that record. - Maintenance Contract and Visit Tasks | The contract is a record with a start and an end date; the visits inside it are dated tasks, and the season's plan is the list of those tasks. - Site Verification | The visit task is closed from the mobile app; the location check, the photo attachment and the signature the person receiving the work gives on the signature screen in the mobile app all collect on the same task record, and spoofed location reports are detected. - Warranty and Renewal Tracking | The plant warranty period and the contract end date are each a field; the ones approaching expiry drop into a list, and the renewal conversation is started from that list. ##### Frequently asked questions - How do we verify that the maintenance team actually went to the site? | Every periodic visit is a task record and the field team closes that task from the mobile app; at the moment of closing a location check is carried out and spoofed location reports are detected. The photo of the work done and the signature of the person receiving it stay under the same task. - Where do we see whether a plant that has died is covered by the warranty? | The plant warranty period is a field on the installation record; because the handover date and the period are kept together, whether the cover still runs is read from the record. And because the same customer's maintenance visits are listed underneath, what was done on the last visit can be seen. - Can we plan the season's maintenance visits up front? | Yes. The maintenance contract is a record with a start and an end date; the visits inside it are opened as dated tasks at the start of the season. Which team goes to which site in which week is read from that task list, and a visit that is not closed stays on the list. - Which is the best CRM software for landscaping? | When choosing a CRM for the landscaping sector, you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your landscaping process, we migrate your data ourselves, and we train your team ourselves in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a landscaping CRM system cost? | In landscaping the field team closes the maintenance visit itself, so the team in the garden goes into the system just as much as the people in the office. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the landscaping sector? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does moving to a CRM system work in the landscaping sector? | We start with a discovery call: we work out your landscaping process together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we train your team ourselves in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product - this is a choice, not a matter of capacity. - Can mobile CRM be used for landscaping? | In landscaping the field team closes the maintenance visit from the mobile app; the location check and the photo sit on the same record. 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 wrote is kept on the device for 24 hours. ### [Language School CRM: Trial Lessons and Exam Tracking](https://rapitek.com/en/language-school-crm) The person who comes to a trial lesson is a candidate record; the 24, 48 and 72 hour follow-up steps are tasks attached to that record. Level and target exam date sit as fields on the same card. ##### What we set up, and how - Follow up a student who has come to a trial lesson with 24-48-72 hour steps over WhatsApp, e-mail and SMS - Track level progression from A1 to C2, level-up tests and achievement reports - Set up a countdown against the TOEFL/IELTS target date and see mock test results and weak topics on one screen - Manage online lessons on the same calendar as the face-to-face lessons at the branch; the meeting link sits in a field on the lesson record - Draw up upper-course lists from existing students' level and course history fields; tie the offer message to that list with a rule - Trial Lesson and Enrolment Conversion | The person who comes to a trial lesson is a candidate record; the 24, 48 and 72 hour follow-up steps are dated tasks attached to that record and are sent over WhatsApp, e-mail or SMS. - Level Tracking | The student's A1-C2 level is a field on the student record; the result of the level-up test is written into the same field, and the progress report comes out of that field. - TOEFL/IELTS Exam Tracking | The target exam date is a field on the student record; reminder tasks at 3, 2 and 1 month before are tied to that date, and mock test results and weak topics accumulate on the same card. - Online and Face-to-Face Hybrid Management | A lesson is a record in the CRM; the meeting link for an online lesson is written into a field on the record and sits on the same calendar as the branch-based face-to-face lessons. We build the connection to video lesson tools ourselves; there is no out-of-the-box module. - Conversation Club and Upselling | The conversation club, private lessons and the intensive course are each a quote item; students who are a fit drop into a list according to their level and course history fields. - Bring a Friend Programme | The referring and the referred student are kept in two separate fields on the same record; bonus tracking is read from that link and the offer task is opened from that list. - Level Completion Certificate Record | The certificate of a student who has completed a level is a certificate record attached to the student record; the level, the issue date and the document number sit in fields, and certificates not yet handed over stay open on the list. ##### Frequently asked questions - Why is a CRM critical for language schools? | In education sales the decision process is 1-4 weeks. If you do not follow up regularly with the person who came to the trial lesson during that time, you lose them. A CRM is also essential for selling upper courses to existing students and for the referral programme. - How does TOEFL/IELTS student tracking work? | Every student's target exam date is a field on the record. Reminder tasks at 3, 2 and 1 month before the exam are tied to that date; mock test results and weak topics accumulate on the same card. - Is there placement test integration? | We build the connection to online placement test tools ourselves; there is no out-of-the-box module. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and fee are shared in writing in the discovery call. As long as the connection is not built, the test results are entered with an import file or by hand; the student's level, target exam and recommended course package are still kept on the student record, and the next-step reminders are generated from there. - How do you manage online and face-to-face lessons? | We build the connection to Zoom, Google Meet or another video lesson tool on request; there is no out-of-the-box module. A lesson is a record in the CRM: the meeting link for the online lesson is written into a field on the lesson record, it appears on the same calendar as the face-to-face lessons at the branch, and attendance is written onto the student record. If you want a connection with the meeting tool, it is built specific to the project over our REST API, OAuth2 and webhooks; its scope and fee are shared in writing in the discovery call. - How is an upper-course offer taken to an existing student? | The student's level, target exam and course history are fields on the record; students suited to the conversation club, private lessons or the intensive course are filtered on those fields and drop into a list. During setup you tie to a rule when and through which channel the offer message goes to that list. - How long does setup take for language schools? | After the discovery call we give you a date, not a range - how many fields, how many stages and how many reports your language school process needs becomes clear in that call. We migrate your existing student data ourselves; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Can more than one person use the same WhatsApp number for language schools? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [Laser Hair Removal Center CRM: Session Balance | Rapitek](https://rapitek.com/en/laser-hair-removal-center-crm) A package is an area-based record on the customer record; every session is written under it and sessions left are calculated from it. The next appointment derives from the repeat interval field. ##### What we set up, and how - Open each customer's package area by area and see the sessions used and the sessions left at any moment - When the area's repeat interval comes due, plan the appointment around device and staff availability - Send a WhatsApp and SMS reminder 24 hours before the appointment, and reduce confirmation and postponement to a single step - Tie the loyalty points on package completion and the discount for a customer who came by referral to a rule during setup - Report which device was used in which session and the number of sessions per member of staff per day - Package and Session Balance Tracking | A package is an area-based record attached to the customer record; every session is written under it, and the sessions left are calculated from that record. - Area-Based Appointment Management | The area's repeat interval is a field; the next appointment date is derived from that field, and device and staff availability are checked on the appointment record. - Appointment Reminder | The reminder is sent based on the appointment date; confirmation and postponement are processed over the same record, and no-shows stay on the list. - Loyalty and Referral Programme | Points and referrals are fields on the customer card; when a package is completed, the discount definition is set up during setup tied to those fields. - Device and Staff Performance Report | The session record carries a device field and a staff field; the daily session count and a broken-down comparison come out of a report on those fields. ##### Frequently asked questions - How is customers' package balance tracked? | On every customer card, the packages purchased, the areas each package covers and the numbers of sessions left are visible at any moment. Packages whose remaining sessions fall below the threshold drop into a list; the renewal offer is drawn from that list, and during setup you tie to a rule how many sessions ahead the reminder goes out. - How do you reduce appointment no-shows? | A reminder is sent over WhatsApp and SMS 24 hours before the appointment. The customer can confirm or postpone in a single step; both are processed onto the same appointment record, and those who do not turn up stay on the list. You define how many hours ahead and how many times the reminder goes out. - Is there session tracking per device? | Yes. For every session the device used, the member of staff performing it, the duration and the customer satisfaction score are recorded. The device's maintenance timing and how heavily it is used are read from a report on those fields. - What can I do with the WhatsApp Business API? | We connect your own Meta WhatsApp Business account to the CRM; appointment reminders, post-session feedback surveys, package renewal offers, campaign announcements and referral programme messaging all run from here. Every message is written onto the customer card. Meta bills you directly - we do not sell message packages or credits. ### [Leather CRM: Batch Shade, Samples, Quality Grade | Rapitek](https://rapitek.com/en/leather-crm) Batch number, shade and quality grade are fields on the order record; the approved sample is written onto the same card, and the square-decimetre price comes from the account field. ##### What we set up, and how - Write the batch number, the shade that came out and the quality grade onto the order record; see which buyer approved which batch - Record the approval status of the leather sample sent to the customer and any objection that comes back - Keep the unit price per square decimetre and the discount that varies by quality grade on the customer account, and carry them into the quote from there - Track shoe, furniture and garment buyers in separate segments and put a quote to each with their own quality expectation - Batch and Shade Tracking | The batch number and the shade that came out are fields on the order record; because the approved batch is written onto the card, it is read from the same record on the next order. - Sample Approval | A sample that has been sent is a stage of the order; the approval date and the note that came back sit on the same record, and samples left unanswered drop into a list. - Quality Grade and Price | First and second grade are separate price lines; the unit price per square decimetre sits in a field on the customer account and comes into the quote from there. - Export Buyer | An overseas buyer is an account record with its own currency field; the shipment and collection lines accumulate under that account. ##### Frequently asked questions - Can I record that the same colour comes out differently in different batches? | Yes. The batch number and the shade that came out are fields on the order record; which batch the customer approved is written onto the card and is looked up on that record for the next order. - Can I price leather per square decimetre? | Yes. The unit price and the discount tied to the quality grade are kept in fields on the customer account; the quote line takes the price from those fields, so no manual calculation is done on every quote. - Can we see it on a list when no answer comes back to a sample we sent? | A sample that has been sent is a stage of the order; as long as the approval date field stays empty, the record stays on the list of unanswered samples and the follow-up task is opened from that list. - Which is the best CRM software for leather? | When choosing a CRM for the leather sector, you should look at sector workflows, integration capabilities, customisation options and support quality. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your leather process, we migrate your data ourselves, and we train your team ourselves in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a leather CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the leather sector? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does moving to a CRM system work in the leather sector? | We start with a discovery call: we work out your leather process together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data ourselves, and we train your team ourselves in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product - this is a choice, not a matter of capacity. - Can mobile CRM be used for leather? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks 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 wrote is kept on the device for 24 hours. ### [Legal CRM: Hearing Calendar and Time Records | Rapitek CRM](https://rapitek.com/en/legal-crm) Every case file is a record attached to the client; the hearing date is a field on it. Time worked is a line attached to the file and activity, and draft invoice items come out of those lines. ##### What we set up, and how - Collect every file on a single record together with its documents and process steps - Keep the hearing date in a field on the file; let upcoming ones appear on the shared calendar and on a list, and tie the reminder to that date with a rule - Record your working time line by line on a file and activity basis; build the draft invoice items from those lines - Send the client a notification when the file's stage changes, and keep every piece of information sent under the file - Connect a single WhatsApp number to the team's shared inbox, with conversations assigned according to the rule you define - Case File Record | Every case file is a record attached to the client; the case number, the court and the stage are in fields on that record, and the documents sit as attachments to the same record. - Hearing Calendar | The hearing date is a date field on the file; upcoming hearings appear on the shared calendar and on a list, and the reminder is tied to that date. - Time Record | Time worked is a line attached to the file and the activity; if an hourly rate is defined, the draft invoice items are built from the total of those lines. - Client Notification | The file's stage is a field; when the stage changes, the notification that goes to the client is tied to that field during setup, and every piece of information sent leaves a trace under the file. - Power of Attorney and Authority Record | The power of attorney taken from the client is a record attached to the file; its scope, the date it was drawn up and which files it was used in sit in fields, and a dismissal or a withdrawal leaves a trace with its date on the same record. ##### Frequently asked questions - How is file tracking done? | You can create every file attached to a client, upload the relevant documents, define the process steps and add the hearing dates. The whole communication history is recorded on the file. - How does time tracking feed into invoicing? | You record the time you work line by line on a file and activity basis. If your hourly rate is defined, the draft invoice items are built from the total of those lines; the draft is generated when you start it and is edited before it is issued. - What is done so that a hearing date is not missed? | The hearing date is a date field on the file; upcoming hearings appear on the shared calendar and on a list. During setup you tie to a rule how many days ahead and to whom the reminder goes; there is no connection that pulls the dates from an external system such as UYAP - your team enters the date or imports it. - When a client asks "what is the state of my case", where do we give the answer from? | The file's stage is a field on the record; everyone in the office sees it from the same card. When the stage changes, the notification that goes to the client is tied to that field during setup, and every piece of information sent leaves a trace under the file. - Can more than one person on a legal team use the same WhatsApp number? | On the legal side, client correspondence is collected in the team's shared inbox and conversations are assigned according to the rule. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [LegalTech CRM: Pilot and Data Processing Review | Rapitek](https://rapitek.com/en/legaltech-crm) The pilot is an opportunity record with its own stages; duration, user count and objections are its fields. The privacy review sits in the same record as a separate approval step. ##### What we set up, and how - Collect demo requests in a single queue and drop them to the relevant sales owner through the assignment rule defined during setup - Run the pilot in a record with its own stages; keep the duration, the user count and the objections raised on the same card - Define the privacy and data processing review as a separate approval step and track which clause it is waiting on - Keep the firm's lawyer and licence counts in account fields and open the renewal task tied to the contract end date in advance - Firm and Legal Department Account | The buyer is an account record; the number of lawyers, the licence count and the contract end date are its fields, and the renewal amount is calculated from them. - Pilot Management | The pilot is an opportunity record with its own stages; the start and end date, the number of pilot users and the objections sit on the same card. - Privacy and Data Processing Review | The review is an approval step; its owner and the pending clause are fields, and the document sent stays attached to the record. - Post-Demo Contact Tasks | Contacts after a demo request are opened as tasks; each step's date and owner are its fields, and when a reply arrives the remaining tasks are closed and the record falls to its owner. ##### Frequently asked questions - Can we track the pilot separately from the opportunity? | The pilot is opened as a record with its own stages: the start and end date, the number of pilot users and the objections raised are its fields. Because it sits under the same opportunity, how far the pilot has stretched and which objection has not been closed are visible in the report. - How do we track the customer's privacy and data processing review? | The review is defined as a separate approval step; the person responsible, the pending clause and the document sent are kept as fields on the record. That way the sentence "legal is still looking at it" turns into which clause has been waiting and for how many days. - Can I see the renewal in advance when the firm's number of lawyers changes? | Yes. The number of lawyers, the licence count and the contract end date are fields on the account record; the renewal amount is calculated from those fields and the renewal task tied to the end date is opened in advance. The change shows up on the record itself, not while the invoice is being issued. - Which is the best CRM software for LegalTech? | When choosing a CRM for the LegalTech sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your LegalTech sales process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a LegalTech CRM system cost? | On the LegalTech side, demo requests are collected in a single queue and land on the relevant sales owner through the assignment rule defined during setup; it is this sales team that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the LegalTech sector? | On the LegalTech side, how many users actually logged in during the pilot sits on the product side, while the objections sit in e-mail. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the LegalTech sector? | We start with a discovery call: we work out your LegalTech sales process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for LegalTech? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Logistics CRM: Route Pricing and Delivery Proof | Rapitek](https://rapitek.com/en/logistics-crm) Route, tonnage and vehicle type are fields on the quote line; the price comes from a predefined list. Each incoming request lands in the same pool as a record, along with its channel. ##### What we set up, and how - Collect and manage requests coming from e-mail, telephone and the website in a single request pool - Keep route, tonnage and vehicle type in the fields of the quote line; have the unit price calculated from a predefined price list - Split your customer portfolio into segments and identify your most profitable customers - Track and report service level commitments on a per-customer basis - Collect incoming WhatsApp conversations on a single business number and distribute them within the team according to the rule you define - Request Management Centre | Requests coming from e-mail, telephone and the website land in the same pool as records; because the source is written in its field, what each channel brought is visible in the report. - Route-Based Pricing | Route, tonnage and vehicle type are fields on the quote line; the price comes from a predefined list, so no manual calculation is made for each quote. - Customer Portfolio Analysis | Segment is a field on the account record; because revenue and trip count accumulate under the card, the most profitable customers are ranked in the report. - Service Level Tracking | The delivery time you promised your customer is a field on the record; it is compared with the dates of the trip records and delays are collected in the report. - Delivery Confirmation and Signature Record | Who the load was delivered to and at what time sit in the fields of the trip record; the person receiving it signs on the signature screen in the mobile app, and that the delivery was made at the right point is confirmed by location verification. ##### Frequently asked questions - How does a quote go out quickly? | Route, tonnage, vehicle type and additional services are fields on the quote line; the unit price comes from the price list you have defined in advance, and the line total is calculated from those values. That way the quote goes out with the same figure even when the person who knows the calculation is not at their desk; there is no engine that updates the price by itself — you set the list values. - Does it integrate with my vehicle tracking system? | If you use a vehicle tracking system, your CRM talks to it — we build the connection; there is no out-of-the-box module. The connection is built specifically for your project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. As long as the connection is not built, location and trip information is entered with an import file or by hand; route, tonnage, vehicle type and delivery time are still kept in the fields of the trip record in the CRM, and reminders are generated from there. - Is there multi-branch management? | Yes, you can manage all your branches on a single platform, run branch-based performance analysis and get central reporting. - Can more than one person use the same WhatsApp number for logistics? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even when staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Manufacturing CRM: Quote Revisions, Due Dates | Rapitek](https://rapitek.com/en/manufacturing-crm) Every revision of the quote is a separate version; price, due date and send date are its fields, earlier versions are not deleted, and the order is born from the due date field. ##### What we set up, and how - Record the incoming request together with the technical drawing and the specification, and produce the quote directly from that record - Keep every revision of the quote as a separate version; see retrospectively on which date it was sent, with which price and which due date - Keep the delivery date given to the customer in a field on the quote so that sales and planning read the same date - Tie spare part and warranty requests to the order number and gather the whole history of the same job on one card - Request and Technical File | The customer request is a record; quantity, material and tolerance are its fields, and the drawing and the specification attachment sit on the same card. - Quote Revision | Every revision is a separate version of the quote; price, due date and send date are its fields, and earlier versions are not deleted. - Due Date Field | The delivery date is a field on the quote; the order is born from that field, and a change of date is written to the record as an update. - After-Sales Request | Spare part and warranty applications are request records; the order number is carried in a field, and the history of the job is collected in a single list. ##### Frequently asked questions - We are on the fifth revision of the same quote; can we see retrospectively which price was sent on which date? | Yes. Every revision is stored as a separate version of the quote; price, quantity, due date and send date are fields on that version. Because earlier versions are not deleted, when the customer brings up an old figure, what was written on which date is read from the record. - The delivery date sales gave the customer does not match planning's date; how does the CRM solve this? | The due date is a field on the quote record, and the order is born from that field. When the date is to be changed, this is written to the record as an update and a task falls to the relevant person; so the date told to the customer and the date discussed internally are read from the same record. - Can we tie spare part and warranty applications to the relevant order? | Yes. Spare part and warranty applications are request records and carry the order number in a field; the quote, the order and the later requests for the same job are collected in a single list. - Which is the best CRM software for manufacturing? | When choosing a CRM for the manufacturing sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your production process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a manufacturing CRM system cost? | In manufacturing, because sales and planning read the delivery date from the same record, people from both departments log into the system together. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the manufacturing sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the manufacturing sector? | We start with a discovery call: we work out your production process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for manufacturing? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Marina CRM: Winter Storage and Documents | Rapitek](https://rapitek.com/en/marina-crm) Berthing, winter storage and haul-out requests are separate records; boat length, period and block position are their fields. Insurance and seaworthiness expiry sit on the boat record. ##### What we set up, and how - Gather every boat owner's contact history and the team's notes on a single customer card - See opportunities stage by stage, and measure where the sales cycle stretches along with the forecast - Keep insurance and seaworthiness certificate expiries on the boat record and see the expired ones in a single list - Compare sales performance, customer behaviour and team productivity through reports - Connect a single WhatsApp business number to the team inbox and move messaging off personal phones - Berthing and Winter Storage Request | Every berthing or winter storage request is its own record; the boat's length, the period requested and the stage the request is waiting at sit in the record's fields; when the season closes, the boat owners who did not come back are filtered from those same fields. - Transit Boat Arrival | A separate record is opened for a transit boat arriving for a short stay; the arrival and departure date, the boat's length and the services taken sit in its fields; the boat owners to be called before the season are filtered from those dates. - Boat Service History | Every boat is its own record; engine maintenance, paint and technical service jobs accumulate under that record with their dates. Because the same owner's two boats sit in separate records, what the harbour office and the technical team said about which boat does not get mixed up. - Insurance and Document Term | The expiry day of the boat insurance and of the seaworthiness certificate are fields on the boat record; boats whose term has run out are collected in a single list by date, and the message written to the owner is recorded against the same record. - Haul-Out and Lift-Ashore Work Order | A separate work order record is opened for every boat hauled ashore; the haul-out date, the boat's length and tonnage, the block position where it stands ashore and the launch date are fields on that record; the antifouling paint and underwater hull work to be done while the boat is ashore are task lines tied to the same work order. ##### Frequently asked questions - Where do we track the work done while the boat is ashore? | A separate work order record is opened for every boat hauled ashore; the haul-out date, the boat's length and tonnage, the block position where it stands ashore and the launch date are fields on that record. Antifouling paint and underwater hull work are task lines tied to the same work order; which job has been finished is read from the list. - Can I see in advance the boats whose insurance or seaworthiness certificate is expiring? | Yes. The expiry day of both documents is a field on the boat record; boats whose term has run out are collected in a single list by date, and the message written to the owner is recorded against the same record. - How long does setup take for a marina? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your marina process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for a marina? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person on the marina team use the same WhatsApp number? | On the marina side, messaging with the boat owner moves off personal phones and is gathered in the team inbox. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even when staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Maritime CRM: Port Calls and Shift Handover | Rapitek](https://rapitek.com/en/maritime-crm) A port call's preparation steps — provisions, paperwork, survey — are dated tasks on the shipowner account; open ones show in one list at handover, messaging in a shared inbox. ##### What we set up, and how - Keep the shipowner and the agency on an account record, and the voyage and the port call on records tied to that account - Split the port call preparation steps into dated tasks and see from the list at shift handover who still has one open - Follow freight and service quotes through their stages, and accumulate notes from past port calls under the same account - Gather the messaging in a shared inbox and set up the watch rota with shift and working hour definitions - Voyage and Port Call | The port call is a record with ship, port and date fields, tied to the shipowner account, and earlier port calls are listed under that same account. - Preparation Tasks | Provisions, paperwork and survey steps are dated tasks tied to the port call; the ones left open are visible in a single list at shift handover. - Shared Inbox | The messaging sits not in a personal mailbox but in the shared inbox under the account; the assignment rule defined during setup drops it to the team on watch. - Quote Stages | A freight or service quote is a record that moves through its own stages; its validity date is a field, and quotes whose term has run out fall into a list. ##### Frequently asked questions - How do we hand over the jobs left open at shift handover? | The port call's preparation steps are dated tasks; at handover the person taking the watch looks at the list of open tasks, and because the messaging also sits in the shared inbox, where the conversation stands does not depend on a personal mailbox. - Can we see what happened on earlier voyages with the same shipowner? | Yes. Every voyage and port call is a record tied to the shipowner account; past port calls, the tasks opened at those calls and the messaging are listed under the same account, and this history is looked at while a new quote is being prepared. - Do expired freight quotes get overlooked? | The quote's validity date is a field; quotes past their date fall into a list by that field, and which shipowner's and which port call's quote it is, is read from under the same account. - Which is the best CRM software for maritime? | When choosing a CRM for the maritime sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your maritime process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a maritime CRM system cost? | In maritime, because the messaging sits in the shared inbox and drops to the team on watch, the people on shift are defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the maritime sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the maritime sector? | We start with a discovery call: we work out your maritime process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for maritime? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Media CRM: Ad Break Bookings and Media Plans | Rapitek](https://rapitek.com/en/media-crm) A booking is a record with inventory unit, air date and status fields. Because bookings on the same date appear in one list, a clash is noticed before the sale closes. ##### What we set up, and how - Keep the brand and the agency representing it on separate account records and tie the commission rate to the agency record - Track ad break, page or impression bookings through the option, confirmed and aired statuses - See bookings falling on the same air date in a single list and catch the clash before the sale closes - Write post-broadcast performance values to the campaign record and draw the period report from those records - Advertiser and Agency Split | The brand and the agency are separate account records and are linked to one another; the commission rate is a field on the agency record and reaches the quote from there. - Inventory Booking | A booking is a record; the inventory unit, the air date and the status (option / confirmed / aired) are its fields, and bookings falling on the same date appear in a single list. - Media Plan | A campaign is a record; the booking lines tied to it make up the plan, and the budget and the discount sit on the campaign card. - Post-Broadcast Reporting | The post-broadcast result values are written to the fields of the campaign record; the period breakdown is taken from the report of those records. ##### Frequently asked questions - Both a brand and its agency work with us; how is that set up? | The brand and the agency are separate account records and are linked to one another. Whichever one the quote is given through, the commission rate comes from a field on that record; the brand's total investment is read from the report of the linked records. - How do we stop the same ad break or page being sold twice? | A booking is a record with inventory unit, air date and status fields. Its status is kept as option, confirmed or aired; because records falling on the same date appear in a single list, a clash is noticed at the quote stage, and an option whose term has run out drops off the list. - When a campaign ends, what do we draw the period report from? | A campaign is a record; the booking lines tied to it make up the media plan, and the budget and the discount sit on the campaign card. Post-broadcast values are written to the fields of the same record, and the period breakdown is taken from the report of those records. - Which is the best CRM software for media? | When choosing a CRM for the media sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your media sales process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a media CRM system cost? | In media, because the booking sits on a shared record rather than in the salespeople's own spreadsheet, the whole sales team looks at the same list. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the media sector? | In media the counterpart the CRM will talk to is the broadcast management system or the ad server. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the media sector? | We start with a discovery call: we work out your media sales process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for media? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Medical Centre CRM: Specialty Calendars, Referrals | Rapitek](https://rapitek.com/en/medical-center-crm) A referral is a job with its own record, tied to the patient card; the history and the test result are seen from the same card in the new specialty, and open referrals stay on the list. ##### What we set up, and how - Set up a separate calendar for each doctor; define the specialty rules (cardiology 30 min, internal medicine 20 min) and the room assignment, and let clashes and overloading be prevented by the rule set during setup - Run cross-specialty referral inside the CRM on a single record; because the patient card, the medical history and the test results are tied to the same record, they appear on the screen of the physician in the new specialty, and let incomplete referrals stay open on the list - Upload laboratory and imaging results to the patient card as PDF and image files and open them from the doctor's screen - Issue the invoice to the right specialty, with each specialty's own price list, package and contracted institution rate - Gather the patient's appointment, report and invoice history on a single card; tie a new incoming request to the same record and assign it to its owner - Multi-Specialty Doctor Calendar | Every doctor carries their own calendar; the appointment length and the room are defined in the specialty's fields, and the clash rule is set up during setup. - Referral Within and Across Specialties | A referral is a record; because it is tied to the patient card, the medical history and the test result are seen from the same card in the new specialty, and referrals that are not closed stay on the list. - Laboratory and Imaging Results | The result file is an attachment on the patient record and is opened from the doctor's screen. We build the connection to the device, LIS, PACS or RIS side; there is no out-of-the-box module, the connection is built specifically for your project over the REST API, and until it is built the results are added with an import file or by hand. - Specialty-Based Invoicing | Each specialty's price list and contracted institution rate are defined separately; because the procedure record carries a specialty field, the invoice is produced from the right list. - Patient Card History | The appointment, report and invoice history sits on the patient card; a new incoming request is tied to the same record and assigned within the team according to the rule you define. ##### Frequently asked questions - From a CRM point of view, what is the difference between a medical centre and a single-specialty clinic? | A medical centre is a multi-specialty, multi-doctor, multi-floor structure — it needs cross-specialty referral, a shared laboratory and shared reception management. It involves more complex flows, clash management and report flow than a single-specialty clinic. Rapitek CRM suits both. - Does it integrate with laboratory and imaging systems? | We build the connection to LIS, PACS, RIS or your local laboratory software; there is no out-of-the-box module, and we do not claim HL7 or DICOM protocol support. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; which system covers what, the scope and the cost are shared in writing in the discovery call. As long as the connection is not built, results are added with an import file or by hand; the result file sits as an attachment on the patient record, which test is still pending is kept in the CRM, and follow-up reminders are generated from there. - Is there contracted institution (SGK, private insurance) integration? | We build the connection to the SGK MEDULA or the private insurance side; there is no out-of-the-box module, and we do not have a product called a "separate module" or a "compatible module" either. The connection is built specifically for your project over our REST API, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. As long as the connection is not built, authorisation and approval information is entered with an import file or by hand; the contracted institution definition, the price tariff per institution and the institution report are still kept in the CRM, and the institution tag on the patient card is processed according to that definition. ### [Medical Device CRM: Calibration and Demo Tracking | Rapitek](https://rapitek.com/en/medical-device-crm) Every unit in the hospital is a separate record carrying a serial number; installation, warranty expiry and calibration period are its fields, and service calls accumulate on that number. ##### What we set up, and how - Keep every unit installed in a hospital on a separate record with its serial number; see the installation date, the warranty expiry and the responsible technician on the same card - Track which clinic a demo or consignment device is in, with whom and since when, and tie the expected return day to a task - Keep the calibration period and the periodic maintenance scope as fields, and run contracts whose end is approaching from a single list - Tie the service call to the unit's serial number; let the technician close the job from the mobile app and the person receiving it sign on the signature screen in the mobile app - Installed Device Inventory | Every unit in the hospital is a record with a serial number; the installation date, the warranty expiry and the responsible technician are its fields, and it sits under the account. - Demo and Consignment Tracking | A device left on loan is the same kind of record; the clinic it is in, the date it went out and the expected return day are fields, and returns past their day fall into a list. - Calibration and Maintenance Contract | The contract is a record tied to the account; the scope, the period and the end date are fields, and an approaching end turns into a task. - Service Call | A fault report is a request record; the serial number is carried in a field, and all the calls for the same unit are collected in a single list. ##### Frequently asked questions - Can we track where the devices we left at the hospital for demo are? | Yes. A demo device is also a record with a serial number; the hospital it is in, the representative who delivered it, the date it went out and the expected return day sit in its fields. Units past their return day are collected in a separate list and a follow-up task is opened for each one. - Can I see all the service and calibration history of the same device over the years in one place? | Yes. Because service call and calibration records are tied to the unit's serial number, when the device card is opened the history appears chronologically; which part was replaced and when also stays on the same record. - Can we see in advance the hospitals whose maintenance contract is ending? | Yes. The maintenance contract is a record tied to the hospital account; the scope, the period and the end date are its fields. Those whose end is approaching fall into a list, and the renewal conversation is opened as a task from the same record. - Which is the best CRM software for medical devices? | When choosing a CRM for the medical device sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your medical device process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a medical device CRM system cost? | In medical devices, because the technician responsible for each unit is written on the record, the people in the service team are defined separately in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the medical device sector? | In the medical device business the counterpart the CRM will talk to is the ERP or the hospital information system. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the medical device sector? | We start with a discovery call: we work out your medical device process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for medical devices? | In the medical device business the technician closes the service call from the mobile app; the person receiving it signs on the signature screen. 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. ### [Metal Industry CRM: Cutting Lists and Quotes | Rapitek](https://rapitek.com/en/metal-industry-crm) Material and labour are separate quote lines; which grade was priced at what sits on the line. When the same part is asked for again, the old quote is opened and the unit price updated. ##### What we set up, and how - Record the request with the material type, the grade and the cutting list; split the quote into material and labour lines and have the total calculated from the line items - On a repeat order of the same part, open the previous quote from the record and update only the unit price that has changed - Track subcontract work such as cutting, bending and welding as stages of the job record, and see from the list which job is waiting at the machine - Keep the scrap and remnant length record per job and price the next quote on actual consumption - Request with a Cutting List | The request is a record; the material type, the grade and the thickness are its fields, and the cutting list sits as an attachment on the same record. - Line-Item Quote | Material and labour are separate lines on the quote; the unit price comes from the product record, and the total and the margin are calculated from those lines. - Repeat Order of the Same Part | The previous quote sits under the customer card; when the same part is asked for again, the record is copied, the cutting list and the labour lines come across as they are, and only the material unit price is updated. - Scrap and Remnant Length | The scrap rate is a field on the job record; when that field of closed jobs is reported, the scrap allowance in the next quote comes from the record rather than from an estimate. ##### Frequently asked questions - How do I find the old price I gave a customer who is ordering the same part for the second time? | The previous quote is recorded under the customer card; you copy the record and change only the current material unit price — the cutting list and the labour lines come across as they are. - How do I tie a price I gave by the kilo to an order that comes in by the piece? | On the quote line the unit weight and the quantity are separate fields; the total weight is calculated from those two fields, and even if the order is opened by the piece, the price is read from the kilo line. - Do we give the scrap allowance in the next quote by estimate? | The scrap rate is a field on the job record; when that field of closed jobs is reported, the scrap allowance in the next quote comes from the record rather than from an estimate. Subcontract work such as cutting, bending and welding are also stages of the job record, so which job is waiting at the machine is read from the list. - Which is the best CRM software for the metal industry? | When choosing a CRM for the metal sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your metal working process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a metal industry CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the metal sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the metal sector? | We start with a discovery call: we work out your metal working process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for the metal industry? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Mining CRM: Lot Grades and Licence Calendar | Rapitek](https://rapitek.com/en/mining-crm) A shipment lot is a record; the assay result, the weighing and the grade range agreed with the buyer are fields on the same card. Lots outside the range are collected in a filtered list. ##### What we set up, and how - Keep every shipment lot on a single record with the assay result, the weighing and the agreed grade range as fields - Open the buyer's objection as a request record tied to the lot and track which assay the price cut came from - Keep licence, permit and contract end dates as fields and tie approaching renewals to a task - Enter site visits and contractor audits from the mobile app; let the form, the photograph and the location verification be written to the record - Shipment Lot | The lot is a record; the assay result, the weighing and the agreed range are its fields, and the laboratory report stays attached. - Buyer Contract | The buyer is an account record; the grade range, the moisture limit and the price formula are fields on the contract record, and shipments are assessed against those fields. - Licence and Permit Calendar | Licences and permits are records; the end date is a field, approaching dates fall into a list, and the renewal task is opened for its owner. - Site and Contractor Audit | An audit is a task; the form and the photograph are its fields, and when it is entered from the mobile app the location verification is written to the record. ##### Frequently asked questions - Can we keep the assay result of a shipment lot in the CRM? | Yes. The lot is a record; the grade, moisture and weighing values are entered as fields, and the laboratory report stays attached. Because the range agreed with the buyer sits on the contract record, lots that fall outside the range are collected in a filtered list. - Does the system remind us of licence and permit renewals? | Licences, permits and environmental obligations are each records with an end date field. According to the day threshold you define, approaching dates fall into a list and the renewal task is opened for its owner; the documents sent stay attached to the same record. - Can I show which assay the buyer's price cut objection came from? | Yes. The objection is opened as a request record tied to the shipment lot; the lot's assay result, its weighing and the grade range in the contract are fields on the same card. Because the price formula also sits on the contract record, which value the cut came out of is read from the record. - Which is the best CRM software for mining? | When choosing a CRM for the mining sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your mining process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a mining CRM system cost? | In mining, because site and contractor audits are entered from the mobile app, the team at the pit also becomes a user of the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the mining sector? | In mining the counterparts the CRM will talk to are the ERP and the laboratory systems. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the mining sector? | We start with a discovery call: we work out your mining process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for mining? | In mining the site visit and the contractor audit are entered from the mobile app; the form, the photograph and the location are written to the record. 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. ### [Home Removals CRM: Inventory of Belongings | Rapitek](https://rapitek.com/en/moving-company-crm) A booking is a record with date and deposit fields; when the date changes, the previous value stays in the history. The inventory of belongings is tied to the same job as photographed lines. ##### What we set up, and how - Record the booking with the deposit amount and the confirmed date; when the date changes, let the old and the new date both leave a trace on the same record - Add the pre-loading inventory of belongings to the record with its photographs and answer a damage claim on the basis of a dated record - Track the entry and exit dates and the number of waiting days for belongings that go into interim storage, and draw the storage charge from the record - Record the outcome of the quotes you gave and measure at which price range, and after how delayed a reply, you lost the job - Booking Record | A booking is a record with date and deposit fields; when the date changes, the previous value stays in the record history, and the calendar is set to the new date. - Inventory of Belongings | The inventory is a set of lines tied to the job record; each line has a condition note and a photograph attachment, and its state before loading is kept with its date. - Damage File | A damage claim is a request record tied to the job; it is matched with the inventory line, and the resolution step and the amount paid sit on the same record. - Storage Tracking | The entry and exit dates for storage are fields on the record; the number of waiting days is calculated from those two fields, and the charge line is produced from there. ##### Frequently asked questions - If the moving date changes, is the old booking information lost? | No. The date is a field on the record and the change stays in the record history with its own date; the old date, the new date and who entered the change can be read afterwards. - On what basis can I answer a damage claim that comes in after the move? | The photographs of the belongings taken before loading and the condition notes sit on the inventory lines with their dates; the damage request is matched with that line, and the resolution and the amount paid are written to the same record. - When belongings wait in storage, what do we base the storage charge on? | The entry and exit dates for storage are fields on the record; the number of waiting days is calculated from those two fields and the charge line is produced from the same record. - Which is the best CRM software for home removals? | When choosing a CRM for the home removals sector, you should pay attention to sector-specific workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your removals process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a home removals CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the home removals sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the home removals sector? | We start with a discovery call: we work out your removals process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for home removals? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their 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. ### [Music School CRM: Timetables and Make-Up Lessons | Rapitek](https://rapitek.com/en/music-school-crm) A lesson is a record with instructor, room and time fields. When a postponement is made, the affected lessons are listed; a missed lesson moves to awaiting make-up. ##### What we set up, and how - Track which stage each student is at, from the trial lesson through to firm enrolment - Plan individual and group lessons together with instructor availability and room/studio assignment - See each instructor's instrument, weekly timetable and student load in a single list - Track monthly fees, course package and instrument sale payments on an instalment basis - Send lesson reminders, timetable changes and concert announcements over WhatsApp - Student Enrolment Management | From the trial lesson to firm enrolment, the same student record moves through its stages; how many candidates are waiting at which step is read from the stage report. - Lesson Timetable Planning | A lesson is a record with instructor + room + time fields; the clash rule is defined during setup, and the timetable appears on the calendar. - Instructor Management | An instructor is a user record; the instrument and the weekly availability sit in its fields, and the student load comes out of the number of lesson records. - Payment and Instalment Tracking | Membership fee, package and instrument sale lines are kept under the student card; the remaining balance is calculated from those lines. - Make-Up Lesson Entitlement | A missed lesson moves to awaiting make-up on its own record; the student's accumulated make-up entitlement is the number of those records, and when the make-up is given the same record is closed, so the entitlement is not left to verbal follow-up. ##### Frequently asked questions - Can I manage different instrument disciplines? | Yes. Piano, guitar, violin, vocals and the other disciplines are a field on the lesson record; a separate timetable and a separate report for each discipline are filtered by that field, and the student distribution is reported from the same field. - Is there trial lesson tracking? | Yes. From the trial lesson to firm enrolment the same student record moves through its stages; because those who convert to enrolment and those who do not are counted separately, which discipline's taster lesson works can be measured. A follow-up task stays open for a candidate who does not enrol. - Is there concert and event management? | Yes. A concert is an event record; the participating students are linked to it, and the ticket fees collected are written to the payment lines on the student card. We do not build a separate ticketing system. - How long does setup take for a music school? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your music school process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Nonprofit CRM: Donor and Volunteer Records | Rapitek](https://rapitek.com/en/nonprofit-crm) A donor is a person record; donation lines accumulate under the card, and the same person is tied to that record through their volunteering and event attendance too. ##### What we set up, and how - Keep donors' giving history and contact preferences on a single record, and tie the thank-you message to the rule you define - Take volunteer applications through a form, assign them by skill and track participation - Plan fundraising evenings, awareness events and meetings, and manage attendance from the same place - Track and report the performance of your donation campaigns while the campaign is still running - Let the whole team reply from a single WhatsApp number, with conversations assigned in the team inbox according to the rule you define - Donor Management System | A donor is a person record; donation lines accumulate under the card, the contact preference is a field, and it is respected on sends. - Volunteer Coordination | A volunteer application is a record and can be defined to come in from a form; the skill fields are used as a filter when assigning, and participation leaves a trace on the task record. - Event Management | An event is a record; attendees are linked to it, and the invitation and attendance status are tracked from the same record. - Campaign Tracking | Because donations are tied to the campaign, the amount collected and the number of donors are visible in the report while the campaign runs. - Aid Application File | A household asking for support is an application record; the item of need, the outcome of the field assessment and the aid given previously accumulate under the file, and repeat applications from the same person are merged into a single file. ##### Frequently asked questions - How is donor tracking done? | Every donor is a separate person record; donation lines accumulate under the card, the contact preference sits in a field and is respected on sends. If you want the thank-you message to go out when a donation line is opened, you tie this to a rule during setup; the message goes out over the connected channel and is written to the card. - How does volunteer management work? | A volunteer application is a record and can be defined to come in from a form; the skill fields are used as a filter when assigning, and participation leaves a trace on the task record. If the same person is also a donor, the two roles come together on a single record. - Is there special pricing for nonprofits? | We have no published nonprofit discount; we do not announce a discount that does not exist. We keep current plan prices in one place and publish them openly on our pricing page; we do not put figures on this page, so that you do not read two different prices 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 in the discovery call and shared in writing. - Can more than one person on a nonprofit team use the same WhatsApp number? | On the nonprofit side the whole team replies to donor and volunteer messages from a single number, and conversations are assigned in the team inbox. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even when staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Notary CRM: Appointments and Journal Numbers | Rapitek](https://rapitek.com/en/notary-crm) A transaction is a record; the missing document, the stage and the journal number are its fields. An institution's regular business accumulates under its own account. ##### What we set up, and how - Take online appointments by transaction type, spread the day's load across the hours and shorten the waiting time - Track from a single record which document is missing on each transaction, which stage it is at and when it will be completed - Gather the regular transactions of banks, companies and law firms under a corporate account - Keep all correspondence with the client and past transactions on the same card - Send the appointment reminder and the document-ready notification over WhatsApp - Appointment Management System | An appointment is a record with transaction type and time fields; the day's load is read from the calendar view, and the quota per hour is defined during setup. - Document and Transaction Tracking | A transaction is a record; the missing document and the stage sit in its fields, and the completion time is calculated from the record dates. - Corporate Account Management | A bank, a company and a law firm are each account records; their regular transactions accumulate under the card, and the authorised people are linked to it. - Client Contact History | Because the correspondence and past transactions sit on the same card, the detail of an earlier job is found without searching. - Journal Number and Copy Request | Every transaction's journal number and date are fields on the record; a copy request that arrives years later is found from that number and is opened as a new record tied to the original transaction. ##### Frequently asked questions - Is there an online appointment system? | Yes, clients can book an appointment by transaction type through the website. The queue number and the estimated waiting time are notified from the appointment record; you define the quota per hour. - Is there a special module for corporate clients? | There is no separate out-of-the-box module; banks, law firms and companies are opened as account records and their regular transactions accumulate under that account. The authorised people are linked to the account, and bulk transactions and the invoice breakdown are taken from the same record. - What does the product cover for KVKK with notary data, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. Your CRM data is kept in a separate database belonging to you, and access is authorised on a role basis. Hosting is in the European Union: the database is in Finland and the media files in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. For your clients' data you are the data controller and Rapitek is the data processor; informing your clients and, where needed, obtaining their consent are your processes, and you add and manage your own privacy notice. - How long does setup take for a notary? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your notarial process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [OB-GYN Clinic CRM: Pregnancy Week Tracking | Rapitek](https://rapitek.com/en/obgyn-clinic-crm) The last menstrual period date is a field; the weekly checks and the screenings are opened as tasks tied to that date. Ultrasound images are dated attachments on the pregnancy record. ##### What we set up, and how - On every pregnancy record, open the week 4, 11, 20, 28 and 36 checks, the screening tests and the ultrasound appointments as tasks tied to the last menstrual period date - Keep the trimester ultrasound images and videos as dated attachments on the pregnancy record; make the comparison between trimesters on the same card - Plan routines such as Pap smear, HPV, mammography and bone density according to the patient's age range - Keep the mode of delivery, the anaesthesia and the breastfeeding preferences on the patient card and plan the week 6, month 3 and month 6 checks as tasks tied to the birth date - Link the newborn's information to the mother's card and send vaccination follow-up and nutrition advice over WhatsApp - 40-Week Pregnancy Tracking | The last menstrual period date is a field; the weekly checks and the screenings are opened as tasks tied to that date. The schedule is defined during setup according to your own protocol. - Ultrasound and Imaging Archive | Images and video are attachments on the pregnancy record; because they sit with their dates, comparison between trimesters is done on the same card. - Gynaecology Routine Tracking | The date of birth and the date of the last procedure are fields on the patient record; the routine call lists are drawn up by filtering on those fields. - Birth Plan and Postnatal Follow-Up | The mode of delivery, the anaesthesia and the breastfeeding preference are fields on the patient card; the week 6, month 3 and month 6 checks are tasks tied to the birth date. - Baby and Mother Communication | The newborn record is linked to the mother's card; the vaccination steps are tasks tied to the birth date, and the message goes out from the team inbox and is written to the card. ##### Frequently asked questions - How is pregnancy follow-up done in the CRM? | The last menstrual period date is a field on the patient record; the 40-week schedule is opened as tasks tied to that date. At each check appointment the required ultrasound, test and examination items are listed; a notification is sent to the expectant mother and to the physician. - Can I track IVF treatment? | Yes. For the IVF process, hormone tracking, the embryo transfer date, the beta HCG results and the handover to the pregnancy week are kept on a single record, in fields defined during setup. - How are gynaecological routines reminded? | The date of birth and the date of the last procedure are fields on the patient record; the call lists for the routine tests needed by age range are drawn up by filtering on those fields. The annual appointment suggestion is sent to the patient over WhatsApp. - Is there postnatal service follow-up? | Yes. The week 6, month 3 and month 6 checks after the birth are opened as tasks tied to the birth date; you define the steps during setup according to your own protocol. The baby's vaccination schedule, breastfeeding support for the mother and depression screening are also items on the same calendar. ### [Oil and Gas CRM: Dealer Network and Field Visits | Rapitek](https://rapitek.com/en/oil-gas-crm) A station is an account record; its region, period volume target and actual figure sit in its fields. Those below target gather in one list, and the visit task opens from that record. ##### What we set up, and how - Open every dealer as a separate account; see the sales target, performance and contract term in a single list - Track bulk fuel contracts, price agreements and renewal dates so that they warn you in advance - Let the field team enter the inspection form, the photo and the maintenance request from the mobile app during the visit - Build the accounting connection on the Logo, Netsis or SAP side over a REST API, specifically for your project - Run dealer correspondence from a single business number with a team inbox, so conversations stay on record independently of staff - Station Network Management | A station is an account record; the region it belongs to, its period volume target and the actual figure sit in its fields; stations below target gather in a single list and the visit task opens from a record on that list. - Contract and Quote Management | A contract is a record attached to the account; the price agreement and the renewal date sit in its fields, and approaching expiries drop into a list. - Field Operations Tracking | A visit is a task; the inspection form, the photo and the maintenance request are entered into the same record from a phone, and the app is live on both the App Store and Google Play. - ERP Connection | We build the Logo, Netsis and SAP connection ourselves; there is no out-of-the-box module. The connection is built specifically for each project over a REST API covering 183 business objects, OAuth2 and webhooks; the scope is shared in writing at the discovery call. - Tank and Pump Calibration Tracking | The tanks and pumps at a station are equipment lines attached to the station record; the last calibration date and the next date sit in fields, and a task is opened for the regional team for equipment whose due date is approaching. ##### Frequently asked questions - How can we manage our dealer network in the CRM? | In Rapitek CRM you can define each dealer as a separate account and track their sales performance, contract terms and visit history. Manage your network efficiently with dealer-based reporting. - Can we digitise field inspections? | Yes. With the mobile app, field teams can enter inspection forms, photos and reports into the system instantly. The entire inspection history is stored centrally. - How long does setup take for Oil and Gas? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your oil and gas process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Can more than one person on the Oil and Gas team use the same WhatsApp number? | On the oil and gas side, dealer correspondence runs from a single business number and conversations stay on record independently of staff. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Optician CRM: Prescriptions and Renewals | Rapitek CRM](https://rapitek.com/en/optician-crm) Every eye test is a dated record attached to the customer card; the right and left prescription sit in fields and are never overwritten. The last test date produces the renewal list. ##### What we set up, and how - Gather every customer's prescription history, frame and lens preference on a single card - Run eye test and collection appointments on one calendar and keep no-shows on a list - Track frame and lens stock by brand, model and prescription - Attach warranty and lens exchange rights to the sale record and send a reminder before they expire - List the customers due for a prescription renewal and set up a win-back contact - Prescription and Test History | Every eye test is a dated record attached to the customer card; the right and left prescription sit in fields and are never overwritten, so the change between two tests is visible on the same card. - Frame and Lens Preference | Brand, model and lens type are fields on the sale line; seen from the customer card, what the customer chose in the past comes out as a list. - Appointment Calendar | An appointment is a record with a staff field and a time field. Eye test and collection are separate types, and the clash rule is defined during setup. - Warranty and Right of Exchange | The warranty start and the right of exchange are fields on the sale record; those approaching expiry drop into a list and a reminder task is opened. - Renewal List | The last test date is a field; customers for whom the period you define has passed are gathered by a filter, and contact runs from that list. ##### Frequently asked questions - Can I see a customer's previous prescription and frame? | Yes. Every eye test and sale accumulates with a date under the customer card; the right/left prescription, lens type, frame brand and model appear side by side on the same card. - How is the prescription renewal reminder set up? | The last test date sits in the record as a field. Customers for whom the period you set (24 months, for example) has elapsed drop into a list based on that field; during setup you tie to a rule whether the reminder goes out over WhatsApp or SMS and how many days in advance, and the send is recorded on the customer card. - How much does an optician CRM system cost? | On the optical and eyewear side an appointment record carries a staff field; the users of the system are that store team. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in optics? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in optics? | We start with a discovery call: together we work out your optical process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for opticians? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Organic Farming CRM: Certificates and Batches | Rapitek](https://rapitek.com/en/organic-farming-crm) A certificate is a record with an expiry date field; those nearing their date drop into a list. The batch number links the shipment to the grower account, and the source is read back from the record. ##### What we set up, and how - Keep your own certificate and every contract grower's document expiry date in the record and gather those nearing their date in a single list - Open the inspection and certification body's audit appointments as tasks and follow the closing of outstanding findings - Record the shipment with a batch number and read back which batch from which grower went where - List growers in conversion separately from certified ones and plan when which product can be sold as organic - Certificate Validity | A certificate is a record with an expiry date field; those nearing their date drop into a list, and the renewal step is a task attached to that record. - Contract Grower | Every grower is an account record; the conversion year, the parcel details and the certificate status sit in its fields, and the shipment is attached to that account. - The Grower Behind a Batch | The batch number is a field on the shipment record; because the batch is attached to the grower account, which parcel of which grower it came from and which certificate was valid on that date are read back from the record afterwards. - Audit Findings | An audit is a record; findings stay open as tasks until they are closed, and the closing date and the supporting documents are kept on the same card. ##### Frequently asked questions - Can I see the certificate terms of my contract growers in one place? | Yes. The certificate expiry date is a field on the grower record; growers whose term is approaching gather in a shared list and the renewal task is attached to that record. - When a buyer asks about the source of a batch, can I answer after the fact? | Yes. The shipment record is attached to the grower account by the batch number; from the batch you can read which grower it came from and which certificate was valid on that date. - How do we follow whether the findings from an audit have been closed? | An audit is a record; every finding stays open as a task until it is closed, and the closing date and the supporting documents are kept on the same card. Because growers in conversion are listed separately from certified ones, when which product can be sold as organic is planned from those same records. - Which is the best CRM software for organic farming? | When choosing a CRM for organic farming you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your organic production and sales process, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does an organic farming CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in organic farming? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in organic farming? | We start with a discovery call: together we work out your organic production and sales process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for organic farming? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Orthodontic Clinic CRM: Wire Appointments, Instalments](https://rapitek.com/en/orthodontics-clinic-crm) Treatment is a single timeline; the note, photo, aligner set and payment from each monthly appointment build up on one patient record. When it ends, the record moves to the retention phase. ##### What we set up, and how - Build up the note, photo and payment from every monthly appointment on the same treatment record and follow progress as a percentage - Track the set number, the change date and the patient's wear compliance in clear aligner treatments - Derive the 4-6 week tightening appointment from the treatment date in fixed wire treatments and offer the patient alternative times from the calendar - Keep the 18, 24 or 36 month instalment plan together with the payment history and produce a reminder for a payment that falls due - Long-Term Treatment Tracking | An 18-36 month treatment is a record; the note, photo, payment and patient comment from every monthly appointment build up under that record, and the progress percentage is turned into a chart from those lines. - Aligner Set Management | In clear aligner treatments every set is a line; the set number, wear period, change date and patient compliance note sit in that line's fields, and sets whose change date is approaching drop into a list. - Monthly Wire Tightening Planning | In fixed wire treatments an appointment every 4-6 weeks is opened, derived from the date on the treatment record; the hours the patient is available are chosen from the calendar. - Instalment and Payment Plan | The 18, 24 or 36 month instalment lines sit under the treatment record; the payment history stays on the same card, and an overdue line drops into a list. - Patient Satisfaction Survey | The survey is sent at the interval you define, tied to the treatment record; low scores create a notification for the clinic manager and open a follow-up task. ##### Frequently asked questions - How does an orthodontic treatment start and end in the CRM? | At the start of treatment a 'Diagnosis and Plan' record is created and it is updated at every monthly appointment. As treatment ends the 'Retention Phase' begins: six-monthly and yearly check-up appointments are opened on the calendar according to the rule you define during setup. - How is Invisalign or ClearCorrect treatment tracked? | Every aligner set is a line under the treatment record; the set number, start date, expected change date and patient compliance note are fields on that line. Sets whose 14-day period is up drop into a list based on that date; during setup you tie to a rule how many days in advance and over which channel the patient is reminded. - Are there different features for child patients? | Yes. For child patients a separate notification is sent to the parent, appointment times are proposed according to the school calendar, and a special template is used for 'tooth change tracking'. - How does the orthodontic photo archive work? | At every appointment intraoral, profile and smile photographs are taken and uploaded to the patient card. The start of treatment and the current state are shown side by side, and progress is presented as a chart. ### [Packaging CRM: Proof Approval and Revision History](https://rapitek.com/en/packaging-crm) The die number, the print proof approval and the quantity left on the annual agreement sit on the same customer record; in Rapitek CRM every shipment is opened as a line on the agreement. ##### What we set up, and how - Write the dimensions, material weight, number of colours and die number into the fields of the packaging record and produce the quote from those values - Attach the print proof approval to the record; let the approved version, the approval date and the person who approved stay in the card's history - Open the annual agreement as a record and attach batched shipments to it, following the remaining quantity from a single list - Queue sample and price requests and distribute them to the relevant sales engineer with the assignment rule defined during setup - Packaging Specification | A job is a record with fields for dimensions, material weight and number of colours; the die number also sits on the same card and is read from there on a repeat order. - Proof Approval | The print proof is a task; the approval date and the person who approved sit in its fields, and the approved file stays as an attachment on the record. - Annual Agreement and Batched Shipment | An agreement is a record; every shipment is a line attached to it, and the remaining quantity is visible from the total of those lines. - Revision History | A design change is not written over the record, it goes into its history; which version was approved and when is read from that trail. ##### Frequently asked questions - Can I keep the approved print proof in the system? | Yes. Proof approval is a task; the approved file sits as an attachment on the record, and the approval date and the person who approved sit in its fields, so a repeat order is opened straight from that card. - How do I see the quantity left on the annual agreement? | An agreement is a record and every batched shipment is opened as a line attached to it; the difference between the total shipped and the agreed quantity is read from that same record. - Can I prove afterwards which design version was approved? | Yes. A design change is not written over the record, it goes into its history; which version was approved on which date and by whom is read from that change trail. - Which is the best CRM software for packaging? | When choosing a CRM for the packaging sector you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your process in the packaging sector, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a packaging CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the packaging sector? | On the packaging side the approval sits in an e-mail, the die details in production and the quantity left on the annual agreement in the accountant's spreadsheet. 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in the packaging sector? | We start with a discovery call: together we work out your process in the packaging sector and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for packaging? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Paper CRM: Weight-Based Quotes and Allocation](https://rapitek.com/en/paper-crm) A quote line carries fields for grade, weight, size and reel or sheet; the validity date is a field on the quote, and those that have expired gather in a separate list. ##### What we set up, and how - Prepare the quote with grade, weight, size and reel-or-sheet lines, and carry the same lines from a past order into a new quote - Keep the quote validity date in a field, separate expired quotes out of the list and reprice them - See from the record which customer a batch in stock has been promised to, and do not commit the same batch twice - Read the repeat buying interval from the customer's history and open a follow-up task, attaching shipment and delivery note details to the order - Specification-Based Quote | A quote line is more than a product; the grade, the weight, the size and whether it is reel or sheet sit in the line's fields. - Price Validity | The validity date is a field on the quote; quotes past their date gather in a separate list, and the repricing task is opened from there. - Batch Allocation | A stock batch is a record; which order it is attached to is seen from that record, and the unattached quantity stays free. - Buying Rhythm | The customer's order history sits on their own record; when the interval lengthens, a follow-up task drops into the list and is assigned to a representative. ##### Frequently asked questions - The price of paper changes often; how do we manage the validity of a quote we have given? | The validity date is a field on the quote; expired quotes gather in a separate list and a repricing task is opened, and the new price that goes to the customer is followed as a revision of the same record. - When the customer says "the same paper as last time", how do we reach the right specification? | Every order sits on the customer's record with its grade, weight, size and reel-or-sheet details; the past order is opened and a new quote is created with the same lines, so cutting the wrong size is prevented at source. - How do we stop the same stock batch being promised to two customers? | A stock batch is a record; which order it is attached to is seen from that record, and the unattached quantity stays free. That way the commitment is visible when the promise is made, not on the loading day. - Which is the best CRM software for paper? | When choosing a CRM for the paper sector you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your paper process, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a paper CRM system cost? | In paper, because the follow-up task for a customer whose buying interval has lengthened is assigned to a representative, representatives are defined individually in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the paper sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in the paper sector? | We start with a discovery call: together we work out your paper process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for paper? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Patent CRM: Files, Oppositions and Renewals](https://rapitek.com/en/patent-office-crm) Renewal, opposition and annual fee dates are separate fields on the file; the task tied to each date is opened for the person responsible before it expires and stays listed until closed. ##### What we set up, and how - Keep every trademark and patent file under the client account with its application number, country and class - Enter the renewal, opposition and annual fee dates as fields; let a reminder task be opened before the deadline - Build up the notification sent to the client and the instruction received under the file, and see files waiting for instructions on a separate list - Show the official fee and the attorney fee as separate items on the quote and follow collection file by file - File Record | A trademark or patent application is a record with fields for the number, the country and the class, attached to the client account. The portfolio is the list of files under that account. - Deadline Fields and Reminders | The renewal, opposition and annual fee dates are separate fields on the file; the task attached to each field is opened before the date, assigned to the person responsible, and stays on the list until it is closed. - Notification and Instruction History | Information sent to the client and the answer that comes back are recorded as activities under the file; files waiting for instructions are a filter on that status. - Official Fee and Attorney Fee | The official fee and the service charge are separate line items on the quote; the collection status file by file is read from those lines. ##### Frequently asked questions - What does the system do so that renewal and opposition deadlines are not missed? | Every deadline is a separate date field on the file record, and the reminder task attached to the field is assigned to the person responsible before the date. It stays on the list as long as it is not closed; so the follow-up is attached to the record itself, not to a person's diary. - Do registry notifications land on the file by themselves? | We build the connection to the registry side ourselves; there is no out-of-the-box module. Notifications are entered on the file by hand, or carried by a flow built specifically for each project over import and a REST API. Once the date field has been entered, the system runs the reminder chain. - Can I see files waiting for instructions from the client separately? | Yes. The notification sent to the client and the answer received are recorded as activities under the file; the file's status is also a field. Files waiting for instructions are opened as a separate list by filtering on that field, and files approaching their deadline are sorted by date on that list. - Which is the best CRM software for patent work? | When choosing a CRM for the patent sector you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your trademark and patent attorney process, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a patent CRM system cost? | In patent work, because the task tied to each deadline field is assigned to a person responsible, the attorneys looking after the files are defined individually in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the patent sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in the patent sector? | We start with a discovery call: together we work out your trademark and patent attorney process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for patent work? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Pet Grooming CRM: Animal Card and Grooming History](https://rapitek.com/en/pet-grooming-crm) The species, breed, allergies and clipping preference sit on the animal's own record; because the treatment time is defined by coat type, the calendar fills by real workload, not by queue. ##### What we set up, and how - Keep a separate profile card for every animal, with the species, breed, allergies and grooming preferences - Take appointments online, assign the job to a suitable groomer and balance the load through the day - Record the details of every visit and leave the note for the next grooming on the same card - Keep the grooming period and the last visit date in a field; let those whose period is up drop into a list and tie the reminder to that list with a rule - Send appointment confirmations, grooming-completed notifications and reminders over WhatsApp - Animal Profile Cards | Every animal is a separate record attached to its owner; the species, the breed, the allergies and the grooming preference sit in its fields. - Treatment Duration by Coat Type | The treatment duration is a field defined on the service record according to the animal's breed and coat type; the slot opened on the calendar is produced from that duration, and a short-haired cat and a long-haired dog cannot be booked into the same slot. - Grooming History Tracking | The note from every visit builds up with a date under the animal's card; at the next grooming it is read from that same card. - Periodic Reminders | The grooming period is a field; those whose period is up according to the last visit date drop into a list and a reminder task is opened. - Vaccination Date Check | The date of the last rabies and combination vaccination is a field on the animal record; animals whose date has passed are flagged on the appointment list, and asking the owner for the document is opened as a task from that flag. ##### Frequently asked questions - Can separate tracking be done for different animal species? | Yes, you can set up separate grooming procedures, price lists and time planning for dogs, cats and other pets. - Where do we see the customers whose grooming is due? | The grooming period and the last visit date are fields on the animal record; animals whose period is up drop into a list based on those fields, and the reminder task is opened from that list. During setup you tie to a rule how many days in advance and over which channel the message goes out; it is not a general message going to everyone but a list produced from that animal's own period. - Can I manage more than one branch for Pet Grooming? | Yes, with multi-branch support you can manage all your pet grooming salons from a single panel. - How long does setup take for Pet Grooming? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your pet grooming process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Pet Shop CRM: Food Preference and Recurring Orders](https://rapitek.com/en/pet-shop-crm) A pet is a record attached to the customer; the food brand, the pack size and the daily consumption are its fields, and the estimated finish date is derived from them and drops into a list. ##### What we set up, and how - Keep the customer's pet, its species and its food preference on their card - Produce a reminder list based on the consumption period before the food runs out - Run recurring orders and deliveries from a single screen - Track product stock by brand and pack size and catch the critical level - Direct loyalty points and campaigns to regular customers - Animal and Preference Record | A pet is a record attached to the customer; the species, the age and the food preference sit in its fields and are read from that same card on the second purchase. - Consumption Period | The pack size and the daily consumption are fields on the product and the animal record; the finish date is derived from them and those approaching drop into a list. - Recurring Order | Customers whose period has come are gathered by a filter; the order record is opened from that list and the delivery task is attached to it. - Brand and Pack Size Variant | The brand and pack size variants of the same food are separate lines on the product record; when the quantity of a variant falls below the threshold, the animal records that regularly buy that variant are seen from the same list, and the task of letting them know is opened from there. - Loyalty and Campaign | Points are a field on the customer card; campaigns are built from lists filtered by purchase frequency. ##### Frequently asked questions - How do I remember which food the customer buys? | A pet is a record attached to the customer, and the food preference is a field on it. On the second purchase the brand, the pack size and the previous purchase date appear on the same card. - How is the reminder set up before the food runs out? | The pack size and the daily consumption sit in the record as fields; the estimated finish date is derived from them. Customers whose time is approaching drop into a list, and the reminder goes to that list over WhatsApp or SMS. - How much does a pet shop CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done on the pet shop 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in a pet shop? | We start with a discovery call: together we work out your pet shop process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a pet shop? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Pharmaceutical CRM: Doctor Visits, Prescription Data](https://rapitek.com/en/pharmaceutical-crm) The visit, the samples left with the doctor and the budget spent build up under the same doctor record; the region's history stays even when the rep changes. Prescription data sits there too. ##### What we set up, and how - Follow the field team's daily visits and route plan as they happen - Record the samples and promotional material left with the doctor together with the budget used - Analyse which doctor prescribes which product and build the field target accordingly - Produce reports, and the history of the field changes users make to records, from the system itself - Open a single WhatsApp number to the whole team with a team inbox, and have conversations assigned according to the rule you define - Doctor Visit | A visit is a task; the representative, the doctor and the date sit in its fields, the visit note and the location are written to the same record, and the region's history stays in the record even when the team changes. - Samples and Promotion | The samples and promotional material left with the doctor are lines attached to the visit record; the quantity and the budget spent sit in fields, and the regional budget is read from the total of those lines. - Prescription Data | The doctor record carries product-based prescription fields; which doctor turned to which product comes out of the report on those fields, and the field target list is built from there. - Audit Trail | Field changes users make to existing records are stored in the record's history with their date and their user; the record's initial creation and some bulk updates the system makes in the background are not recorded there; for record deletions, user and permission settings, automations and background processes, the user shown in the history may not be the person who actually made the change. - Scientific Meeting Attendance Record | A congress or scientific meeting the doctor attended is an attendance record attached to the doctor record; the meeting name, its date and the items covered sit in fields, and the invitation and the internal approval step leave a trace on the same record. ##### Frequently asked questions - What happens to the doctor history when a representative changes region? | A visit is a task; the representative, the doctor and the date sit in its fields, and the visit note builds up under the doctor record. Because the samples left and the budget spent are also attached to the same record, the region's history stays in place even when the team changes. - How long does setup take for Pharmaceuticals? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your pharmaceutical process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for Pharmaceuticals? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for Pharmaceuticals? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Pharmacy CRM: Pack Tracking and SGK Provision](https://rapitek.com/en/pharmacy-crm) The pack finish date is a field on the customer record; when the date approaches a reminder task is opened. Packs close to expiry gather in one list by the expiry date field. ##### What we set up, and how - Keep the pack finish date for chronic medication on the customer record; let those approaching their date drop into a list and tie the reminder to that list with a rule - Identify regular customers with points and special discounts and follow their return - See products approaching their expiry date, running low on stock and selling the most on the same screen - Make the fields required for provision mandatory on the sale record and take SGK and insurance statements from the report - Let the whole pharmacy team reply from a single WhatsApp number, so correspondence does not stay on personal phones - Customer Loyalty Programme | Points and discounts are fields on the customer card; a regular customer appears in a list filtered on their purchase dates. - Medicine Reminder System | The pack finish date is a field on the customer record; when the date approaches a reminder task is opened and the message is sent from the same card. - Packs Close to Expiry | The expiry date is a field on the product record; packs with fewer than the set number of days left gather in a single list, and the decision to return them or to push them is handled from the card on that list. - SGK and Insurance Processes | The fields required for provision are made mandatory on the sale record, and the statements are taken from reports. The SGK and insurance connection is built specifically for each project; there is no out-of-the-box module. - Medicine Supply Request | A request opened for a pack that is not on the shelf is a request attached to the customer record; which warehouse it was requested from, the expected date and the task of letting the customer know sit on that request, and the correspondence in the inbox is attached to the same request. ##### Frequently asked questions - Does the system bring a customer whose chronic medication has run out in front of me by itself? | The pack finish date is a field on the customer record; when the date approaches a reminder task is opened and the message is sent from the same card. How many days in advance it warns is defined during setup. - Can we follow a customer who asks for a pack that is not on the shelf? | The request is a separate record attached to the customer record; which warehouse it was requested from, the expected date and the task of letting the customer know sit on that request, and the correspondence in the inbox is attached to the same request. - How long does setup take for a Pharmacy? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your pharmacy process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for a Pharmacy? | In a pharmacy the fields required for provision are made mandatory on the sale record and the statements are taken from reports. 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; the same applies to SGK, insurance and pharmacy automation. Because access and field structure on the other side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. When no connection is built, the provision fields are entered on the sale record by hand and the statements are taken from the report. - Can more than one person on the pharmacy team use the same WhatsApp number? | On the pharmacy side customer correspondence does not stay on personal phones; the whole pharmacy team replies from a single number. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Photography CRM: Deposits and Selection Delivery](https://rapitek.com/en/photography-crm) A shoot is a record with fields for the date, the time and the deposit status. The selection, album approval, printing and delivery are each tasks; those waiting with the client gather in one list. ##### What we set up, and how - Record the shoot date together with the deposit status; keep a confirmed date apart from one that was only enquired about - Advance the post-shoot steps of selection, album approval, printing and delivery as tasks - Follow the selections waiting with the client and the uncollected balance from the same list and send reminders - Attach the signed version of the contract and the image usage consent to the customer record - Date Reservation | A shoot is a record with date and time fields; the deposit status sits on the same card, and unconfirmed dates appear in a separate list. - Steps After the Shoot | The selection, the album approval, the printing and the delivery are each tasks; the owner of each task and the party it is waiting on sit in fields, and those waiting with the client gather in a separate list. - Package and Balance | The package chosen and the amount are fields on the customer record; the deposit and the remaining balance sit under it as lines, and the uncollected balance is read from the report. - Usage Consent | The image usage consent and the contract are attachments to the record; the signature date sits in a field, and jobs without consent stand separately on the list. ##### Frequently asked questions - Can I see from the system what to tell a second client asking for the same date? | Yes. The shoot record holds the date and the deposit status together; because dates with no deposit taken sit in a separate list, which day is confirmed is read from the calendar. - Can I follow the selections waiting with the client after the shoot? | Yes. The selection is a task and the party it is waiting on is written in its field; jobs waiting with the client gather in a single list, and the reminder is sent to that list. - Can I see afterwards which frame can be published where? | The image usage consent and the contract are attachments to the record; the signature date and the scope of the consent sit in fields, and jobs without consent stand separately on their own list. - Which is the best CRM software for photography? | When choosing a CRM for the photography sector you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports around your shoot and delivery process, we migrate your data and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much does a photography CRM system cost? | In photography, because the selection, album approval and printing steps have separate owners, the people in the studio are defined separately in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the photography sector? | 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 access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and its cost at the discovery call and share them in writing. - How does the move to a CRM system work in the photography sector? | We start with a discovery call: together we work out your shoot and delivery process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for photography? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phone. The app is live on both the App Store and Google Play. The web interface also works on tablets and phones. 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. ### [Physiotherapy CRM: Session Entitlement, SGK Provision](https://rapitek.com/en/physiotherapy-crm) The total sessions on the doctor's report and its validity date are fields on the patient record; each session is deducted from that number and a renewal task opens before it runs out. ##### What we set up, and how - Run online booking, reminders and recurring session planning on a single calendar - Create a treatment plan for every patient and record the session progress step by step - Enter SGK and private insurance provision details on the record and follow patient payments from that same record - Produce comparative progress reports from before and after treatment - Send appointment reminders and home exercise programmes over WhatsApp - Patient Appointment Management | An appointment is a record with fields for the patient, the therapist and the time; recurring sessions are opened as a series, and the reminder is tied to the date. - Treatment Programme Tracking | The treatment plan is a record attached to the patient card; the note from each session builds up under it, and which step has been reached is visible on the card. - Insurance and Payment Tracking | The payment and provision details are fields on the session record; the remaining balance is totalled on the patient card and the statements are taken from the report. There is no out-of-the-box module for SGK and insurance companies — these fields are filled in by hand or with an import file. - Patient Progress Reports | Because measurements build up as dated fields, the before-and-after comparison is produced from those same records and no separate file is kept. - Referral Report and Session Entitlement | The total number of sessions written on the doctor's report and the report's validity date are fields on the patient record; every session performed is deducted from that number, and a renewal task is opened before the entitlement runs out or the date expires. ##### Frequently asked questions - Is there SGK integration? | We build the connection to SGK or to private insurance companies ourselves; there is no out-of-the-box module, and we have no product called a "compatible module" either. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and its cost are shared in writing at the discovery call. As long as no connection is built, provision details are entered with an import file or by hand; the session entitlement on the referral report, the remaining balance and the collections are still kept in the CRM, and report renewal reminders are produced from there. - Can I manage more than one therapist? | Yes, you can follow all your physiotherapists' schedules, patient loads and performance from a single panel. - Is patient data safe for Physiotherapy? | Every customer's data is kept in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256 and two-factor authentication secrets are encrypted at rest; access is limited by role-based authorisation. Hosting is in the European Union: the database is in Finland and media files are in Frankfurt. This counts as a transfer abroad under KVKK Article 9; that is why we run the notification and explicit consent processes. A small number of sub-processors operate outside the EU; we list each of them and where they process the data one by one in our privacy policy. - How long does setup take for Physiotherapy? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your physiotherapy process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. ### [Pilates CRM: Reformer Quota and Class Type | Rapitek CRM](https://rapitek.com/en/pilates-yoga-crm) In equipment classes the quota is not a head count but the number of reformers; capacity sits in the class type field, and when a machine goes for maintenance that day's capacity drops. ##### What we set up, and how - Set up private, duo and group classes as separate class types; define capacity and price separately for each type - Tie the quota in equipment classes to the number of reformers; when a machine goes in for maintenance, reduce capacity and move the overflow booking to the waiting list - Define as a rule whether a late cancellation costs a class credit, and notify the member on the waiting list when a place opens up - Keep the restriction note and the programme end date of a member referred by a physiotherapist on the record, so every instructor who takes the class sees the same note - Private, Duo and Group Class Types | The class type is a field on the class record; capacity is defined separately for each type, and the price sits on its own line in the price list for each type. - Quota per Machine | In a mat class capacity is a head count; in an equipment class it is the number of reformers. When a machine goes in for maintenance that day's capacity is reduced and the overflow booking moves to the waiting list. - Restriction Note and Physiotherapy Referral | Injury, pregnancy and doctor's restrictions are fields on the member record; for a member who comes with a post-injury programme, the referring person and the end of the programme sit on the same card. - Instructor Certification Level | The certification level is a field on the instructor record; which class types the instructor can teach is read from that field, and an instructor whose level is not sufficient is not assigned to that class in the calendar. ##### Frequently asked questions - Is a member's injury information lost when the instructor changes? | It is not lost. The restriction note is a field on the member record, not an entry in an instructor's notebook; because the class is attached to the member, whoever takes the class that day sees the same note. When the note is updated, every subsequent class shows its current version. - Can the system decide whether a last-minute cancellation costs a class credit? | Yes. A rule is defined that looks at how long before the class time the cancellation was made; if the rule says the credit is forfeited, the deduction is written to the record, otherwise the credit is returned. At the same time the first member on the waiting list is notified that a place has opened up. - Can we prevent an instructor without the required certification level from being assigned to a class? | Yes. The certification level is a field on the instructor record, and which class types the instructor can teach is read from that field. During setup we define that an instructor whose level is not sufficient is not assigned to that class type when the calendar is filled in; the decision is then not left to the memory of whoever is on duty. - Which is the best CRM software for pilates? | When choosing a CRM for the pilates sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your pilates studio process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Pilates CRM system cost? | In pilates, which instructor can teach which class is determined by the certification level field, so instructors are defined separately in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the pilates sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the pilates sector? | We start with a discovery call: together we work out your pilates studio process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for pilates? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Plastics CRM: Tiered Pricing and Annual Draw | Rapitek CRM](https://rapitek.com/en/plastics-crm) A quote carries fields for its validity date and the raw material price it rests on. When the resin line moves, expired quotes gather in one list and the revision call opens as a task from it. ##### What we set up, and how - Write the validity date and the raw material price it rests on onto the quote, and gather expired quotes in a separate list - Show the different unit prices for one thousand, ten thousand and fifty thousand pieces on the line items of the same quote - Attach the monthly draws of the annual agreement to orders and follow how much of the agreed quantity is left - Write the shipment batch to the record; when a complaint comes in, attach the case to the batch concerned and to the customers affected - Quote Validity Field | The quote is a record with fields for its validity date and for the raw material price it rests on; the ones that have expired gather in a single list through the filter on that date. - Tiered Pricing by Quantity | The quantity tiers are the line items of the quote; each line holds a quantity field and a unit price field, and the price applied to the order comes from that line. - Annual Agreement and Draws | The agreement is a record and the monthly draws are order lines attached to it; the remaining quantity is the difference between the agreed quantity and the total of those lines. - Injection Batch | The shipment batch is a field on the order record; a complaint is opened as a case record and attached to the batch that was moulded, and the other customers shipped from the same batch are listed through the filter on that field. ##### Frequently asked questions - How do we find which quotes need updating when the raw material price changes? | On the quote record the validity date and the raw material price it rests on are separate fields; quotes that have expired or that were given before a certain date are gathered in a single list through a filter. The revision call is opened as a task on the records in that list. - When a complaint comes in, can we see which batch the product came out of? | Because the shipment batch is a field on the order record, the complaint case is attached directly to that batch. The other customers shipped from the same batch are listed through the filter on the same field; they are informed from that list rather than by calling one by one. - Where do we see how much of the annual agreement is left? | The annual agreement is a record of its own; the monthly draws sit as order lines attached to it. The remaining quantity is the difference between the agreed quantity and the total of those lines, and it is read off the agreement record; no separate spreadsheet is kept. - Which is the best CRM software for plastics? | When choosing a CRM for the plastics sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your plastics production process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Plastics CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the plastics sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the plastics sector? | We start with a discovery call: together we work out your plastics production process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for plastics? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Plumbing CRM: Emergency Call and Site Visit Quote | Rapitek](https://rapitek.com/en/plumbing-crm) The site visit turns into a quote record; materials and labour are separate line items. An emergency call is a case record with a priority field and sits on the same day list as planned jobs. ##### What we set up, and how - Prepare the quote that comes out of the site visit with separate material and labour line items, and take the customer's approval from the signature screen in the mobile app - Drop emergency calls to a plumber according to priority, using the queue and the assignment rules defined during setup, and see them on one day list together with the planned jobs - Build up the plumbing history of every address on the record and attach a call that comes back within the warranty period to the first job - Keep the management of blocks of flats and housing estates on an account record and follow the flat-by-flat jobs and collections under the same account - Site Visit and Quote | The site visit turns into a quote record; materials and labour are separate line items, and the customer's approval is taken from the signature screen in the mobile app and stays on the record. - Emergency Call | The call is a case record; it has a priority field, the queue and the assignment rules defined during setup drop it to a plumber, and calls that have not been closed stay in a single list. - Address History | The work carried out accumulates under the address record; the warranty end date is a field, and a new call from the same address is attached to the first job. - Managing Agent Account | The management of a block of flats or a housing estate is an account record; the individual flats are records attached to it, and the work and the collections gather under the same account. ##### Frequently asked questions - When an emergency call comes in, can I see how the planned jobs are affected? | Yes. The call is a case record with a priority field, and the queue rules drop it to a plumber; because the planned work orders sit on the same day list, which job has been pushed back is visible in the list and the notification to that customer is sent from the same record. - How do I prevent an argument between the price said at the site visit and the amount at the end of the job? | The site visit turns into a quote record; materials and labour are written as separate line items and the customer's approval is taken on site, from the signature screen in the mobile app. If the scope changes during the job, the new line item is added to the same record and approved again, so which amount rests on what can be read afterwards. - If a call comes from the same address again within the warranty, can I attach it to the first job? | Yes. The work carried out accumulates under the address record and the warranty end date is a field; a new call from the same address is attached to the first job, and which job has come back is read from the report on that link. - Which is the best CRM software for plumbing? | When choosing a CRM for the plumbing sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your plumbing process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Plumbing CRM system cost? | In plumbing an emergency call reaches the plumber through assignment rules, so the plumbers who share the planned work and the calls are defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the plumbing sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the plumbing sector? | We start with a discovery call: together we work out your plumbing process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for plumbing? | In plumbing the customer's approval of the quote that comes out of the site visit is taken from the signature screen in the mobile app and stays on the record. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [PR Agency CRM: Media List and Coverage Record | Rapitek CRM](https://rapitek.com/en/pr-agency-crm) Journalists and editors are contact records; the subject they cover, the outlet they belong to and the last contact date sit in fields. Coverage is attached to the client and that contact. ##### What we set up, and how - Keep journalists and editors on the record together with the subject they cover, the outlet they belong to and the last contact date - Send the release not to a fixed list but to a list of contacts filtered by subject, and collect the replies under the contact - Attach every published story to the client and to the contact approached, so the monthly coverage report comes out of the record - Run launch and press conference invitations, attendance status and the follow-up tasks afterwards from a single record - Media Contact Record | The journalist and the editor are each a contact record; the subject they cover, the outlet they belong to and the last contact date sit in fields, and the relationship stays with the firm. - Release Distribution | Distribution is a series of contacts made to a list of people filtered by subject; the send and the reply that comes back are written as activities under the contact. - Coverage Record | A published story is a record attached to the client and to the contact approached; the publication date and the link sit in its fields, and the monthly report is the list of these records. - Event and Invitation Tracking | A launch is an event record; the guests are contacts attached to it, and the attendance status and the follow-up task afterwards are run from the same record. ##### Frequently asked questions - Are journalist relationships lost when someone leaves the team? | They are not lost. Every journalist and editor is a contact record in the agency's own database; the subject they cover, past correspondence and the last contact date sit under that record. Because it is kept by the firm rather than in a personal phone book, the handover happens through the record rather than by sharing a list. - Can we produce the monthly coverage report without collecting it by hand? | Every published story is written as a record attached to the client and to the contact approached; the publication date and the link sit in fields. At the end of the month the report comes out by listing these records over a date range, and which contact turned into a story is read from the same link. - Can we track who came to the launch and who was called afterwards? | Yes. The launch is an event record; the guests are contact records attached to it and the attendance status is a field. Post-event follow-up tasks are opened from the same record; because who was called, who was not called and the reply received all accumulate under the contact, the list shows who has been waiting how many weeks. - Which is the best CRM software for a PR agency? | When choosing a CRM for the PR agency sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your PR agency process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a PR Agency CRM system cost? | In a PR agency the journalist relationship sits on the firm's record rather than in team members' phone books, so the whole team goes into the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the PR agency sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the PR agency sector? | We start with a discovery call: together we work out your PR agency process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for a PR agency? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Pre-Accounting CRM: Balance and Cheque Due Date | Rapitek](https://rapitek.com/en/pre-accounting-crm) The balance, the due date and the risk limit are fields on the customer record; an account over its limit is flagged as the order is opened. A payment promise is a dated task. ##### What we set up, and how - Keep the balance, the due date and the risk limit as fields on the customer record and flag accounts over their limit in the list as the order is opened - Record the payment promise with its date, so that customers who have passed the promised date gather in their own list and a follow-up task is opened - Bring cheque and promissory note due dates together in one calendar and set an alert for the ones approaching their date - Build up the invoice, delivery note and collection trail under the customer card and produce the month-end list for the accountant from there - Account Card | The customer is an account record; the balance, the due date and the risk limit sit in its fields, and because the sales team looks at this card too, an overrun of the limit is visible at the moment the order is placed. - Payment Promise | A promise to pay is a task with a date; because the task does not close when the date passes, it stays in the list, and who took the promise is written on the record. - Cheque and Promissory Note Due Dates | Every cheque is a record with a due date field; the ones approaching their due date gather in a single list, and when it is collected the status field changes. - Accounting Program Connection | The mapping of the account and invoice fields is set up specifically for the project; there is no out-of-the-box module, the connection is made over the REST API and webhooks, and its scope is set out in writing at the discovery stage. ##### Frequently asked questions - Can the sales team see the customer's balance and risk limit? | Yes. The balance and the limit are fields on the customer record; when the permission is given, the sales team sees them on the same card and an account over its limit is flagged as the order is opened. - Can I follow cheques falling due and the payment promises given from a single place? | Yes. Cheques are attached to the customer record with a due date field and payment promises as dated tasks; both gather in the list of items approaching their date. - What do we produce the month-end list for the accountant from? | The invoice, delivery note and collection trail accumulate under the customer card; the list taken for a chosen period is produced from those records. Official e-document generation is not done in the CRM; we build the connection to the accounting program. - Which is the best CRM software for pre-accounting? | When choosing a CRM for pre-accounting you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your pre-accounting process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Pre-Accounting CRM system cost? | In pre-accounting the sales team looks at the same account card as much as the accounting side does, so the people on both sides go into the system together. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in pre-accounting? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in pre-accounting? | We start with a discovery call: together we work out your pre-accounting process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for pre-accounting? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Preschool and Nursery CRM: Places and Instalments | Rapitek](https://rapitek.com/en/preschool-crm) The application is an opportunity record and the instalment plan sits line by line on the enrolment card; an overdue line drops into the report, and whoever collects the child is a record. ##### What we set up, and how - Bring all correspondence with the parent together in a single channel and keep the message history on the record - Follow the application, pre-registration and final enrolment steps together with the available places - Share the daily activity, meal and sleep information with the parent during the day - Follow monthly payments, instalment plans and delays from a single list - Send announcements, reminders and daily reports over WhatsApp - Parent Communication Centre | The parent is a contact record and is attached to the child record; the WhatsApp correspondence and the call note accumulate on the same card, and the history stays even when the teacher changes. - Enrolment and Places Management | The application is opened as an opportunity record; it moves through the pre-registration and final enrolment stages, and occupancy by class is read from the stage report. - Daily Activity Reporting | Notes taken during the day are written to the child record; what the parent sees is produced from that record, and which piece of information was passed on and when can be traced. - Payment and Instalment Tracking | The instalment plan is kept line by line on the enrolment card; an overdue line drops into the report, and the reminder task is tied to that condition during setup. - Collection Authority and Departure Record | The people allowed to collect the child are separate contact records attached to the parent card; every departure is written to the child record with the member of staff who handed the child over and the time, and when someone not on the list arrives, the departure is not processed and an approval task drops to the person in charge. ##### Frequently asked questions - Is there a parent portal? | The daily activity, the announcements and the payment status are produced from the child's record and sent to the parent over WhatsApp or e-mail; if you wish, a user account with limited permissions is opened for the parent in the CRM and they see only their own child's record. We do not have a separate branded parent portal product — what they see is the CRM itself, as far as their permissions go. Which piece of information was passed on and when stays on the record either way. - What does the product cover for KVKK with preschool and nursery data, and what does it not? | KVKK compliance does not come with the product; here is what the product does and where its limits are. Child and parent data are held in a separate database set aside for each institution, and access is limited by role-based permissions. The hosting is in the European Union: the database is in Finland and the media files are in Frankfurt. For organisations in Turkey this counts as an international data transfer under Article 9 of KVKK; we establish the basis for that transfer together during the contracting process. For child and parent data your institution is the data controller and Rapitek is the data processor; informing parents and, where needed, obtaining their consent are your institution's processes, and you add and manage your own privacy notice. - Can I manage more than one branch for a preschool and nursery? | Yes, with multi-branch support you can manage all your nurseries and preschools from a single panel. - How long does setup take for a preschool and nursery? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your preschool and nursery process needs becomes clear in that call. We migrate your data; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. ### [Printing CRM: Proof Rounds and Reprint Records | Rapitek CRM](https://rapitek.com/en/printing-crm) Every proof is a line attached to the job record; which round it is and what changed in the quantity and the paper type sit on that line. The move to print is made on the last approved round. ##### What we set up, and how - Bring each customer's past jobs, the prices given and the call notes together on a single card - Attach recurring print jobs to the record with their cycle, and call up the previous quantity and plate number from the same record - Line up open quotes by stage and see on the pipeline which of them have turned into work - Plan the shipment as a task; have the person receiving the goods sign on the signature screen in the mobile app, and write any short delivery to the same record - Handle the price enquiries that come in on a single WhatsApp number as a team, with every conversation written to the record - Print Work Order Record | Every job taken to print is a work order record of its own; the quantity, the size, the paper type and weight, the number of colours and the post-press operations such as lamination and cutting are fields on that record; which machine and which delivery date the job is tied to sit on the same record. - Reprint Cycle | Catalogue, label and packaging jobs that recur during the year sit on the customer record with their own cycle; the quantity, the paper type and the plate number of the previous job are called up from the same record, and the job whose turn has come drops into the list by date. - Proof and Revision Round | Every proof that goes to the customer is a line attached to the job record; which round it is, what changed in the quantity and the paper type, and who gave the approval on what date sit on that line; the move to print is made on the last approved round. - Delivery and Acceptance Signature | Shipping the printed job is a task attached to the record; the delivery address, how many boxes went out and the person receiving them sit in its fields; the person receiving them signs on the signature screen in the mobile app, and a note of a short delivery stays under the same task. - Print File Version Control | Every print file that comes from the customer is added to the work order with a version number; the result of the bleed, resolution and font embedding checks sits in the fields of that line; a file whose check is not complete holds the job at the waiting stage and drops as a task to the person responsible. ##### Frequently asked questions - When the customer says "the price you gave us last time", how do we find which quote they mean? | The quote history sits in order under the customer card; in every version the quantity, the paper type and the delivery time stay in fields. Which figure was given last and on what terms is visible the moment the record is opened; quotes that have not turned into work wait at the open stage. - Does the system hold the file check before the job goes to print? | Every print file that comes from the customer is added to the work order with a version number; the result of the bleed, resolution and font embedding checks sits in the fields of that line. A file whose check is not complete holds the job at the waiting stage and drops as a task to the person responsible. - How long does setup take for a print shop? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your printing process needs becomes clear in that call. We migrate your data; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Will it integrate with my existing systems for a print shop? | In a print shop every job taken to print is a work order record of its own; which machine and which delivery date it is tied to sit on the same record. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - Can more than one person in the print shop team use the same WhatsApp number? | On the print shop side, price enquiries coming in on a single number are handled as a team and every conversation is written to the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all the messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can follow the conversations and the response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Private School CRM: Parent Tracking and Enrolment | Rapitek](https://rapitek.com/en/private-school-crm) The parent who comes on a school tour is attached to one file together with the source; the document status, the payment plan and the bus stop stay in fields on the same file after enrolment. ##### What we set up, and how - Bring the parents who come on a school tour and those who ask for information together in a single list and follow them step by step until they turn into an enrolment - Keep the online enrolment forms, the document completion status and the payment plans in the same parent file - Filter by class, form or custom groups and send bulk or individual SMS, e-mail and WhatsApp messages - Build an alumni database and win new enrolments through referral programmes - Open the school's single WhatsApp number to the whole enrolment team; have conversations assigned according to the rule you define, and the message history stay even when staff change - Prospective Parent Tracking | A school tour and a request for information are each a lead record; the source sits in a field, and it moves through its stages until it turns into an enrolment. - Enrolment File | The entry coming from the application form can be defined to drop straight into the parent file; the document status and the payment plan sit in fields on the same file. - Parent Communication Centre | The class and the form are fields on the parent record; a bulk send goes to the list filtered by those fields, and the send is written to the card. - Alumni and Referrals | An alumnus record is not deleted, its status changes; because a candidate who arrives on a referral shows the alumnus in the source field, the chain can be followed. - Bus Route and Stop Record | The bus the pupil takes, the stop and the drop-off time are fields on the pupil record; a change of route is entered from that field, and the new stop drops as a task to the person responsible for the buses. ##### Frequently asked questions - How is prospective parent tracking done? | You can record every parent who joins a school tour or asks for information in the system, plan the follow-up steps and follow the conversion process. - Will it integrate with our existing student information system for a private school? | We build the connection to the school management system or the student information system; there is no out-of-the-box module. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and its fee are shared in writing in the discovery call. When no such connection is built, pupil and parent information is entered in bulk with an import file or by hand; in either case the parent file sits in the CRM as a single record. - How is bulk communication with parents done? | You can filter by class, form or custom groups and send bulk SMS, e-mail or WhatsApp messages. You can use personalised templates. - Can more than one person in the private school team use the same WhatsApp number? | On the private school side, the school's single number is opened to the whole enrolment team; the message history stays even when staff change. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all the messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can follow the conversations and the response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [PropTech CRM: Portfolio Migration and Approvals | Rapitek](https://rapitek.com/en/proptech-crm) The portfolio manager, finance and IT are separate contact records under the same organisation; what each objected to sits in a note on their own card and is handed over with the organisation. ##### What we set up, and how - Follow the demo, pilot and contract stages on a visual pipeline and produce a forecast - Keep the estate agency, developer and portfolio owner records in one place together with the history of the meetings - Keep head office and the branch on separate account records and read from the record which approval the opportunity is waiting for - Report which customer type drops out at which stage and measure the productivity of the sales team - Have the whole team reply from a single WhatsApp number, with conversations assigned according to the rule you define - Developer Project Calendar | For a property developer that is your customer, every housing project is a record of its own under the account; the project's launch, sales office opening and handover dates are fields on that record; which project the software will go live on is attached to the opportunity through that project record, and projects with a launch coming up drop into the list by date. - Office User Licences | The number of user licences given to an estate agency and the renewal day are fields on the account record; when the office increases the number of agents, the request for extra licences is opened as a new opportunity record under the same account. - Decision Maker's Objection Note | The portfolio manager, finance and IT are separate contact records attached to the same estate agency organisation; what each of them objected to sits in a note on their own contact card, and when the salesperson changes those notes are handed over together with the organisation's record. - Franchise Head Office Approval | In estate agencies belonging to a chain, whether the decision will come from head office or from the branch is a field on the opportunity; head office and the branch are separate account records, and the fact that a conversation running at the branch is waiting for head office approval is read from the same opportunity. - Pilot Portfolio Migration Record | How many of the listings of an estate agency running a pilot have been migrated is a migration record attached to the opportunity; missing fields and error notes sit on that record, and who corrected what in the second round is seen from the same place. ##### Frequently asked questions - Where do we see that a conversation running at a branch is waiting for head office approval? | In estate agencies belonging to a chain, head office and the branch are separate account records, and where the decision will come from is a field on the opportunity. That a conversation running at the branch is waiting for head office approval is read from that field; opportunities waiting for approval are gathered in a single list through the filter on the same field. - How long does setup take for proptech? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your property technology process needs becomes clear in that call. We migrate your data; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Will it integrate with my existing systems for proptech? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for proptech? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all the messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can follow the conversations and the response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Psychology Clinic CRM: Session Notes and Balance | Rapitek](https://rapitek.com/en/psychology-clinic-crm) A recurring session is set up as a single plan; a group session is one record, every client who attends is attached to it as a separate line, and the places are read from that record. ##### What we set up, and how - Keep client information and session notes in a single system whose access is set therapist by therapist - Set up the online appointment and the recurring session plan together; tie the timing of the reminder to a rule, and paste the meeting link into the field on the appointment record yourself - Build up the note of every session in the same client file and read the progress from beginning to end - Keep the session fee and the package lines on the client card; have the remaining balance calculated from those lines and overdue ones dropped into the list - Send appointment reminders over your WhatsApp Business account connected during setup and keep the communication on a corporate channel - Client Access Permissions | Access is limited by role-based permissions; a therapist can be authorised to see only their own clients. Each tenant's data sits in a separate database, and transfer is done over TLS. - Appointment and Session Planning | An appointment is a record with therapist and time fields; recurring sessions are opened as a series and the reminder is tied to the date. For an online session the meeting link is a link you paste into a field on the record; the Zoom and Meet connection is built specifically for the project, there is no out-of-the-box module. - Session Note | The session note accumulates under the client record with its date; the progress is read from beginning to end on the same card. - Payment and Package Balance | The fee and package lines sit under the client card; every session takes one use off the package, the remaining balance is calculated from those lines, and an overdue line drops into the list. - Group Session Attendance | A group session is a single record; every client who attends is attached to that record as a separate line, and who came to which sitting and whether the group's places are full are read from the same record. ##### Frequently asked questions - Is client information safe? | Each customer's data is held in a separate database; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256, two-step verification secrets are encrypted at rest, and access is limited by role-based permissions. Authorisation is done therapist by therapist. The hosting is in the European Union: the database is in Finland and the media files are in Frankfurt. Under article 9 of KVKK this counts as a transfer abroad; that is why we run the disclosure and explicit consent processes. A small number of sub-processors work outside the EU; we list each of them and where they process the data one by one in our privacy policy. - Can I manage online therapy appointments? | You plan face-to-face and online sessions from the same calendar; we build the Zoom and Google Meet connection as well, there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and its fee in writing in the discovery call. When this is not built, you use the meeting link field on the appointment record: you open the meeting in your own account, paste the link into that field, and the reminder that goes to the client carries that link; if the field is left empty, the reminder goes out with the time only. - How are the session fee and the package balance followed? | The fee and package lines sit under the client card; every session takes one use off the package and the remaining balance is calculated from those lines. An overdue payment line drops into the list; you tie when and through which channel the reminder goes out to a rule during setup. It is not a module that issues invoices; the collection trail is kept on the record. - Can group therapy sessions be tracked? | Yes. A group session is a single record; every client who attends is attached to that record as a separate line. Who came to which sitting and whether the places are full are read from the same record; individual sessions sit separately on the client's own record. - How long does setup take for a psychology clinic? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your psychology clinic process needs becomes clear in that call. We migrate your data; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. ### [Psychology and Psychotherapy CRM: Session Notes | Rapitek](https://rapitek.com/en/psychology-crm) The session note sits inside the session's own record and is visible to no one but the psychologist who wrote it; appointment, collection and invoice are attached to the same client card. ##### What we set up, and how - Keep every client's reason for referral, the therapy approach applied and the session history on a single card open only to you - Have the date and the duration written to the record on their own while you fill in the session note with the CBT, EMDR, ACT and couples therapy templates defined during setup - Turn the request that comes from the booking form you placed on your website into a session record and paste the meeting link into the field on that record - Keep the sale of session packages and the invoice record in the CRM; have overdue payments drop into a list and tie the reminder to that list by a rule - Keep the case notes you open to supervision in a separate field and follow session continuity through anonymous reports - Client Card and Access | The client is a record of their own; the reason for referral, the therapy approach applied, the session history and the payments are its fields. Notes are visible only to the psychologist who is logged in; access is limited by role-based permissions. Because the hosting is in Finland, the processing counts as a transfer abroad under article 9 of KVKK; that is why we run the disclosure and explicit consent processes. - Session Note Template | The session note sits inside the session record; separate templates for CBT, EMDR, ACT and couples therapy are defined during setup, and the date and the duration are written to the record on their own. - Online Appointments and Video Sessions | The booking form is placed on your website; the request that comes in is turned into a session record, and the reminder runs off that record. The meeting link is a field on the record; you open the meeting in your own Zoom or Google Meet account, paste the link into that field, and the reminder carries that link. - Invoicing and Collection | The sale of a session package, the payment and the invoice record are kept inside the CRM; overdue payment lines drop into a list and the reminder is tied to that list by a rule. The payment provider and e-invoice connection is built specifically for the project; there is no out-of-the-box module, and until it is built the collection is entered by hand on the payment line. - Supervision Note | A case note opened to a supervisor is a separate field and is shared independently of the session note; session continuity and anonymous case statistics come out of the report on these records. ##### Frequently asked questions - Is a CRM essential for a psychologist? | Even for a psychologist working alone, a CRM simplifies client tracking, invoicing and appointment processes and saves hours. If you run a clinic or a centre it is already essential — it prevents several psychologists from clashing over the same client and applies the confidentiality rules. - Can other psychologists see the session notes? | No. Every session note is by default visible only to the psychologist who wrote it. There are separate, opt-in fields for supervisor sharing and case discussion. The hosting is in the European Union: the database is in Finland and the media files are in Frankfurt. Under article 9 of KVKK this counts as a transfer abroad; that is why we run the disclosure and explicit consent processes. - Can I hold online video sessions? | We build the Zoom and Google Meet connection; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and its fee in writing in the discovery call. Without this being built you use the meeting link field on the session record: you open the meeting in your own Zoom or Google Meet account and paste the link into the field; the e-mail and WhatsApp reminders that go to the client (24 hours and 1 hour before) carry that link. The invoice record after the session is opened inside the CRM. - How do I add the online appointment system to my website? | The booking form is added to your website, your Instagram bio or your Linktree page with a single line of embed code; the client sees your available hours, fills in the form, and the request reaches you as an appointment request that you then turn into a session record in the calendar. To take payment on the form, we build the payment provider connection; there is no out-of-the-box module. The connection is built specifically for the project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and its fee in writing in the discovery call. Without this connection being built, the collection is entered by hand on the payment line on the client card. ### [Real Estate Development / Contractor CRM | Rapitek CRM](https://rapitek.com/en/real-estate-development-crm) Whether a unit is available, on option or sold is a field on the unit's own record — as is who holds the option and since when. Down payment and instalments sit line by line under the sale record. ##### What we set up, and how - Keep projects, blocks and units on one screen together with their available, on option and sold statuses - Segment prospective buyers by budget, location and unit type preference - Keep down payment and instalment lines with their due dates; let overdue ones drop onto a list, and tie the late-payment reminder to that list as a rule - Watch which salesperson ran how many tours and closed how many sales from a live dashboard - Let your whole sales team answer customers over a single WhatsApp number - Project and Unit Management | A unit is a record, tied to a block and the block to a project; available/on option/sold is a field, and stock is read from the list of that field. - Unit Type Preference Matching | A prospective buyer's budget, preferred floor and unit type are fields on the prospect record; when a unit whose option has lapsed goes back on sale, prospects matching those fields are filtered and a contact task falls to their consultant. - Payment Plan Tracking | Down payment and instalments sit line by line under the sale record; a line past its due date drops onto a list, and the notification task is tied to that. - Sales Team Performance | Tour and sale records carry a representative field; who ran how many tours and closed how many sales is read from the dashboard of that field. - Key Handover Report | The handover of a unit is a report tied to the sale record; the handover date, the snag list the buyer dictates and the person handing over the keys sit in fields, and the person taking delivery signs on the signature screen in the mobile app. ##### Frequently asked questions - Can the same unit be put on option for two buyers at once? | A unit is a record, and its available/on option/sold status is a field on that record; who was given the option and on what date sits on the same record. Because the whole team looks at the same list, the status is seen before a second option is given. - Which prospective buyers can I offer a unit to when its option lapses? | A prospective buyer's budget, preferred floor and unit type are fields on the prospect record. When the unit goes back on sale, prospects matching those fields are filtered and a contact task falls to their consultant. - How do we see a buyer whose instalment is late without waiting for the end of the month? | Down payment and instalments sit line by line under the sale record; each line's due date and paid status are in its fields. Lines past their due date drop onto a list according to those fields, and the call task is opened from that list. How many days late a buyer has to be, and through which channel the reminder goes, is set as a rule during setup. - How long does setup take for Real Estate Development / Contractor? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your real estate development process needs becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for Real Estate Development / Contractor? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for Real Estate Development / Contractor? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Recycling CRM: Containers and Buyer Quotes | Rapitek CRM](https://rapitek.com/en/recycling-crm) Every container in the field sits under the waste producer's account with its last collection date. Ticket number and tonnage are written to the same record as the task closes. ##### What we set up, and how - Keep waste producer companies and the number of containers on site on the account record, and see fill status and the last collection date - Open the collection request as a task, assign the vehicle and driver, and close arrival on site from the mobile app with GPS verification - Issue quotes with a validity date to buyers of processed material, and close the old quote's validity when the price changes - Track the expiry dates of licences, permits and transport documents, and create the renewal task in advance - Waste Producer Accounts | The factory handing over its waste is an account record; contract start, waste code and the number of containers on site sit in that record's fields. - Collection Request | Every collection is a task; it sits in vehicle, driver and address fields, and the weighbridge ticket number and tonnage are written to the record as the task closes. - Buyer Quote | A sales quote is a record with a validity date; tonnage and unit price sit in line items, and once the date passes the quote drops off the open list. - Document Tracking | Licences and permits are date fields on the account record; documents approaching expiry drop into a list and the renewal task is opened from there. ##### Frequently asked questions - Can I see from the CRM which containers in the field are full? | The container sits under the waste producer's account together with its count and last collection date; when the driver closes the emptying from the mobile app the date updates, and points that have not been collected for a long time move to the front of the list. - Which record are the weighbridge ticket and tonnage written to? | As the collection task closes, the weighbridge ticket number, the tonnage and the waste code are written to that task's fields; this way how much material came from which company in which month is read from the account record's history. - Can I be warned before licences and permits expire? | Licences and permits are date fields on the account record; documents approaching expiry drop into a list and the renewal task is opened from that list. - Which is the best CRM software for recycling? | When choosing a CRM for the recycling sector you should look at sector workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself — we do: we configure the fields, stages and reports around your recycling process, we migrate your data, and we train your team. Before building our own platform our team completed more than 200 enterprise CRM projects in the Salesforce era; we bring that experience to the setup. - How much does a recycling CRM system cost? | On the recycling side every collection is a task with vehicle, driver and address fields; it is this field crew that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope and any setup fee are worked out together in the discovery call and shared with you in writing. The Rapi AI credit and ERP integration are items priced separately. - How are CRM integrations done in the recycling sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built per project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them with you in writing. - How does migrating to a CRM work in the recycling sector? | We start with a discovery call: we work out your recycling process together, which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for recycling? | In recycling a vehicle and driver are assigned to the collection task, and arrival on site is closed from the mobile app with GPS verification. 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. ### [Renovation CRM: Site Survey and Trade Scheduling | Rapitek](https://rapitek.com/en/renovation-crm) The survey note and photo are attachments to the quote, and every revision is kept with its own date. Budget and actual cost are lines on the same project record; the gap shows during the work. ##### What we set up, and how - Attach the site survey note and the photo to the quote, and write every revision and approval step to the record - Keep a material list per project and compare the budgeted cost with the actual cost side by side - See which tradesman is on which project and on which day in a single schedule - Follow the stage, the photo diary and the handover date of every project - Send progress photos and status updates to the customer over WhatsApp - Project Quote Management | The site survey note and photo are attachments to the quote; every revision is kept with its own date, and the approval is written to the record as a stage change. - Material and Cost Tracking | The budget and the actual cost are line items on the project; the difference appears on the project card as the total of those lines. - Tradesman and Team Coordination | Jobs are tasks assigned to a person; which tradesman is where on which day is read from the calendar and the task list. - Project Progress Tracking | The stage, the handover date and the photo diary sit on the project record; progress is followed from the same card without keeping a separate file. - Snagging List at Handover | Every item found missing at the handover of the keys is a separate task; the person responsible and the closing date sit on the task, and the project file does not count as complete until all of these tasks are closed. ##### Frequently asked questions - How does the site survey and quoting process work? | Record the customer's request, plan a site survey appointment, take photos and notes on site, then create a detailed quote. The whole process is followed in the CRM. - Can I track material costs? | Yes, you can carry out a profitability analysis by comparing the material list per project, the supplier prices and the actual costs. - Can I manage more than one project at the same time? | Yes, you can see and manage all your active projects, their priorities and their team assignments from a single panel. - How long does setup take for renovation work? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your renovation process needs becomes clear in that call. We migrate your data; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. ### [Restaurant CRM: Bookings and No-Show Records | Rapitek CRM](https://rapitek.com/en/restaurant-crm) A booking is a record with date, time, party size and table fields, attached to the guest card. The no-show is a field, so repeated cancellations are read from the history. ##### What we set up, and how - Take the booking onto the record with date, time, party size and table fields, and schedule the confirmation message from that record - Mark the guest who did not turn up on the record and see repeated cancellations in the history on the guest card - Send a satisfaction survey after service, turn a negative reply into a case record and drop it to the person responsible - Gather corporate guests on an account record, build up the bills over the month and produce the month-end invoice from there - Booking Record | A booking is a record with date, time, party size and table fields; it is attached to the guest card, and the evening's list comes out of it. - No-Show Information | A guest who does not turn up is marked in a field on the record; repeated cancellations are visible in the history on the guest card. - Satisfaction and Complaints | The survey after service is sent to the guest; a negative reply opens a case record and stays in the list until its owner closes it. - Corporate Account | A company is an account record; the bills over the month accumulate under the account, and the month-end invoice is compiled from those records. ##### Frequently asked questions - What does tracking no-shows actually give you in practice? | The no-show is a field on the booking record and it is written to the guest card. How many times the same person has failed to turn up without warning is read from the history; and because the confirmation message is scheduled off the booking record, you hear back before the table is left empty. - What is done so that a guest's complaint does not stay with the service staff? | A negative reply to the satisfaction survey sent after service opens a case record; it does not leave the list until an owner is assigned and it is closed. How many times the same issue has recurred is also visible from the report on these records. - How do we produce the month-end invoice for corporate guests? | A company is an account record and the bills over the month accumulate under that account. The month-end invoice is compiled not by collecting receipts one by one, but by listing the records under the account over a date range; which person came on which day sits in the same list. - Which is the best CRM software for a restaurant? | When choosing a CRM for the restaurant sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your restaurant process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Restaurant CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the restaurant sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the restaurant sector? | We start with a discovery call: together we work out your restaurant process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for a restaurant? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Retail CRM: Store, Website and Marketplace Records | Rapitek](https://rapitek.com/en/retail-crm) Store sales, online orders and return cases accumulate under one customer record, and duplicate cards are merged. Every store is a unit, with the target and the actual in its fields. ##### What we set up, and how - Bring the store, website and marketplace records together on a single customer card, matching duplicate records and merging them down to one card - Compare the target, the actual sales and staff performance store by store and region by region in the same report - Gather return, exchange and complaint cases in a single channel-independent queue and route them with the assignment rule defined during setup - Send campaign and loyalty communication from a single customer segment rather than from channel lists - A Single Customer Record | The customer is a single record independent of the channel; the store sale and the online order are attached beneath it, and duplicate records are merged down to a single card. - Store Unit and Target | Every store is a unit record; the target and the actual sales sit in its fields, and the regional comparison is the report in which these units are grouped. - Case Queue and Assignment | Returns and complaints are case records; the channel they came in from sits in a field, and the assignment rule defined during setup drops the case to the store concerned or to the head office team. - Segments and Communication | A segment is a filter defined on the customer fields; SMS and WhatsApp sends go to that filter, and no separate channel lists are kept. ##### Frequently asked questions - How do we bring the same person who shops in store and online down to a single record? | The customer record is opened for the person, not for the channel; duplicate records that match on fields such as the phone number and the e-mail address are merged and the history is gathered on a single card. After the merge the store sale and the online order appear side by side in the same history. - Can we compare the performance of dozens of stores from one place? | Because every store is a separate unit record, the target, the actual sales and the number of cases are kept store by store; the regional and chain totals come out of the report in which these units are grouped. A store manager can be authorised to see only their own unit's data. - When an item bought online is returned to a store, who does the case go to? | The return or the complaint drops into a single case queue together with a field for the channel it came in from. The assignment rule defined during setup drops the case to the store concerned or to the head office team; whichever channel the case comes in from, it appears under the same customer record, so the store sale and the online order are not closed without seeing each other. - Which is the best CRM software for retail? | When choosing a CRM for the retail sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your retail process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Retail CRM system cost? | In retail a case drops to the store concerned or to the head office team, so the people in the store and at head office are defined in the same system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the retail sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the retail sector? | We start with a discovery call: together we work out your retail process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for retail? | Yes. Field and branch teams can update the customer card, the note and the follow-up task from their phones. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Robotics CRM: Commissioning and Cell Records | Rapitek CRM](https://rapitek.com/en/robotics-crm) A cell is a project record; the part weight, the reach and the target cycle time sit in its fields. After handover the same cell lives on as an equipment record. ##### What we set up, and how - Write the part weight, the reach and the target cycle time into the fields of the project record and attach the site survey photo - Follow feasibility, commissioning, the acceptance test and operator training as separate stages and see which project is waiting where - Keep every cell you have handed over on an equipment record and write the software version loaded and any later change to that record - Put the case opened at a line stoppage into the queue and route it to the engineer on duty with the assignment rule defined during setup, then close the site visit with location verification - Application Feasibility | A cell is a project record; the part weight, the reach and the target cycle time sit in its fields, and the site survey photo is attached to it. - Commissioning Stages | The acceptance test, the operator training and the handover report are stages of the project record; the steps still waiting are filtered by that field. - Installed Cell Record | A cell that has been handed over is an equipment record; the software version and any later changes are written to that record with their dates. - Line Stoppage Case | A line stoppage is a case record; it drops into the queue, its owner is set by the assignment rule defined during setup, and the site visit is closed with a location-verified task. ##### Frequently asked questions - How are the cycle time and the part weight taken at the site survey attached to the quote? | These measurements — the part weight, the reach and the target cycle time — are fields on the project record, and the quote is produced under that record. When one of the measurements changes, the quote is prepared again and the previous version stays on the record with its date; which figure was given on which assumption is not lost. - Can we find the software version of a cell we handed over afterwards? | Yes. A cell that has been handed over is not deleted when the project closes, it stays as an equipment record; the version loaded and every change made later are written to that record with their dates. A fault report that comes in years later is attached to the same record, so the history accumulates in one place. - Which engineer does the case opened at a line stoppage go to? | A line stoppage is a case record and it drops into a single queue; the assignment rule defined during setup determines its owner. Because the case is attached to the equipment record of whichever cell it belongs to, the engineer on the way reads the software version and the past interventions en route; the visit is closed from the mobile app with location verification. - Which is the best CRM software for robotics? | When choosing a CRM for the robotics sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your robotics process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Robotics CRM system cost? | In robotics a line stoppage case is routed to the engineer on duty, so the people on the service side are defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the robotics sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the robotics sector? | We start with a discovery call: together we work out your robotics process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for robotics? | In robotics the site visit made for a line stoppage is closed with a location-verified task. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Security Services CRM: Shift Plan and Patrol Record | Rapitek](https://rapitek.com/en/security-services-crm) Every customer site is an account record; the headcount in the contract, the shift pattern and the monthly fee sit in its fields. Certificate and ID card expiry are dates on the staff record. ##### What we set up, and how - Keep the customer sites and the number of people to work at each site on an account record, and build the shift plan with working hour definitions - Have patrols and site checks marked from the mobile app and confirm the location with GPS verification - Have the incident report written on site, attach it to the site record and send a push notification to the person responsible - Follow staff certificate, ID card and contract renewal dates and drop the ones coming up into the list - Service Site | Every customer site is an account record; the headcount in the contract, the shift pattern and the monthly fee sit in the fields of that record. - Shift Plan | The guard duty is set up with shift and working hour definitions; who goes to which site is determined by the assignment rules defined during setup, and any change is read from the plan. - Patrol Record | The patrol round is marked from the mobile app; the location is verified by GPS and spoofed location reports are detected. - Document Expiry Dates | Certificate and ID card expiry are date fields on the staff record; the ones coming up drop into the list, and the renewal task is opened from there. ##### Frequently asked questions - Can I see from the CRM which officer is at which site and on which shift? | Yes. The site is an account record and the plan is built on shift and working hour definitions; the assignment rules defined during setup determine who goes where, and a change made during the day is read from the same plan. - Can patrols and incident reports be recorded on site? | The patrol round is marked from the mobile app and the location is verified by GPS, with spoofed location reports detected; the incident report is written on site and attached to the site record, and a push notification is sent to the person responsible. - Where do I see the staff whose certificate or ID card is about to expire? | Certificate and ID card expiry are date fields on the staff record; the ones coming up drop into the list on that field and the renewal task is opened from there. The contract renewal date is a date field in the same way. - Which is the best CRM software for security services? | When choosing a CRM for the security sector you should look at sector-specific workflows, integration capabilities, customisation options and the quality of support. You do not set Rapitek CRM up yourself, we set it up: we configure the fields, the stages and the reports around your security process, we migrate your data, and we train your team in Turkish. Before building our own platform our team completed more than 200 enterprise CRM projects in its Salesforce years; we carry out the setup with that experience. - How much does a Security CRM system cost? | On the security side, who stands guard at which site is determined by the assignment rules; it is this body of staff that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi artificial intelligence credit and the ERP integration are separately priced items. - How are CRM integrations done in the security sector? | If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because the access rights and the field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - How does the move to a CRM system work in the security sector? | We start with a discovery call: together we work out your security process and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data, and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that built and develops the product — this is a choice, not a matter of capacity. - Can a mobile CRM be used for security services? | In security the patrol round is marked from the mobile app; the location is verified by GPS and spoofed location reports are detected. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Skincare Center CRM: Skin Analysis & Sessions | Rapitek CRM](https://rapitek.com/en/skincare-center-crm) Skin type, allergies and goals are fields on the client record; the package's remaining sessions and end date sit on the same card, and the renewal offer comes from there. ##### What we set up, and how - Record skin type, allergies and goals at the first consultation and attach the device analysis results as files to the same card - See the number of sessions, the session interval and the remaining sessions in a package on the client record; let those nearing their end drop into a list - Recommend home care products suited to the skin type at the end of a session and post the sale to the same record - Segment seasonal campaigns such as summer sun protection or winter dryness by skin type and send them over WhatsApp and email - Archive the standard-angle photographs taken at each session and compare the change over 3-6 months - Skin Analysis and Type Assessment | Skin type (dry, oily, combination, sensitive), allergies and goals are fields on the client record; the image and report from the device analysis sit as attachments on the same card. - Care Package and Session Tracking | A package is a record; the number of sessions, the interval between sessions, the remaining sessions and the end date are its fields, and a renewal task drops into the list according to the time left until it ends. - Product Recommendations and Sales | The home care product recommended at the end of a session, the sales record and the product history are fields on the client record; the e-commerce connection is set up specifically for your project, there is no out-of-the-box module. - Season and Campaign Segmentation | The campaign list is filtered on the skin type field; summer sun protection, winter dryness and holiday campaigns are built onto that list and sent over WhatsApp and email from the same record. - Before and After Photo Archive | The standard-angle photograph taken at each session is an attachment on the client record; because it is stored with its date, the change over 3-6 months is compared from the same card. ##### Frequently asked questions - How does the skin analysis system work? | We build the connection to devices such as VISIA or a dermatoscope ourselves; there is no out-of-the-box module. The image and report the device produces are added to the client record as files; skin type, allergies and goals are fields on the same card. If a device connection is wanted, it is set up specifically for your project by our professional services team over our REST API, OAuth2, webhooks and import/export, and its scope and cost are shared in writing at the discovery meeting. When the analysis is repeated every 3-6 months, the comparison is made on the same card. - How are session packages sold and tracked? | An upfront payment is taken for each package; the number of remaining sessions and the package expiry date are fields on the package record and are visible on the client card. Packages nearing their end drop into a list according to those fields; you set a rule at setup for how many sessions or how many days ahead the renewal offer appears. - Are home care product sales integrated? | We build the connection to Shopify, WooCommerce or another e-commerce platform ourselves; there is no out-of-the-box module. The connection is set up specifically for your project by our professional services team over our REST API covering 183 business objects, OAuth2, webhooks and import/export, and its scope and cost are shared in writing at the discovery meeting. Until the connection is in place, store orders are entered with an import file or by hand; the product recommendation that comes out of the skin type at the end of a session, the sales record and the client's product history are still kept in the CRM, and renewal reminders are produced from there. - How does the loyalty programme work? | Each package and product bought is written to the sales record; you define at setup how many points a given amount corresponds to, and the points accumulate in a field on the client record. The points are used on the next session or product; because the spending total sits in a field, the VIP campaign list is filtered from that field. ### [Smart City Technologies CRM: Tender Calendar | Rapitek CRM](https://rapitek.com/en/smart-city-crm) A tender is an opportunity record: decision date, specification and bid sit on one card; municipal and private-sector lines run in separate stages, commissioning ties to the project. ##### What we set up, and how - Track every tender on a single opportunity record with its own bid stages, decision date and documents - Set up separate sales processes with different stages and rules for municipal and private-sector customers - Record every meeting held with municipal officials, project stakeholders and technical teams - Prepare bids that match the tender requirements and run the contract process digitally - Let the whole team answer from a single WhatsApp number, with the conversation history staying on the record even when staff change - Tender and Project Tracking | Every tender is an opportunity record; the bid stages, the decision date and the tender documents sit on the same card. Stage names are named to fit your own process at setup. - Public-Private Sector Pipeline | Two separate sales lines are defined; municipal and private-sector opportunities move through their own stages and are seen both separately and together in the report. - Stakeholder Relationship Management | The authorised contact, the stakeholder and the technical team are each a person record linked to the organisation card; whoever a meeting note comes from, it stays in that organisation's history. - Bid and Contract Process | The bid is produced with its line items under the opportunity; the contract stage moves along on the same card, and the signature and revision steps are defined at setup. - Field Commissioning Record | Pole, sensor and camera installations are commissioning records tied to the project; the number of points, the installation date and the authority's acceptance status sit in fields, and the team being on site is confirmed with location verification in the mobile app. ##### Frequently asked questions - How can we track public tenders in the CRM? | In Rapitek CRM you can define each tender as a separate opportunity and track the bid preparation stages, the decision dates and the related documents. With tender calendar reminders, do not miss a single opportunity. - Can we manage municipal and private-sector customers separately? | Yes. In Rapitek CRM you can create different sales pipelines for different customer segments. The public sales process and the private-sector process are managed with separate stages and rules. - How long does setup take for Smart City Technologies? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your process on smart city projects needs becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Can more than one person on a Smart City Technologies team use the same WhatsApp number? | On the Smart City Technologies side the whole team answers stakeholder correspondence from a single number, and the history stays on the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Software Development CRM: Proposals and Support Records](https://rapitek.com/en/software-development-crm) Support requests, bug reports and development requests land in the same queue; the type field separates them, and the licence renewal date is a field on the customer card. ##### What we set up, and how - Produce a proposal from the customer request, track its stages, measure the conversion rate - Collect support requests, bug reports and development requests in a single queue and separate them by type - Run project-based invoices, monthly licence tracking and payment reminders - Move potential projects forward through the Request, Analysis, Proposal and Contract stages - Let the whole team answer the customer from a single WhatsApp number - Project Proposal Management | A request is opened as an opportunity record; the proposal is produced under it with its line items, and the conversion rate comes out of the stage report. - Customer Support Tracking | Support requests, bug reports and development requests land in the same queue as records; because the type is written in its field, separating them is done with a filter. - Revenue And Invoice Tracking | Licence and project lines sit under the customer card; a reminder task is opened based on the renewal date field. - Pipeline Management | The Request, Analysis, Proposal and Contract stages are defined on the sales pipeline; the time spent waiting at a stage is calculated from the record dates. - Scope Change Request | An additional request arriving on an ongoing project is a change request linked to the project; the delivery date it affects, the additional fee and the customer's approval sit in fields, and no development task is opened until the approval arrives. ##### Frequently asked questions - How do we tell a bug report apart from a paid development request? | Support requests, bug reports and development requests land in the same queue as records; because the type is a field on the record, separating them is done with a filter, and billable work is collected in a separate list. - How is an additional request on an ongoing project managed? | An additional request is a change request linked to the project; the delivery date it affects, the additional fee and the customer's approval are its fields. No development task is opened until the approval arrives, so out-of-scope work does not quietly begin. - How long does setup take for software development? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your software sales and support process requires becomes clear in that call. We migrate your data ourselves; the scope of the migration, and its cost if there is one, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for software development? | On the software development side, the proposal in sales, the incoming bug record and the monthly licence invoice most often sit in separate tools. 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - Can more than one person use the same WhatsApp number for software development? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can follow the conversations and the response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Solar Energy CRM: Bids and Grid Applications | Rapitek CRM](https://rapitek.com/en/solar-energy-crm) Roof area, consumption data and target installed capacity are fields on the project record; bid revisions are versioned, and a price past its validity date drops off the open list. ##### What we set up, and how - Run rooftop and ground-mount projects through separate processes, and keep consumption data and target installed capacity on the opportunity record - Version the bid together with its revisions, and stop a price past its validity date from staying on the open list - Track connection application and contract dates as fields, and list the files awaiting an answer by date - Set up a follow-up task and reminder sequence for projects that have been inactive for a long time - Project Opportunity | Every solar project is an opportunity record; roof area, consumption data and target installed capacity sit in fields on that record. - Bid Version | A bid is a record with a validity date; revisions accumulate as separate versions, and a price whose term has expired drops off the open list. - Application Tracking | The distribution company application is a date field; the application date and the expected answer date are entered on the record, and overdue files drop into a list. - Follow-up Sequence | A contact sequence can be defined for a project that has gone quiet; when the number of days you set runs out, that definition supports opening a task for the person responsible and scheduling a message to the customer. ##### Frequently asked questions - How does the CRM keep bid revisions and price validity? | Every bid is a record with its own validity date and revisions accumulate as separate versions; which price went to the customer last and on what date is read from the record, and a bid whose term has expired drops off the open list. - Can I track the applications made to the distribution company? | The application date and the expected answer date are fields on the project record; these dates do not arrive automatically from the distribution company's systems, your team enters them, but once entered, files whose answer is overdue drop into a list and a reminder goes to the person responsible. - Can I run a rooftop project and a ground-mount project through separate processes? | Every solar project is an opportunity record; roof area, consumption data and target installed capacity sit in fields on that record. Because the stages are set up to fit your process, rooftop and ground-mount projects move through separate stage sets and do not get mixed into the same list. - Which is the best CRM software for Solar Energy? | When choosing a CRM for the Solar Energy sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your solar energy process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Solar Energy CRM system cost? | On the Solar Energy side it is your project team that enters the grid application date onto the record; that team is who uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Solar Energy sector? | On the Solar Energy side the distribution company application is a date field; your team enters the application date and the expected answer date. 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Solar Energy sector? | We start with a discovery meeting: we work out your solar energy process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Solar Energy? | Yes. Field and branch teams can update the customer record, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Solar Panel Installation CRM: Survey to Commissioning](https://rapitek.com/en/solar-panel-installation-crm) Every installation is a work order record; crew, date and site address are its fields. Warranty expiry and periodic maintenance dates sit on the same record, and sites that are due drop onto a list. ##### What we set up, and how - Plan the survey, installation and commissioning steps on the work order record, and see crew and date clashes on the calendar - Add the roof measurement and site photos to the record from the mobile app, and confirm the crew's arrival on site with GPS verification - Have the handover report signed on site from the signature screen in the mobile app, and keep the signed document attached to the installation record - Keep warranty and periodic maintenance dates on the installation record, and let sites due for maintenance drop onto a list - Work Order | Every installation is a record; crew, planned date and site address are in its fields, and the stages from survey to commissioning move forward on that record. - Site Verification | The crew's arrival on site is marked from the mobile app; the location is verified by GPS and fake location reports are detected. - Handover Report | The person taking delivery signs the commissioning report on the signature screen in the mobile app; the signed document is attached to the installation record and read from there in a warranty dispute. - Maintenance Calendar | Warranty expiry and periodic maintenance are date fields on the installation record; sites that fall due drop onto a list, and the visit task is opened from that list. ##### Frequently asked questions - How do I see that the installation crew went to site and finished the job? | The crew opens and closes the work order from the mobile app; arrival on site is verified by GPS, fake location reports are detected, and the photos taken and the measurement note accumulate as attachments on the same record. - Can I have the commissioning report signed on site? | Yes. The person taking delivery signs the report on the signature screen of the mobile app on a phone or tablet, and the signed document is tied to the installation record; when a warranty question comes up later, what was delivered on which date is read from the same record. - Where do I see the installations due for maintenance? | Warranty expiry and periodic maintenance are date fields on the installation record; sites that fall due drop onto a list and the visit task is opened from that list. A fault call, meanwhile, is opened as a request record tied to that installation. - Which is the best CRM software for Solar Panel Installation? | When choosing a CRM for the solar panel installation sector you should look at industry workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports around your solar panel installation process, we migrate your data, and we train your team in Turkish. Before we built our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce years; we do the setup with that experience. - How much do Solar Panel Installation CRM system prices cost? | On the solar panel installation side the work order carries crew, planned date and site address fields; it is this field workforce that uses the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. 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 in the discovery call and shared in writing. The Rapi AI credit and ERP integration are separately priced items. - How are CRM integrations done in the Solar Panel Installation sector? | On the solar panel installation side the survey information stays on one person's phone and the dispatch of the material in another exchange of messages. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the Solar Panel Installation sector? | We start with a discovery call: we work out your solar panel installation process together, and which fields and which stages are needed. After the call we give you a date, not a range. We migrate your data and we train your team in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Solar Panel Installation? | In solar panel installation the roof measurement and site photos are added to the record from the mobile app, and the crew's arrival on site is verified by GPS. The app is live on both the App Store and Google Play. The web interface works on tablets and phones too. The app does not work offline; if the connection drops while you are filling in a form, what you have typed is kept on the device for 24 hours. ### [Spa & Wellness CRM: Session Balance & Booking | Rapitek CRM](https://rapitek.com/en/spa-crm) Remaining sessions, therapist availability and room assignment are fields on one appointment record; the package balance drops each session, and a voucher stays tied to buyer and user. ##### What we set up, and how - Put the booking link on your website and in your Instagram bio, and let the customer pick the therapist, the service and the time themselves - Draw down package sessions at every appointment; let those nearing zero balance drop into a list, and tie the renewal offer to that list with a rule - Keep therapist specialisms, availability and room assignment on the same calendar so no clashing appointment is created - Keep the points built up at each session in a field on the customer record; let those passing the threshold and those with a birthday coming up drop into a list, and tie the bonus to that list with a rule - Manage gift voucher and combo package sales, including corporate bulk purchases, from a single interface - Online Booking Widget | The booking link goes on the website, in the Instagram bio or on Linktree; the therapist, service and time the customer picks are written into fields on the appointment record and appear on the therapist's calendar. - Package and Session Balance | A package is a line linked to the customer record; the total sessions and the remaining sessions are its fields. Every completed appointment draws down the remainder, and packages whose balance is nearing zero drop into a list. - Therapist and Room Assignment | The therapist's specialisms and availability are fields on their own record; the appointment carries the therapist field and the room field together, so a second entry cannot be opened for the same hour. - Loyalty Points | Points are a field on the customer record and rise with every completed session; customers who pass the threshold you define drop into a list, and the birthday is a separate date field. - Gift Vouchers and Combo Packages | A voucher is a record carrying the buyer and the user in separate fields; when it is used it appears in both people's history. Combo packages are defined with a line-item list. ##### Frequently asked questions - What are the Spa CRM features? | Spa CRM offers an online booking widget, package balance tracking, a therapist calendar, customer loyalty points, gift voucher sales and appointment reminders that go out from your own WhatsApp account. You define how many hours ahead the reminder goes. Because the package balance and the last visit date sit on the same customer card, no-show appointments and unrenewed packages are visible from the list; you report the effect from your own data. - Which types of spa is it suitable for: hamam, massage salon, day spa, hotel spa? | For a hamam (peeling-scrub-foam rotation), a massage salon (package-based) and a day spa (multi-service combo), the service durations, package definitions and therapist specialisms are defined as fields at setup. For a hotel spa we build the connection to the property management system (PMS) ourselves; there is no out-of-the-box module — matching by room number or posting to the hotel bill is not a setting that works the same way in every installation. The connection is set up specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; we share its scope and cost in writing at the discovery meeting. When this connection is not in place, the hotel guest's appointment is held in the CRM on their own customer record, the room number is entered in a field or a note, and matching with the hotel bill is done separately in the hotel's own system. - How do we add online booking to Instagram? | The booking link created in the CRM is added to the Instagram bio. The customer clicks the link, picks therapist + service + time, and the appointment takes its place on the therapist and room calendar; a confirmation message goes out from the WhatsApp Business account connected at setup. This is a link share: messages and comments arriving on Instagram do not reach the CRM this way. - Are gift voucher sales integrated with the loyalty programme? | Yes. A gift voucher is a record carrying the buyer and the user in separate fields, and it is linked to the customer record of both. When the voucher is used it appears in both people's history and their point fields rise; you tie who the notification message goes to with a rule at setup. ### [Sports Club CRM: Licence Expiry & Dues | Rapitek CRM](https://rapitek.com/en/sports-club-crm) An athlete's licence, medical report and insurance expiry are date fields on the same person record; those nearing expiry drop into a list before the squad is filed. ##### What we set up, and how - Keep each branch's squad separately, and write the athlete's licence, medical report and insurance expiry dates into fields on the record - Drop documents nearing expiry into a list and open the renewal task, sending the reminder to the athlete and their parent by SMS or WhatsApp - Tie sponsorship contracts to a record with their term, fee and committed items, and start the conversation before the renewal date - Track club membership and dues collection on the member record, and draw the general assembly invitation from that list - Branch Squad | Every branch is a squad record; the athlete is linked to it as a person record, and squad changes during the season leave a trace on the card. - Licence and Medical Report Expiry | The licence, medical report and insurance expiry are date fields on the athlete record; those nearing expiry drop into a list, and the renewal task is opened from here. - Sponsorship Contract | A sponsor is an account record; the term, the fee and the committed items sit in its fields, and the renewal date is read from this record. - Membership and Dues | Club membership is a record; the dues lines are held under it period by period, and those past due drop into a list. ##### Frequently asked questions - Can I see in advance which athlete is missing a document when filing the match squad? | Yes. The licence, medical report and insurance expiry are date fields on the athlete record; while the squad is being prepared, athletes whose documents have expired or are about to expire are listed with a filter, and the renewal task is opened from the same record. - How do we run an away trip inside the club? | An away trip is a record; the squad list and the transport and accommodation tasks are tied to it. Notification goes to the athlete, and to the parent of an athlete under eighteen, by SMS or WhatsApp from the same record, and who gave consent is visible on the card. - Can I see a sponsorship contract's renewal date in advance? | Yes. A sponsor is an account record; the term, the fee and the committed items sit in its fields. Contracts whose renewal date is approaching drop into a list, and the meeting task is opened from the same record. - Which is the best CRM software for a Sports Club? | When choosing a CRM for the Sports Club sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your sports club process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Sports Club CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Sports Club sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Sports Club sector? | We start with a discovery meeting: we work out your sports club process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a Sports Club? | Yes. Field and branch teams can update the customer record, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Staffing Agency CRM: Submissions & Fees | Rapitek CRM](https://rapitek.com/en/staffing-agency-crm) A submission is a record tying the candidate to the role; its date and the consultant who made it are its fields. On a placement, guarantee end and fee sit in the same chain. ##### What we set up, and how - Open every vacant role as a separate job record linked to the client account, and keep the salary range and the commission terms on the same card - Tie the submitted candidate, the submission date and the submitting consultant to the record, and prevent the same candidate going to the same company a second time - Log client feedback round by round and read from the role record which profile was rejected and why - Track the post-placement guarantee period and the fee date, and see approaching invoices on a single list - Open Role | A role is a job record linked to the client account; the salary range, the commission rate and the guarantee period sit in its fields. - Candidate Submission | A submission is a record tying the candidate to the role; the submission date and the submitting consultant are in fields, and a duplicate submission is seen from this record. - Feedback Rounds | Every reply from the client is a note tied to the submission; as the stage field changes, the candidate's status on the role is updated. - Placement and Fee | A placement is a record with a start date; the guarantee end and the fee amount are in fields, and approaching dates drop into a list. ##### Frequently asked questions - How do we prevent the same candidate being submitted to the same company by two consultants? | A submission is a separate record tying the candidate to the role, and it carries the submitting consultant and the date; when the candidate card is opened, which company they were previously submitted to and by whom is visible, so a duplicate submission is noticed while the record is being created. - Can we track the post-placement guarantee period and the commission fee? | Yes. The start date, the guarantee period and the fee amount are fields on the placement record; records whose guarantee end and invoice date are approaching drop into a list, and if the candidate leaves within the guarantee, the process is reopened on the same record. - Where do I read which profile the client rejected and why? | Every reply from the client is a note tied to the submission, and as the stage field changes, the candidate's status on the role is updated. That way, in the second round, which profile was rejected and why is read from the chain on the role record. - Which is the best CRM software for a Staffing Agency? | When choosing a CRM for the Staffing Agency sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your staffing agency process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Staffing Agency CRM system cost? | At a staffing agency, because every submission records the consultant who made it, the agency's consultants are each defined separately in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Staffing Agency sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Staffing Agency sector? | We start with a discovery meeting: we work out your staffing agency process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a Staffing Agency? | Yes. Field and branch teams can update the customer record, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Swimming Pool CRM: Service Visits & Chemicals | Rapitek CRM](https://rapitek.com/en/swimming-pool-crm) Every pool is a separate record; volume, equipment model and installation date are its fields, and service visits and the chemicals used build up under the same card. ##### What we set up, and how - Keep every pool in a separate record with its volume, equipment models and installation date, and link it to the estate or hotel account - Hold the scope and end date of annual maintenance contracts as fields and run approaching renewals from a single list - Plan season opening, periodic maintenance and chemical resupply as tasks; see that the technician has reached the site through location verification - Move the construction process of survey, quote and revisions along on a single opportunity record, and tie the breakdown call to the pool record - Pool Record | Every pool is a separate record; the volume, the equipment model, the installation date and the linked account are in its fields, and the whole service history builds up under this record. - Seasonal Pool Agreement | The season agreement tied to the estate or hotel account is a record; whether opening and closing jobs fall within scope, the visit frequency and the season end date are in its fields; those nearing their end drop into the renewal list. - Service Visit | Maintenance and season opening are each a task; the technician, the date and the pool are in fields, the job is closed from the mobile app, the location is verified, and the customer signs on the signature screen in the mobile app. - Chemicals and Readings | The chemical used and the reading taken are lines on the visit record; the same pool's past values are compared from the record. ##### Frequently asked questions - How do we plan maintenance appointments for hundreds of pools at the season opening? | Every pool is its own record and the visit frequency of the contract it belongs to sits in a field. Season opening jobs are opened from these records as bulk tasks and distributed by technician and date; because those left incomplete stay on a separate list, it is visible in the April pile-up which pool has not been visited. - Can we see which pump was fitted to a pool last season and which chemical was used? | Yes. The equipment model and the installation date are fields on the pool record; the chemical used and the reading taken at each service visit are written to that visit's lines. When the pool card is opened, all past visits are visible in chronological order. - Can we see in advance which estates and hotels have a season contract ending? | Yes. A season agreement is a record tied to the account; the scope, the visit frequency and the season end date are its fields. Those nearing their end drop into the renewal list and the meeting task is opened from there. - Which is the best CRM software for a Swimming Pool business? | When choosing a CRM for the Swimming Pool sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your pool construction and maintenance process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Swimming Pool CRM system cost? | In a swimming pool business the service task is opened with a technician field and closed from the mobile app, so the technicians are defined separately in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Swimming Pool sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Swimming Pool sector? | We start with a discovery meeting: we work out your pool construction and maintenance process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a Swimming Pool business? | In a Swimming Pool business, maintenance and season opening are each a task; the technician closes the job from the mobile app and the location is verified. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Telecom CRM: Commitment End & Line Inventory | Rapitek CRM](https://rapitek.com/en/telecom-crm) Every line and service carries its own commitment end date as a field; sites are separate records linked to the customer account, and those nearing their end drop into one list. ##### What we set up, and how - Keep a corporate customer's sites, and the lines and services at each site, in separate records linked to the account record - Track commitment end dates as fields, drop approaching renewals into a list, and open the meeting task from there - Plan field installation and circuit delivery jobs as tasks; take the location verification, and let the person taking delivery sign on the signature screen in the mobile app - Record sales coming through the dealer channel with their source and report on a single list which dealer brought in what - Customer and Site | A corporate customer is an account record; every site is a separate record linked to it, and the lines and services sit under the site. - Commitment Date | Every service's start, end and commitment end are its own date fields; those nearing their end are listed with a filter and the renewal task is opened. - Installation Task | Field installation is a task; the technician, the appointment time and the address are in its fields, the location is verified, and the person taking delivery signs on the signature screen in the mobile app. - Dealer Channel | A dealer is an account record; the source of an incoming sale sits in a field on the opportunity record, and the commission is read from the report on that field. ##### Frequently asked questions - How do I track dozens of lines for the same customer, each with its own commitment end? | The customer is an account record, the sites are linked to it, and every line carries its own commitment end date as a field. Services nearing their end come out on a single list with a date filter; you decide which range to look at, and the renewal task is opened from the list. - Can I see the sale coming from a dealer and the field installation in the same place? | Yes. The source of the sale is a field on the opportunity record, and the installation is a task tied to the same account; when the sale closes, the installation task drops to the field team through the assignment rule defined at setup, and everyone looking at the customer record sees which stage the job is at. - How do we record that the field installation was done on site and that delivery was accepted? | Field installation is a task; the technician, the appointment time and the address are its fields. When the technician closes the job from their phone, the location is verified, the person taking delivery signs on the signature screen in the mobile app, and the task leaves a trace on the customer record. - Which is the best CRM software for Telecom? | When choosing a CRM for the Telecom sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your telecom process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Telecom CRM system cost? | In telecom, because field installation is planned with technician and appointment fields, the field team enters the system just as much as the office side does. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Telecom sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Telecom sector? | We start with a discovery meeting: we work out your telecom process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for Telecom? | In telecom, field installation is a task; the location is verified and the person taking delivery signs on the signature screen in the mobile app. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Textile CRM: Sample Tracking, Season & Export | Rapitek CRM](https://rapitek.com/en/textile-crm) Which sample went to whom, in which variant, and did approval come back — all three sit on the customer record. Orders stay tied to the sample they came from; exports in their own currency. ##### What we set up, and how - Measure sales by season and collection, and compare them against the previous season - Record who each sample went to, its approval status and the feedback that came back - Manage export customers in USD, EUR and GBP on records whose exchange rate updates automatically - Log the prospects you meet at a trade fair against that event and plan the follow-up steps - Let the whole sales team answer on WhatsApp from one business number; conversations are assigned by the rule you define and the correspondence stays with the company - Collection-Based Sales | A collection is a campaign record; products and sales are linked to it, and the season comparison comes out of the report on that link. - Sample Management | A sample is a stage on the customer record; who it went to, on what date and in which variant sit in fields, and the ones awaiting approval drop into a list. - Multi-Currency | Currency is a field on the record and rates update daily; an export customer's revenue is reported both in their own currency and in its equivalent. - Trade Fair and Event Tracking | A fair is an event record; the prospect records opened there are linked to that event, and follow-up tasks are opened from the same list. - Order Size Assortment | The size and colour breakdown on an order is made up of line items on the order record; each line's quantity and shipping date sit in fields, a size shipped short stays open on the same order and drops in as a completion task. ##### Frequently asked questions - How can I manage collection seasons? | In Rapitek CRM you can define each collection as a separate campaign and link the relevant products and sales to that collection. This lets you compare performance from season to season. - How do I manage my customers abroad? | There is multi-currency support and reminders that respect different time zones; the interface is fully translated into Turkish and English, and text that has not been translated into other languages appears in English. An export customer's revenue is reported in their own currency together with its equivalent. - Is there a Logo/Netsis integration? | If you use Logo Tiger, Go, Wings or Netsis, your CRM talks to it — we build the connection. There is no out-of-the-box module: because access and field structure on the ERP side change from one installation to the next, a single button does not work the same way everywhere. The connection is built per project over our REST API covering 183 business objects, OAuth2 and webhooks; the scope and the cost for the account, stock and order fields are worked out in the discovery call and shared with you in writing. - Can more than one person on the textile team use the same WhatsApp number? | In textiles the whole sales team answers the buyer's messages from a single business number, and the correspondence stays with the company. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from one business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Theater CRM: Season Subscriptions & Group Seats | Rapitek](https://rapitek.com/en/theater-crm) The subscription end date is a field on the person record; a group booking moves through request, hold, deposit and confirmed stages, and expired holds show on the list. ##### What we set up, and how - Keep the season subscription's end date as a field and call subscribers entering the renewal period from a single list - Run school and company group bookings through request, hold, deposit and confirmed stages - Build up on each theatergoer's record which play they saw and when, and split the new production announcement by that history - Track venue conversations in tour cities, technical requirements and the revenue-share terms on a single record - Season Subscription | A subscription is a record linked to the person record; the package, the start date and the end date are in fields, and those nearing their end drop into the renewal list. - Group Seat Hold | A school or company request is a record with request, hold, deposit and confirmed stages; the seat count, the performance date and the deposit status are in its fields, and blocked seats whose hold period has expired appear on the list. - Audience History | Every play seen is a line under the person record; the announcement list is filtered on the genre and the date in that history. - Tour and Venue | The tour city and the venue are each a field; the technical requirements and the revenue-share terms sit on the same record and are compared with the previous season. ##### Frequently asked questions - Does the system remind us of theatergoers whose season subscription is about to end? | The subscription end date is a field on the record; subscriptions falling within the number of days you set are gathered on a separate list, and a renewal call is opened as a task for each one. The announcement going to the subscriber is also sent by SMS or WhatsApp from the same list. - How do you track the deposit and the confirmation on school group bookings? | A group booking is a record that moves through request, hold, deposit received and confirmed stages. The seat count, the performance date and the teacher's contact details sit in fields; because bookings whose hold period has expired appear on the list, seats are not left blocked for nothing. - Can we send a new production announcement only to the relevant theatergoers? | Yes. Every play seen is a line under the person record; the announcement list is filtered on the genre and the date in that history, the message goes out by SMS or WhatsApp from the same list, and who received which message leaves a trace on the card. - Which is the best CRM software for a Theater? | When choosing a CRM for the Theater sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your theater process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Theater CRM system cost? | There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Theater sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Theater sector? | We start with a discovery meeting: we work out your theater process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a Theater? | Yes. Field and branch teams can update the customer record, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Theme Park CRM: Group Entry & Daily Capacity | Rapitek CRM](https://rapitek.com/en/theme-park-crm) Every group booking is a record with visit date and headcount fields; those opened for the same day gather on one list, and the day's expected headcount is read from the total. ##### What we set up, and how - Gather school, company and agency group bookings on a single calendar with date, headcount and agreed price fields - See the bookings falling on the same day together and draw the staffing, catering and car park plan from that list - Track the end dates of season passes and corporate allocation agreements and send the renewal reminder by SMS or WhatsApp - Send the post-visit satisfaction survey from the record, tie an incoming complaint to a request record and assign it to the person responsible - Group Entry Booking | A booking is a record; the visit date, the headcount, the agreed entry price and the payment status sit in its fields, and which group is coming to the gate is known from this record. - Corporate Account | The school, the company and the agency are each an account record; the allocation agreement and the special price are in a field on the account and come to the booking from there. - Daily Capacity | Bookings opened for the same date gather on a single list from the date field; the day's expected headcount is the total of that list. - Season Pass | A pass is a record carrying an end date and is linked to its holder's person record; those nearing their end drop into a list, and the renewal task is opened from there. - Post-Visit Feedback | The survey is sent from the visit record; an incoming complaint turns into a request record, and the person responsible is determined by the assignment rule defined at setup. ##### Frequently asked questions - Can I see in advance how many groups have been promised the same day? | Yes. Every group booking is a record with date and headcount fields; bookings opened for one day gather on a single list, and that day's expected headcount is read from the total of that list. You define the capacity threshold, and days that go over it are flagged on the list. - Do I have to renegotiate the special price in agency and school agreements every time? | No. The agency and the school are each an account record; the agreed allocation and price sit in a field on the account, and when a new booking is opened the price comes from that account. Because past visits also build up under the same account, you go into the conversation with the organisation's history. - Can we see in advance when a season pass is due for renewal? | Yes. A season pass is a record carrying an end date and is linked to the pass holder's person record; those nearing their end drop into a list, and the renewal reminder goes out by SMS or WhatsApp from the same record. - Which is the best CRM software for a Theme Park? | When choosing a CRM for the Theme Park sector, you should pay attention to sector workflows, integration capabilities, customisation options and support quality. You do not set up Rapitek CRM, we do: we configure the fields, the stages and the reports to fit your theme park process, we migrate your data, and we give your team training in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects during its Salesforce years; we do the setup with that experience. - How much does a Theme Park CRM system cost? | In a theme park, because the person responsible for an incoming complaint is determined by an assignment rule, more than one owner is defined in the system. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same on every project; the scope and the setup fee, if any, are worked out together at the discovery meeting and shared in writing. The Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the Theme Park sector? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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 in the Theme Park sector? | We start with a discovery meeting: we work out your theme park process together, and which fields and which stages are needed. After the meeting we give you a date, not a range. We migrate your data ourselves and we give your team training in Turkish. There is no call centre on our support line. Your question is answered by the team that builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a Theme Park? | Yes. Field and branch teams can update the customer record, notes and follow-up tasks from their phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Tourism CRM: Guest Profile & Agency Records | Rapitek CRM](https://rapitek.com/en/tourism-crm) The guest's room preference and past stays sit on their own record; the agency allotment and its last cancellation date are a separate record, and a room left empty turns into a task. ##### What we set up, and how - Gather the guest's room preference, special requests and past stays into a single profile - Track corporate agreements, group booking requests and MICE events stage by stage as opportunity records - Bring returning guests into the loyalty programme and send them an offer that fits their history - See OTA, agency and direct bookings on the same screen and keep the channels coordinated - Answer as a team from a single WhatsApp number; let conversations be assigned by the rule you define and the history stay on the record - Guest Profile | A guest is a person record; the room preference, the dietary note and special requests are its fields, and past stays build up under the card. - Group and Corporate Sales | A company agreement and a group request are each an opportunity record; the quote stage, the stay date and the number of rooms sit in fields, and the season plan comes out of the report on these records. - Post-Stay Survey | The survey sent to a departing guest is linked to the guest record; the score given and the note written sit on the same card, and a low-scoring response drops to the person responsible as a task. - Multiple Channels | The channel a booking came through is a field on the record; OTA, agency and direct bookings are separated by that field on the same list. - Agency Allotment Record | The allotment granted to an agency and the last cancellation date are an allotment record linked to the agency account; the number of rooms used and the number left empty sit in fields, and a task is opened for the sales owner before that date for the allotment being released. ##### Frequently asked questions - Does it integrate with PMS systems? | We build the connection to the property management system ourselves; there is no out-of-the-box module. The connection is set up specifically for your project over REST API, OAuth2, webhooks and import/export; we share its scope in writing at the discovery meeting. - How are group sales tracked? | You can create a separate opportunity record for each group request and track the quote stages and the contract processes. - Is there integration with OTA channels? | We build the connection to the booking channels ourselves; there is no out-of-the-box channel manager module. The data transfer is set up specifically for your project over REST API, OAuth2, webhooks and import/export; we share its scope in writing at the discovery meeting. - Can more than one person on a Tourism team use the same WhatsApp number? | On the tourism side, guest correspondence is answered by the team together from a single number and the history stays on the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Course Centre CRM: Attendance and Instalments | Rapitek CRM](https://rapitek.com/en/training-center-crm) A student is a person record; course selection, attendance and instalment lines sit under the same card. Absence and balance are read together, and an overdue instalment drops into a list. ##### What we set up, and how - Keep enrolment, course selection, absence and performance tracking on a single student card - Build instalment plans and track payment reminders and the balance - Manage teacher assignment, classroom capacity and lesson times in one schedule - Send absence notifications, exam results and announcements to the parent by SMS and WhatsApp - Let the whole team answer student and parent messages over a single WhatsApp number - Student Enrolment and Tracking | A student is a person record; course selection, absence and grade fields sit on the same card, and the term history accumulates without being erased. - Payment and Instalment Management | The instalment lines sit under the student record; an overdue line drops into a list, and the reminder task is tied to that condition. - Class Schedule and Classroom Management | A class is a record with teacher, classroom and time fields; capacity is kept in a field, and the clash rule is defined during setup. - Parent and Student Communication | A parent is a person record attached to the student record; announcements and notifications go out from here, and who was told what and when leaves a trace on the card. - Trial Lesson Record | A candidate who comes to a trial lesson is a lesson attached to the student record; which group they joined, the instructor's assessment and the parent's feedback sit in fields, and when no enrolment is opened the follow-up task stays open. ##### Frequently asked questions - Can I see a student who has not come two weeks in a row before the payment falters? | Yes. Attendance and instalment lines are under the same student card; absence and balance are read on one screen. An overdue instalment drops into a list and the reminder task is tied to that condition, so the intervention does not wait for the end of the month. - What happens if a candidate who comes to a trial lesson does not enrol? | The trial lesson is a lesson attached to the candidate's student record; which group they joined, the instructor's assessment and the parent's feedback sit in fields. When no enrolment is opened, the follow-up task stays open and the candidate does not drop off the list. - How long does setup take for a course centre? | After the discovery call we give you a date, not a range - how many fields, how many stages and how many reports your course process needs becomes clear in that call. We migrate your data ourselves; the scope of the migration and its fee, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for a course centre? | 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 access and field structure on the ERP side differ from installation to installation, a single button does not work the same way everywhere. The connection is built specific to the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the fee in the discovery call and share them in writing. - Can more than one person on a course centre team use the same WhatsApp number? | On the course centre side, the whole team answers student and parent messages over a single number. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and every message appears in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta bills you directly - we do not sell message packages or credits. ### [Translation Agency CRM: Language Pairs & Deadlines | Rapitek](https://rapitek.com/en/translation-agency-crm) Every job is a project record; the language pair, the word count and the delivery date are its fields. Translation, editing and final check move as stages on that same record. ##### What we set up, and how - Keep every job on a single list with its language pair, word count, delivery date and current status - Keep freelance translators' specialisms, availability and past performance on record - Have the price calculated from the language pair and the word count and produce the quote from the same screen - Run translation, editing and final check as stages separate from one another - Send project status and delivery notifications to the customer over WhatsApp - Project Management | Every job is a project record; the language pair, the word count and the delivery date sit in its fields, and the status moves along on the same record. - Translator Pool Management | A translator is an account record; the specialism and the availability are in fields, and past jobs build up under the card. - Preparing a Quote | The unit price per language pair is in the price list; the amount multiplied by the word count comes out on the quote line, and the calculation is not repeated by hand. - Quality Control Process | Translation, editing and final check are stages of the same project; the owner and the duration of each stage are read from the record. - Notarisation and Apostille Step | Notarisation, assigning a sworn translator and the apostille are separate stages of the project; which document is waiting at the notary and on which day it will be collected sits on the project record as a task. ##### Frequently asked questions - Can I include freelance translators in the system? | Yes, you can record your freelance translators in the system by their specialisms and language pairs, and assign projects through those fields according to the rule you define. - Is notarised translation tracked? | Yes, you can track notarised and sworn translation processes separately and report the document statuses to the customer. - Is there a current account for bulk customers? | Yes, you can open a dedicated current account for law offices, companies and institutions, and invoice monthly. - How long does setup take for a Translation Agency? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your translation agency needs becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. ### [Travel Agency CRM: Quotes & Visa Files | Rapitek CRM](https://rapitek.com/en/travel-agency-crm) WhatsApp, email, phone notes and web forms drop into the same request pool; the source is a field, and because a tour package is a product record the quote line feeds from it. ##### What we set up, and how - Combine requests from WhatsApp, email, phone notes and web forms in a single inbox - Template your tour packages as product records; write the date and headcount onto the quote line and have the total calculated from the price list - Keep the guest's past tours, preferences and budget on the record and build the next recommendation on that - Send early booking and last-minute campaigns to targeted lists - Answer as a team from a single business number, let conversations be assigned by the rule you define, and let the history stay even when staff change - Multi-Channel Request Centre | WhatsApp, email, phone notes and web forms are set up so that they drop into the same pool as records; because the source is written in a field, channel performance is visible in the report. - Fast Quotation | A tour package is a product record; the quote line feeds from it, and the total is calculated on the quote card according to the date and headcount fields. - Customer Travel History | Past tours build up under the customer card; because the budget and the preferences sit in fields, the next recommendation is built from that same card. - Season and Campaign Management | The target list is filtered on customer fields; because bookings are tied to the campaign, what each campaign brought in is measured. - Visa File Document List | A visa application is a file linked to the traveller record; the appointment date, the documents submitted and the outcome sit in fields, and a reminder task is opened for the traveller for a missing document. ##### Frequently asked questions - Why is a CRM important for travel agencies? | Tourism is seasonal and demand peaks shift. With a CRM every request is caught, a quote is given quickly, and customers are brought back with campaigns in the low season. - How are requests coming from different channels managed? | WhatsApp, email, phone notes and web forms come together in a single inbox. The customer history is visible and communication stays consistent. - How does the quotation system work? | Tour packages are templated as product records. When a customer request comes in, the template is selected; because the date and the headcount are fields on the quote line, the total is calculated from those fields and the selected price list. You update the price list yourself; when you update it, new quotes open with the current value. - Can more than one person on a Travel Agency team use the same WhatsApp number? | On the Travel Agency side, traveller correspondence is answered by the team together from a single business number; the history stays even when staff change. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Tutoring Center CRM: Topic-Level Tracking | Rapitek CRM](https://rapitek.com/en/tutoring-center-crm) The curriculum tree is marked up under the student record; topics solved and topics struggled with build up there. The target exam date is a field and the mock plan ties to it. ##### What we set up, and how - Mark on each subject's curriculum tree the topics the student has solved and the topics they struggle with, and follow their progress on a chart - Tie the countdown, the mock exam calendar and the topic completion plan to the student card according to the LGS, TYT or AYT target - Set a rule for when the weekly or monthly progress report goes to the parent by WhatsApp or email; let the send be logged on the record - Open a parent contact task for a student who misses two lessons, and make contact before the term is over - Compare student success rates by teacher and see how effective the topic teaching is - Topic-Level Progress Tracking | The curriculum tree is a structure that can be marked up under the student record; the topics solved and the topics struggled with build up there, and the progress chart comes out of those marks. - Exam Calendar and Countdown | The target exam and its date are fields on the student record; the mock exam calendar and the topic completion plan are opened as tasks tied to that date. - Parent Reporting | The report is produced from the data on the student card; it is sent to the parent by WhatsApp or email, and the send leaves a trace on the record. - Absence Early Warning | Absence is marked on the lesson record; the number of consecutive lessons missed appears on the list and a parent contact task is opened. The threshold is defined at setup. - Teacher Performance Tracking | The lesson record carries a teacher field; student results are grouped through that field and compared in a report broken down by teacher. - Referral and Results Tracking | The result information sits on the student card; asking a satisfied parent for a referral is a task tied to that record, and who was asked and when is tracked. - One-to-One Lesson Hour Record | In a private lesson, every hour the teacher and the student meet is a lesson line tied to the student record; the duration, the topic covered and the fee sit in fields, and the end-of-month teacher payment and the parent invoice come out of those same lines. ##### Frequently asked questions - Why is a CRM needed for a tutoring center? | Student success brings parent satisfaction, and parent satisfaction brings new enrolments. With a CRM you track student progress, keep the parent informed, and turn successful results into marketing. - How does topic-level tracking work? | A curriculum tree is defined for each subject. Which topics the student has worked through, which ones they struggled with, which topics they made mistakes on in mock exams — all of it sits under the same student record. - Is parent reporting automatic? | The report is produced from the data on the student card; you tie it to a rule at setup so that it goes to the parent by WhatsApp or email on a weekly or monthly cycle. You define the cycle and the channel; the send leaves a trace on the student record. - I have more than one branch, is there central management? | Yes. The branch is a field on the student and lesson record; performance comparison by branch, the breakdown by teacher and student success rates are taken from the report on that field. Who can see what is defined with permissions at setup. - How long does setup take for Tutoring Centers & Private Lessons? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your tutoring center process needs becomes clear in that meeting. We migrate your existing student data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Can more than one person use the same WhatsApp number for Tutoring Centers & Private Lessons? | Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [University CRM: Application Tracking & Alumni | Rapitek CRM](https://rapitek.com/en/university-crm) An applicant is a record; diploma equivalence, the language certificate and the visa step are tasks tied to it, and who waits at which step is read from the list, no file opened. ##### What we set up, and how - Gather all student applications into a single pool and track the assessment stages - Follow an international applicant's document, visa and orientation steps on the application record - Set up an alumni database and run event invitations and donation campaigns from there - Connect a single institutional WhatsApp number to the team inbox, let conversations be assigned by the rule you define, and let the history stay with the institution even when staff change - Application Management System | An application is a record; the assessment steps move along as stages and the documents are attached to the same card. - International Student Tracking | The document, visa and orientation steps are tasks tied to the application record; which step is waiting with whom is visible on the list. - Multilingual Interface | The interface is fully translated into Turkish and English; in other languages, untranslated text appears in English. The applicant's language is held in a field on the record, and the correspondence template is matched to that field. - Alumni Relations | An alumni record is not deleted, its status changes; event invitations and donation campaigns go to a list filtered from those records. - Open Day Attendance Record | An applicant who signs up for a campus open day is an attendance line tied to the applicant record; the faculty they are interested in, the province they come from and their attendance status sit in fields, and the messages going out through the preference period are ordered by those fields. ##### Frequently asked questions - How can I track international student applications? | With Rapitek CRM you can gather all international applications on a single platform, track document statuses, and correspond using templates selected according to the applicant's recorded language. - How does alumni management work? | You can keep your graduates in a database, follow their career progress, send event invitations and run donation campaigns. - Does it integrate with our existing student information system for a University? | We build the connection to your student information system ourselves; there is no out-of-the-box module. The connection is set up specifically for your project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing at the discovery meeting. Until the connection is in place, applicant and student data is entered with an import file or by hand; the application stage and the document and visa steps are still held in the CRM and reminders are produced from there. - Can more than one person on a University team use the same WhatsApp number? | On the university side, applicant correspondence is gathered on a single institutional number; the history stays with the institution even when staff change. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Vehicle Inspection CRM: Digital Report, Vehicle History](https://rapitek.com/en/vehicle-inspection-crm) The inspection report is a record attached to the vehicle; on a second visit the previous measurements sit side by side. Appointments open by lift duration and the lifts free at that hour. ##### What we set up, and how - Create the photographed inspection report in the system and send it to the customer as soon as the inspection is finished - Open the past records of a vehicle inspected before on a single screen when it comes back - Take appointments online, send reminders and see the day's calendar along with how full it is - Send the inspection report to the dealer and the insurance company as a link or a PDF from the record - Let the whole team reply from a single WhatsApp number, so appointment and price messages go on record - Digital Inspection Report | The report is a record attached to the vehicle; the measurement values and the photos sit in its fields, the send to the customer is made from the same record, and who it went to and when leaves a trace. - Vehicle History Lookup | The chassis number is a field on the vehicle's record; when a vehicle inspected before comes back, the previous reports open under the same card in date order. - Lift Queue and Package Duration | The inspection package (engine, paint and body, full inspection) carries its own duration on the service record; the appointment is opened according to that duration and the number of lifts free at that hour, and a second vehicle is not booked onto the same lift. - Sharing with Dealers and Insurers | The inspection report is sent to the dealer and the insurance company as a link or a PDF from the record; who it was sent to and when sits on the same record. We build the connection to dealer and insurer systems ourselves; there is no out-of-the-box module, and if a direct connection is needed it is built specifically for each project over a REST API and webhooks. - Dealer Inspection Allowance Counter | The contracted dealer's periodic inspection allowance and the number remaining are fields on the dealer account; at every vehicle intake a line that decrements this counter is written, and before the allowance runs out a renewal task is opened for the person responsible. ##### Frequently asked questions - Can I see the previous measurement when the same vehicle comes in a second time? | The report is a record attached to the vehicle; on a second visit, through the chassis number, the previous measurements sit side by side and what changed in between is read from the same screen. Even if the vehicle is measured again, the difference between the two rounds stays in the record. - How do we follow a contracted dealer's remaining inspection allowance? | The periodic inspection allowance and the number remaining are fields on the dealer account; at every vehicle intake a line that decrements the counter is written. Before the allowance runs out a renewal task is opened for the person responsible. - How long does setup take for Vehicle Inspection? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your inspection process requires becomes clear in that call. We migrate your data; the scope of the migration and its cost, if any, are worked out in the same call and shared in writing. - Does it integrate with my existing systems for Vehicle Inspection? | On the vehicle inspection side the report is sent to the dealer and the insurance company as a link or a PDF from the record. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection ourselves; the same applies to dealer and insurer systems. There is no out-of-the-box module: because access and field structure on the other side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for each project over our REST API covering 183 business objects, OAuth2, webhooks and import/export, and its scope and its cost are shared in writing at the discovery call. When no connection is built, report sharing runs over a link generated from the record or a PDF. - Can more than one person on the Vehicle Inspection team use the same WhatsApp number? | On the vehicle inspection side the whole team replies to appointment and price messages from a single number, and the messages go on record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits. ### [Veterinary Clinic CRM: Vaccination and Parasite Calendar](https://rapitek.com/en/veterinary-crm) Each animal is its own record linked to its owner; species, allergy, vaccination interval and treatment history belong to it, and the reminder says which animal it is for. ##### What we set up, and how - Open every animal as a separate record linked to its owner, and keep the species and breed on the card - Run the vaccination and parasite calendar per animal and remind the owner when it falls due - Keep examinations, treatments and test results on the animal's card in date order - Plan appointments per vet and per room, and keep no-shows on the list - Link pet food and care product sales to the same animal record and track repeat orders - Animal Record Separate From The Owner | The animal is its own record linked to the owner's contact record; the species, breed, date of birth and allergy fields belong to it. The same owner's second animal opens a separate card, and the histories do not get mixed up. - Vaccination And Parasite Calendar | The date and the repeat interval of every vaccination are fields on the animal record; those that fall due appear in a list and the reminder task is linked to the owner. - Treatment And Test History | Examinations, treatments and test results accumulate under the animal's card in date order; on a second visit the history stands up front without being searched for. - Appointment Plan | An appointment is a record with a vet, a room and a time field. The clash rule is defined during setup, and cancellation is handled on the same record. - Product Sales And Repeat Orders | Pet food and care product lines are linked to the animal record; according to the consumption interval field, those due for a repeat order can be pulled out with a filter. ##### Frequently asked questions - How do I keep several animals belonging to the same owner apart? | Each animal is opened as a separate record linked to the owner's record. The species, breed, date of birth, allergies and the entire treatment history belong to that animal; they are all listed from the owner's card, but the histories do not get mixed up. - Who receives the vaccination reminder, and when? | The repeat interval of the vaccination sits as a field on the animal record. Animals that fall due appear in a list, the reminder is sent to the owner's contact details, and the message states which animal it is for. - How much does a veterinary CRM system cost? | On the veterinary clinic side an appointment record carries a vet field and a room field; the system is used by this clinic staff. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope, and the setup fee if there is one, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in a veterinary clinic? | 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in a veterinary clinic? | We start with a discovery call: we work out your clinic's process together, along with which fields and which stages are needed. After the call 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 builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a veterinary clinic? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [VR AR CRM: Pilot Tracking and Headset Inventory](https://rapitek.com/en/vr-ar-crm) Every headset is a record with a serial number; the event it is at, the person who received it and the expected return date are its fields, and overdue ones appear in a list. ##### What we set up, and how - Plan trade fair and customer demos as tasks; record where, with whom and with which device they were done, with location verification - Write the pilot project's scope, scene count and success criterion into fields on the opportunity record so that sales and production share the same definition - Track headsets and stations by serial number; see which device is with whom and its return day from a single list - Keep the technical, purchasing and marketing stakeholders at the enterprise buyer in separate contact records and link their objections to the record - Demo Task | A demo is a task; the date, the venue, the participants and the device used are in fields, it is closed from the mobile app, and the location is verified. - Pilot Opportunity | The pilot is an opportunity record with its own stages; the scene count, the device model and the success criterion sit in fields, and a change of scope is recorded. - Hardware Inventory | Every headset and station is a record with a serial number; the event it is at, the person who received it and the expected return date are in its fields. - Stakeholder Map | The technical, purchasing and marketing representatives are separate contact records under the account; the role field and the meeting note stay separate on each one. ##### Frequently asked questions - Can we track where the headsets that go to trade fairs and customer demos are? | Yes. Every device is a record with a serial number; the event or customer it is at, the person who received it and the expected return date sit in its fields. Devices past their return day are collected in a separate list, and a follow-up task is opened for each of them. - The pilot project's scope is discussed in the meeting and then changes; how does the CRM hold that? | The pilot's scope, scene count, device model and success criterion are fields on the opportunity record. When the scope changes, it is written onto the record as an update and the previous state is not deleted; that way you can read back where the link between the budget and the content volume broke. - Can we track the objections of different stakeholders at an enterprise buyer separately? | Yes. The technical, purchasing and marketing representatives are separate contact records under the account; the role field and the meeting note stay separate on each of them, and who raised which objection can be read from their own card. - Which is the best CRM software for VR and AR? | When choosing a CRM for the VR and AR sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports according to your VR and AR process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce era; we carry out the setup with that experience. - How much does a VR and AR CRM system cost? | On the VR and AR side, because the demo task is closed from the mobile app, the people who go to fairs and to customers are users of the system as well. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope, and the setup fee if there is one, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the VR and AR sector? | 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the VR and AR sector? | We start with a discovery call: we work out your VR and AR process together, along with which fields and which stages are needed. After the call 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 builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for VR and AR? | In the VR AR business a demo is a task; it is in the venue and device-used fields, it is closed from the mobile app, and the location is verified. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Warehouse CRM: Space Allocation, Dispatch and Storage Fees](https://rapitek.com/en/warehouse-crm) Goods receipt and dispatch requests are dated records on the customer account; pallet count and the in and out dates sit in fields, and the period storage fee statement comes from them. ##### What we set up, and how - Link the stored goods to the account of the customer who owns them; keep the pallet, rack and occupied space details on the record - Collect goods receipt and dispatch requests in a single pool and see which request is waiting at which stage - Produce the end-of-period storage fee statement from the records, based on storage duration and movement count - Track the end dates of storage contracts and open a task in advance for the renewal conversation - Customer And Space Allocation | The storing company is an account record; the allocated space, the pallet count and the unit storage price sit in the fields of that account. - Goods Receipt And Dispatch Request | Every inbound and outbound request is a record with its own date; which stage it is waiting at is visible in the list, and the person responsible is written in its field. - Storage Fee Period Statement | The storage duration is calculated from the entry and exit date fields; because the movement records accumulate under the account, the period statement is taken from a report. - Contract Renewal | The contract end date is a field on the account; accounts whose date is approaching appear in a list, and the renewal task is opened onto that list. ##### Frequently asked questions - Can I track the goods of more than one customer in the same warehouse separately? | Yes. Every customer is a separate account record; the allocated space, the pallet count and all the movements sit under that account, and statements are taken per customer. - Can I have the storage fee calculated according to the days stored? | The entry and exit dates are kept as fields on the record, and the unit price sits on the account; the period statement comes out of these fields. Your calculation rule is defined during setup. - Can I be notified when the end date of a storage contract approaches? | The contract end date is a field on the account; accounts whose date is approaching appear in a list according to that field, and the renewal task is opened from the same list. - Which is the best CRM software for a warehouse? | When choosing a CRM for the warehouse sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports according to your warehouse process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce era; we carry out the setup with that experience. - How much does a warehouse CRM system cost? | On the warehouse side the person responsible for every inbound and outbound request is written into a field on the record; the system is used by this warehouse staff. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope, and the setup fee if there is one, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the warehouse sector? | 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the warehouse sector? | We start with a discovery call: we work out your warehouse process together, along with which fields and which stages are needed. After the call 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 builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for a warehouse? | Yes. Field and branch teams can update the customer card, notes and follow-up tasks from a phone. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Waste Management CRM: Container Tracking and Tonnage](https://rapitek.com/en/waste-management-crm) Every customer site is a record with container type and count in its fields; in Rapitek CRM the weighed tonnage goes on the collection task and the month-end statement comes from these records. ##### What we set up, and how - Keep customer sites and the containers and equipment standing there in separate records, and see from a list which equipment is where - Link collection and emptying visits to a recurring task; let the field team close it from the mobile app with location verification - Write the waste code, the weighed tonnage and the shipment document number into the task's fields, and produce the period statement from the records - Track the delivery of the disposal certificate and the contract renewal as separate tasks and close them before the dates pass - Customer Site And Equipment | Every site is a record; the container type and count standing there are in its fields, and when equipment moves, it is written into the record's history. - Collection Task | Collection is a task; the date, vehicle and driver are in its fields, it is closed from the mobile app, and the location verification goes onto the record. - Waste Code And Tonnage | The waste code is a field on the contract line item; the weighed tonnage is written onto the collection task, and the period statement is read from the total of these records. - Document Delivery | Delivering the disposal certificate to the customer is a task; the document number sits in a field and a copy of the document sits as an attachment on the record. ##### Frequently asked questions - Can I track how many of my containers are standing at which customer? | Yes. Every site is a record, and the type and count of the equipment standing there are in the record's fields; when equipment is moved to another site, the change goes into the record's history. - How do I get the tonnage statement per customer at the end of the month? | The weighed tonnage is a field on every collection task; a report with a chosen customer and date range adds up those tasks. We build the transfer to the accounting system ourselves: it is done specifically for the project over an export or an API — there is no out-of-the-box module. - Can I see from the record that the disposal certificate has reached the customer? | Delivering the disposal certificate is a separate task; the document number sits in the task's field and a copy of the document sits as an attachment on the record. As long as the task is not closed, it stays on that customer's list of open work. - Which is the best CRM software for waste management? | When choosing a CRM for the waste management sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports according to your waste management process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce era; we carry out the setup with that experience. - How much does a waste management CRM system cost? | In waste management, because the field team closes the collection task from the mobile app, the crew in the vehicle are users of the system as well. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope, and the setup fee if there is one, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the waste management sector? | 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the waste management sector? | We start with a discovery call: we work out your waste management process together, along with which fields and which stages are needed. After the call 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 builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for waste management? | In waste management, collection and emptying visits are recurring tasks; the field team closes them from the mobile app with location verification. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ### [Water Dealer / Carboy CRM: Subscription & Route | Rapitek](https://rapitek.com/en/water-delivery-crm) Full carboys given out and empties taken back are written to the same delivery record; the customer's holding and depot stock update together, and payment stays tied to that delivery. ##### What we set up, and how - Keep the subscription period in a field on the customer record; let those whose period has come round drop into the day's list, and open the order record from that list - Route deliveries by region, assign a driver and record the delivery confirmation - Track credit, cash and bank transfer collections per customer on a single list - See at a glance the empty carboys left at the customer and the full stock in the depot - Handle order messages arriving on a single WhatsApp number as a team - Order and Subscription Management | The subscription period is a field on the customer record; customers whose period has come round drop into a list, and the order record is opened from there. - Delivery Route Planning | A delivery is a task; the driver, the region and the address are in its fields, and the delivery confirmation is written to the same record. - Payment Tracking | The credit, cash and bank transfer lines sit under the customer card; the balance is calculated from those lines. - Stock and Carboy Count | The number of empty carboys at the customer is a field on the customer record; it is updated at delivery, and the total stock on hand is visible in the report. - Water Cooler Maintenance Visit | Cleaning and filter changes for the cooler standing at the customer are a maintenance task linked to the customer record; the last maintenance date and the member of staff responsible sit in fields, and that the visit was made at the address is confirmed with location verification in the mobile app. ##### Frequently asked questions - How do we track how many empty carboys are left at a customer? | The number of empty carboys at the customer is a field on the customer record; the full ones given out and the empties taken back at each delivery are written to the same record, and the total held at customers is visible in the report. - Can we see where the water cooler maintenance was marked as done? | Water cooler maintenance is a task linked to the customer record; the last maintenance date and the member of staff responsible are fields on that task. When the technician closes the visit from the mobile app, the location information is written to the record, so it is seen that the visit was made at the address. - How do we avoid forgetting a regular customer's weekly order? | The subscription period and the last delivery date are fields on the customer record; customers whose period has come round drop into the day's list according to those fields, and the order record is opened from that list. You tie how many days it repeats over and which region is visited on which day to a rule at setup; the reminder list turns into the morning's route. - How long does setup take for a Water Dealer / Carboy business? | After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your water dealer process needs becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing. - Does it integrate with my existing systems for a Water Dealer / Carboy business? | 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 ERP side differs from one installation to the next, a single button does not work the same way everywhere. The connection is set up specifically for your 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. - Can more than one person on a Water Dealer / Carboy team use the same WhatsApp number? | On the Water Dealer / Carboy side, order messages arriving on a single number are handled by the team together. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team answers from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Wealth Management CRM: Portfolio and Document Tracking](https://rapitek.com/en/wealth-management-crm) Risk profile and investment preference are fields on the customer card; every recommendation stays on the record with the profile it rests on, and the previous state stays in the history. ##### What we set up, and how - Keep every client's risk profile, investment preferences and portfolio history in a single file - Record the meetings, the recommendations presented and the client's decision stages in order - Run the documents and processes tied to regulatory requirements through the client record - Define a separate service level and priority support for high-value clients - Handle the sharing of sensitive financial information through the record and keep all communication on file - Client Portfolio Tracking | The risk profile and the investment preference are fields on the client card; the portfolio history accumulates under the same card. - Advisory Process Management | The meeting, the recommendation and the decision leave a trace in order under the same record; which answer was given to which recommendation can be read afterwards. - Mandatory Document Tracking | Mandatory documents are kept as fields on the client record; clients with missing documents stay on a list, and the completion task is opened from there. - VIP Client Programme | The service level is a field; priority and the assignment rules defined during setup are linked to that field, and response time is reported from the record dates. - Data Separation | Access is limited by role-based permissions, your CRM data sits in a separate database that belongs to you, and transfer is done over TLS; correspondence stays on the record rather than in a personal channel. ##### Frequently asked questions - Do you have a ready-made module for SPK regulations? | There is no out-of-the-box module; what there is, is configuration — and we do that ourselves. Know-your-customer information, the risk profile and mandatory documents are defined as fields on the record; which field will be mandatory and which report will be produced are decided together during setup. The assessment of regulatory compliance remains with your institution's compliance unit. - Is client data safe? | Your CRM data is kept in a separate database that belongs to you; TLS is used in transit, passwords are hashed one-way with PBKDF2-SHA256, two-factor authentication secrets are encrypted at rest, and access is limited by role-based permissions. Hosting is in the European Union: the database in Helsinki, media files in Frankfurt. Under KVKK Article 9 this counts as a transfer abroad; that is why we run disclosure and explicit consent processes. A small number of sub-processors operate outside the EU; we list each of them, and the place where each processes data, one by one in our privacy policy. - Can I manage more than one advisor? | Yes, you can follow each advisor's client portfolio, performance and meeting calendar from a single dashboard. - How long does setup take for wealth management? | After the discovery call we give you a date, not a range — how many fields, how many stages and how many reports your wealth management process requires becomes clear in that call. We migrate your data ourselves; the scope of the migration, and its cost if there is one, are worked out in the same call and shared in writing. ### [Wedding and Event Planning CRM: Day Run Sheet](https://rapitek.com/en/wedding-event-crm) Every wedding is a single record carrying its own dates and assigned suppliers; from bridal preparation to the band, the hour-by-hour run sheet is lines linked to that record. ##### What we set up, and how - Keep the proposal's sending and validity dates on the opportunity record; let those past their term appear in a list, and open the call task from that list - Link every milestone of the plan to a dated task; attach a rule so that a notice goes to the couple and to the supplier concerned - Bring close to twenty suppliers together on a single platform; track deadlines and approval flows from the supplier card - Attach a rule so that the satisfaction and referral request task is opened when the event closes - Let the whole team answer from a single business number, have conversations assigned by rule, and let the manager see response times - Tracking From Proposal To Contract | The proposal's sending date and validity date are fields on the opportunity record; proposals past their term appear in a list, the follow-up task is opened from that list, and how many couples are waiting at which stage is read from the stage report. - 12-Month Timeline | Every milestone is a dated task linked to the wedding record; tasks whose date is approaching appear in a list, and you can attach a rule to that list so that a notice goes to the couple and to the supplier concerned. - Supplier Coordination | Every supplier is an account record; contact details, price and performance notes sit in the fields of that account. Assignment per wedding and the deadline are lines linked to the wedding record, and a line whose approval is overdue stays open on the list. - Post-Event Referral Request | When the event closes, a satisfaction survey and a referral request are opened as tasks; on the incoming couple's record, the source field shows which wedding they came from. - Wedding Day Run Sheet | The bridal preparation, ceremony, dinner and band times are run-sheet lines linked to the event record; the person responsible and the supplier for each line sit in fields, a change during the day is updated on the same line, and a notification goes to the person concerned. ##### Frequently asked questions - Why is a CRM necessary for wedding planning? | Planning a wedding takes 6-18 months and has more than 50 touchpoints. This complexity cannot be managed in Excel. A CRM puts timeline management, supplier coordination and customer communication on a system. - How does supplier management get easier? | Every supplier is an account record: contact details, price and performance notes sit in its fields. Assignment per wedding and the deadline are lines linked to the wedding record; a line whose approval is overdue stays open on the list, and the correspondence accumulates under the same card. - Can we see whether the proposal we sent has been opened by the couple? | No — there is no read receipt tracking whether the proposal PDF has been opened, and we do not say that there is. What you do see is this: the date the proposal was sent and its validity date are fields on the opportunity record; proposals that pass the number of days you set appear in a list based on those fields, and the call task is opened from that list. When the couple comes back you move the stage forward, and how many couples are waiting at which stage is read from the stage report. - How does the referral system work? | When the wedding closes, a satisfaction survey and a referral request are opened as tasks; from that task you send happy couples the 'would you recommend us?' question and the Google review request. On the record of every new couple that comes in, the source field shows which wedding they came from; you count how much new business a wedding brought from that field. - Can more than one person on the wedding and event planning team use the same WhatsApp number? | On the wedding and event planning side the couple's questions are collected on a single business number; the manager sees response times. Yes. We connect your own Meta WhatsApp Business account to the CRM ourselves; there is no out-of-the-box module, and connecting the account is done during setup. After that your team answers from a single business number; incoming messages land in the team inbox and are written onto the customer card. Conversations are assigned to a representative according to the rule you define; managers see the conversations and the response times. Even if staff change, the correspondence history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message bundles or credits. ### [Weight Loss Clinic CRM: Measurement and Diet Tracking](https://rapitek.com/en/weight-loss-clinic-crm) Weight, BMI and waist circumference go onto the patient record with a date at every check; pre-op preparation items are tasks on the surgery record, and the date does not move until each closes. ##### What we set up, and how - Record weight, BMI, waist circumference and body fat ratio at every check-up and see the trend on a chart - Link the personal nutrition and exercise plan to the patient record, and have the daily calorie tracking land where the doctor sees it - Run the pre-operative preparation, the surgery day and the post-operative check-up calendar for bariatric surgery in a single flow - Have a psychologist session suggested for emotional eating and adherence problems, and keep the session history on the patient card - Organise post-operative periodic check-ups, vitamin and mineral levels and protein intake tracking spread over the years - Weight And Measurement Tracking | Weight, BMI, waist circumference and body fat ratio are written with a date onto the patient record at every check-up appointment; the monthly and yearly trend is read from the chart of those lines. - Diet And Exercise Plan | The nutrition programme is a record linked to the patient record; the plan written by the dietitian and the daily calories the patient enters from the mobile app sit on the same card, and the doctor sees them from the same place. - Bariatric Surgery Process | The diet period, the tests, the anaesthesia assessment, giving up smoking and insurance approval are prerequisite tasks linked to the surgery record; an unclosed task is visible on the record. - Psychological Support | A psychologist session is an activity linked to the patient record; the session date and note are in its fields, and patients flagged with an adherence problem are listed according to that field. - Long-Term Post-Operative Follow-Up | Periodic check-ups are opened as tasks linked to the surgery date; vitamin and mineral levels and protein intake are fields on the record, and a patient who does not come stays on the list because the task is not closed. ##### Frequently asked questions - How does a weight loss programme start in the CRM? | At the first consultation the patient's health profile, BMI, target weight and any accompanying medical conditions are entered onto the record. The personal 3-6-12 month programme is set up according to these fields; weekly and monthly check-up appointments are opened as date-based tasks. - How is the preparation before bariatric surgery managed? | The pre-operative diet period, psychologist sessions, anaesthesia assessment, endoscopy and giving up smoking are prerequisite tasks linked to the surgery record; a task that is not closed is visible on the record. SGK and private insurance approvals are also tracked from the same record. - How is communication between the dietitian and the doctor provided? | On every patient card, the dietitian's notes, the doctor's comments and the psychologist's reports sit in shared visibility. Each specialist adds their own note, the others see it from the same card and receive a notification. - Don't patients get lost after surgery? | No. After bariatric surgery, periodic check-ups are spread over the years as tasks linked to the surgery date. A reminder is sent for every check-up; if the patient does not come, the task is not closed, so it stays on the list and an alert lands for the clinic manager. ### [Wind Energy CRM: Land Owners and Turbine Maintenance](https://rapitek.com/en/wind-energy-crm) Every plot owner is a contact record; the meeting note, the price offered and the stage reached accumulate on it. The lease's end date is a field, and those approaching appear in a list. ##### What we set up, and how - Keep every plot owner in a separate contact record, write in the meeting note and the stage reached, and run the site as the project those records are linked to - Track the start and end dates of lease and easement agreements as fields, bring those whose term is approaching onto a list and open a task - Keep every turbine in an equipment record, and link the planned maintenance interval and the fault history to that record - Plan the field team's maintenance visit as a task, and take the closure from the mobile app with location verification - Land Owner Record | Every plot owner is a contact record; the meeting note, the price offered and the stage reached accumulate in the fields of that record. - Contract Dates | The start and end dates of the lease and easement agreements are each a field; those whose term is approaching appear in a list, and the renewal task is opened from there. - Turbine Equipment Record | Every turbine is an equipment record; the planned maintenance interval and the fault history are written onto that record with their dates. - Turbine Maintenance Round | A maintenance round is a task; which turbine, which team and which date sit in its fields; the team closes the job at the foot of the tower from the mobile app, the location is verified, and a fake location report is detected. ##### Frequently asked questions - How do we track conversations running with dozens of land owners? | Every owner is a separate contact record and is linked to the site's project record; the meeting note, the price offered and the stage reached accumulate on the record. Where things stand with whom on which plot is read from the list, and even if the person running the work changes, the history stays in place. - Can we track turbine maintenance and the team out in the field? | Every turbine is an equipment record; the planned maintenance interval and the fault history are written onto that record, and maintenance is assigned to the team as a task. The site visit is closed from the mobile app with location verification, and a fake location report is detected. - Can we be notified before the lease and easement agreement expires? | Yes. The start and end dates of the contract are each a field; contracts whose term is approaching appear in a list sorted by date, and it is defined during setup that the renewal task is opened for the person responsible. Because the contract is linked to the plot owner's record, who is running the conversation is read from the same place. - Which is the best CRM software for wind energy? | When choosing a CRM for the wind energy sector, you should pay attention to sector workflows, integration capabilities, customisation options and the quality of support. You do not set up Rapitek CRM — we do: we configure the fields, the stages and the reports according to your wind energy process, we migrate your data, and we train your team in Turkish. Before building our own platform, our team completed more than 200 enterprise CRM projects in its Salesforce era; we carry out the setup with that experience. - How much does a wind energy CRM system cost? | In wind energy, because the team closes the maintenance round at the foot of the tower from the mobile app, the field team is defined in the system as well. There are three tiers and all of them are priced per user per month: Sales 39 USD, Platform 69 USD, and Enterprise from 119 USD. Prices are based on annual billing; Sales and Platform require a minimum of 5 users, Enterprise a minimum of 10. For teams under 5 there is a separate starting point: Inbox, at 149 USD per company per month. The scope of setup, data migration and training is not the same in every project; the scope, and the setup fee if there is one, are worked out together in the discovery call and shared in writing. Rapi artificial intelligence credit and ERP integration are separately priced items. - How are CRM integrations done in the wind energy sector? | 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 ERP side differ from one installation to the next, a single button does not work the same way everywhere. The connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out the scope and the cost in the discovery call and share them in writing. - How does the move to a CRM system work in the wind energy sector? | We start with a discovery call: we work out your wind energy process together, along with which fields and which stages are needed. After the call 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 builds and develops the product — this is a choice, not a matter of capacity. - Can mobile CRM be used for wind energy? | In wind energy, on a turbine maintenance round the team closes the job at the foot of the tower from the mobile app, and the location is verified. The app is live on both the App Store and Google Play. The web interface works on tablets and phones as well. 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. ## Blog ### [History of CRM: Timeline from Rolodex to AI (1950–2026)](https://rapitek.com/en/blog/history-of-crm) Trace the history of CRM from the 1950s Rolodex through Siebel and the SaaS revolution to today's AI-augmented platforms — a complete timeline to 2026. History of CRM: From the Rolodex to AI CRM 2026-05-03 CRM · History #### Seven decades, three waves CRM software emerged in the 1980s as digital Rolodex applications and evolved through three great waves — the database-marketing era, the SaaS revolution, and today's AI-augmented platforms. This is the full timeline, from a rotating card file in 1958 to autonomous sales agents in 2026. ##### Contents ##### Why CRM exists at all Customer Relationship Management (CRM) software exists because of a simple commercial truth: it costs far more to win a new customer than to keep an existing one. For most of business history, companies chased volume — sell to as many people as possible — and ignored what they already knew about the customers they had. Purchase history, preferences, and behavior went unrecorded, so every sale started from zero. CRM turned that logic around. It rests on two functions: store what you know about each customer, and act on it — serve the right person, at the right moment, through the right channel. Those two functions are much older than software. What has changed over seven decades is the technology that carries them: from a rotating card file on a sales rep's desk to cloud platforms that draft emails with AI. If you want the practical, present-day view first, our CRM guide covers what modern systems actually do. This article is about how we got here. Rolodex Everything that followed was, in essence, an attempt to do what the Rolodex did — faster, with broader access, and across many offices at once. ##### Pen, paper, and the Rolodex (before 1980) The earliest CRM "system" was a salesperson's notebook: names, phone numbers, and a few notes, retrieved by flipping pages. The most iconic upgrade arrived in 1958, when Arnold Neustadter patented the Rolodex — a rotating card index in which every customer had a card with name, phone, address, and notes. Large enterprises ran "account books" maintained by departmental secretaries; banks kept account cards at each branch. These paper systems already embodied the fundamental CRM insight — every customer interaction should be tracked centrally — but they were slow to search, painful to update, impossible to analyze, and chained to a single desk. A rep who left the company often took the relationships with them, card by card. ##### Database marketing and the digital Rolodex (1980s) CRM's efficiency jumped dramatically when it moved from the physical world into software. In the early 1980s, two parallel tracks emerged. On PCs, contact-management software digitized the Rolodex. ACT! (Conductor Software, 1986) was the first commercial product of its kind — later acquired by Symantec in 1993, then Sage in 1999, and still active today. GoldMine (1989) followed with early multi-user network capabilities. Meanwhile, large enterprises built database marketing systems on Oracle, DB2, or Sybase mainframes. Airlines, banks, and retailers used statistical modeling on customer data to personalize communication — American Airlines' AAdvantage loyalty program (1981) is a landmark example. This era introduced the core concepts that persist in every CRM today: contact records, activity history, sales pipelines, and reporting. The limitation was reach — systems were single-user or LAN-based, and sharing data across geographies required nightly batch syncs. ##### Sales force automation and the birth of "CRM" (1993–1999) In 1993, Tom Siebel — a former Oracle executive — founded Siebel Systems and took contact management enterprise-wide. His category, Sales Force Automation (SFA), combined database marketing with contact management and centered it on the sales process: contact management, pipeline management, and task tracking in one system. The mid-90s also settled a naming battle. Competing labels — Enterprise Customer Management (ECM), Customer Information System (CIS), Personal Information Manager (PIM) — faded away, and by about 1995 Customer Relationship Management became the permanent term. Siebel expanded from sales into marketing and customer service, and by the late 1990s was the leading enterprise CRM vendor of its era, with customers including Cisco, Honda, IBM, and JP Morgan. Siebel also shipped one of the first mobile CRM products in the late 1990s. But enterprise CRM of this era was heavy. Deployments were multi-year programmes run by systems integrators, with budgets to match — which is precisely why the next wave found an opening. Oracle acquired Siebel in 2006 for $5.85 billion; SAP (2001) and Microsoft (2003, later Dynamics 365) entered the market in the same period. ##### The SaaS revolution (1999–2015) In February 1999, Marc Benioff — another former Oracle executive — founded Salesforce.com in a rented San Francisco apartment, with co-founders Parker Harris, Dave Moellenhoff, and Frank Dominguez. The mission was radical for its time: deliver CRM entirely through a web browser, on subscription, with no servers to install — famously branded as "the end of software." The milestones came quickly: IPO in 2004, the AppExchange marketplace in 2005, the Force.com platform in 2007 (turning CRM from an application into a platform), Service Cloud in 2010, and Marketing Cloud via the ExactTarget acquisition in 2013. Around 2008, social CRM shifted the industry's focus from transactions to ongoing interactions, as companies met customers on the social platforms where they actually spent time. SaaS also opened the market beyond the enterprise giants. SugarCRM (2004) took an open-source route, Zoho CRM (2005) bootstrapped from India without venture capital, HubSpot (2006) built inbound-marketing-first CRM, and Pipedrive (2010) put a visual pipeline at the center. For the first time, a 20-person company could afford the same class of tooling as a Fortune 500. Timeline ##### CRM history at a glance Year | Milestone - 1958 | Arnold Neustadter patents the Rolodex — the rotating card index that defined pre-software contact management - 1986 | ACT! by Conductor Software — the first commercial contact-management software for PCs - 1993 | Tom Siebel founds Siebel Systems; sales force automation goes enterprise-wide - 1995 | "Customer Relationship Management" wins the naming battle over ECM, CIS, and PIM - 1999 | Marc Benioff founds Salesforce.com — CRM moves to the browser - 2004 | Salesforce IPO; SaaS proves itself as a business model - 2006 | Oracle acquires Siebel Systems for $5.85 billion - 2007 | Force.com launches — CRM becomes a platform, not just an application - 2008 | Social CRM: the focus shifts from transactions to interactions - 2020s | AI-augmented CRM: natural-language queries, lead scoring, drafted emails ##### AI-augmented and vertical CRM (2020–present) The 2020s brought two parallel shifts. AI integration. Starting around 2020–2021, every major vendor began layering AI onto CRM. Salesforce launched Einstein GPT (2023) and then Agentforce (2024); HubSpot introduced Breeze AI (2024); Microsoft shipped Copilot for Sales (2024). Typical AI features today include natural-language queries ("show me deals over $50k untouched for two weeks"), AI lead scoring, drafted emails that a human reviews before sending, sales forecasting, sentiment analysis on incoming messages, and business-card OCR. Vertical and regional CRM. The dominance of global platforms opened space for CRMs built around a specific industry or region — closer to local language and business practices than a one-size-fits-all giant. Bitrix24 (2012) grew this way in Russia and the CIS, and country-specific CRMs now thrive across LATAM, MENA, and Southeast Asia. Rapitek CRM belongs to this wave: launched in 2025 in Türkiye by a team that delivered 200+ enterprise CRM implementations during its Salesforce era. Customer data is hosted in the EU: the database in Helsinki, Finland, and media storage in Frankfurt, Germany. You can see how that experience shaped the product. ##### What's next for CRM (2026–2030) The active frontiers of CRM innovation as of 2026: - Autonomous AI agents | Complete multi-step tasks — research a prospect, draft a personalized outreach, schedule a meeting if they reply. - Messaging-first CRM | WhatsApp and other messaging channels displace email in many B2B contexts — especially in Türkiye, MENA, LATAM, and Southeast Asia. - Voice-first workflows | For field sales: speak your meeting notes, get them transcribed and structured automatically. - Privacy-preserving AI | GDPR, KVKK, and sector rules tighten around what customer data can feed AI models. - An open-source resurgence | SuiteCRM, EspoCRM, Twenty — driven by frustration with SaaS lock-in. One thing is unlikely to change: the CRM remains the system of record. What is changing fast is the interface on top of it — increasingly a natural-language conversation rather than forms and lists. ##### Today's constraint: not the software, the setup Finding a CRM in 2026 is not hard. What is hard is for a team that keeps its leads in a spreadsheet, its conversations in WhatsApp and its quotes in email to tie the three to the same record. Rapitek CRM does not leave that job to the customer. We configure the fields, the stages and the reports around your sales process, we migrate the data, and we run the training. There is a structural reason we can: the core team is small and senior, and the team that does the setup is the team that answers support. The technical position is equally plain. Your CRM data is kept in a separate database that belongs to you: separate table files, a separate backup and separate file storage. That separation is at the database level; the application chooses which customer's database each request goes to. Hosting and storage sit in three separate locations inside the European Union; traffic passes through Cloudflare's global network. The city-level breakdown and the backup detail are on the security page. The product ships with 183 business objects out of the box, and a tenant adds its own fields without writing code. ##### Our limits Rapitek CRM does not have sixty years of product history behind it. The product is new; the team is not. The history in this article is the industry's, not ours. We do not publish customer numbers. We cannot write a sentence such as “this many businesses use it” today, because the usage base is not yet mature enough to produce a reference and there is no figure for us to fill in. We do not commit to an uptime figure. The only way we could write something like 99.9% would be to write it without measuring it; there is no independent service watching our tenant addresses from outside today. Our mobile app does not work offline. Offline mode was removed from the product on 30 May 2026: there is no read cache and no write queue. The sentence that can be written is this one — if the connection drops while you are filling in a form, what you typed is held on the device for 24 hours. We do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. What we measure on the security side, and what we do not, is written out item by item on our security page. We do not offer an option to keep data in Türkiye. There is no region-selection mechanism: none of the 30 fields on the tenant record carries a region or a country. ##### Frequently asked questions - When was the first CRM software released? | The first commercial contact-management software was ACT!, released by Conductor Software in 1986. Earlier paper-based systems — the Rolodex (1958), and account cards in banking even before that — implemented the same fundamental idea manually. - Who invented Salesforce? | Salesforce.com was founded in February 1999 by Marc Benioff, a former Oracle executive, together with Parker Harris, Dave Moellenhoff, and Frank Dominguez. The company pioneered the SaaS delivery model for enterprise software — CRM in the browser, paid by subscription. - What is the difference between CRM and ERP? | CRM manages the customer-facing side of a business: leads, sales, marketing, and customer service. ERP manages internal operations: accounting, inventory, manufacturing, and HR. They complement each other, and in practice the two are typically connected through REST APIs, webhooks, and import/export rather than one replacing the other. - How is the CRM market structured in 2026? | The market has a long tail. A handful of global platforms — Salesforce, Microsoft, Oracle, SAP, Adobe, HubSpot — hold the largest single shares, but no vendor comes close to a majority, and the combined remainder is divided among hundreds of regional and vertical CRM vendors. Analyst firms such as Gartner and IDC publish current revenue and share figures; check their latest reports rather than relying on numbers quoted second-hand, which age quickly. - Will AI replace CRM? | No. The CRM is the system of record — the database that stores customer relationships. AI runs on top of it, augmenting the people who use it: drafting emails for review, scoring leads, and answering natural-language questions. The record-keeping layer stays; the interface on top of it is what AI is transforming. ##### Curious what 70 years of CRM evolution looks like in practice? Rapitek CRM was built by the team that delivered 200+ enterprise CRM implementations during our Salesforce era. A 30-minute demo shows you where that experience landed. Book a demo Data hosted in the EU Written by - Kerim Yıldırım | Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era ### [How to Choose a CRM: The Questions That Decide It](https://rapitek.com/en/blog/how-to-choose-a-crm) CRM selection guide for sales teams of 5+: process fit, customization cost, data migration, training, 3-year total cost, and KVKK and data location in Turkey. Choosing a CRM: The Questions That Actually Decide the Outcome Rehber 2026-08-02 Most CRM evaluations start the same way: a spreadsheet with vendors across the top and features down the side. Six weeks later the spreadsheet is full, every vendor scores well, and the decision is no easier than on day one. Across 200+ CRM implementations we delivered during our Salesforce era, the projects that went badly almost never failed on a missing feature. They failed because the software did not match how the team actually worked, because the data that came in was a mess, because nobody owned the system after go-live, or because the real cost showed up in month four. This guide covers the questions that decide it, written for the person who has to sign: a company with a sales team of five or more, real customers, and a process that already exists, even if it currently lives in spreadsheets and WhatsApp threads. Process fit Feature lists do not predict outcomes. ##### Contents ##### Start with how your team actually works Before you look at any product, write down how a deal moves through your company today. Take three deals from last quarter: one you won, one you lost, one still stuck. For each, list every step and every place information was recorded. The WhatsApp thread. The quote in someone's downloads folder. The email chain the manager was never copied on. Then answer: - How many people touch a deal between first contact and invoice? - Where does the work happen: office, phone, customer site, showroom? - How long is a normal cycle, and what does "stuck" look like in practice? - Who approves a discount, and how does anyone else know it was approved? - What does your sales manager genuinely need to see on Monday morning? This takes an afternoon and it is uncomfortable, because it usually reveals that nobody agrees on the process. It is also the only thing that makes a demo useful. Without it every demo looks impressive, because every demo is built to look impressive. ##### Process fit beats feature count A feature you never use costs you nothing. A mismatch costs you every day, in small amounts, forever. Five extra clicks per record is not a rounding error when a rep enters twenty records a week. So do not let the vendor drive the demo. Ask them to enter your deal, with your stages, your product names and your approval step, while you watch. Count the clicks. Count the fields a rep would fill in on a phone, standing in a customer's warehouse, with one hand. You will also hear the opposite advice: adopt the software's process, because it encodes best practice. Sometimes that is right and a bad habit is worth losing. But be honest about which is which. If your process exists because your customers pay in stages, or because dealers order differently from direct accounts, that is not a bad habit. That is your market. ##### Configuration, automation or development: know which one you are buying Almost every vendor says "fully customizable." The phrase covers three different things with three different price tags, set out in the table below. Take your requirement list into the pre-sales conversation and ask the vendor to sort every item into one of those three buckets, in writing. Then ask the question people forget: what happens in month six, when you need a change? Who makes it, how long does it take, and is it billable? A system you cannot change is a system you will outgrow, faster than you expect. What you are buying | What it covers | What it costs - Configuration | Fields, pipeline stages, page layouts, roles and permissions | Should be included, and done before go-live rather than left as homework - Automation | Assignment rules, approval flows, reminders, alerts when a deal goes quiet | Usually included, sometimes limited by tier - Development | A custom object your business needs, logic nobody else has asked for, an integration with a system the vendor has never touched | A project with a scope and a price ##### Data migration is the project, not a step inside it Ask what is in your current system before you ask how it moves. In most companies the honest answer is duplicates, three spellings of the same company name, contacts that exist only in one person's phone, and quotes in a shared drive nobody has opened since last year. Decide these before migration starts, not during: - What actually moves | Accounts and contacts only, open deals, or full history? - How far back does history go? | Five years of dead leads is not an asset. - Who does the cleanup? | You know which records are real. The vendor does not. - Can you export from your current system? | And in what format? Ask for a full export now, while you are still a paying customer with leverage. Insist on a test migration into a sandbox before go-live, and have two people who know the data check it. Once a rep finds three wrong records, they quietly go back to their own spreadsheet, and you do not get them back. ##### Adoption is decided in the first six weeks Training is not a day. It is short, role-based sessions on real data after migration: one for reps, one for managers, one for whoever handles orders and back office. A single four-hour session for everyone at once teaches nobody anything. One thing decides adoption more than all the training: the manager. If the weekly sales meeting still runs off a spreadsheet or from memory, the CRM is already dead, and the team knows it within two weeks. If the meeting runs off the pipeline, and "it is not in the CRM" means "it did not happen," adoption takes care of itself. Settle two more things before go-live. Who owns the system internally, by name? And what does the field team see on a phone? If your reps work outside, mobile is the whole product for everyone on the team who never sits at a desk. ##### Total cost of ownership: the lines that are not on the pricing page The per-user monthly price is the smallest number in this decision. Build a three-year total instead, and make the vendor answer every line: - License, per user per month, and what happens to it at renewal. - Implementation and configuration, one-off, with the scope written down. - Data migration: included or priced separately, and up to how many records? - Integrations, usually priced per integration: accounting, e-invoice, website forms, WhatsApp, telephony. - Training sessions, including refreshers for people you hire next year. - Ongoing changes: hourly, retainer, or included? - Your own internal hours. No invoice arrives, but the cost is real. - Limits on storage, API calls, automation runs and email volume, since overages are where "cheap" becomes expensive. - Adding users mid-term, and exporting everything if you part ways. A platform with a low license fee and expensive changes can cost more over three years than one with the opposite shape. Neither is wrong. You need to know which one you are signing. ##### Buying a CRM in Turkey: the questions international checklists skip Four things matter here that a generic evaluation list will not raise. KVKK and the paperwork. Your company is the data controller. The vendor is a processor acting on your instructions. You need a written data processing agreement, and your VERBIS entry and privacy notice have to reflect the new system. Ask for the vendor's agreement text early. If they do not have one ready, that itself is information. Where the data physically sits. Ask for the country and the hosting provider, in writing. This is not paranoia, it changes your obligations. Under Article 9 of KVKK, personal data sent to servers outside Turkey is a cross-border transfer: it needs a valid legal basis, disclosure in your aydınlatma metni, and depending on the route you choose, explicit consent from the data subject. Here is our own answer, plainly. The Rapitek CRM database runs in Helsinki, Finland; uploaded files are stored in Frankfurt and database backups in Falkenstein, both in Germany. All three are in the EU. So yes, using Rapitek CRM involves a cross-border transfer under KVKK. And there is a second one you need before you write your notice: if you switch on the AI features, that request goes to the United States. We say all of this during the sales conversation, not after signature, and we give you the wording for your privacy notice and the consent line on your web forms. We are direct about it because "don't worry about it" is the answer that should worry you: a vendor who cannot name the country their servers are in cannot help you defend that choice to an auditor. What we do not claim: we hold no ISO 27001 or SOC 2 certification, because we have not completed those processes. What we do have is specific: TLS on data in transit, a separate database for your CRM records rather than shared tables, and two-factor authentication on accounts. E-fatura and accounting. A CRM is normally not the system that issues your e-fatura or e-arşiv document; your accounting software or integrator does that. The real question is the handoff. When a deal is won, does the order reach accounting automatically, or does someone retype it? Ask which specific integrators and ERP systems the vendor has actually connected before. Do not ask whether integration is possible. Everything is possible. You want to know whether it has been done. Support and WhatsApp. Ask what language support is delivered in, what hours, and whether the person answering has seen your configuration before. Our own position: support is in Turkish, in Turkish working hours, from the same team that built your setup. In practice we reply the same working day. We deliberately do not put a number on that: we have no system measuring ticket times yet, and we do not publish a duration we have not measured — so treat it as our working practice, not as a commitment. We run no 24/7 desk and no ticket queue. Separately, in the projects we have worked on, a great deal of B2B conversation in Turkey happens on WhatsApp, and if those conversations live on personal phones your pipeline is fiction and your customer history walks out with the employee. Ask every vendor how a WhatsApp conversation ends up attached to the customer record. ##### What good looks like six months in Four signals tell you it worked. The weekly sales meeting runs off the pipeline, not a spreadsheet. The forecast comes from records rather than memory and optimism. A new hire can read an account's history without asking a colleague what happened. And the number of required fields has gone down, not up, because someone kept pruning. A quieter fifth signal: you have changed something twice without paying a project fee and without waiting on a change-request queue. That is usually the difference between a system you own and a system you rent. Frequently asked ##### Frequently asked questions about choosing a CRM - What should I evaluate first when choosing a CRM? | How your team actually works, not the feature list. Map your current sales process first — who records what, at which point a deal moves forward, what happens after a lost deal. Every vendor scores well on a feature matrix; almost no failed implementation we saw failed because a feature was missing. They failed on process fit, migration and adoption. - How long does a CRM implementation take? | It depends on whether your requirements are met by configuration, automation or custom development — those are three different cost and time classes, and knowing which one you need is the single most useful thing you can establish before signing. Where the vendor takes on setup, data migration and training, the work is scoped and dated up front. Where you do it yourself, plan for months. - Which costs are missing from the price list? | Usually four: data migration and cleanup, configuration and later changes, training and re-training as people join, and either an internal administrator or hourly external consulting for every subsequent adjustment. Compare offers on three-year total cost of ownership, not on monthly licence fee. - Does CRM data have to be stored in Turkey? | No. Turkish law (KVKK) does not require local storage; it requires that transfers abroad rest on a lawful basis, with explicit consent and a disclosure text where that basis is consent. What matters is that the vendor can name the country. Rapitek CRM is hosted in the European Union — database in Finland, media in Germany — and we state that plainly rather than saying "the cloud". - Can I try Rapitek CRM on a free trial? | No. We do not offer a self-service free trial, and that is deliberate: the product is configured to your process before you use it, so an empty trial account would not show you what you would actually be buying. Instead we run a working session with your own deals and pipeline in front of you. ##### See it against your own process If you are evaluating, the useful next step is not another feature list. It is a working session with your real deals in front of you. We do not offer a self-service free trial, and that is deliberate. Rapitek CRM is configured for you: your fields, your pipeline, your data migrated and your team trained. After the discovery call, we give you a date, not a range. There is nothing meaningful to try alone inside an empty system. Book a demo, or message us on WhatsApp: +90 212 963 22 84 — the same line we answer ourselves, every working day. Bring one real deal and your current spreadsheet. That is enough for us to tell you honestly whether we are a good fit. Rapitek CRM is built for teams of five or more with a real sales function, so if you are a one-person office looking for a ten-dollar-a-month tool, we will tell you that too. Written by - Kerim Yıldırım | Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era ### [Lead Management: From First Contact to Qualified Opportunity](https://rapitek.com/en/blog/lead-management-guide) How to qualify, score, route and follow up on leads — plus the KVKK, explicit consent and İYS rules that apply when you collect leads through a form in Turkey. Lead Management: From First Contact to a Qualified Opportunity Rehber 2026-08-02 A form gets submitted at 14:12. The reply goes out the next morning at 09:40. In between, the buyer has already opened three other vendor sites, sent two more forms, and started forming an opinion about what a good answer to their problem looks like. The deal is not lost yet, but the frame has been set by someone else. Lead management is the set of rules that decides what happens in those hours. Not a philosophy — rules: who owns the record, what has to be true before it moves forward, what the second message says, when the file gets closed. Below is how we structure it, based on what we saw across 200+ CRM projects delivered during our Salesforce era, plus the part most English-language guides skip entirely: what Turkish law requires when you collect those leads through a form. First response An autoresponder is not a response; it is a receipt. ##### Contents ##### A lead is not an opportunity A lead is an unverified claim of interest. Someone typed a name into a box. It may be a buyer, a competitor, a student writing a thesis, or a person who wanted the PDF. An opportunity is different in kind, not in degree. It has a named company, an identified problem someone inside that company wants solved, a person who can talk about money without leaving the room, and a plausible time frame. Everything before that is research. The distinction matters because it decides what your pipeline number means. If leads and opportunities share one bucket, your forecast is a wish list and your conversion rate has no denominator you can trust. Make the transition an explicit, dated event with written criteria — a stage change someone performs on purpose, not a field that drifts. A workable conversion rule: you can name the company and the role of the person, you understand the problem in their words, you know who else is involved in the decision, and there is an agreed next step with a date on it. - Lead: interest claimed, nothing verified. - Marketing-qualified: fits your target profile on paper. - Sales-qualified: a human has spoken to them and the problem is real. - Opportunity: named need, identified decision-makers, next step with a date. ##### Qualification frameworks: use one, do not worship it BANT asks about Budget, Authority, Need and Timeline. It is fast and it fits shorter, more transactional cycles. Its weakness is the ordering: asking about budget first assumes a budget already exists. In the mid-market Turkish companies we have seen it usually does not — the budget gets created after someone builds an internal business case, and often the person you are talking to is the one who will build it. MEDDIC asks about Metrics, Economic buyer, Decision criteria, Decision process, Identified pain and Champion. It is built for long, multi-stakeholder deals where the risk is not losing to a competitor but losing to indecision. It costs more discovery time, and on a two-week cycle it is overkill. Need-first variants such as CHAMP reorder the same questions to start with the problem. None of these is correct in the abstract. A framework is not a script — it is a checklist of things you do not know yet. Two practical rules. First, pick one and write down what each letter means in your own business, in your own words; "Authority" in a 40-person distributor means something different than in a bank. Second, put the fields in the CRM so the answers are inspectable by someone other than the rep. A framework that lives only in a salesperson's head is a personality, not a process. And if two people on the same team use two different frameworks, you have neither — you cannot compare their pipelines. ##### Scoring: a rule you can read out loud Keep two axes separate: fit (who they are) and engagement (what they did). A very engaged bad fit and a barely engaged perfect fit are not the same object, and collapsing them into one number hides exactly the thing you need to see. Fit signals are structural: sector, company size, how many people are actually in the sales team, whether there is a field team, how many locations the work runs from, what they use today. Engagement signals are behavioural: a demo request weighs more than a newsletter sign-up, a reply to a message weighs more than a page view, a booked meeting outweighs both. Negative scoring matters as much as positive. Job applications, student research, competitor domains, free mail addresses with no company name, countries you do not serve — subtract, and route them out of the sales queue. Calibrate against reality, not opinion. Take last year's closed-won and closed-lost deals, run your proposed rule backwards over them, and see whether it would have ranked them correctly. If it would not, the rule is wrong. Review it quarterly, because your ideal customer moves. One caution: a score is a queue order, not a verdict. Auto-discarding low scores is how teams quietly delete their own market. ##### Routing: one owner, within minutes Every lead needs exactly one named owner, assigned automatically, fast. Shared inboxes and "whoever sees it first" are not routing rules; they are a way of guaranteeing that busy periods get the worst service. Choose a basis and write it down: round robin, territory, sector specialisation, or company size. Weighted round robin with capacity caps works well when reps have unequal loads. Whatever you pick, add the two rules people forget: - Fallback: if the owner has not touched the record within a set number of minutes, reassign it automatically. - Escalation: if it is still untouched after a second threshold, notify a manager — quietly, in a channel, not as a public shaming. - Out-of-hours: decide in advance who covers evenings and weekends, and what an acceptable holding reply looks like. Also deduplicate before you create. Check email domain and phone number against existing records at the moment of submission. Merging duplicates three months later is where the history dies — two owners, two versions of the story, one annoyed buyer who has explained the same thing twice. Rapitek CRM #### Owner, source and status, on the record itself The Leads screen in Rapitek CRM: status chips for Open, Working and Closed, the lead source and owner fields, the date each record was created, and filter chips at the top that carry their own counts. ##### Why first response time decides more than the pitch We deliberately will not quote a statistic here, because the mechanism is more useful than a number someone else measured on someone else's market. When a person submits a form, they are in an active decision window that they opened themselves. They have context loaded: the problem is on their screen, the alternatives are in open tabs, and they are willing to talk. That window closes on its own. Reach them inside it and you are having a conversation. Reach them two days later and you are interrupting a different task, and the criteria they will judge you by have already been written — usually by the vendor who answered first. Measure first response as the first meaningful contact by a human. And measure the tail, not the average: a p90 of eleven hours with a two-minute average tells you the truth that "average 40 minutes" hides. In Turkey the channel that closes this gap in practice is WhatsApp. A short message that uses the person's name, refers to what they actually asked about, and offers two specific times tends to do better than a formal email with an attached brochure. Keep the first message under five lines and end it with one question. ##### Follow-up cadence: written down, or it does not exist A cadence is a specific answer to four questions: how many touches, over how many days, on which channels, carrying what content. Without those four, "we followed up" means whatever the rep felt like doing that week. A reasonable starting cadence for an inbound demo request: contact within minutes on the channel they used; a second touch the same day on a different channel; then spaced touches over the following two weeks, alternating channels. Adjust to your cycle length, not to a template you read. The rule that actually changes results: every touch must add something the previous one did not. A relevant example from their sector, a specific question about their process, a short note on how the setup would work for a team their size. "Just following up" adds nothing and trains people to ignore you. Have a stop rule. After the cadence ends without a reply, move the record to nurture with a dated re-entry — do not leave it open. Leads that stay open forever inflate your pipeline and destroy your ability to read conversion rates. Log every touch in the CRM, not in someone's personal phone. Two reasons: when that person leaves, the relationship history leaves with them; and under KVKK, personal data sitting in a private handset with no record, no retention period and no access control is its own problem. ##### Collecting leads in Turkey: KVKK, explicit consent and İYS A lead form is a personal data collection point. Three obligations apply, and the most common mistake is merging them into one checkbox. 1. The privacy notice (aydınlatma metni). Under Article 10 of KVKK (Law No. 6698), you must inform the person at or before the moment of collection — regardless of which legal ground you rely on. The Communiqué on the obligation to inform sets out the required content: the identity of the data controller (and representative, if any), the purposes of processing, to whom and for what purpose the data may be transferred, the method and legal ground of collection, and the person's rights under Article 11. This is a standalone text, readable before submission. Version it and archive each version. 2. The legal ground. You do not automatically need consent. Responding to a demo request can rest on the pre-contractual ground in Article 5/2-c or on legitimate interest in Article 5/2-f. Consent is the correct ground for later marketing use, not for answering the question the person asked you. Bundling everything into a single "I accept" box weakens the whole structure, because explicit consent must be freely given and specific to a defined subject. If the form will not submit without the marketing box ticked, that consent is not freely given. 3. İYS for commercial messages. Under Law No. 6563 and the regulation on commercial electronic messages, marketing sent by messaging apps requires the recipient's prior approval; for SMS, email and phone calls the same prior approval is required, and that approval must be registered in the İleti Yönetim Sistemi (İYS) within three business days. If the address is not in İYS when you send, the message is treated as sent without consent. Opt-out must be free and must be actioned within three business days. The approval regime differs for recipients who are traders (tacir/esnaf), but registration and opt-out handling still apply — confirm your own case with counsel. 4. Cross-border transfer. If your CRM, email platform or support tool runs on servers outside Turkey, that is a transfer under Article 9, which was amended by Law No. 7499 in 2024. The routes are an adequacy decision, appropriate safeguards such as standard contractual clauses (which must be notified to the Board within five business days of signing), or — for occasional transfers — a separate, standalone explicit consent obtained after the person has been informed of the risks. "Separate" is the operative word: it cannot be folded into the general consent line. We apply this to ourselves. Rapitek CRM's database runs in the EU (Helsinki, Finland) and media storage in Frankfurt, Germany. That is a cross-border transfer under Article 9, we say so in our own notice, and we do not claim otherwise. 5. Evidence. Store what you would need to prove consent a year later: the exact version of the text displayed, timestamp, IP address, the state of each checkbox, and the İYS transaction reference. If you cannot reconstruct what the person saw that day, you cannot demonstrate consent. 6. Retention. Dead leads are not a keepsake. Set a written retention period, run periodic deletion, anonymisation or destruction, and check whether you have a VERBİS registration obligation. A CRM full of eight-year-old untouched leads is both a compliance exposure and a source of bad metrics. ##### What to measure Measure the funnel and the hygiene separately. The funnel tells you how the business is doing; hygiene tells you whether the funnel numbers are real. - Funnel | Leads by source · qualified rate · lead-to-opportunity conversion · opportunity win rate · pipeline created per source. - Speed | Time to first human contact (p90, not average) · time from lead to opportunity · number of touches before the first meeting. - Quality | Demo no-show rate · rate of leads disqualified after the first call · cost per qualified lead if you are paying for traffic. - Hygiene | Percentage of leads with an owner inside your target window · percentage with the source filled in · percentage with a dated next step. One warning from our own logs: form counts and search impressions are inflated by bots. We once traced a large batch of submissions on one of our own English pages to automated traffic, not people. Before you judge a channel on volume, separate the real submissions from the noise — otherwise you will fund the wrong source and starve the one that actually produces meetings. Review response time and stuck leads weekly. Review conversion rates monthly. Anything reviewed less often than that turns into decoration. Frequently asked ##### Frequently asked questions about lead management - What is the difference between a lead and an opportunity? | A lead is an unverified contact: someone filled a form, wrote on WhatsApp or left a card. An opportunity is a lead that has passed qualification — there is a real need, a budget range, an identified decision path and a timeframe. Treating every lead as an opportunity inflates your pipeline and destroys forecasting; treating none of them as opportunities means nothing ever moves. - Which qualification framework should I use — BANT, MEDDIC or something else? | Use one, and do not worship it. A framework is a checklist for the conversation, not a scoring ritual. Pick the one that matches your sales motion, write down what each criterion means in your business, and make sure a salesperson can apply it in a two-minute call. A framework nobody can recite is not in use. - How quickly should we respond to an inbound lead? | Faster than you think is necessary, and faster than the pitch quality would suggest. In practice the first team to reply frames the conversation, and in Turkey a large share of B2B enquiries now arrive over WhatsApp, where the expectation is minutes rather than hours. Measure your median first response time as a KPI — not the average, which one fast reply can flatter. - What does KVKK require when I collect leads through a form? | A disclosure text (aydınlatma metni) explaining what data you process, why, on what lawful basis and for how long — and, where the basis is consent, explicit consent collected separately from other terms. If the data leaves Turkey, that transfer needs its own lawful basis under Article 9 and must be disclosed. Pre-ticked boxes and consent bundled into terms of service do not count. - What is İYS and does it apply to my lead follow-up? | İYS (İleti Yönetim Sistemi) is Turkey's central registry for commercial electronic messages. If you send marketing messages — SMS, email or phone calls — to recipients in Turkey, the consent must be registered there and recipients must be able to opt out. Transactional replies to someone who contacted you are a different case. Check your own obligations with counsel; this is a description, not legal advice. ##### Where to go from here If you want to see this running rather than read about it, book a demo. We will walk through your actual lead flow — form to owner to cadence — and show how it looks in Rapitek CRM, including the consent fields and the İYS sync, which runs when you connect your own İYS account through Verimor. You can also reach us on WhatsApp: +90 212 963 22 84. That is a WhatsApp line, and it goes to the founding team during business hours; there is no ticket queue in between. Two honest notes. We do not offer a self-service free trial — setup is customisation-first and covers data migration and training; after the discovery call we give you a date, not a range, and it makes sense for teams of roughly five sales users and up. And WhatsApp is not an add-on for us; it sits in the middle of the lead workflow, which is where it sits in most Turkish sales teams already. Written by - Kerim Yıldırım | Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era ### [Pharmacy Inventory: Expiry Tracking & Compliance | Rapitek](https://rapitek.com/en/blog/pharmacy-inventory-managing-expiry-dates-regulatory-compliance) How pharmacies manage expiry dates, FEFO rotation, lot traceability and audit trails — plus how a configurable CRM supports compliance, hosted in the EU. Pharmacy Inventory Management: FIFO, Expiry Tracking & Audit Trail Rehber 2026-05-03 Pharmacy operations How pharmacies keep thousands of products safe, in date and audit-ready — expiry monitoring, FEFO rotation, lot traceability and the systems that hold it all together. Book a demo ##### Contents ##### Quick answer Pharmacy inventory management combines stock tracking with expiry-date monitoring, batch/lot traceability for recalls, controlled-substance audit logs and dispensing analytics. The typical building blocks are barcode scanning at receipt, automated expiring-soon alerts (often set at 90/60/30-day windows), documented disposal of expired stock and supplier qualification records. Exact compliance requirements vary by jurisdiction — the FDA and DEA in the United States, the EMA in the EU, TİTCK in Turkey — so always confirm the specifics with your own regulator or pharmacy board. Patient safety Two failure modes matter more than the rest: stock that expires unnoticed on the shelf, and stock that cannot be traced to a lot when a recall lands. ##### Why pharmacy inventory is different In pharmacy operations, inventory management is a cornerstone of patient safety, not just cost control. A pharmacy tracks thousands of products, each with its own expiration date, storage requirements and regulatory obligations. Modern pharmacy inventory management therefore tracks far more than quantities. Lot numbers, expiration dates, manufacturer details and storage conditions all live on the same record, and digital systems have made real-time tracking and predictive reordering practical for independent pharmacies as well as chains. The regulatory layer adds real complexity. Different agencies mandate specific documentation, storage conditions and handling procedures for different categories of medication: controlled substances need extra security and logging, biological products need temperature monitoring and specialised storage. Which rules apply depends on where you operate — treat any list of requirements (including the ones in this article) as a starting point, and verify against your own regulator's current guidance. ##### What a modern pharmacy inventory system tracks - Lot and batch numbers | Every unit ties back to a manufacturer lot, so a recall becomes a filtered list instead of a shelf-by-shelf hunt. - Expiration dates and FEFO | First Expired, First Out rotation with automated expiring-soon alerts — commonly at 90, 60 and 30 days before expiry. - Storage conditions | Temperature logs and storage-class flags for cold-chain and biological products, kept alongside the stock record. - Controlled-substance logs | Additional security, counts and audit entries for regulated categories, ready for inspection. - Supplier qualification | Approved-supplier records, receipt scanning and discrepancy notes at the point of goods-in. - Disposal documentation | A written trail for expired or damaged stock leaving the pharmacy — what, when, how much and why. ##### Key benefits of getting it right 1. Patient safety. The mechanism is specific, not vague: an expiry alert fires before the stock reaches a patient, and enforced FEFO rotation means the shelf hands out the soonest-expiring lot rather than whichever box is at the front. Both remove a decision from human memory at the exact point where memory fails. 2. Financial control. Two costs shrink at once — the write-off cost of stock that expired unsold, and the carrying cost of holding more than you need. Systems that use historical dispensing data to forecast demand prevent both stockouts and overstock, so capital is not tied up on the shelf while availability stays high. Measure your own baseline before and after; the size of the gain depends entirely on your product mix and current waste rate. 3. Audit readiness. Automated systems maintain the trails regulators expect — controlled-substance movements, temperature logs, disposal records — as a by-product of daily work. The practical difference at inspection is not that the records are better written, but that they exist at all before the inspector asks. Implementation ##### A realistic implementation roadmap - Assessment | Map current stock processes, count the pain points — expired write-offs, count discrepancies, recall response time — and define what the new system must fix. - Technology selection | Choose software that fits your dispensing workflow and integrates with the systems you already run, rather than the longest feature list. - Staff training | Train everyone who touches stock — receiving, shelving, dispensing, disposal. Adoption fails at the bench, not in the back office. - Standard operating procedures | Write down the protocols: receiving checks, cycle counts, expiry sweeps, quarantine handling. The system enforces what the SOP defines. - Monitoring and optimisation | Set KPIs — waste rate, stockout rate, count accuracy — and review them on a schedule. Phase the rollout by function rather than switching everything at once, and keep the reviews running until those KPIs settle. ##### Common challenges and how to overcome them The recurring obstacles are integration and adoption. Connecting a new inventory system to existing dispensing or accounting software takes real technical work, and staff who have run the pharmacy on paper and habit will resist a screen that slows them down in week one. Structured training and change management are what separate a system that gets used from one that gets worked around — budget for them as part of the project, not as an afterthought. The other persistent problem is perpetual-inventory drift: the system says 40 boxes, the shelf holds 36. Regular cycle counting — small, scheduled counts rather than one painful annual stocktake — combined with barcode verification at receipt and dispensing is what keeps the records honest. Track your discrepancy rate as a KPI so you can see whether it is actually falling. ##### Where a CRM fits — and a note on data protection A CRM does not replace a licensed dispensing system — it complements one. The customer-facing half of a pharmacy business (clinics, care homes, B2B accounts, suppliers, follow-ups, complaints and recall communication) lives naturally in a CRM, and inventory-adjacent records such as lots, expiry dates, quarantine status and quality-control checks are configurable in Rapitek CRM — setup is part of the deployment; its scope and any fee are worked out in discovery and agreed in writing. For connecting to ERP or accounting software, Rapitek CRM works through REST API, OAuth2, webhooks and import/export, delivered by our professional services team. You can see the full integration list on the integrations page, and how we approach regulated sectors under sectors. Data location matters in healthcare-adjacent work. Rapitek CRM is hosted in the EU — the database in Helsinki, Finland and media storage in Frankfurt, Germany — so records sit on GDPR-governed infrastructure. For pharmacies in Turkey, KVKK — Turkey's data protection law (No. 6698) — treats EU hosting as an international data transfer, which your consent and disclosure texts need to reflect; our security page covers the architecture, including a separate database per customer and TLS in transit. New to CRM selection? Start with the CRM buyer's guide or browse the rest of the blog. ##### Frequently asked questions - What is the difference between FIFO and FEFO? | FIFO (First In, First Out) dispenses the oldest-received stock first. FEFO (First Expired, First Out) dispenses the stock that expires soonest first — which is not always the oldest, because different lots carry different expiry dates. For pharmaceuticals, FEFO is the safer rule and is what modern pharmacy inventory systems enforce. - What expiry alert windows should a pharmacy set? | A common pattern is tiered alerts at 90, 60 and 30 days before expiry: at 90 days you can still return or redistribute stock, at 60 you prioritise dispensing it, at 30 you prepare documented disposal. Tune the windows to your product mix — fast-moving generics need less lead time than slow-moving specialty items. - Which regulations apply to pharmacy inventory? | It depends entirely on where you operate. In the United States the FDA and DEA set the framework, in the EU the EMA and national agencies, in Turkey TİTCK — and state or provincial pharmacy boards add their own rules on top. This article describes common patterns, not legal advice: confirm current requirements with your own regulator or professional association. - Which metrics show whether inventory management is improving? | Track four: waste rate (value of expired stock written off, as a share of purchases), stockout rate, physical-count accuracy against the system, and recall response time. Measure all four before you change anything — without a baseline you cannot tell whether the new system helped, and vendor-quoted improvement figures are not a substitute for your own numbers. - Can a CRM replace a dedicated pharmacy dispensing system? | No. Dispensing systems are licensed, regulated software for prescriptions and point of sale. A CRM complements them by managing the relationship side — B2B accounts, clinics, suppliers, follow-ups, recall communication — and by holding configurable records such as lots, quarantine and quality-control checks. We do that configuration as part of the deployment. - Where is Rapitek CRM data stored? | In the European Union: the database runs in Helsinki, Finland and media files are stored in Frankfurt, Germany, on GDPR-governed infrastructure with a separate database per customer and TLS in transit. For Turkish organisations, KVKK (Law No. 6698) treats EU hosting as an international transfer, so consent and disclosure texts should reflect it. ##### See pharmacy workflows in a live demo A 30-minute walkthrough with our team — setup, training and integrations are scoped in discovery, with any fee agreed in writing. Book a demo Built by the team behind 200+ enterprise CRM implementations completed during our Salesforce era. Written by - Kerim Yıldırım | Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era ### [What Is a Customer? Definition, Types & Lifecycle Guide](https://rapitek.com/en/blog/what-is-customer) What is a customer? Clear definition, customer vs consumer, B2B and B2C types, segmentation and the customer lifecycle — a complete guide from Rapitek CRM. What Is a Customer? CRM 2025-04-22 CRM Guide Who counts as a customer, how do customers differ from consumers, and what types are there? From the B2B/B2C distinction to segmentation, the customer lifecycle and CRM — a complete guide. ##### Contents ##### Introduction: Why the Customer Concept Is Critical for Business The customer is one of the foundation stones of business success, and in today's competitive markets the concept matters more than ever. In its simplest form, a customer is a person or organization that purchases goods or services from a business. In modern business practice, however, the concept carries a strategic weight that goes far beyond this simple definition. That is why a deep understanding of who customers are, what types exist and why they matter is the first step in building a successful business strategy. Customer-centric thinking is the common trait of today's most successful companies. In this guide we look at the different dimensions of the customer concept, examine customer types, and explain why effective customer relationship management is vital for any business. If you are starting customer relationship management from scratch, our step-by-step CRM guide is a good companion read. In modern marketing and sales strategy, concepts such as customer experience, customer satisfaction and customer loyalty play a central role. Businesses no longer simply sell products or services — they build long-term relationships with their customers to achieve sustainable growth. Customer-centric Customers are the reason a business exists. Without them, no commercial activity is sustainable. ##### Customer Definition and Core Characteristics ###### The Traditional Definition Traditionally, a customer is an individual or corporate buyer that purchases goods or services from a business. This definition centres on the moment of the transaction — the act of buying. Today the definition has broadened considerably. In modern business, a customer is anyone who interacts with the company, exchanges value with it, and contributes directly or indirectly to its success. This wider view may include active purchasers, prospects who have shown interest but not yet bought, past customers who may return, and advocates who recommend the brand without being paid to. It is this broader perspective that brings the customer lifecycle into focus. ###### Customer vs. Consumer: What Is the Difference? The terms customer and consumer are often used interchangeably, but there is an important distinction. The customer is the person or organization that makes the purchase; the consumer is the person who actually uses the product or service. When a parent buys a toy for their child, the parent is the customer and the child is the consumer. In many everyday purchases the customer and the consumer are the same person, but in B2B scenarios and gift purchases they are often different. ##### Core Characteristics of a Customer - Has a need | Customers engage with businesses to satisfy specific needs - Makes decisions | They play an active role in the buying process and set their own preferences - Expects value | They expect satisfying value in return for what they pay - Judges the experience | They evaluate the entire buying experience, not just the product - Builds relationships | They have the potential to develop long-term relationships with a business ##### Types of Customers and Segmentation ###### Customer Types by Demographics Classifying customers by demographic characteristics is critical for building effective marketing strategies. This segmentation approach helps businesses understand their target audiences far better. Individual customers (B2C): - By age group: young, middle-aged and senior customers - By income level: low, medium and high income - By education: primary, secondary and university graduates - By lifestyle: traditional, modern, technology-driven B2C customers typically have shorter decision cycles, are influenced by peer reviews and social media, and expect personalized experiences and quick service. Corporate customers (B2B): - By company size: SMEs, large enterprises, multinationals - By industry: technology, healthcare, finance, manufacturing, education - By geography: local, national, international B2B buying involves longer decision processes with multiple stakeholders, a focus on ROI and business value, and relationship-based transactions that require detailed product information and support. ###### Customer Types by Buying Behaviour How customers buy shapes a company's sales and marketing strategy, and this classification is essential for optimizing the customer experience. By purchase habit: - New customers: buying for the first time - Repeat customers: buying regularly - Loyal customers: committed to the brand over the long term - Advocate customers: recommending the brand to others ###### Segmenting Customers by Profitability Not all customers are equally valuable to a business. Profitability analysis supports strategic decisions about where to invest resources: - Gold customers: high profitability, low cost to serve - Silver customers: medium profitability, standard service needs - Bronze customers: low profitability, high cost to serve - Loss-making customers: unprofitable and expensive to serve From first contact to advocacy ##### The Customer Lifecycle - Awareness | A potential customer discovers your brand or solution for the first time. - Consideration | The prospect evaluates your offering against the alternatives. - Purchase | The decision is made and the first transaction takes place. - Onboarding | The new customer is introduced to your product or service and starts seeing value. - Retention | Ongoing engagement and value delivery keep the relationship alive and encourage repeat business. - Advocacy | Satisfied customers become ambassadors who recommend you to others. Rapitek CRM lead list: full name, company, e-mail, phone, lead status, lead source, owner and created date columns. Lifecycle stages become trackable data in a CRM: every prospect carries a status and a source on a single screen. ##### Customer Relationship Management and Why It Matters ###### The Role of CRM Systems Today, customer relationship management is unthinkable without technology. A CRM (Customer Relationship Management) system gathers customer data on a central platform, so a business can analyse it and deliver personalized experiences at every stage of the lifecycle described above. Modern CRM platforms provide valuable insight at each of those stages — from the first enquiry to long-term advocacy. You can find more detail on CRM strategy across our blog. ###### Customer Satisfaction and Loyalty Customer satisfaction expresses how well a product or service meets customer expectations. Loyalty goes beyond satisfaction: it is the emotional bond that ties a customer to a brand. What drives customer satisfaction: - Quality products and services - Fast, effective customer service - Personalized experiences - Transparent, trustworthy communication - Quick resolution of problems - Regular customer surveys that feed back into decisions ###### Optimizing the Customer Experience Customer experience is the customer's total perception across every point of interaction with a business. Optimizing it requires an omnichannel approach: physical locations, website, mobile app, social media and customer service all need to deliver one consistent experience. ##### The Strategic Importance of Customers ###### Impact on Revenue and Profitability Customers are a company's primary source of revenue — but the story goes further. Customer Lifetime Value (CLV), the total revenue a customer is expected to generate over the entire relationship, is critical to long-term strategic planning. A loyal customer can keep generating revenue for years. Winning a new customer costs materially more than keeping an existing one: advertising spend, sales effort and a lower conversion rate all stack up. The widely quoted "X times more expensive" multipliers mostly trace back to no verifiable source, and they do not describe your business. Work out your own figure instead: calculate your customer acquisition cost (CAC) and compare it with what retention costs you. The gap tells you how much budget retention deserves. ###### Brand Image and Reputation Satisfied customers are a company's strongest brand ambassadors. In the social media age, one customer's experience can influence thousands of potential customers. Positive experiences feed organic, word-of-mouth growth. ###### The Customer's Role in Innovation Customer feedback is an indispensable input to product and service development. Understanding customer needs — and anticipating future demand — is a durable source of competitive advantage. ##### Conclusion: The Future of Customer-Centric Business The customer sits at the centre of modern business. Beyond a simple buyer–seller relationship, customers act as strategic partners, sources of innovation and brand ambassadors. Defining customers correctly, segmenting them well and building effective relationships with them is a fundamental condition of sustainable business success. In today's digital environment, customer relationship management depends on technology. CRM platforms, data analytics and AI-supported tools let businesses optimize the customer experience end to end. At Rapitek, we draw on the experience of more than 200 enterprise CRM implementations delivered during our Salesforce era to help businesses manage customer relationships strategically. Adopting a customer-centric approach means looking beyond short-term sales targets and focusing on long-term customer value. Customer satisfaction, loyalty and advocacy have become core performance indicators of modern business. The successful businesses of the coming decade will be the ones that put customer experience at the centre, personalize at scale and keep learning. If you want technology on your side in that transformation, take a look at what Rapitek CRM offers. ##### Our limits This is a concept article, not a product pitch for Rapitek CRM. What follows is where the expectations this topic raises actually stand with us. - There is no module that builds your customer segmentation for you. You define the segment; the CRM applies that definition and repeats it. Fields and objects can be added without writing code. - There is no box that calculates CLV or CAC for you. The inputs to both numbers sit in your own accounting and marketing data; the CRM reports them, it does not produce them. - There is no rule-based assignment that advances the lead status or the opportunity stage by itself. The assignment-rule object exists, and in all eight tenants we can reach the record count is zero. Your team, or a workflow you define, moves the status and the stage. - Your CRM data is kept in a separate database that belongs to you: separate table files, a separate backup and separate file storage. That separation is at the database level; the application chooses which customer's database each request goes to. - There is no free tier in Rapitek CRM; the route runs through a demo request. ##### Related reading - CRM Guide — a step-by-step introduction to customer relationship management. - Rapitek CRM Product Tour — manage customers and their full communication history on one screen. - CRM Pricing — real costs, transparently listed. ##### Frequently Asked Questions - What is the difference between a customer and a consumer? | The customer is the person or organization that makes the purchase; the consumer is the person who actually uses the product or service. When a parent buys a toy for their child, the parent is the customer and the child is the consumer. The same person can be both customer and consumer. - What do B2B and B2C customers mean? | B2C (business-to-consumer) is the model in which a business sells to individual consumers, who are segmented by age, income, education and lifestyle. B2B (business-to-business) is the model in which a business sells to other businesses; corporate customers are classified by company size, industry and geography. - What are the main types of customers? | Customers are classified along several axes: demographically as individual (B2C) or corporate (B2B); by buying behaviour as new, repeat, loyal and advocate customers; and by profitability as gold, silver, bronze and loss-making customers. - What is Customer Lifetime Value (CLV)? | Customer Lifetime Value is the projected total revenue a customer will generate over the entire relationship with a business. Because retention costs materially less than acquisition, CLV is the core metric behind customer retention strategies. Work out the gap with your own data: calculate your customer acquisition cost (CAC) and compare it with what retention costs you — the widely quoted industry multipliers do not describe your business. - What are the stages of the customer lifecycle? | The typical customer lifecycle runs through awareness, consideration, purchase, onboarding, retention and advocacy. A CRM system helps a business track and improve each of these stages on a single platform. ##### Know every customer on one platform Built on experience from more than 200 enterprise CRM implementations completed during our Salesforce era, Rapitek CRM is configured to the way your team works — and we do the setup. Request a Demo Setup scope and any fee are agreed in writing. Written by - Kerim Yıldırım | Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era