--- title: "Topic: Enquiry Flow and CRM | Sağlık Ajansı" description: "Pages on building single-record tracking, ownership, first-response discipline and loss-reason analysis across the chain from enquiry to appointment." canonical: https://saglikajansi.com.tr/en/topics/enquiry-flow-and-crm.html language: en last_modified: 2026-08-22 alternates: - en: https://saglikajansi.com.tr/en/topics/enquiry-flow-and-crm.html - tr: https://saglikajansi.com.tr/konular/basvuru-akisi-ve-crm.html publisher: "Sağlık Ajansı — Marka Studio Dijital Reklam Tasarım Ajansı" note: "Bu dosya, kanonik HTML sayfasının makine-okunur alternatifidir. Kanonik kaynak yukarıdaki canonical URL'dir." --- *TOPIC* # Enquiry Flow and CRM Most enquiries lost in medical tourism disappear through ownerlessness rather than indifference. This topic brings together the pages on single-record tracking, stage definitions, first-response time and loss analysis. The same patient writes to the form, messages the next day, then asks on social media. Internally those reach three different people and everyone assumes someone else replied. ## An order of responsibility before software What a CRM engagement really installs is accountability, not a product. One record per enquiry, a named owner, a reply inside an agreed window and a stage anyone can read at a glance. Only once that holds does the choice of tool start to matter. If "warm enquiry" means five different things to five people inside the institution, both measurement and reporting lose sense. The first task is writing the stages so everyone reads them the same way. ## Loss reasons are the most valuable data Most institutions record the enquiry that converted and not the one that did not. Yet the improvement opportunity hides in loss reasons: price, dates, language, response delay, visa. Kept for three months, that list clearly separates operational problems from communication ones. Making the field mandatory meets short-term resistance from the team, and still determines the quality of every later decision. ## Pages under this topic Services ### [CRM and Patient Enquiry Management](https://saglikajansi.com.tr/en/services/crm-and-patient-enquiry-management.html) A tracking system where every enquiry lands in one record with an owner, a defined first-response time, a visible stage and a mandatory loss-reason field. Knowledge Centre ### [CRM and Patient Enquiry Guides](https://saglikajansi.com.tr/en/knowledge/crm-and-enquiry-guide.html) Record discipline, shared stage definitions and loss-reason analysis across the chain from first enquiry to confirmed appointment, before software is chosen. ### [Website and Patient Enquiry Systems](https://saglikajansi.com.tr/en/services/website-and-patient-enquiry-systems.html) Building the path where a foreign patient finds information, asks a question and receives an answer as one connected system. ### [Data, Reporting and Revenue Tracking](https://saglikajansi.com.tr/en/services/data-reporting-and-revenue-tracking.html) A measurement system with fixed shared definitions that makes the chain from first enquiry through to revenue readable in one view and decision-ready. Our Approach ### [Our Measurement and Reporting System](https://saglikajansi.com.tr/en/approach/measurement-and-reporting.html) A measurement approach where indicators mean one thing, reports trigger decisions and weak periods are explained in the same detail. ### [Patient Experience, Reputation and Referral](https://saglikajansi.com.tr/en/services/patient-experience-reputation-and-referral.html) Building reputation from the inside by mapping and improving patient touchpoints, with feedback and review handling kept inside promotion-regulation limits. ### [Medical Tourism Landing Page Design](https://saglikajansi.com.tr/en/services/landing-page-design.html) A single-purpose page built for paid traffic: promise match, patient decision order, verifiable trust evidence, form limits, speed and language. ### [Medical Tourism Landing Page Checklist](https://saglikajansi.com.tr/en/knowledge/landing-page-checklist.html) What belongs on a page receiving paid traffic and what must not: promise match, trust evidence, form limits, speed, accessibility and language checks. *Frequently asked questions* ## What institutions ask about this topic ### Which CRM should we use? No single product is recommended. Scale, budget, language support and existing infrastructure decide; in most mid-sized institutions configuring the existing tool works better than buying a new one. ### How do messaging records enter the system? Through the platform’s official business interface or an integration it approves. Bringing conversations from personal accounts into institutional records is problematic both technically and for data protection. ### How long does setup take? Typically four to eight weeks including the definition work. The determining factor is not the software but internal agreement on definitions. ### What if the team does not use the system? The tracking system will not work. That is why setup always ships with a usage rule, a daily rhythm and a simple audit indicator. ### What should the first-response time be? Decisions here are made within hours, not days. Commit publicly only to a window your shift pattern can actually cover; an unmet promise costs more than a modest one. ### Can clinical information sit in the CRM? Contact and process information can; clinical information belongs in a separate, access-controlled environment. That split is defined in writing during setup. *Next step* ## Not sure where this topic starts for you? Share your current position and we will identify which page in this topic applies to your institution first. *Other topics* ## Continue by topic --- Kanonik sayfa / Canonical page: https://saglikajansi.com.tr/en/topics/enquiry-flow-and-crm.html Site haritası / Site map: https://saglikajansi.com.tr/llms.txt