Practical guide
Building a repeatable claim follow-up process
Define the problem before choosing the next action
An unresolved claim can require several different kinds of work. The practice may need to supply missing information, review documentation, confirm an account requirement or understand a payer response. Start with the source record and the current stage of the claim. A broad label such as “billing problem” is too vague to tell the next person what to do and can lead to repeated work that does not address the actual issue.
This guide describes an operating process for reviewing and coordinating follow-up. It does not select codes, interpret a patient’s coverage or prescribe an appeal strategy. Those decisions require the actual documentation, current payer requirements and the appropriate qualified reviewer. The practical aim is to make unresolved work visible, give it an owner and preserve enough context for the next action to be understandable.
Jelo’s insurance and payer services are handled by Taiga. The AI biller service is available in beta at 10% of insurance reimbursement, separately from the platform subscription. A practice using that service still needs a clear process for supplying requested information and reviewing unresolved questions. The steps below help organize that coordination without assuming that every payer or transaction has the same requirements.
Choose a worklist scope that people can explain
Before reviewing a queue, define which items belong in it. Identify the locations, date range, relevant statuses and type of follow-up the team intends to examine. If two employees use different filters, they can report different totals without either total necessarily being wrong. The scope should be written down so the same review can be repeated and another person can understand what was included.
Jelo’s claims worklists distinguish drafts, in-progress, closed and cancelled work. Those categories help organize the record, but a category alone does not explain every unresolved item. Staff should review the relevant status, balance and source response before deciding the next action. A closed-looking record should not be used as proof of a bank deposit, and an in-progress record should not automatically be described as a denied claim.
Use a small, defined queue to establish the process before broadening it. For example, the practice might review a fictional set of items needing a response from its own team. The key is to choose a scope with a clear action owner. A list that combines unrelated stages without explanation can make it difficult to distinguish work the practice can complete from work awaiting another party.
Preserve the source response and its context
The source response tells the reviewer what was actually reported. Keep the relevant payer or service response associated with the item in the approved workflow, together with the date and any reference needed to locate it. Avoid replacing a specific response with an informal summary that loses the reason for the follow-up. A short note is useful when it points back to the evidence rather than becoming the only record of it.
CMS distinguishes a remittance explanation from the movement of funds and describes adjustments as part of the payment information. That distinction is useful when reviewing a record: the amount billed, amount paid, adjustment and remaining responsibility should not be collapsed into one unlabeled figure. For the official explanation, consult the CMS remittance reference.
When something is unclear, record the question precisely. “Need clarification of the response associated with this item” is more useful when it names the source and the missing information. Keep patient and claim details within the practice’s approved systems. A public spreadsheet or marketing demonstration should use fictional examples and aggregate counts, not a copy of actual patient billing information.
Assign one next action and a responsible person
A useful follow-up record answers three questions: what happens next, who is responsible and when the item will be reviewed again. The next action should be specific enough for the owner to perform. “Work denial” is broad; “obtain the missing information requested in the recorded response and return it through the approved service workflow” describes a concrete action without inventing the content of the request.
The person responsible may be in the practice or part of the billing service, depending on the agreed scope. The practice should know when it owes a response and when it is waiting on another party. A handoff is incomplete if the item moves between teams without an acknowledged next action. Document the change in responsibility so another employee can understand why the item is waiting.
Choose review dates based on the actual circumstances and applicable requirements. This guide does not supply a universal filing or appeal deadline. Record any relevant deadline from the appropriate payer source and verify it with the qualified billing reviewer. A calendar reminder can help organize work, but it cannot correct a deadline that was entered from an unsupported assumption.
Group causes without turning them into coding decisions
Grouping unresolved items can reveal where the practice’s process needs attention. Useful operational groups might include missing practice information, a question requiring clinical review, an enrollment dependency or an unresolved payment reconciliation. The categories should describe the work to investigate. They should not be used to infer a diagnosis, choose a code or decide that the patient owes a particular amount.
Start with categories your team can apply consistently. If two reviewers repeatedly classify the same example differently, refine the definition before relying on a category report. Keep an “unresolved classification” option in the practice’s operating record rather than forcing every item into a convenient bucket. An uncertain classification is a prompt to review the source, not evidence that the item has been understood.
Review recurring causes with the relevant role. An intake-information problem may need a front-desk process change. A documentation question belongs with the clinical team. An account dependency may need the person managing enrollment. This prevents the billing queue from becoming a place where every problem is treated as the same task, regardless of the person who can actually resolve it.
Review the encounter before changing billing information
The clinical record and the billing record should describe the actual encounter. When a follow-up requires a documentation or code review, involve the appropriate clinician and billing professional. Do not change a code solely to pursue a preferred payment result. A software suggestion, a website example or a familiar pattern in another claim does not establish that the change is appropriate for this encounter.
Prepare the review by identifying the question and the relevant record. The reviewer should be able to see what information was requested and which documentation is being considered. Avoid asking a clinician to approve an unexplained change without the context needed to evaluate it. A clear question can make the review more efficient while preserving the clinician’s responsibility for the record.
Keep the outcome understandable. If the reviewer confirms a correction, record the supported next step through the practice’s approved process. If the record does not support the proposed action, preserve that conclusion and determine the next appropriate path. This guide’s purpose is coordination and traceability; it does not provide a clinical or coding answer for a specific denied service.
Coordinate with the service using complete questions
When insurance and payer work is handled through Taiga, the practice should agree on how requests and responses are exchanged. Identify the contact or workflow for an unresolved item and the information needed to locate it. A useful question names the stage, source response and specific uncertainty. A general message that a claim is “not working” can require additional exchanges before anyone knows what needs investigation.
Keep a record of what the practice supplied and what remains outstanding. If the service asks for information, assign the request to someone with the authority and knowledge to provide it. If the question requires a clinician’s review, do not route it only through administrative staff and assume the review occurred. The practice’s internal handoff should be as clear as the handoff to the service.
Review the agreed service scope before assuming a task is automated or included. Jelo confirms that insurance and payer services are handled by Taiga and that the AI biller is available in beta. Exact payer coverage, transaction requirements and account prerequisites still need confirmation. A clear scope discussion prevents a workflow gap from being hidden behind a general product label.
Use corrections and appeals only through the appropriate process
Different source responses can require different next steps. The correct route may involve supplying information, reviewing an account requirement, correcting an eligible error or pursuing a formal review process. The practice should use the actual response and current payer requirements to determine the route with the appropriate reviewer. This guide deliberately does not provide a universal appeal letter or claim that one response works for every situation.
Before taking an action, confirm what has already been attempted. Repeating a submission without understanding the previous result can make the record harder to interpret. Preserve the reference to the earlier action and identify what has changed. If the next step is uncertain, escalate the question rather than treating another attempt as evidence of progress.
After the action, record the observed result and the next review point. An action being sent is not the same as a payer accepting it or paying the claim. The useful operational record distinguishes those events. It should allow another reviewer to understand the current position without reconstructing the entire history from scattered messages or memory.
Reconcile payment, adjustment and remaining balance
Jelo’s payer-remittance interface records payment and contractual adjustment separately, with a reference and remaining payer balance. This distinction matters because an adjustment is not money received. Staff should enter or review amounts against the actual remittance and inspect any suggested amount before relying on it. The screenshot on the billing page uses fictional figures to show the interface without posting a real remittance.
Consider a fictional record with a billed amount, a payment and an adjustment. The reviewer needs to understand each component and the remaining responsibility under the actual source information. This guide does not assign numerical patient responsibility or explain a specific plan’s benefits. Its operating recommendation is to keep the components labeled and matched to the source before closing the reconciliation task.
Also distinguish reconciliation in the billing record from reconciliation at the bank. A remittance can explain a payment, while the deposit or transfer provides evidence of funds movement. The appropriate person should compare the relevant records through the practice’s process. Closing a worklist item should reflect the defined completion criterion, not simply the presence of a number in a payment field.
Define completion before measuring the queue
A completed follow-up is not necessarily a paid claim. Decide what your operating measure is intended to count. For example, the practice may measure whether the next action assigned to its team was completed by an agreed checkpoint. That is a useful process measure, but it should not be labeled a reimbursement rate, denial overturn rate or collection result.
Define the eligible cohort and completed event in writing. If the denominator includes twenty items assigned to the practice and fifteen have the defined action completed, the completion rate is 75%. This is a fictional arithmetic example. It says nothing about whether the payer later pays all fifteen claims. Keep the underlying counts and the completion definition next to the percentage so the result remains interpretable.
The practice operations worksheet uses completed divided by eligible and marks a zero denominator as not applicable. It rejects a completed count greater than the eligible count. Use aggregate counts without patient details. Repeat the same definition in a later period if you want a meaningful comparison, and explain any change in scope rather than comparing unlike queues.
Review age and workload without inventing benchmarks
The age of an unresolved item can help the team decide where to investigate, but the meaning depends on the stage and applicable requirements. An item waiting for a practice response differs from an item awaiting an outside response after the required action was completed. Record why it is waiting and who owns the next step. A single age figure cannot explain those differences on its own.
Choose a review order appropriate to the actual obligations and the practice’s operating needs. Give relevant deadlines and missing responsibilities attention before using a convenient sorting rule as a substitute for judgment. This guide does not prescribe a universal number of days at which a claim becomes problematic. Use the actual source requirements and the team’s agreed process.
When discussing workload, show counts as well as percentages. A reviewer handling ten straightforward requests has a different workload from someone coordinating ten complex documentation questions. If the team wants to compare periods, record changes in volume, payer mix, staffing and case complexity where relevant. That context helps avoid attributing every difference to the software or service.
Turn repeated issues into a specific process improvement
A recurring issue is an opportunity to examine the earlier handoff. If the same information is frequently missing, investigate where it should have been collected and who should have reviewed it. If staff repeatedly misunderstand a status, improve the definition and training. If an outside dependency is unresolved, keep it with the person who can address that dependency rather than repeatedly assigning it to the same administrative queue.
Choose one change and describe the expected observation. For example, the practice might revise a handoff checklist so the requested source reference accompanies every service question. The expected result is fewer incomplete handoffs, not a guaranteed increase in reimbursement. Record the before-and-after definition and review actual examples to see whether the change solved the intended problem.
Avoid changing several unrelated processes at once when you want to understand the result. If the queue definition, staffing and workflow all change, a later percentage may be difficult to interpret. That does not make the changes wrong; it means the measurement needs context. A useful operating review describes what changed and what can reasonably be concluded from the available evidence.
Prepare a repeatable weekly review
A short review can follow a consistent agenda: confirm the queue scope, inspect items that need a practice response, identify unowned work, review unresolved reconciliation and discuss one recurring cause. The practice chooses the frequency and participants. The value comes from leaving with specific actions, not from adding another meeting or a large report that nobody uses.
Invite the roles needed for the questions on the agenda. An administrative coordination issue may be resolved by the manager, while a documentation question may need a clinician. Keep patient information within the approved environment and use aggregate summaries when a broader group does not need individual details. A review should help the right person act without distributing more information than the task requires.
End with an action record that names the owner, next step and review date. At the next meeting, check the observed result rather than only whether someone sent a message. This creates a continuous operating loop: identify, act, inspect and learn. It also gives a new staff member a clearer way to understand the workflow than an undocumented collection of personal reminders.
What to ask during a Jelo billing demonstration
Bring a fictional or de-identified example that includes an unresolved step, not only a normal completed claim. Ask how the record is found, which status and source response are visible, how a practice question is coordinated with Taiga and how payment is distinguished from adjustment. Confirm the actual payer list and enrollment requirements that matter to your practice.
Review the commercial terms alongside the workflow. The platform is $300 per month per location or $3,000 per year per location. The AI biller service costs 10% of insurance reimbursement; no beta usage caps does not mean the service fee disappears. Patient-payment processing through Stripe is another separate cost. Keep these lines distinct when comparing a service quote with a software-only price.
Joel or Loreli leads demo calls. Leave the session with demonstrated steps, unresolved requirements and named next actions. Use the downloadable checklist to organize the process, and keep clinical and coding decisions with qualified reviewers. A useful billing workflow gives the team a reliable way to understand and advance the work it is responsible for, while preserving the evidence needed for each decision.