Last updated: 2026-09-17
Front desk work inside Epic answers to somebody else's build, so this page starts with what the day looks like in Epic. How much of the booking decision Epic's scheduling rules make before a caller is even greeted comes next, followed by what the receptionist still decides once those rules have run. A pooled In Basket moves ownership of a patient's question away from any one named person, and working a shared pool remotely without a request going missing sits right behind it. MyChart changes the work that reaches the desk, which gets its own treatment here. Access is the question clients ask first and read about last, so it lands in the middle, covering how a remote hire gets a login and when a start date is real. Why two health systems running the same software hand a receptionist different screens follows. Phone work sits outside Epic, which surprises people. The limits the health system keeps for itself come after that, then what to look for when you hire, and the page closes by naming where these Epic facts come from.
A medical receptionist in Epic moves between three surfaces all day. One is the scheduling grid for the departments and providers they cover. Another is the In Basket, where patient messages, portal requests and staff notes land. The third is the patient record itself, where demographics, contact preferences and coverage on file get confirmed and corrected.
Epic runs in large health systems and academic medical centers, so the front desk there is rarely one person doing everything. Work gets split by department, by clinic and by role, and a receptionist covering ophthalmology clinics may never touch a surgical schedule. A medical assistant sitting one desk over works a different queue entirely.
Five jobs account for most of a shift at a department running Epic.
Nothing on that list is unusual for a front desk. What changes in Epic is how little of it the person at the desk gets to define.
Epic scheduling decision support decides most of the booking question before the receptionist reaches it. A health system's Epic team builds visit types, sets how long each one runs, publishes provider templates by day and session, and writes the question sequences that steer a caller toward the right visit type. By the time a receptionist searches for an opening, the system has already filtered what's bookable.
That filtering carries real content. A visit type can require a referral or an order on file. Tuesday mornings on a provider template may sit reserved for post-operative follow-ups, with new patients refused in that block. Screening questions route a caller describing chest pain somewhere other than a routine slot three weeks out.
The receptionist sees the survivors. Openings that break a rule don't appear, and an override needs somebody with more access than the desk has.
Practices coming from a small-office system find this jarring. Anyone at a two-provider clinic can drop a patient wherever there's white space. Nobody does that in an Epic build, and the discipline is the point rather than a defect.
A receptionist still decides everything the rules can't see. Which of three allowed openings a working parent can genuinely reach is a human question. So is whether the caller who answered the screening questions calmly is describing something that belongs with a nurse today rather than a visit next month.
Judgment shows up in four places even on a heavily built schedule.
Tone belongs on that list too, and it's the part no build controls. A patient who waited nine minutes in a phone queue arrives at the conversation already frustrated, and the receptionist decides what the next ninety seconds sound like.
Scheduling responsibilities in an enterprise build are narrower and deeper than they are at a small practice. Fewer choices, higher stakes on each one.
A pooled In Basket changes ownership because a message sent to a pool belongs to whoever opens it rather than to a named person. Epic routes patient messages, portal requests and internal notes into shared baskets that a department covers as a group. Nobody's name sits on a message until somebody takes it.
The upside is coverage. A receptionist calls in sick and their messages aren't stranded behind a password nobody has. Four people see a patient's refill request instead of one.
The downside is the same fact read from the other side. A message everyone can see is a message everyone can assume somebody else took. Two staff reply to the same patient an hour apart with different answers, or a request sits opened and untouched because reading it felt like handling it.
Front desk ownership in this setting is a working agreement, not a system setting. Departments that run pools well write down who sweeps which pool at which hours, and they name the person who checks that nothing aged past a day.
A remote receptionist keeps a pool honest by working it in scheduled sweeps with a stated rule for what gets taken, what gets left, and what gets escalated. Discipline replaces the thing an on-site desk has for free, which is somebody glancing over and asking whether you got that one.
Six habits hold a shared queue together across a distance.
Internal chat carries more weight for a remote hire than most clients expect. A quick question a receptionist would ask across the desk becomes a message, and slow answers turn into voicemails patients receive a day later. Candidates who describe how they ran a queue rather than what buttons they pressed tend to hold up, and our guide to medical receptionist skills covers what that sounds like in an interview.
MyChart changes the mix of work reaching a receptionist rather than the total. Patients who self-schedule a follow-up, cancel online, or request a refill through the portal never generate a call. What's left on the phone is the harder average call, because self-service already absorbed the easy ones.
Three patterns show up once portal adoption climbs in a department.
Proxy access deserves a mention because it goes wrong quietly. A parent asking for access to a teenager's record, or an adult child asking for access to a parent's, runs into rules about what a proxy may see at what age. The receptionist collects the request and applies the health system's policy rather than deciding it.
Staffing plans built on call counts alone age badly here. Counting messages alongside calls gives a truer picture, and our rundown of medical receptionist tools and software maps the rest of the stack sitting around the portal.
A receptionist gets Epic access from the health system, never from a staffing company and never from Epic directly. The organization creates the account, assigns the access that matches the role, and requires its own end-user training before the login turns on. Epic's own training and certification program serves staff of organizations that run the software, so no candidate walks in holding a login they bought.
Start dates have two halves as a result. One half belongs to the staffing side, covering selection, contracts and a signed Business Associate Agreement where the professional will handle protected health information. The other half belongs to the client's identity, security and training teams, and that half sets the real date.
Four moves shorten the gap without cutting a corner.
Work that needs no login fills the wait productively. Phone scripts, department contact lists, payer basics and escalation rules all get learned first. Duties overlap heavily with the platform-neutral view in how a virtual assistant works in Epic, and the handling rules for that access sit with the US Department of Health and Human Services in the HIPAA Privacy and Security Rules.
Two Epic health systems give a receptionist different screens because most of what a user touches is local build. Department names, visit types, screening question sequences, In Basket pool names, message types and the access tiers attached to each role are decided by the organization running the system, and in many builds by the individual clinic inside it.
So a resume line reading five years in Epic describes fluency with the concepts. It doesn't describe your build. Somebody who has worked pools, templates and visit types in an academic medical center will recognize the shape of your setup within days and still needs a map of your names.
Ask for that map during onboarding and keep it in writing.
Four items cover most of the confusion in the first two weeks. Department and clinic names as they appear on screen. Which pools this role sweeps and which it leaves alone. Bookable visit types need separating from the ones that wait on a clinical decision. Who authorizes an override, by name and by backup. For the interview questions that separate build fluency from button memory, see our guide to what EHR skills to look for in a virtual assistant.
A receptionist's phone work sits in a separate telephony system the health system runs alongside Epic. Calls arrive through a contact center platform or a departmental queue, and the receptionist listens there while typing into Epic on the same screen. Some organizations connect the two so an inbound number pulls up a matching record, and plenty don't.
Queue behavior matters more to a remote receptionist than the brand on the phone contract. Honest Taskers uses Nextiva as its own phone tool, and a placement works whatever platform the client already pays for, such as an enterprise contact center suite or a cloud phone service.
Four settings decide whether remote coverage works at all. A named queue seat, so the receptionist receives calls rather than waiting for forwards. Warm transfer to a named extension for clinical handoffs. Somebody has to own the shared voicemail box. Departments need a call log they can pull without filing a ticket.
Monthly listen-backs are worth the time. What they catch is rarely a wrong answer, and more commonly the moment a patient asked something clinical and got a warm reply instead of a transfer. Whether a remote hire can reach your systems at all is the prior question, covered in our explainer on whether a virtual assistant can work in your EHR.
A medical receptionist can't make or record a clinical decision in Epic, and a well-built access tier blocks most of the attempts before judgment gets involved. Triage over the phone, advising on symptoms, ordering, refilling, signing anything clinical, and changing a provider's published template without authorization all sit outside the role.
The health system keeps more than the clinical line. It owns the build, the screening questions that encode a department's protocol, the access granted to each role, the escalation path, and the audit log that records who opened which record and when.
Honest Taskers staff do administrative and clinically adjacent work and never give clinical advice or make clinical decisions. The talent pool includes licensed nurses and physicians, which describes how the company recruits rather than what a placement does, so a nurse working your message pool works administratively under your protocols.
Published occupational descriptions draw the same boundary. The US Bureau of Labor Statistics describes the closest listed occupation, medical secretaries and administrative assistants, in its "Occupational Outlook Handbook" (Source: Bureau of Labor Statistics, 2025), where the duties are schedules, records and correspondence rather than clinical judgment. Enterprise front desk work is a narrower job than the title suggests, and our definition page on what is a medical receptionist sets the baseline worth writing against.
Look for somebody who has worked a shared queue under rules they didn't write. That habit transfers to Epic far better than familiarity with any one screen, because the enterprise version of front desk work is mostly about discipline inside a build somebody else owns.
Five questions surface that habit in an interview.
Honest Taskers can prioritize candidates who have worked in Epic, and candidates report experience with many platforms besides it. More than 200 EHR systems are in use across US healthcare, so treat any software list as the start of a conversation. Rates run $10.00 to $12.65 an hour depending on the role, candidate background, schedule and location. Professionals are recruited in the Philippines, Latin America, India and Pakistan, and they work the client's US time zone and approved schedule.
New clients may receive a two-week working trial with their first selected professional, subject to current service terms, and replacement support is unlimited. Honest Taskers reports 99.6% average monthly retention, which matters on an Epic account because the training and access investment sits in the person rather than in a handover document. Professionals are HIPAA-trained with quarterly HIPAA and data privacy training under a dedicated compliance officer, and the company describes its own security environment as SOC 2 audit ready. For the arrangements available beyond a direct hire, compare the best virtual medical receptionist companies.
Honest Taskers rates, recruiting geography, trial terms, retention figure and compliance posture come from the company's own published service terms and rate card. Epic behavior described here is limited to functions we can state with confidence, meaning the In Basket and its pools, the MyChart patient portal, visit types and provider templates on the scheduling side, and access granted by the health system. No menu path, screen name or version number appears anywhere on this page. Business associate obligations come from the US Department of Health and Human Services, and the administrative occupation description from the Bureau of Labor Statistics. Pool discipline, phone queue practice and onboarding sequence reflect general healthcare administrative operations rather than one organization's protocol. No Epic install count, market share, customer count, training duration, call volume or time-saved figure appears here, because none of those was verifiable for this page.
Training is the question that follows access, and it splits in two for an Epic desk. One half belongs to the health system, which runs its own end-user classes and controls the calendar. The other half is the role knowledge a candidate brings before any login exists, covering medical terminology, insurance basics, phone handling and privacy rules. Clients hiring for an enterprise account get more value from the second half than they expect, because it's the part that transfers between systems and the part a staffing partner can screen for. Anyone drafting that screen can borrow from our overview of medical receptionist training and certification.
Request candidates with experience in your specialty and software.
