Field staff text. Back office chats. Rubi Bridge closes the gap.
Home care caregivers, field technicians, and traveling installers all have one thing in common: they live on SMS. It's fast, universal, works on every phone, and doesn't require another app. The back office, meanwhile, runs on Slack or Microsoft Teams — threaded conversations, channels per client, shared files, audit trails.
Between those two worlds sits a communication gap. Coordinators paste screenshots of SMS threads into Slack, field staff miss critical updates from Teams channels, and nobody has one clean record of what was said to whom.
Field workers prefer SMS for its simplicity. Back-office teams depend on Slack and Teams for collaboration. Existing solutions don't bridge the two — so agencies end up with two parallel, disconnected communication streams.
What Rubi Bridge does.
Rubi Bridge is a small service that sits between Twilio and your collaboration platform. When a caregiver texts the agency's SMS number, Rubi Bridge routes that message into the right Slack or Teams channel — with the right metadata attached. When anyone in that channel replies, Bridge sends the text back out via Twilio. The caregiver sees an SMS. The office sees a threaded conversation.
Your caregivers stay on SMS. Your office stays in Slack. Rubi Bridge keeps both sides in sync — with one unified audit trail.
Directory-aware routing.
Rubi Bridge doesn't just forward messages — it uses your existing employee and client directories to attach real context. Before dropping a message into a channel, it looks up the phone number against AlayaCare, Q360, or whatever system holds your people, and enriches the thread with:
- Who it's from — name, role, branch, current visit or job, so nobody has to ask "who is +1-303-555-0142?"
- Which channel it should go to — per-client, per-branch, or a general intake channel depending on your routing rules
- Recent history — last few exchanges with that person so the context is in-thread, not buried in another tool
Two-way, not one-way.
Most SMS-to-Slack tools only go one direction — inbound SMS lands in a channel, but replies from the channel don't make it back out. Rubi Bridge is bidirectional: anyone with access to the channel can reply, and the reply is sent as an SMS from the same agency number the caregiver originally texted. No new tools for the office team to learn. No new numbers for field staff to save.
Coordinators can pull a supervisor into a Slack thread the moment a situation escalates. The supervisor types in Slack. The caregiver gets an SMS. The whole conversation — including every office-side back-and-forth — lives in one auditable channel.
Features.
- Slack + Microsoft Teams — first-class support for both platforms. Pick whichever your team already uses.
- Auto-channel creation — per-client, per-visit, or per-incident channels spin up on-demand and archive themselves when the conversation is done.
- Internal-only threads — drop a message in the channel without sending it as SMS (great for office notes, supervisor hand-offs, or "don't text this part" commentary).
- Full message history — every SMS in, every reply out, with timestamps and user attribution, retained for audit and compliance.
- AlayaCare + Q360 directory sync — zero manual phone-book maintenance.
- Twilio-native — you own the number, you own the account, you pay Twilio directly.
On the roadmap.
Pairs naturally with Rubi Space.
If you already run Rubi Space for visit reminders and credential tracking, Rubi Bridge is the next layer up — it adds the human-to-human conversation channel that Space's automation can't replace. Same AlayaCare API integration. Same Twilio account. Same Rubi support.
How we deploy it.
- Discovery call. We confirm your collaboration platform (Slack or Teams), your SMS provider (new Twilio number or existing), and your directory source (AlayaCare, Q360, CSV import, etc.).
- Twilio + platform setup. We help you provision a Twilio number and install the Bridge bot/app into your Slack or Teams workspace.
- Directory mapping. We wire up the employee + client lookups and test a handful of inbound messages against staging.
- Routing rules. You tell us how incoming messages should be channeled — per-client, per-branch, per-role — and we configure the routing.
- Pilot with one team. We launch to a small pilot group (one branch or one service line) for a week to validate the workflow.
- Full rollout. Once the pilot is steady, we open it up to the rest of your staff.
Frequently asked questions.
Yes. If you already have a Twilio account and a number configured, we'll connect Bridge to it. If not, we help you set up a new one during onboarding.
Messages queue in the channel until someone picks them up. For urgent situations you can configure a fallback — email alert, PagerDuty page, or a secondary "on-call" channel — so nothing gets missed overnight.
No. From the caregiver's perspective it's just a text conversation with the agency's number. The routing layer is invisible. Many agencies choose to tell staff anyway as part of their communication policy.
Bridge itself can run in a HIPAA-aligned configuration (BAA with Twilio, encrypted at rest, minimal PHI retention). The bigger question is whether your chosen platform — Slack or Teams — is covered under your HIPAA compliance program. We'll work through that with you during discovery.