Built for Medical Practices

The CRM for the patient outreach the EHR was never built to run.

Medical practices run their clinical record in an EHR. That is the right tool for charts, orders, visit notes, and insurance claims. What the EHR was never built to run is the patient outreach layer: the recall, reactivation, referral tracking, service-line growth, loyalty program, review request, and new-patient marketing attribution. Strkr is the CRM that fills that gap. It sits next to the EHR, pulls contact-level data (not clinical records), and runs the outreach practice managers quietly glue together in spreadsheets today.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Independent and group medical practices live inside two separate motions. The clinical motion runs in the EHR, which is where it should run, and nobody is suggesting a CRM should replace it. The outreach motion is the one that leaks: recall lists exported to Excel, referral thank-yous forgotten, service-line pipelines invisible, reactivation campaigns one-off, loyalty programs built in a punch-card app, review requests sent manually, new-patient attribution guessed at. The five pains below are the ones we hear on every discovery call with practice managers and physician-owners, and they are consistent across primary care, dermatology, orthopedics, dental-adjacent, aesthetic, and specialty practices. The clinical surface is not the point here. The patient-contact outreach surface is, and the rest of the page shows how Strkr makes it one record instead of six spreadsheets.

EHR cannot run outreach

The EHR holds the chart, not the outreach plan.

Every practice manager has tried to run patient recall and reactivation out of the EHR and found the same wall. The EHR is built for clinical workflow, not for cadenced outreach, saved segments, A/B tested messaging, or attribution reporting. The practice ends up exporting a CSV, mail-merging in Excel, and sending from a free email tool, and the loop never closes back on the record. Strkr runs the outreach loop in a CRM shaped for cadence and attribution, syncing patient-contact fields (not clinical fields) in from the EHR so the recall list is always current.

Referral thank-yous missed

The referring provider never hears back and stops sending.

A specialty practice lives on referrals. The referring internist sends a patient, the specialist sees the patient, and the thank-you letter, the referral loop-close, and the follow-up visit confirmation never make it back. The internist stops sending within six months because they assume the specialist did not value the referral. Strkr tracks every referring provider as an account with a referral timeline, auto-fires the thank-you and loop-close letter, and surfaces which referrers are cooling off before the pipeline dries up.

Service-line growth invisible

We launched a new service and have no way to track interest.

The practice adds a new service line (aesthetics, weight management, chronic-care program, in-office procedure, telehealth) and the front desk tracks interest on a notepad. Three months in the owner cannot answer which marketing channel drove the inquiries, which turned into consults, which converted to paid procedures, and which lapsed. Strkr runs a service-line pipeline per offering with stage-by-stage conversion, channel attribution, and the drip to re-engage inquiries that did not book.

Reactivation one-off

Lapsed patients are a goldmine we never dig into.

Every practice has a tail of patients who have not been seen in 12, 18, 24 months. Reactivation is high-margin because the acquisition cost is zero and the trust is pre-built. Most practices run a reactivation campaign once a year, in a panic, through a mail-merge. Strkr runs it as a standing flow: patients past the recall window hit a reactivation sequence tuned per service line, with the front-desk escalation for a live call on high-value lapses, and attribution on which messages brought the patient back.

Reviews and loyalty bolted on

The review request and loyalty punch card live in three apps.

Google reviews drive new patients, and the practice uses a separate review request app. Patient loyalty for aesthetic or elective services runs in a punch-card app. Birthday emails come from a Mailchimp list that nobody has updated in 18 months. Each tool costs money, nobody updates them in sync, and the patient experience is fragmented. Strkr runs reviews, loyalty, and the lifecycle email stack native on the patient record, with the three motions coordinated instead of racing each other.

New-patient attribution guessed

We spend on ads and have no idea what actually works.

Practices spend four to six figures a month on Google Ads, Meta, local SEO, print, radio, and sometimes a referral partner. Attribution is the "How did you hear about us?" dropdown at check-in, which nobody fills in reliably. The owner cannot answer which channel actually drives booked visits. Strkr captures source on every new-patient contact via UTM, call tracking, and online booking source, and reports on the full new-patient funnel from inquiry to booked visit to paid encounter.

How Strkr fits next to the EHR

The patient-outreach primitives practice managers actually run.

Strkr is explicit about scope. The EHR owns the chart, the clinical record, the orders, the medications, the lab results, the problem list, the billing claim, and the insurance eligibility check. Strkr does not touch any of that and does not store PHI. What Strkr does own is the patient-contact outreach layer: names, emails, phones, consent, service-line interest, source of inquiry, referring provider, cadenced messaging, review request state, loyalty points, lifetime value of elective services, and the attribution trail from first touch to booked visit. The primitives below are what practice managers repeat every week, and they are the ones a CRM shaped around outreach handles cleanly where an EHR extension never will.

Contact record

One patient-contact record, not a clinical chart.

Each contact holds the fields the outreach layer needs: preferred name, email, mobile, consent state per channel, source of inquiry, service-line interest, referring provider, last visit date (synced from EHR), next scheduled, lifetime elective spend, and loyalty tier. Clinical data is not here by design. A sidebar renders the one or two fields the outreach team needs with the EHR deep-link for anything beyond that.

EHR sync

Contact-level sync from the EHR, not chart sync.

Strkr integrates with Athena, eClinicalWorks, DrChrono, Kareo, NextGen, Elation, Practice Fusion, and the common dental and chiro PMs through contact-level sync. Patient name, email, phone, last visit, next scheduled, provider, insurance plan name (not member ID), and visit type sync both directions. PHI stays in the EHR. The CRM holds the contact and the outreach history.

Service-line pipelines

A pipeline per new service, not per diagnosis.

Launch a service line (aesthetics, chronic-care program, in-office procedure, weight management, telehealth, hormone therapy, cosmetic consult) and spin up a stage-based pipeline: Inquiry, Consult Scheduled, Consult Completed, Treatment Plan Sent, Treatment Scheduled, Treatment Completed. Each stage has entry criteria, next-step tasks, and the drip for stalled inquiries, so the service line stops being a notepad and starts being a book.

Referral timeline

Every referring provider as an account.

Each referring provider is a Strkr account with practice name, specialty, referring physician, preferred contact method, and a timeline of every patient referral they sent. The timeline captures referral received, consult booked, consult completed, loop-close letter sent, follow-up visit, and discharge. The specialist can tell at a glance which referrers are warming up and which have gone quiet.

Recall and reactivation

Standing flows, not annual mail-merges.

Recall and reactivation are standing flows. The flow reads last-visit-date from the EHR sync, computes the recall interval per service type, and fires the cadence through SMS, email, and voice drop in the order the patient has opted in to. Reactivation on 18-month-plus lapses escalates to a front-desk task for a live call on high-LTV patients.

Reviews native

Google and health-vertical reviews from the record.

Post-visit flows fire a review request SMS or email at a configurable interval. Google Business Profile is the default target; Healthgrades, Zocdoc, RateMDs, and vertical-specific review sites plug in as additional targets. The practice sees the request-sent, request-opened, review-posted trail on the patient record and the aggregate review funnel in reporting.

Loyalty and lifetime value

Loyalty for elective-service practices.

Aesthetic, dermatology, chiropractic, dental, and vision practices with elective service lines run a loyalty program native on the patient record. Points per spend category, tier thresholds, and redemption against procedures or products. Lifetime elective spend is a first-class field so the top 10% of patients surface for VIP outreach without a quarterly spreadsheet pull.

Service-line growth

The pipeline the practice owner actually wants to see.

When a practice launches a new service line, the physician-owner wants to know three things weekly. How many new inquiries came in, how many booked a consult, and how many are moving through the plan toward treatment. Most practices answer that with a Monday morning spreadsheet pulled from four tools and a lot of guessing. Strkr runs the service line as a pipeline with the same stage logic a B2B deal would get, tuned for the clinical consult motion. The next cards show the specifics that make the pipeline usable for a practice manager who was never trained on CRM, and reportable for an owner who wants the one-page summary of this quarter is this service line pulling its weight.

Inquiry capture

Every inquiry lands on the pipeline.

Web form, phone call (via call tracking), chat widget, walk-in, referral, event, direct message on social: each inquiry source lands as a new contact with a service-line interest flag and source attribution. The front desk sees the fresh inquiries by channel on the Monday standup view and the automation picks up the ones nobody actioned within 24 hours.

Consult booking

From inquiry to booked consult without the chase.

Inquiry triggers a consult-booking flow. Online scheduling link in the first touch, two reminders if no booking in 48 hours, a front-desk live-call task on the fifth business day. Booked consult syncs to the EHR calendar, confirmation sequence fires, no-show rules kick in if the patient does not show. The front desk stops the end-of-day scramble to catch unbooked inquiries.

Treatment plan

Plan sent, follow-up, closed won.

Post-consult, the clinician writes the treatment plan in the EHR and the pipeline advances to Treatment Plan Sent. Strkr fires a plan-review follow-up at the cadence the practice has set (24 hours, 3 days, 7 days, 14 days). The patient who booked the first treatment moves to Treatment Scheduled; the patient who went quiet moves to a stalled-plan drip the practice has tuned per service.

Price range tracked

Expected spend on every opportunity.

Elective service inquiries carry an expected spend band set from a per-service price range. A full cosmetic case worth four to seven figures reports differently from a single-treatment inquiry worth three figures. The owner sees the pipeline by both inquiry count and expected revenue, so the service-line decision gets both volume and value in the same view.

Channel attribution

The source of every inquiry on the record.

UTM capture, call tracking numbers per channel, online booking source, offline source dropdown, referrer handoff. Every inquiry carries its first-touch source and the full channel path. Reporting shows which channels fed consults and which fed revenue, not just inquiry count, so the ad spend decision moves off gut feel and onto the attribution trail.

Stalled drip

The inquiries that went quiet get another shot.

Stalled inquiries at Consult Scheduled, Consult Completed, or Treatment Plan Sent fall into service-line-tuned drip sequences. The aesthetic plan that paused gets a follow-up on seasonal promos and testimonial content. The chronic-care program that paused gets a check-in on the pain point that drove the inquiry. The pipeline reactivation rate climbs 15-25 points over practices that never run the drip.

Owner dashboard

One-page view the physician-owner can read in a minute.

Per-service-line dashboard: inquiries this period, consults booked, consults completed, treatment plans sent, treatments completed, revenue, average deal size, channel mix. Toggle to prior period for the comp. The physician-owner reads it in a minute between patients, and the Monday staff meeting runs off the same dashboard everyone can see live.

Referral tracking

The referring-provider network the specialist can grow.

For specialty practices (orthopedics, dermatology, ENT, GI, cardiology, physical therapy, pain management, surgery), the referral network is the single biggest growth lever. A practice that loses a top referrer loses six figures of annual revenue without a sales-rep-equivalent to catch it in time. Strkr treats every referring provider as an account with a referral timeline, loop-close automation, cooling-off alerts, and a per-referrer scorecard that lets the practice manager or practice relations rep run a real network motion instead of hoping the referrers remember to send.

Referrer accounts

Every referring provider is an account.

Account for the referring practice, contact records for the physicians and MA/office staff who actually route the referrals, preferred communication method, specialty mix, geographic radius, in-network status. The account is the unit a practice relations rep works, not a line in a spreadsheet that gets rebuilt every quarter.

Referral timeline

Every patient referral on the account.

Referral in from the referring account becomes a timeline event. Consult booked, consult completed, loop-close letter sent, follow-up visit, discharge, follow-up with the referrer at the 90-day mark. The account history is the full referral stream, not a wall of guesses, and the renewal conversation with a top referrer runs off the record.

Loop-close letter

The thank-you and summary letter fires automatically.

Within the configured window after the consult, Strkr fires a loop-close letter to the referring provider summarizing the plan and visit outcome at the level the referral workflow needs (not clinical note depth, which the EHR handles). The practice manager sees the loop-close rate per referrer and the referrers who stopped getting them during an EHR migration surface fast.

Cooling-off alerts

Referrers who stopped sending surface on a dashboard.

The referrer activity view flags any account whose referral count has dropped more than 40% versus their trailing six-month baseline. The practice relations rep sees the shortlist each Monday and runs the outreach motion (lunch drop, in-person check-in, educational dinner invite) before the account goes fully quiet.

Referrer scorecard

Volume, conversion, revenue by referring account.

Scorecard per referring account: referrals this period, consult-to-case conversion, revenue contributed, average case value, lapsed-patient reactivation count. The scorecard underpins the quarterly referrer-partner review conversation and shows which referrers are the growth lever to double down on.

Field rep playbook

A playbook for the practice relations rep.

The field rep (or physician liaison, or practice manager wearing the hat) runs the referrer-growth motion out of a saved view with route planning, visit history, and the next-touch recommendation. Lunch drops, in-office visits, event invites, and educational materials all log to the account. The owner sees the activity, the referrer sees the attention, and the pipeline grows without a quarterly audit.

Co-marketing

Joint events and co-branded outreach.

Co-branded educational events for referring providers (lunch-and-learns, CME-adjacent dinners, patient-education nights) run from Strkr with the event invite list, RSVP tracking, attendance logging, and post-event follow-up all on the referrer account. The practice relations rep stops rebuilding the invite list every quarter and the event ROI finally gets measured on the record.

Flows for the practice

Automations that run the outreach day.

The practice manager who installs Strkr is wearing six hats on a given Tuesday. Hiring, scheduling, insurance verification, patient complaints, review responses, supply orders, and somewhere in there, the growth motion. Flows handle the pieces of the growth motion that should never require a human to remember them: the recall, the reactivation, the loop-close, the review request, the birthday, the no-show follow-up, the new-patient welcome. Each flow below ships native and the practice manager can edit the cadence, copy, and segment without an IT ticket or a Salesforce admin.

Recall

Last-visit date fires the recall cadence.

The flow reads last-visit-date from the EHR sync and computes the recall interval per service type (annual physical, 6-month cleaning, quarterly injection, monthly weight-management check). Cadence fires through the channel the patient has opted in to with escalation to front-desk live call for high-value or past-due lapses.

Reactivation

18-month-plus lapses hit the reactivation flow.

Patients past the 18-month reactivation threshold fall into a service-line-tuned sequence that leads with a soft re-engagement message, follows with a service-update message if no reply, and ends with a front-desk live-call task for high-LTV patients. The reactivation conversion rate reports monthly so the practice can tune cadence by season.

Review request

Post-visit review request on the right channel.

The flow fires 24-48 hours after a completed visit on the channel the patient prefers. SMS by default for most practices, email where the patient has opted in. Google Business Profile is the primary target. The practice manager sees the request-to-review conversion rate and the stars-posted trail per provider.

No-show follow-up

No-shows and cancellations re-engaged.

When the EHR flags a no-show or late cancellation, Strkr fires a two-touch re-engagement: a same-day apology-tone SMS with a rebooking link and a next-day email with the context. Rebook rate reports monthly and the chronic no-show pattern surfaces for front-desk flagging.

New-patient welcome

First visit kicks off the welcome sequence.

The first completed visit from a new patient fires the welcome sequence: thank-you, portal invite, review request on a lagged schedule, and the invitation to join the loyalty program for practices that run one. The sequence sets the trust layer that the practice relies on for referrals and reviews a year out.

Birthday and anniversary

Birthday messages that are not creepy.

Birthday messaging fires on the patient-provided birthdate (not the EHR DOB used for insurance) with a tone the practice has approved. Elective service lines run a birthday promo; primary care runs a wellness check-in. The anniversary of first-visit fires a loyalty milestone where loyalty is enabled.

Front-desk daily brief

The staff standup view, pre-built.

Each morning the front-desk standup view assembles: new inquiries overnight, consult confirmations needed today, high-value lapses to call, referrers who need a loop-close, review requests that posted overnight, scheduled events this week. The practice manager runs the standup off the view instead of five tools.

The scope line

Where Strkr stops and the EHR starts.

Buyers in medical practices rightly ask the scope question up front. The honest answer is that Strkr and the EHR are two tools solving two different problems. Strkr is the CRM for patient-contact outreach, referral management, service-line growth, loyalty, reviews, and attribution. The EHR is the clinical record and billing system. The two integrate on contact-level fields and leave clinical data where it belongs. The cards below spell out the specific boundary so a HIPAA-conscious practice manager can read the scope line and know exactly what Strkr handles and what it hands back to the EHR.

Not an EHR

Strkr does not store charts, orders, or clinical notes.

Strkr is not an EHR. It does not store SOAP notes, visit notes, orders, prescriptions, lab results, imaging, problem lists, allergies, or clinical history. Those stay in the EHR. Strkr integrates on contact-level fields and leaves the chart in the system of record where regulatory, continuity-of-care, and clinical workflow all require it to live.

Not for billing

Insurance claims and RCM stay in the practice management system.

Strkr does not file claims, run clearinghouse workflows, or hold insurance member IDs. The billing stack, whether that is Athena, Kareo, AdvancedMD, or a dedicated RCM vendor, keeps the claim lifecycle. Strkr pulls plan name (not member ID) as a segmentation field for payor-mix reporting, and that is the extent of the overlap.

No PHI storage

No PHI in Strkr by design.

Strkr does not store PHI as a design choice. The CRM holds patient-contact fields (name, email, phone, consent, service interest, source) that the outreach layer needs, and that set does not meet the HIPAA definition of PHI when kept separate from clinical identifiers. The integration pulls what the outreach surface needs and leaves the chart in the EHR.

BAA on request

A BAA is available when the practice policy requires one.

Even though Strkr is scoped away from PHI, some practices require a Business Associate Agreement with any vendor touching patient contact data. Strkr executes a BAA on request as part of the standard onboarding. The practice compliance officer reviews the scope and the agreement in parallel, not after the implementation starts.

Access controls

Role-based access on the outreach surface.

The front desk, the practice manager, the practice relations rep, the physician-owner, and the marketing agency each have different visibility on the contact record. Strkr role permissions keep the agency out of the lifetime-spend field, keep the front desk out of the referral-partner strategy notes, and leave the owner with the full view.

Audit trail

Every message and record change on the audit log.

Every outbound message, every record edit, every consent flip, every bulk-import carries an audit entry with timestamp, actor, and the before-after values. The practice compliance officer runs an audit in minutes, not days, and the record of outreach is defensible if a patient complaint ever requires one.

Reporting the owner asked for

The reports a physician-owner reads on a Monday.

A physician-owner has one hour of administrative time between the Monday morning sprint and the first clinical block. That hour is for the one-page view of what the practice looks like this week. Strkr ships default dashboards that answer the questions an owner actually asks: are the service lines growing, are the referrers warming or cooling, is the ad spend producing booked visits, is the review feed on an upward trend, is the recall engine firing and converting. The cards below are the default saved dashboards; the practice manager can duplicate and tune without a report-writer ticket.

Service-line roll

Each service line on one row.

Per-service-line roll: inquiries this period, consults booked, consults completed, treatments scheduled, revenue booked, average deal size, versus prior-period deltas. The owner reads the five rows in two minutes and knows which service line to lean into for Q2 marketing.

Referrer heat

Top referrers warming or cooling, color-coded.

Top 20 referring accounts with referral count this period versus trailing six-month average, color-coded for warming, steady, or cooling. The practice relations rep gets the Monday work list from this view, and the owner sees whether the field motion is driving the number.

New-patient funnel

Inquiry to booked visit by channel.

New-patient funnel: inquiries by channel, inquiry-to-consult conversion, consult-to-booked-visit conversion, cost per booked visit (where ad spend data is loaded). The marketing agency reads this view with the owner and the budget conversation stops being guesswork.

Recall health

The recall engine on one view.

Recall health: patients due in the next 30/60/90 days, recall-to-booking conversion, average days from recall touch to booked appointment. The practice manager sees the health of the engine at a glance and the owner knows the base-load volume for the quarter is defended.

Review feed

Review requests, posts, star trend.

Review funnel: requests sent, requests opened, reviews posted, average star rating, star trend over 90 days. Per-provider breakdown surfaces the clinician whose patient reviews are consistently five-star and the one whose feedback is drifting, so coaching happens on evidence not vibes.

Loyalty engagement

Top-tier patients and lifetime value.

Loyalty cohort: patients in each tier, average lifetime elective spend, redemption count, VIP outreach activity. The owner sees the top 10% of patients and the practice manager runs the VIP calling list for the quarter without a spreadsheet export.

Head-to-head

Strkr vs the typical medical-practice outreach stack.

A typical independent or group medical practice runs the outreach layer across four to seven tools. EHR for the chart. Weave or Solutionreach for recall and reminders. A separate review request app. Mailchimp for broadcast email. A punch-card loyalty app for elective services. A call-tracking vendor for ad attribution. A spreadsheet for referral tracking that updates on good months. Strkr collapses the whole set into one record of patient outreach, keeps the EHR as the clinical system of record, and leaves the practice with one bill and one admin surface for everything that is not clinical.

Feature Strkr EHR + Weave + Mailchimp + review app + punchcard + spreadsheet
Scope Patient-contact outreach, referral, service-line, loyalty, reviews Six vendors each doing one slice
Clinical record Stays in the EHR by design, not in Strkr Stays in the EHR
PHI handling No PHI storage; BAA available on request Varies vendor by vendor; mixed BAA coverage
Recall and reactivation Native flows reading EHR last-visit-date Weave or Solutionreach for recall; manual CSV for reactivation
Referral tracking Native with referrer accounts and timeline Shared spreadsheet, no loop-close automation
Service-line pipeline Native stage-based pipeline per service Notepad or spreadsheet by service lead
Review requests Native, multi-site (Google, Healthgrades, Zocdoc) Dedicated review app, separate SKU
Loyalty program Native, lifetime-spend tied to contact record Punchcard app, separate SKU, no CRM link
Call tracking + attribution Native call tracking, UTM capture, booking source CallRail or similar, separate SKU
Email broadcast Native, segmented against the contact record Mailchimp with stale list that never syncs
Reporting Default dashboards tuned for practice owners Six vendor dashboards, nothing adds up
Monthly bill One Strkr seat line, flat per-user Six vendor invoices, hidden overage SKUs
How teams use Strkr

How medical practices run Strkr.

The patterns below are from independent and small-group practices that moved the outreach stack onto Strkr. The common thread: one record of patient outreach, with the EHR left to do what the EHR does well, and the growth motion finally measurable on a dashboard the physician-owner can read in the Monday hour before clinic. Each playbook is a real motion a practice runs today.

3-provider primary care

Recall engine plus review funnel plus reactivation.

A three-provider primary care practice replaced Weave plus a review app plus Mailchimp with Strkr. The recall flow reads last-visit date from Athena, fires the annual physical cadence, and reactivates the 18-month lapses with a service-tuned sequence. Review requests landed on the Google profile at 2.3x the prior rate within the first quarter. The front desk standup runs from one view. The practice manager saved roughly four hours a week of CSV-wrangling and the owner cut three vendor subscriptions.

2-location dermatology

Service-line pipeline for aesthetics plus loyalty.

A two-location dermatology practice runs medical derm (insurance-billed) and aesthetic derm (cash-pay) side by side. The aesthetic service line runs in Strkr as a stage-based pipeline with price-band tracking per inquiry. Loyalty tier is tied to lifetime elective spend. The practice launched a cosmetic weight-management line and tracked it end-to-end on the pipeline from day one; eight months in they can see which marketing channel drove the booked treatments and which drove unqualified consults.

6-surgeon orthopedic group

Referring provider network with loop-close and cooling alerts.

A six-surgeon orthopedic group with 40% of volume coming from referring internists and PCPs runs Strkr as the referral network tool. Every referring account carries the full referral timeline. Loop-close letters fire automatically on consult completion. Cooling-off alerts surface the referrers who have dropped more than 40% in a trailing six-month window. The practice relations rep works the shortlist each Monday and the group has retained referrers through two local hospital-system acquisitions that normally would have shifted referral patterns away.

Multi-site dental

Recall, review, and loyalty across 7 locations.

A seven-location dental group runs Strkr as the outreach layer across all locations with the EHR (Dentrix) staying as the clinical record. Recall cadence is tuned per location to match the hygiene schedule. Review requests fire 24 hours post-visit on the location-specific Google profile. Loyalty points tie to lifetime cosmetic spend and the top tier gets quarterly VIP outreach from the practice manager. The group CFO sees one dashboard rolling up all seven locations instead of seven vendor dashboards.

Specialty + practice relations rep

Full referral-growth motion with a field rep.

A GI specialty practice with a part-time practice relations rep runs the referral motion out of Strkr. The rep works a saved view of referring accounts in each ZIP, logs lunch-and-learn visits, routes CME-adjacent dinner invites, and sees per-referrer scorecards. In the first year the referral count from the top 20 accounts grew 23% without a change in clinical staff, and the owner can trace revenue contribution to specific field-rep activities on the account timeline.

See the CRM medical practices actually run their outreach from.

Start a 14-day trial with the full practice stack enabled: patient-contact records with EHR sync, service-line pipelines, referring-provider accounts with loop-close automation, recall and reactivation flows, native review requests across Google and vertical sites, loyalty program with lifetime-spend tracking, call tracking plus UTM attribution, and the owner dashboard that rolls everything up in one page. The EHR keeps the chart, Strkr keeps the outreach, and the practice stops paying for six vendors to cover one surface.

See pricing Explore the features
Common questions

What buyers in this bucket ask most.

Is Strkr an EHR or does it replace our EHR?

No, Strkr is not an EHR and does not replace one. The EHR owns the clinical record: SOAP notes, orders, prescriptions, labs, imaging, problem list, allergies, and the claim lifecycle. Strkr sits next to the EHR as the CRM for patient-contact outreach, referral tracking, service-line pipelines, recall and reactivation, loyalty, reviews, and attribution. The two systems integrate on contact-level fields and leave clinical data in the EHR where regulatory and continuity-of-care workflows require it to live. A practice keeps their Athena, eClinicalWorks, DrChrono, Elation, NextGen, Kareo, Practice Fusion, Dentrix, or specialty EHR and adds Strkr as the outreach layer.

Does Strkr store PHI, and do we need a BAA?

Strkr does not store PHI as a design choice. The CRM holds patient-contact fields (name, email, phone, consent, service-line interest, source, loyalty tier, lifetime elective spend) that the outreach layer needs, and that set does not include clinical identifiers, diagnoses, medications, or treatment history. We treat insurance plan name as a non-PHI segmentation field; the plan member ID stays in the practice management system. If the practice compliance policy requires a Business Associate Agreement for any vendor touching patient contact data, Strkr executes a BAA on request as part of standard onboarding. The compliance review runs in parallel with implementation so onboarding is not blocked.

Which EHRs does Strkr integrate with?

The ambulatory and specialty EHRs Strkr integrates with cover most independent and group practice categories: Athenahealth, eClinicalWorks, DrChrono, Elation, Kareo, NextGen, Practice Fusion, AdvancedMD for the general ambulatory space; Dentrix, Open Dental, and Eaglesoft for dental; ChiroTouch and Jane for chiropractic and allied; Modernizing Medicine and Nextech for dermatology and ophthalmology; athenaOne, Epic Community Connect, and Cerner Ambulatory for larger groups. For an EHR not on the list, Strkr integrates through the standard contact-level APIs or HL7 feeds that most ambulatory EHRs expose, and the implementation team scopes the connector during onboarding. The sync is contact-level only; chart data stays in the EHR.

How does Strkr handle patient communication consent?

Consent is a first-class field on the contact record, broken out per channel: email marketing, SMS marketing, voice drop, mail, and transactional. The practice captures consent at the intake form, the patient portal, in-office kiosk, or post-visit survey, and the consent flip is logged to the audit trail with timestamp and source. Flows read consent before sending, so a patient who opted out of SMS never receives an outbound SMS and the compliance officer can prove it on the audit log. Unsubscribe links in every outbound message fire a consent flip automatically. The practice can also set tenant-wide quiet hours and per-channel frequency caps to stay within TCPA and CAN-SPAM norms without a sidebar app.

Can Strkr run reviews, reactivation, and loyalty in one place?

Yes. These three motions are the biggest reason mid-sized practices stack five vendors. Strkr runs them native on the patient record. Review requests fire post-visit on the channel the patient prefers and target Google Business Profile by default with Healthgrades, Zocdoc, and vertical-specific sites as additional targets. Reactivation is a standing flow that reads last-visit-date from the EHR and fires service-line-tuned cadence on the 18-month-plus lapses with front-desk escalation for high-value patients. Loyalty is a native program with points per spend category, tier thresholds, and redemption against procedures or products, tied to a lifetime-elective-spend field that updates with every paid encounter. One record, three motions, one subscription.

How does the service-line pipeline work for elective offerings?

Each service line (aesthetics, chronic-care program, weight management, in-office procedure, telehealth, hormone therapy, cosmetic consult, functional medicine) runs as its own stage-based pipeline. Default stages are Inquiry, Consult Scheduled, Consult Completed, Treatment Plan Sent, Treatment Scheduled, Treatment Completed, with per-stage entry criteria, next-step tasks, and stalled-inquiry drip sequences. Each inquiry carries first-touch source attribution (UTM, call tracking, booking source, offline source) and an expected spend band from a per-service price range. The owner sees the pipeline by inquiry count and by expected revenue in the same view, and the per-service dashboard rolls up weekly without a spreadsheet export.

How does Strkr track referring providers and the referral network?

Every referring provider is modeled as an account with the practice name, address, specialty mix, in-network status, and the contact records for the physicians and office staff who route the referrals. Each patient referral is a timeline event on the account with consult booked, consult completed, loop-close letter sent, and follow-up visit stages captured. Loop-close letters fire automatically within the window the practice has set. The referrer scorecard reports referral volume, conversion to case, revenue contribution, and trailing-six-month trend per account. Cooling-off alerts flag accounts whose referral count has dropped more than 40% versus baseline so the practice relations rep works the warming list before the referrer goes fully quiet. The field rep runs a route-planning saved view with lunch-drop and visit history on every account.

Also built for

Related audiences.

For Healthcare For Dentists For Chiropractors For Small Business For Professional Services For Marketing Managers

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing