Tebyar
Care meets control.
Multi-tenant software for Canadian caregiver agencies and health support providers — running lead generation, care delivery, compliance and billing in one place, with isolated tenant data and a single common-user identity that follows a client across every provider they work with.
What Tebyar does
Run lead generation, care delivery, compliance and billing in one place
Care providers usually run four systems and a shared inbox. The lead arrives in one, the assessment happens in another, the agreement is emailed as an attachment, and the invoice is raised somewhere else entirely — with a coordinator holding the whole thing together from memory.
Tebyar carries the same record from the first enquiry through agreement, payment, scheduling and delivery — with the regulatory capture, escalation ladders and audit trail that a regulated care business needs behind it.
Lead engine
Capture, qualify and convert — with a public interest form configured per business, service and province.
Staff operations
Capacity-aware allocation, vacation shielding and controlled case transfer with approval.
Control matrix
Roles, SLA timers and tiered escalation with named owners and breach actions.
Analytics
Commercial and operational reporting across conversion, completion, SLA and fill rate.
Three workspaces
The same platform, seen from three positions
Every role lands on the dashboard that matches what it is responsible for — and sees nothing beyond it.
Platform admin
Cross-tenant governance for the operator of the platform itself.
- Dashboard — cross-tenant events needing visibility
- Subscriptions and billing rules per tenant
- Business onboarding with regulatory capture
- Packages and agreements, platform-wide or segment-restricted
- Reporting across commercial, operational and compliance
Business workspace
The care provider's own operation, scoped to its own tenant.
- Lead pipeline with interest, qualification and converted stages
- Public interest form with conditional questions
- Workflow builder with low-code rule editing
- Staff management with roles and live workload
- Scheduling and controlled case transfers
- Client service desk and patient intake
- Roles, SLA and escalation matrix
Common user
One login, multiple businesses, one dashboard.
- My dashboard — services across all businesses
- Documents and payments with e-signature
- Pending requests from each provider
- Login and OTP registration
- Scoped visibility: each business sees only its own relationship
Onboarding
One unified registration flow with regulatory capture
Legal name, business type, province, dedicated route, licence or registration number, insurance expiry and authorised services — captured at registration rather than chased later.
Dedicated route
A branded path such as /ca/<business> reserved at registration if available.
Admin account & roles
Role-based permissions seeded automatically on approval.
Commercial policy
Conversion thresholds and discount scope configured per tenant or segment.
Package access
Platform packages entitled to the tenant, alongside its own private packages.
Workflow
How a lead becomes an active case
The workflow canvas is configurable per business and service. Escalation windows, payment triggers and transfer approval rules are all set in a low-code rule editor rather than hard-coded into the product.
Conditional logic example
If the client is a returning user, skip account creation. If new, send a registration link and hold payment until the one-time code has been completed.
Interest received
Create the lead and start the first-response SLA clock.
Qualification
Patient information, eligibility and routing to the right queue.
Fee proposal
Package, plan and add-ons assembled against the service selected.
Agreement & forms
Send the agreement package, or register the client first if they are new.
Payment gate → schedule
Staff assignment happens after the payment condition is satisfied.
Control
Roles, SLA and escalation as a matrix, not a policy document
| Role | Visibility | Lands on |
|---|---|---|
| Platform admin | Cross-tenant governance | Admin dashboard |
| Business owner | Own tenant only | The business's dedicated route |
| Coordinator | Assigned queues | Operations workspace |
| Common user | Own cross-business view | Client portal |
Lead intake SLA · Tier 1
First-response timer with escalation to the operations manager on breach.
Agreement SLA · Tier 2
Reminder at the first threshold, recovery queue at the second.
Continuity breach · Critical
Raised when a case has no owner after leave has been approved — the failure mode nobody schedules for.
Staff operations
Allocation that knows who is actually available
Assignment is capacity-aware by role, region, language and live workload. Approved leave blocks new tasks and suggests cover rather than silently leaving a case unattended.
Capacity-aware assignment
By role, region, language and current load.
Vacation shield
Blocks new tasks and proposes cover before the gap opens.
Controlled transfer
Approval matrix with supervisor sign-off where fees change, and a full audit trail.
Reporting
A report library, split by who needs it
| Report | Audience | What it measures |
|---|---|---|
| Lead conversion economics | Admin / owner | Conversion performance across the funnel and revenue outcome |
| Staff allocation health | Operations | Workload distribution and vacation overlap risk |
| Agreement & form completion | Coordinators | Pending and overdue documents by client and package |
| Regulatory coverage | Compliance | Expiring licences, insurance and mandatory documents |
Rooted in the Sundarbans. The world's largest mangrove delta and home of the Royal Bengal Tiger — resilient, adaptive and protective by design. The name and the palette are deliberate: a system for care work should be built the same way.
Care meets control
See it from all three sides
before you decide.
A walkthrough of the platform admin, business and client workspaces against your own operating model — including onboarding, workflow rules and the escalation matrix.