Help center
Operate payer work safely
A concise guide to the focused ApprovalHelp workflow. Signed-in users keep the application sidebar while reading this page.
Start with Today
Today is the operating queue. It prioritizes work that needs review, a verified deadline action, missing evidence, a payer follow-up, or an outcome update. Opening an item takes you to the same case record used at every payer stage.
Use one case across the payer journey
A case can move from eligibility and prior authorization into denial, appeal, external review, and outcome without re-keying its identity. Facts, evidence, document versions, payer policy, tasks, deadlines, communications, access grants, billing references, and events stay attached.
Verify deadlines and payer rules
A date is either verified, a candidate, uncertain, or absent. Review its source before acting. ApprovalHelp does not invent a generic filing window when the payer, plan, governing process, or source is unknown.
Build a reviewable evidence packet
Confirm extracted facts against the source. Keep each evidence item and document version traceable. A clinician or other qualified reviewer remains responsible for medical necessity, accuracy, signatures, submission channel, and final action.
Assign the right role
Owners and admins manage the workspace. Prescribers review and sign clinical work. Coordinators move operational work forward. Viewers are read-only. Capabilities are enforced at the action boundary; a hidden button is not the security control.
Handle patient sharing by consent
A DenialHelp case is visible to a practice only after an explicit access grant. The patient can revoke current access. Historical access and case events remain auditable; revocation does not rewrite the past.
Protect your account
Use an individual account and complete mandatory MFA. Security settings show enrolled passkeys or TOTP, recovery-code status, and active devices. Sensitive changes require recent authentication. Revoke an unfamiliar session immediately and contact support without sending PHI in the first message.
Read integration status literally
Available, private pilot, sandbox-validated, in certification, planned, and unsupported are distinct states. Review the Integration register before designing a workflow around a connection.
Still blocked?
Use the monitored support channel. Include a case ID and a redacted description—not patient information—in the first message.