A good inbox still creates work
Spruce is one of the obvious tools for DPC.
Patients text. Patients call. Patients ask quick questions that are not actually quick. Spruce gives clinics a clean place for that communication instead of trying to run modern care through voicemail and portal messages from 2009.
That part is good.
The problem is what happens after the message arrives.
A patient asks about labs. Someone needs the chart. A patient asks for a refill. Someone needs meds, allergies, pharmacy, and maybe a provider decision. A patient asks about a bill. Someone needs Hint. A patient sends a symptom update. Someone needs to decide if this is a message, a call, a visit, or a task for later.
Spruce handles the message.
Your team still has to close the loop.
The short version
- Spruce is good at patient communication, calls, texts, inbox routing, and keeping patient conversations in one place.
- Tabflows is better when those messages create work in the EHR, labs, billing, refills, scheduling, tasks, or staff handoffs.
- Choose Spruce if your main problem is helping patients reach the clinic and organizing communication.
- Choose Tabflows if your clinic already has patient messages coming in, but the follow-up work needs owners, due dates, patient context, and visibility across the team.
- The real distinction is that Spruce helps patients reach you. Tabflows helps your team finish what those messages start.
The inbox is not the workflow
Patient messaging feels like the center of the day because so much work enters there.
But the work rarely stays there.
It moves into:
- the EHR
- lab portals
- refill workflows
- billing tools
- staff handoffs
- provider decisions
- follow-up tasks
- morning huddle lists
That is why inbox-only workflows get messy. The inbox is great at showing messages. It is not always great at showing what the clinic owes the patient next.
And in DPC, the next step is the product.
The Spruce stack most DPC clinics actually run
Spruce usually sits in the middle of a stack, not alone.
| Patient asks | Tool the team needs next | What can fall through |
|---|---|---|
| "Can you explain my labs?" | Quest, Labcorp, EHR | Review, interpretation, callback, repeat order |
| "Can I get a refill?" | EHR, pharmacy, med list | Provider review, documentation, follow-up timing |
| "Did my payment go through?" | Hint Core | Billing context, front-desk ownership, patient response |
| "Should I come in?" | Chart, schedule, provider decision | Triage, booking, care plan, staff handoff |
| "Can someone check on this next week?" | Task layer | Owner, due date, visibility, follow-through |
None of this means Spruce is weak.
It means Spruce is where work enters. Your clinic still needs somewhere for that work to go.
The hidden cost of a busy DPC inbox
A busy inbox makes the team feel productive because everyone is responding.
But response speed is not the same as closure.
The clinic can answer messages quickly and still lose work if:
- the follow-up is never assigned
- the provider decision is buried in a thread
- the chart context is not visible when replying
- a lab result is discussed but not tracked
- the front desk thinks the provider owns it
- the provider thinks staff owns it
- the patient gets a reply but no next step
That is how good communication software turns into a queue of unresolved clinical work.
Where Tabflows fits
Tabflows does not replace Spruce.
Spruce should stay the communication hub. Tabflows makes sure the work created by communication does not stay trapped inside the inbox.
With Tabflows, Spruce can sit beside Elation, Hint Core, lab portals, refill workflows, and the team's task layer.
So when a message needs chart review, the chart is there. When it creates a follow-up, the task has an owner. When it touches billing, the membership context is close. When the patient needs a callback next week, the work shows up next week instead of relying on someone to remember.
Messages are the start.
Closure is the job.
If you use Spruce, ask this instead
Do not ask, "Is our inbox organized?"
Ask:
- Which messages created follow-up work today?
- Who owns each next step?
- Which messages need provider review?
- Which messages are waiting on labs, billing, or chart context?
- Which replies need a task after the reply is sent?
- Can the team see unresolved patient work without rereading the inbox?
If those answers are fuzzy, the inbox is not the thing to replace.
The workflow around the inbox is.
For the broader category, read The DPC workflow layer: why the work lives between the apps and our guide to DPC workflow software. If the problem is follow-through, start with DPC task management software. If your stack also includes Elation, read why Elation was never meant to be the whole clinic workflow.
FAQ
Does Tabflows replace Spruce?
No. Spruce stays the patient communication platform. Tabflows helps the clinic connect Spruce messages with the EHR, labs, billing, tasks, and follow-up work around them.
Why do DPC clinics using Spruce still need workflow software?
Because messages often create work outside the inbox: chart review, lab follow-up, refills, scheduling, billing questions, and staff tasks. Workflow software makes sure those next steps have context, owners, and visibility.
Can Tabflows connect Spruce with Elation and Hint?
Yes. Tabflows is built for clinics using tools like Spruce, Elation, Hint Core, Hint Clinical, Cerbo, Quest, Labcorp, and other DPC systems. It helps keep patient context and follow-up work organized across the stack.
What is the risk of managing DPC follow-ups only from an inbox?
Inbox-only workflows make it easy for clinical work to get buried under new messages. A patient message may need a chart check, lab review, refill task, or provider decision. If that next step stays in the inbox, ownership and follow-through can get fuzzy.
Try Tabflows free and turn patient messages into closed loops.