--- title: "Website and Patient Enquiry Systems | Sağlık Ajansı" description: "Building the path where a foreign patient finds information, asks a question and receives an answer as one connected system." canonical: https://saglikajansi.com.tr/en/services/website-and-patient-enquiry-systems.html language: en last_modified: 2026-08-22 alternates: - en: https://saglikajansi.com.tr/en/services/website-and-patient-enquiry-systems.html - tr: https://saglikajansi.com.tr/hizmetler/web-sitesi-ve-hasta-basvuru-sistemleri.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." --- *Medical-tourism agency service* # Website and Patient Enquiry Systems A website and an enquiry system are not two separate projects. The page where a patient finds information, the form where they ask and the channel where they receive an answer form one flow. Break any link and all the visibility work turns into unanswered enquiries. The authorisation rules require institutions to have a website where foreign patients can easily reach information. Most institutions meet this by opening an English page; the real test is not whether the page exists but whether the patient gets an answer. > Website and patient enquiry flow designed as a single connected system ## Structure the site around the patient's question Institutional sites are usually organised around the org chart: departments, services, corporate. Patients arrive with questions: can this treatment be applied to me, how long does it take, how many days must I stay, who will perform it, what does it cost, what happens afterwards. Building the information architecture around those questions improves findability substantially without increasing page count. Every treatment page sits on the same skeleton, so once a patient reads one they know where to look in the next. Sections a treatment page must carry - A short, direct definition paragraph - Who it suits and who it does not - The steps of the process and an estimated duration for each - Length of stay in Türkiye, companion and accommodation information - Post-procedure follow-up and the route to reach someone - Frequently asked questions specific to that treatment ## The enquiry form is a contract, not a data-collection tool Submitting a form creates an expectation. The cheapest way to manage it is to state on the confirmation screen what happens next: "Your request has reached the health-tourism unit; you will hear from us within 24 hours on working days." The form itself must be honest too. Fifteen fields depress completion; three fields produce enquiries the team cannot assess. The right balance is the minimum information needed for the team to give a first answer. ## Multiple channels must land in one record A patient writes to the form, then messages on WhatsApp, then asks on Instagram the next day. Internally those reach three different people and the patient explains the same thing three times. This is the most common reason enquiries are lost. The technical fix is not complex: every channel lands in the same record and every record has an owner. The hard part is not technology but team discipline, so the setup is always delivered with a usage rule. Measurement note Enquiry count alone means little. Measurement done before the qualified-enquiry definition is fixed shows volume, not improvement. ### Question-led structure Pages follow the patient's decision questions, not the org chart. ### An honest form Minimum fields, clear expectations and a specific post-submission message. ### One record Form, WhatsApp and phone land together; every record gets an owner. *Working sequence* ## How we move, step by step 1. 01**Information architecture**A map of treatment, market and institutional pages built from patient questions. 2. 02**Template design**Shared, easy-to-populate templates for treatment and market pages. 3. 03**Enquiry flow**Form fields, validation, consent texts and the confirmation screen designed. 4. 04**Channel consolidation**WhatsApp, phone and form records brought into one place. 5. 05**Team hand-over**First-response rule, ownership and follow-up rhythm transferred in writing. *Official sources* ## Primary sources for Website and Patient Enquiry Systems These links are general orientation; review the current text with your legal team. *Frequently asked questions* ## What institutions ask most about this ### Do we have to rebuild our site from scratch? Usually not. In most cases fixing information architecture and the enquiry flow is enough. A rebuild only comes up when the technical platform cannot carry the target languages or performance requirements. ### How many languages does the site need? Only the languages of the target market. Opening a page in a language you cannot answer produces unanswered enquiries and reputational damage. ### How many fields should the form have? The minimum needed for a first response. Typically name, contact, treatment interest and short context; clinical information is not requested on the form. ### Can we ask for health information on the form? We advise against it. Health data is special-category data and a marketing form is not an appropriate environment. Clinical information should be collected through a secure, notified channel. ### Does site speed affect enquiries? Directly. In markets with slower mobile connections, heavy pages measurably increase the share of visitors who leave before seeing the form. ### How long does the project take? Information architecture and enquiry-flow work typically four to eight weeks. A full rebuild takes longer depending on page and language count. *Next step* ## Let us connect visibility to an answer Share your current site and enquiry process and we will find the broken link together. *Related topics* ## Continue with the next relevant topic --- Kanonik sayfa / Canonical page: https://saglikajansi.com.tr/en/services/website-and-patient-enquiry-systems.html Site haritası / Site map: https://saglikajansi.com.tr/llms.txt