Ask us the difficult question first.
We would rather lose a deal at the first email than at month four. Tell us what you run, what is not working, and what you are sceptical about — and we will tell you plainly what is shipped, what is roadmap, and what we do not do at all.
Four reasons people write to us
Picking the right one is not bureaucracy — it is how your message reaches someone who can actually answer it instead of forwarding it twice.
See it on your workflows
Not a generic demo tenant with fake patients in it. Bring a form you actually use and we will build it in Studio while you watch — that is the fastest way to know whether the engine bends the way we say it does.
Pick “Book a demo” belowJoin the network
A lab, pharmacy, ambulance fleet, blood bank or clinic that wants to plug into the hospitals and patients around you. Read the partner page first — it answers most of it — then come back.
Read the partner pageSomething is wrong in your account
You already run CareSewa and something is broken or confusing. Tell us the portal, the model and what you expected to happen — specifics get you a fix instead of a first round of questions.
Pick “Support” belowYou found a vulnerability
Please tell us. Choose “security disclosure” and it routes to people who can act on it rather than to a sales queue. Include steps to reproduce, give us a window to fix, and do not test against real tenants.
Read the disclosure processTwo things worth knowing
A real person reads this
Your message posts to our inbox and a person replies — no automated ticket, no drip sequence. If the send ever fails, the form hands you the same message as an email to send yourself, so nothing is lost quietly. We would rather show you that than a green tick that means nothing.
The answer might already be written down
We put real detail on these pages rather than gating it behind a form. If your question is architectural, it is probably already answered — and you will get a better conversation by arguing with what is there than by asking us to summarise it.
What happens — and what does not
Three things happen. A great many of the things you have come to expect from a B2B contact form do not.
A person reads it
Not a routing rule that scores you and files you. Someone who understands the architecture reads what you actually wrote.
You get a real answer
Including “that is roadmap, not shipped” and “no, we do not do that”. The point of talking to us is finding out, not being sold to.
We meet, if it is useful
A demo shaped around your workflows, or a technical review with your team, or nothing at all if the answer was in the reply.
What does not happen
- A five-email nurture sequence you did not ask for
- A tracking pixel scoring you as a lead
- A newsletter you were opted into by a hidden checkbox
- Your details sold, shared or enriched by a third party
- A “just circling back” email in three days
Bring the form that annoys you most
The worst possible demo is us showing you a beautiful tenant full of invented patients. It proves nothing, because we built it. Bring your own material and the demo becomes a test instead of a performance.
The single most useful thing you can do is bring a real form or register your practice actually uses — the one with the awkward field your current vendor quoted six weeks for. We will build it in Studio while you watch. Either it takes minutes, in which case you have learned something real, or it does not, in which case you have learned something more valuable still.
Bring any of these
- A form or register you actually use — paper or from your current system
- The field your vendor said would take six weeks and a change fee
- The workflow that currently lives in a spreadsheet next to the real system
- The list of who on your team should never see billing
- The integration you gave up on — an analyser, a PACS, an existing HIS
- Your hardest question about security, isolation or data ownership
You do not need a requirements document, a procurement brief, or a decision. Curiosity and one annoying form is genuinely enough.
If you are a patient, this is the wrong page
We are saying this plainly rather than letting you write a message that reaches a sales inbox. This page goes to the people who build and sell the platform. We cannot see your records, we cannot book your appointment, and we are not your provider.
It is an emergency
Contact your local emergency services. Do not use a web form.
You need care
Contact your provider directly. They hold your record, not us.
You want CareSewa
Start with CareSewa One. Create your Health ID and connect providers yourself.
You probably do not need to talk to us
If you are here to find out whether you can integrate, the answer is on a page, not behind a form.
Every model you define gets a REST API automatically — same envelope, same auth, same entitlement checks, same tenant filter, same audit logging as everything else. There is no privileged internal API with the checks turned off, which means there is nothing about an integration for us to gatekeep. Read the developer docs; write to us only when you have hit something they do not cover.
Questions the docs already answer
Can I bridge an analyser or an existing HIS?
Yes — the API accepts writes to any model you define.
What is the response shape?
One envelope, every endpoint, with named error codes.
How do I authenticate?
JWT access tokens with a short TTL, plus refresh tokens.
What are the limits?
Rate limited; pagination defaults to 20 and caps at 100.
We are not going to invent an SLA
Every contact page in this industry promises a reply within 24 hours. Most of them cannot keep it, and everyone involved knows it — which is exactly why nobody believes the number and nobody is embarrassed when it slips.
So here is what we will commit to instead, because it is true. A person reads what you send and a person replies to it. Not a queue, not an autoresponder pretending to be a queue, not a sequence. If your message is a security disclosure it goes to people who can act on it, and it is not going to sit while we decide whether it is convenient.
What we will not do is put a number here that we have not staffed to meet. If that reads as less confident than the page next door — good. It is also the only claim on it we can actually keep.
Before you write
Including what this form does and does not do.
It posts straight to our contact inbox and a real person reads it — no automated ticket number, no drip sequence. If the send ever fails (a network hiccup on either end), the form does not pretend otherwise: it hands you the same message pre-composed as a mailto: link so nothing is lost. A company asking you to trust it with medical records should not start by lying about a contact form.
Tell us what is not working
The most useful message you can send us is the one that starts with what your current system will not let you do.
Multi-country by design · tenant-isolated · every change audit-logged