Telehealth support workflows
Take the chasing
out of support.
Summer investigates the records behind a customer’s question and helps your team carry the next step through. These are the workflows to start with, the sources they need and the results to check.
Find out why an order is late
“I paid last week. Where is my order?”
Summer compares the original purchase, care record, pharmacy update and carrier tracking. The case shows where the order is waiting, who needs to act and what the customer has already been promised.
Help desk · care platform · pharmacy · shipping
A source-linked status and a proposed follow-up. Delivery is confirmed from the carrier record when available.
Explain a charge and prepare the right correction
“I canceled. Why was I charged again?”
Summer reads the cancellation request alongside the subscription, payment and matching order. Your team can review the timeline, the applicable policy and the exact proposed changes together.
Customer conversation · Stripe · order history · company policy
A clear answer, with any cancellation or refund presented for human approval. The original result stays with the case.
Follow up with a pharmacy without losing the thread
“The pharmacy said someone needs to contact them.”
Summer checks the current pharmacy order and previous inquiries before proposing another contact. Vendor replies return to the customer's case so the next person can see the outstanding question.
Pharmacy portal · vendor messages · original support request
A specific inquiry for review and a visible follow-up owner. Sending an inquiry does not close the customer's problem.
Answer customers in your website and help center
“How do I find my visit or talk to someone?”
Summer Messenger uses your company knowledge and published help articles to answer routine questions. Verified customers can reach their own account and care links. Your team can take over the conversation.
Company knowledge · published articles · verified account context
A useful reply or the right account link. Deeper support work can move into an investigation; clinical questions go to the care team.
Carry a broken portal report through to a checked repair
“The link opens an error page.”
Summer keeps the original report and affected record with an engineering handoff. The case can distinguish a reported bug, a proposed fix and a deployed repair your team has checked.
Customer report · portal evidence · engineering issue
A traceable handoff and a customer update based on the checked result.
See how Rebody uses Summer.
Rebody Health describes using Summer to check charges, trace orders and investigate refill questions, with its staff reviewing proposed changes.
Read Rebody’s customer story ↗Bring us a case your team keeps chasing.
We’ll look at the tools, access and decisions involved, then agree what Summer should handle and what stays with your team.