AbbaDox For AbbaDox employees Support Request Training

Support Request Training

A complete, click-through walkthrough of the AbbaDox support process — built to use live with a client, on a screen share or in person, to show them exactly how it works.

How to use this page: work through it top to bottom with the client, in order. The "Try it" section is a real, click-through copy of the live tool’s screens — nothing you do in it creates a ticket or sends an email. Sections marked For employees are notes for you, not the client.

Getting access

There are three ways in, depending on whether the client already uses CareFlow.

From CareFlow

Log in to AbbaDox (CareFlow), click the ? icon top right. Contact details fill in automatically.

Client Portal

Once invited, sign in directly to follow and reply to requests, or start a new one.

No CareFlow access?

Use Request access on the support guide. We verify the person against their organization first.

Who can open the ? icon in CareFlow

Only someone with the Administrator or Support role in CareFlow sees it. Their own organization’s administrator grants that role, in CareFlow under Settings → User and Role Assignment — we can’t grant it from our side.

How Client Portal access actually gets set up

The first time someone submits a request from CareFlow, the form asks them to confirm an email for Customer Portal login. Once they submit, we send an invitation to that address. From then on they can sign in directly — no need to go back through CareFlow every time, though CareFlow is still the fastest path for most clients since their details are already filled in.

Lost access or forgot a password

Use Forgot password on the sign-in screen with the same email the invitation went to. There’s no separate "request a new invite" step — resetting the password is enough once someone has an account.

More than one person at the same organization

Each person signs in with their own email. If the organization has Organization view turned on, everyone with access also sees each other’s requests, not only their own — worth mentioning to clients with more than one point of contact.

For employeesIf the client doesn’t have CareFlow access yet, that’s an administrator-side setting on their end — we can’t flip it for them. Point them to their own CareFlow admin, or to Request access on the support guide if they genuinely have no CareFlow account at all.

Try it: submit a request

This is a working copy of the real tool’s screens, step by step. Click through it together with the client — pick a real example that matches something they’ve actually needed help with, so it feels concrete rather than hypothetical.

🧪 Practice mode. Nothing you enter or submit here is sent anywhere or creates a real ticket.

What happens at each step, in detail

  1. 1
    Contact details. Name, email, phone (with an optional extension) and Client / Company. Signed-in clients get these pre-filled from their record — point out that they should still check it, since it can be out of date. Add CC email copies one more person on every update for this request.
  2. 2
    Product. CareFlow, CRM, Transcription And Dictation, Interface, or Legacy Products.
  3. 3
    Area. Shown only for CareFlow, CRM and Transcription And Dictation — Interface and Legacy Products skip straight to Topic, just like in the demo above.
  4. 4
    Topic. The specific thing the request is about. The live tool has more than 2,000 topic paths in total, each tuned to its product and area, so the client will always find a closer match than the handful shown here.
  5. 5
    Request type. What kind of request this is — a question, something not working, a billing issue, a feature idea, or an outage. This is what drives priority and routing.
  6. 6
    Details. Specific questions for that topic, with required ones first; a free-text "Anything else?" box; and, once signed in or arriving from CareFlow, file uploads and screen recordings. Fields like Patient MRN, Accession #, or Appointment ID offer + Add another for more than one value.
  7. 7
    Review & submit. A read-back of every answer. The Submit button disables itself the instant it’s clicked, so a double-click can’t create two tickets. The confirmation screen shows a reference like ABX-261027-7XWG, with buttons to copy the confirmation or submit another request.
For employeesIf the client clicks Start over partway through, their contact details stay filled in but their product/topic selections clear — it’s worth narrating that out loud the first time so it doesn’t look like a bug. A cleared attempt is logged on our side as an abandoned request, so nothing is lost from our view either.

After you submit

What happens behind the scenes, and what the client actually sees.

Within minutes

A "Ticket received" confirmation email, with the same reference shown on screen.

Automatically

The request is routed to the right team and given a priority, based on the product, topic and request type chosen.

Along the way

We follow up by email with questions or updates. We’re steadily adding more automatic status emails as the pipeline matures.

Any time

The request and its full history are visible in the Client Portal, whether or not an email ever arrives.

For employeesDon’t promise clients a specific turnaround time in general terms — it depends on priority and current load. The honest answer is: their reference number and portal access let them check anytime, and we’ll email if we need anything further.

Tracking & replying

Everything a client needs to follow up without opening a new request.

Finding a request

Sign in to the Client Portal (from CareFlow: the ? icon, then View & update your company’s requests). My view shows their own requests; Organization view, where enabled, shows their colleagues’ too. They can search by reference number or subject.

Replying — two ways, same result

Either open the request in the Client Portal and reply under the conversation, or reply to any email about that request directly — keeping the subject line intact, since the reference number in it is what routes the reply to the right place.

Closing and reopening

Once resolved, a reply saying so is enough — our team closes it on our end. If the same issue comes back, reply again rather than opening a new request; that keeps the full history in one place.

If it’s urgent

System down or major outage
Choosing this as the request type gets it prioritized immediately — and it’s the only request type available even without signing in at all. If a client mentions anything is actively down during a session, point them straight here rather than the general flow.

Troubleshooting

What to say when something looks like it’s not working, during a live session.

No confirmation email arrived+
Check Spam and Promotions for the reference (ABX-…). If it’s genuinely not there, sign in to the Client Portal — the request is visible there regardless of whether the email delivered.
Can’t sign in to the Client Portal+
Use Forgot password on the sign-in screen with the email the original invitation went to. If they’re not sure which email that was, check with their administrator or AbbaDox contact.
The ? icon isn’t showing up in CareFlow+
That means their CareFlow account doesn’t currently have the Administrator or Support role. Their own organization’s administrator assigns it under Settings → User and Role Assignment — we can’t grant it from our side.
They submitted the wrong information+
Reply to the confirmation email or the request in the portal with the correction, rather than submitting a second request for the same issue — that keeps everything in one thread.
Attachments or screen recording aren’t showing up as an option+
Those controls only appear when someone is signed in, or arriving from CareFlow. A visitor filling out the form without signing in won’t see them at all — that’s expected, not a bug.
A colleague they CC’d says they never got anything+
Double-check the CC address was typed correctly before submitting — it can’t be edited afterward on that request. Have them reply-all to loop the colleague in going forward.
They have several unrelated issues to report+
Encourage a separate request per issue rather than bundling them — each is tracked, routed and prioritized independently, so bundling usually slows things down rather than saving time.

Frequently asked questions

The deeper questions that tend to come up once a client has used the process once or twice.

GETTING ACCESS
Do you need an account to submit a request at all?+
No. Anyone can submit a request without signing in. An account (the Client Portal) is only needed to follow up on one afterward.
Can more than one person at the same organization have access?+
Yes — each with their own sign-in. Organization view, if turned on, lets everyone see each other’s requests too.
SUBMITTING A REQUEST
Can patient information go in the description box?+
Only in fields that specifically ask for it, such as Patient MRN or Accession #, and only what’s needed to describe the issue — not freely in the general notes.
What’s the file size limit on attachments?+
100 MB per file, 500 MB total per request, available once signed in or coming from CareFlow.
What if they’re not sure which product, area or topic fits?+
The closest match is fine — it doesn’t need to be exact. Routing is based on the whole combination of answers, and our team can redirect a request internally if it lands in the wrong place.
PRIVACY & SECURITY
Does submitting a request add someone to a marketing list?+
No — submitting a support request never adds anyone to a marketing or newsletter list.
Who at the client’s organization can see a given request?+
By default, only the person who submitted it, plus anyone they CC’d. With Organization view enabled, colleagues with portal access can see the organization’s requests too.
AFTER SUBMITTING
How is priority decided?+
Automatically, from the combination of product, topic and request type — an outage is treated very differently from a how-to question. If something is more urgent than it looks from the category, say so explicitly in the description.
Can they add more information after submitting?+
Yes — reply to the confirmation email, or reply inside the Client Portal. No need to start a new request for the same issue.
For AbbaDox employees only

Running a training session

A script and checklist for walking a client through this for the first time — on a call, a screen share, or in person.

Before the call

  • Know whether the client uses CareFlow — if so, access runs through CareFlow roles, not a separate sign-up.
  • Have their company name exactly as it appears in HubSpot, so you can confirm it matches what they’ll see in Client / Company.
  • Check whether anyone at the client already has Client Portal access, so you’re not walking them through an invitation they already have.
  • Have this page’s link ready to send afterward, along with the AbbaDox support guide.

Opening the conversation

Frame it as faster service, not a new hoop to jump through:

"We’ve moved to a guided request form so your questions get to the right person faster, with less back-and-forth. I’ll walk you through submitting one now, and show you where to check on it afterward — it takes about five minutes."

Walking through it live

Use the Try it section above, screen-shared if possible. Pick something the client has actually needed help with recently, so the walkthrough produces a realistic example rather than a throwaway one. Narrate each step as you go — especially + Add another and the CC option, which clients miss on their own most often.

Common questions and how to answer them

Client asksSay
"Why can’t I just email you like before?"Email still works during the transition, but the form gets your request to the right team faster because it asks the right questions up front.
"Is this going to put me on a mailing list?"No — submitting a request never adds anyone to a marketing list.
"Can my coworker see this too?"Only if you CC them, or if your organization has Organization view turned on in the portal.
"What if it’s urgent?"Choose System down or major outage as the request type — it’s prioritized automatically, and it’s the one option available even without signing in.
"How do I know you got it?"A confirmation email arrives within a few minutes, and it’s visible in the Client Portal right away.

Before ending the session

  • They submitted at least one real request (or a realistic practice one) and know their reference number.
  • They know where to find that request again — Client Portal, or their email.
  • Client Portal access is either set up, or they know exactly how to get it.
  • They know how to reply, and what to do if something is urgent.
  • You’ve sent them this page’s link and the support guide by email or chat.