The short answer
MediConcierge handles routine patient enquiries and the clinic work that follows. The patient concierge answers through the website or phone. Clinic staff work from the CRM and diary. Anything clinical goes to a person.
It is built for UK private clinics. The product is operated by RSE Labs Ltd.
Facts at a glance
- Category
- Multi-tenant clinic operations platform for UK private healthcare.
- Operator
- RSE Labs Ltd, a UK software studio owned and run by Miguel De Santos Rodrigues.
- Market
- UK private clinics. Other countries are outside the current service boundary.
- Patient channels
- Web chat is live. Voice and SMS run on MediConcierge test and sales lines.
- Clinic-side tools
- CRM and scheduling share one admin area. Insights report activity and conversion.
- Schedule model
- Bookings write to the MediConcierge diary today. Third-party PMS write-through is not built.
- Patient data at rest
- A Neon Postgres database in AWS eu-west-2, London.
- Application compute
- Vercel functions in lhr1, London. Static assets use Vercel's global edge.
- External processing
- AI replies and live phone calls use processors outside the UK application boundary.
- Certifications
- MediConcierge holds no ISO 27001 or SOC 2 certification. It claims no NHS clinical-safety standard.
- Published plans
- Starter £149/mo. Professional £299/mo. Enterprise is quoted after scoping. See the current pricing page.
Available today
- The web concierge answers routine questions and books against the MediConcierge diary.
- Voice and SMS are active on public test lines. The caller hears an AI disclosure before the conversation continues.
- Clinic staff can review leads and patients. Appointments and follow-up tasks sit in the same admin area.
- Insights show enquiry activity and no-shows. They also report conversion by clinician.
- Stripe checkout provisions a tenant with a 14-day trial. The separate demo path uses sample data and an invite code.
Outside the shipped boundary
These items are not available today. They are excluded from product claims until the code is live.
- Write-through to a clinic's third-party practice-management system or calendar.
- Automated appointment reminders or cancellation-gap filling.
- WhatsApp as a patient channel.
- Database row-level security or self-serve patient-data export and erasure.
Production clinic gates
A real patient booking must reach the clinic's working calendar or practice-management system. MediConcierge writes only to its own diary today, so that connection remains a go-live gate.
The clinical escalation rules also need sign-off against the clinic's own protocol. Simple keyword triggers do not cover every way a patient can describe an urgent symptom.
Phone deployment adds a separate data-flow review. The clinic receives the processor identity and retention position before real patient calls begin.
Source and change control
This record is maintained against the running product and its codebase. A material change updates the review date and the sitemap entry. Roadmap work stays outside the live column.
The product page explains the workflow. The security page records the current data flow and the contractual boundary.
