gBell is software that carries patient calls through scheduling, intake, system updates, and staff handoffs for clinics and hospitals. It is a software product, not an agency or a staffing service.

Small and mid-size medical and dental practices where the front desk is understaffed, and every missed call is a patient who books somewhere else or a no-show nobody confirmed.

Is gBell HIPAA compliant, and does it sign a BAA?

gBell operates as a business associate under HIPAA and signs a Business Associate Agreement with a practice before any patient information moves. The BAA governs how protected health information is handled and takes precedence over the standard terms of service. A vendor claiming its terms of service already cover HIPAA is not describing how the law works.

Yes. The agent states at the start of every call that the caller is speaking with an automated assistant and that the call is recorded. A practice can adjust the wording and the voice but cannot remove the disclosure or move it later in the call. If a caller asks not to be recorded, the agent offers to take a message or transfer to a person. Several states, California among them, require every party to a confidential conversation to consent before it is recorded.

Does gBell use patient data to train AI models?

No. Protected health information is not used to train, fine-tune, or evaluate any AI model, and agreements with model providers prohibit them from doing so with data gBell sends. Where a provider offers zero data retention it is enabled. Where a provider retains data briefly for abuse monitoring, that retention is covered by a business associate agreement and the data is still not used for training.

What happens if a caller has an emergency?

The agent is instructed to tell a caller describing an emergency to hang up and call 911, and to flag the call to staff at the highest priority. gBell is not an emergency service, cannot dispatch help, and must not be relied on as a triage mechanism. A practice remains responsible for an emergency plan that does not depend on the service being available or correct.

What happens when a call needs a human?

The call escalates to staff, who receive the transcript and a patient summary before they pick up rather than after. Practices configure when, how, and to whom calls escalate.

Can patients book without calling?

Yes. gBell provides an embeddable self-scheduling widget a practice can place on its own website, and patients who booked by phone can reschedule or cancel through a link sent to them.

How does gBell protect patient information in emails and text messages?

Patient-identifying detail is not placed in email or SMS message bodies. Those messages carry a link, and the patient verifies with a one-time passcode before anything is shown, so a forwarded message or an unlocked phone does not expose someone’s appointment.

Does gBell verify insurance?

Yes. gBell sends a 270 eligibility request, reads the payer’s 271 response, explains the returned coverage and benefits, and routes missing detail to the next action.

Does gBell post EOBs and ERAs?

Yes. gBell Payment Posting matches an EOB or ERA to the right claim lines, applies approved posting rules, and reconciles the remittance to its check or EFT before clean work reaches the practice system.

Does gBell include a clinical scribe?

Yes. gBell Scribe turns post-visit clinician dictation into a case-specific draft with exact source quotes, uncertainty review, clinician approval, and export.

Does a practice keep its own phone number?

Yes. Practices keep their own number, their own calendar, and their own tone. The agent answers in the practice’s name, not the vendor’s.

Insurance & eligibility · August 2026 · 7 min read

What a 271 eligibility response tells your front desk

When your system checks a patient's insurance, what comes back is a 271, the payer's standardized answer to the 270 inquiry your side sent. Billing software usually renders it as a wall of benefit segments, which is why plenty of front desks glance at "Active" and move on. That glance leaves most of the response's value, and several of its warnings, unread.

Here's each field that matters, what it means in plain terms, and the specific thing a front desk should do with it before the patient walks in.

The fields, one by one

Coverage: active or terminatedDoes this person have insurance right now. "Terminated" means the policy ended, usually a job change or a lapsed plan, and the patient frequently doesn’t know. This single field is most of the check’s value, because a visit delivered on dead coverage becomes either an awkward bill to the patient or a write-off.

Plan name and typeWhich product inside the insurer this person holds: an Aetna Choice PPO is a different animal from an Aetna HMO. The plan determines everything below it, and it confirms the check matched the right person on the right policy.

CopayThe fixed amount the patient owes at the visit, say $25 for an office visit. This is the collect-at-check-in number, and the number worth telling the patient before they arrive so nobody is surprised at the desk.

Deductible remainingHow much the patient must still pay out of pocket this year before the plan starts paying. "$500 remaining of $1,500" means full price until they’ve spent $500 more. A patient with an unmet deductible may owe the entire visit fee rather than the copay, which is exactly the kind of thing to know before the visit, not after.

Referral requiredSome plans, mostly HMOs, refuse specialist claims without a referral from the primary doctor on file. Active coverage plus a missing referral still equals a denial. For specialty practices this flag alone justifies running the check at booking, while there’s still time to chase the paperwork.

Service-level detailRicher 271s carry benefit detail per service type: telehealth coverage, visit limits, out-of-network terms. Quality varies by payer. Treat detail beyond the core fields as helpful when present rather than guaranteed.

What to do with each answer

Terminated coverage: call the patient before the visit. Most have a new card from a new employer and the fix is two minutes; the rest can decide about self-pay rates with warning instead of at the desk.

Copay known: say it out loud at booking or in the reminder. "Your copay Thursday is $25" collects itself; an uncommunicated copay becomes a statement, a stamp, and sometimes a collection.

Large deductible remaining: flag the account so check-in collects the visit fee, not the copay, and nobody has to have that conversation unprepared.

Referral required: verify one is on file before the appointment. If not, the patient's primary care office needs a nudge now, because after the visit is too late.

The timing point hiding in all four: every one of these actions is cheap before the visit and expensive after it. That's the argument for checking at booking rather than the night before, and it's why we wired eligibility into the booking call itself in gBell's design: the person who can fix a coverage problem, the patient holding their new card, is literally on the phone at that moment.

What the 271 will not tell you

It won't adjudicate a claim in advance: the payer's answer describes benefits, and payment still depends on the claim itself. It isn't a prior authorization, which is a separate per-service approval process for costly procedures. And it's a snapshot, true at the moment it was run; coverage that was active at booking can lapse by the visit, which is why high-value appointments deserve a re-check closer to the date.

One more honest caveat: payers differ in how much detail they return, and a minority of responses come back ambiguous, a mismatch on the member ID, a plan the payer reports oddly. The measure of a good verification workflow isn't that this never happens, it's that ambiguity routes to a human quickly instead of silently passing as verified.

Common questions

What are a 270 and a 271, exactly?

The standardized electronic messages HIPAA mandates for eligibility. The 270 is the question your side sends: this clinic (identified by its NPI) asking about this member (ID and date of birth). The 271 is the payer's answer. Every clearinghouse and EHR eligibility feature is a wrapper around this pair.

How current is the information in a 271?

It reflects the payer's enrollment records at the moment of the inquiry, which is as current as anything gets. The stale-data risk is on your side: a check run last month says nothing about today. Cheap checks are what make re-checking normal.

Why did the check say active and the claim still got denied?

Because eligibility and claim adjudication are different steps. The usual culprits: a referral or authorization requirement the 271 flagged but nobody actioned, a deductible that made the "denial" actually patient responsibility, or a coding issue on the claim itself. The 271 rules out the biggest failure, dead coverage; it can't rule out all of them.

gBell

gBell is the AI operations layer for medical practices. Calls answered and booked, reminders run, after-hours covered, and the intake and insurance work behind the phone carried. It's the product these notes come from.

See how it works

Sources