Groups with more than one facility end up with more than one Kipu account. We connect each of them to a single Salesforce org, so admissions works one pipeline and every patient goes to the right Kipu account, with the right program, and comes back with its Kipu ID.
900+ integrations completed · Salesforce partner · We sign BAAs
How several Kipu accounts share one Salesforce org
Leads and opportunities for every facility in one Salesforce org
The facility and program on the opportunity decide which Kipu account it goes to
The patient created in that Kipu account, with the program from its own list
Master ID, admit and discharge dates and insurance carrier returned to the record
Admissions by facility and by program, across every Kipu account
Each Kipu account has its own API access, its own locations and its own program list. A single integration built for one account sends patients to the wrong place, or fails, once a second facility is added.
We give each Kipu account its own connection and access, link our vendor app to its locations, and load its program list. The facility on the Salesforce record decides where each patient goes.
The Kipu Master ID comes back to Salesforce for each patient, so updates, re-admits and discharges match the right chart in the right account. Kipu and Salesforce stay two-way for every facility.
Errors are logged in Salesforce and summarized by email, so a failed send for one facility is fixed before admissions notices.
What's included
Each Kipu account set up with its own API access and permissions to create and update patients.
Our vendor app linked to each Kipu location your team admits into.
The program list for every Kipu account loaded and mapped, so reps pick from the right one.
The facility on the opportunity decides which Kipu account receives the patient.
The Master ID stored on the record for each patient, with IDs matched in both systems.
Admit and discharge dates, insurance carrier and program history returned to the record.
A diagram and field mapping sheet for each Kipu account, kept with your docs.
Existing Kipu patients loaded into Salesforce when a new account is connected.
Failed sends logged in Salesforce, error summary emails, and alerts for Kipu records missing an opportunity.
A new Kipu account or state added to the same org when you open a new facility.
Every system we connect to Salesforce, in one list
CallRail and CallTrackingMetrics native integrations, with recordings and AI call summaries on the lead
Gravity Forms, Jotform and Typeform fills create leads with tracking attached
LiveChat, SnapEngage, Tawk.to and Avochato conversations saved to the lead
Kipu and Sunwave: admissions in Salesforce, clinical in the EMR, kept in step
CollaborateMD, AdvancedMD and HiLite, with insurance payments on the patient
Stripe, PayTrace and PayPal payments recorded on the opportunity
Google Ads, Microsoft Ads, Meta and TikTok leads in, offline conversions out
ActiveCampaign lists and automations that follow Salesforce
Open other systems from the Salesforce record with SSO
Salesforce data in Google Sheets, BigQuery and Looker Studio
No app for it? We build the connection with Apex and the APIs
Book a free call. We look at your Kipu accounts and your Salesforce org and show you how they fit together.
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
How it works
We look at your facilities, your Kipu accounts and how admissions works across them.
Facilities, programs and fields mapped for each Kipu account, in a document you keep.
Each Kipu connection tested with sample patients before go-live.
Deployed to production, with error alerts and support as you add facilities.
Working with us
US and overnight hours
Our teams cover all hours, so work keeps moving after your day ends.
AI agents in the workflow
We use AI agents in development and content creation, on a HIPAA-compliant Claude Enterprise license, so builds move faster.
900+ integrations completed
We have done this before, and it shows in how we plan and test.
Free call first
Honest advice before any work starts, even if you never hire us.
Yes. Each Kipu account gets its own connection, and the facility on the Salesforce record decides which account each patient goes to.
We load the program list for every Kipu account, so the program a rep picks matches the account the patient is sent to.
The Master ID, admit and discharge dates, insurance carrier and program history, on the Salesforce record for each patient.
The error is logged in Salesforce and included in an error summary email, so it is fixed and re-sent.
Yes. A new Kipu account or location is connected to the same org, with its programs and mapping.
Yes. We sign BAAs for healthcare work.
By project, not by the hour. The first call is free, and you get a project quote after it.
