Care-Team Tools Beyond the Portal

Who this is for: care-team/support staff, admins, new hires.

The idea

Staff don’t work only inside the care portal’s own pages. Several outside tools are wired into the platform so staff activity and patient conversations stay in sync across systems.

Support/helpdesk sync

Every new in-app message thread (see Messaging & notifications) is mirrored out to an external helpdesk tool in real time. This means support staff working inside that outside helpdesk tool see the same conversation as staff working inside the care portal, without anyone manually copying messages over. There’s also a direct lookup by patient email into that external helpdesk system, for staff who need a patient’s helpdesk history without leaving the care portal.

Live chat ticket creation

A separate live-chat/support-widget tool can have tickets created for it directly from the care portal’s automated systems (for example, from the automated phone outreach assistant escalating something a caller needs human follow-up on).

Marketing/CRM sync

Patient contact details and marketing tags can be pushed to an external CRM system — for example, tagging a patient’s CRM record, or triggering the CRM’s “new patient” automation flow, or bulk-syncing many patients at once. This is separate from operational messaging and mainly serves the sales/marketing team’s own outreach.

The browser extension

Care-team/print-station staff also use a separate browser extension (a distinct codebase from the care portal itself) that talks to the care portal through two dedicated API endpoints:

One endpoint lets a staff member route a case into the right print-station queue (stamped-needed, remail, or hand-sign — see Printing & fulfillment) directly from the extension’s dropdown, without opening the full care portal.
A second endpoint lets the extension pull a case’s key details for display inline wherever the staff member is working.

Both endpoints are authenticated with their own dedicated API key, separate from a staff member’s normal login session.

Open questions

The browser extension’s own UI and full feature set live in a separate repository not covered by this review — only the care portal’s side of the contract (the two API endpoints) was confirmed here.
The exact triggers for automatically creating a live-chat ticket (versus a staff member creating one manually) were not fully traced.

Where this comes from

parkingmd-care-portal/src/app/api/zendesk/route.ts, .../zendesk/[email]/route.ts
parkingmd-care-portal/src/lib/webhooks/ (support-system mirroring of new thread messages)
parkingmd-care-portal/src/app/api/crisp/create-ticket/route.ts
parkingmd-care-portal/src/app/api/ghl/add-contact-tag/route.ts, .../ghl/bulk-operations/route.ts, .../ghl/trigger-new-patient-flow/route.ts
parkingmd-care-portal/src/lib/ghl-service/action.ts
parkingmd-care-portal/src/app/api/extension/packet-queue/route.ts, .../extension/task-details/route.ts
parkingmd-care-portal/src/lib/tasks/packet.ts