Asaanbil is an AI front-desk platform for small independent specialty practices. Scheduling, prior auth, appeals, staff coordination, patient communication — one platform, built for a practice that runs on 1–2 admin staff, not a hospital department.
A front-desk coordinator answers calls, books appointments, chases prior authorizations, coordinates staff, manages patient records, and handles denials — all before lunch. Each of those tasks used to require either expensive specialist staff or hours of manual effort.
That's not how it should work. A physician's practice shouldn't need a PA coordinator, a scheduling specialist, a billing coordinator, and a receptionist just to keep the lights on. Most independent practices can't afford that stack — and most are paying for it in overtime, burnout, and revenue that never got collected.
We built Asaanbil because the problem isn't clinical. It's operational. And operational problems are solvable.
Asaanbil replaces the fragmented, expensive admin stack with a single AI-powered platform any practice can actually use — without an IT project, without EHR migration, without hiring a specialist for every function.
Handles incoming calls automatically — routing, answering common questions, booking follow-ups — so no call goes unanswered and no staff member spends their morning on hold.
Patients book directly on your public profile. Real open slots, no account required. Telehealth room created automatically when applicable.
Both the doctor and the patient can generate a prior authorization letter — structured, payer-criteria-cited, downloadable as PDF. A human reviews and approves before anything goes out.
Generate an appeal directly from a denial notice. Same structured, criteria-cited approach. No starting from scratch, no guessing what the reviewer wants to see.
Assign roles, duties, and tasks directly from the platform. PA, appeals, patient intake — every staff member knows their queue. No Slack, no sticky notes, no dropped handoffs.
One screen showing everything happening in the practice: PA requests, patient count, appeals status, today's schedule, staff roster, and a live "needs attention" list. Nothing falls through the cracks.
When a patient grants access, the doctor sees their full details and medical history directly in the platform. No faxing. No phone calls chasing records.
Patients own and control their own medical records, personal information, and appointments. They're not passive recipients — they're participants with their own dashboard and their own agency over their care.
A searchable public directory. Patients find doctors by specialty, insurance accepted, language, and availability. Practices get a patient-acquisition surface without building one separately.
Doctors, staff, and admins can publish medical insights and practice updates — keeping patients informed and building the practice's visible expertise over time.
Doctor-to-staff messaging inside the same dashboard everything else runs on. No WhatsApp groups, no messages that get missed because they were sent through a personal number.
Assign a task to a specific person with a due date, mark it team-wide or personal, and see who's actually completed it — a real to-do system, not a sticky note on someone's monitor.
I'm Ruman Shahid. I built Asaanbil because I kept seeing the same pattern: a physician or their staff knew exactly why a procedure was medically necessary. The clinical judgment was never in question. What ate the time was translating that judgment into the specific structure, language, and citation a payer reviewer expects — or tracking down a record that should have been a click away, or answering a call that should have been handled automatically.
That's not clinical work. It's an operational problem. And operational problems don't fix themselves — they just compound until someone builds the tool that should have existed already.
I'm not a doctor. I'm a builder who went deep on the problem and built for the practices nobody else was building for: solo-to-small-group specialty practices, 1–10 physicians, where the same 1–2 people handle everything from intake to appeals. They don't need a hospital system's software. They need something built for their actual size, their actual staff, their actual payer mix — and priced accordingly.
That's Asaanbil. Starting narrow, on purpose.
Not spend 13 hours a week on prior authorization forms. Not answer calls that an AI could handle. Not manage five different tools just to coordinate a two-person staff. The admin layer should run itself, quietly, so the clinical layer can do its actual job.
Not depend on a practice to fax their records to the next doctor. Not sit outside the prior authorization process while decisions are made about their own treatment. A patient who has access to their own records, their own appointment history, and their own ability to generate an appeal letter is a patient who's actually in control of their care.
We'd rather tell a practice honestly when a payer has no published criteria for a case than pretend we found a citation that isn't there. Every letter Asaanbil drafts is reviewed and approved by a human before it goes out. We draft — your clinic decides.
Every action on a PA request, letter, patient record, or claim denial is logged with user, action, and timestamp. A practice's data is isolated from every other practice at the database layer — by policy, not convention. Each practice sets its own data retention window. A Business Associate Agreement is required and enforced at onboarding.