runnrrAssign a callback and keep the response together
A callback with a named owner, source conversation and recorded next action.
Talk to sales
Clio
MyCase
Filevine
Smokeball
Xero
QuickBooks
Sage
a3innuva (A3)
Reapit
Alto
Arthur Online
Houzz Pro
Programa
Studio Designer
Gmail
Outlook
Microsoft 365
Google Workspace
Slack
What starts the work
A patient asks for a callback or an enquiry needs a member of your team.
- Contact details
- Reason for callback
- Approved callback owner and handover rules
Work in your tools
Collect the callback request without giving clinical advice
Match the conversation to the permitted record
Assign the callback to the right team member
Keep the response and next appointment with the request
| What your team does today | What comes back |
|---|---|
| Leave a message for a colleague and chase whether the patient was called back. | A callback with a named owner, source conversation and recorded next action. |
Built around the tools you use
Agree how you will measure the result
Compare staff handling time, completed requests and exceptions before and after setup. The written scope defines which requests count and what a completed result means.
Calculated from your inputs. Include review and exception handling. Validate the target during your pilot.
Start with one recurring job. We agree the result, connect your tools and test the workflow with your team.
Questions before you start
Which software can this use?
Runnrr checks your exact software, version, permissions and available actions before agreeing the workflow. Connections, data access, retention and approval rules are confirmed and tested during setup.
What counts as completed work?
A callback with a named owner, source conversation and recorded next action.
What needs a person?
Treatment concerns, suitability and medical advice stay with your clinical team.
What happens when something fails?
Urgent concerns follow the clinic's own escalation instructions. An unaccepted handover stays open.
Does this require the Mac app?
The Runnrr Mac app requires macOS 14 or later and checks connected sources while it is running. A managed workflow is scoped separately: required software, hosting and operating hours are agreed and tested before live use.
What does setup and operation cost?
US$299 covers one-time setup for one agreed workflow. Ongoing operation and support are quoted separately, along with any call, messaging, AI or other provider charges. Runnrr confirms recurring costs and usage limits in writing before you commit. If the workflow is not running within two weeks or does not deliver the result agreed in writing, Runnrr refunds the US$299 setup fee.
Who handles ongoing support?
Dmitrijs Vitjazevs is your contact for setup and workflow questions at dv@runnrr.io. The written quote sets out ongoing maintenance, support hours, response arrangements and how to end the service. Your team names the person who handles exceptions and professional decisions.
Work your team can hand over
Assign a callback and keep the response together
A callback with a named owner, source conversation and recorded next action.
Talk to sales