Companion calls01
The full Amigo call engine
Scheduled and on-demand phone conversations built on reminiscence-therapy frameworks, daily check-ins and medication reminders — the same companion experience, running under your brand.
Senior care companies
White-label Amigo, deployed inside your infrastructure.
Run the full Amigo voice AI platform — companion calls, alerts, family view and the CogPath and VGDS signal modules — under your own brand, on your own infrastructure, with complete control of the data path.
Data sovereigntyWhite-labelOn-premise readyGDPR-aligned
What it is
The full Amigo platform, running as your product.
Not a chatbot bolted onto your stack — the complete companion platform Verbasync operates, installed inside your environment and branded as your own.
Alerting02
Real-time alerts to your teams
Detection of alarming pain or strong discomfort in a conversation triggers alerts to caregivers, routed through your escalation chain rather than a third-party console.
Family view03
Family visibility layer
A daily check-up summary of mood, condition and cognition that families and care teams can see, with alerts the whole circle shares.
Signal modules04
CogPath and VGDS built in
Longitudinal cognitive pattern analysis and geriatric mood signal run over every conversation, giving your operation a continuous measurement layer without extra tests.
Why on-premise
Control the data path, keep resident trust.
Senior care runs on sensitive data and long relationships. An on-premise deployment keeps both inside your control.
What's included
Everything needed to run the voice layer yourself.
A complete deployment package — the apps, the runtime, the dashboards and the integration surface.
White-label apps
Companion, dashboards and family views rebranded to your identity, running as your product.
Call engine
The telephony and conversation runtime that places, receives and structures every call.
CareLM runtime
The senior-safe GPT-OSS base model that powers interaction, running inside your deployment with locked, versioned weights.
Dashboards
Operational views for care teams: resident status, mood and cognition trends, and call history.
Alerting
Configurable alert rules wired into your escalation chains and on-call model.
Integration APIs
Endpoints to connect rostering, care records and teleassistance systems to the voice layer.
Deployment
From scoping to production in six defined steps.
Each stage has a clear owner, a clear output and your sign-off before the next begins.
Step 01
Scoping
We map your infrastructure, data residency requirements, resident population and integration surface, then agree the target architecture.
Step 02
Install
The platform is deployed inside the environment you designate — your cloud tenancy, private cloud or on-premise hardware.
Step 03
Brand
Apps, dashboards and family views are white-labeled to your identity, so residents and staff see your product.
Step 04
Integrate
Rostering, care records, CRM/EHR and teleassistance systems are connected through the integration APIs.
Step 05
Train
Care teams are trained on the dashboards, alert handling and day-to-day operation of the voice layer.
Step 06
Operate
You run the platform in production with agreed SLAs, versioned model weights and a defined update path.
Who it's for
Built for operators who own the resident relationship.
Any senior care operation that wants a branded voice layer inside its own perimeter.
Home care
Care continuity, alert monitoring, medication reminders and a soothing presence for recurring dementia calls — keeping people at home longer and healthier.
Senior living
A memoir activity that supports cognitive health, organisation-wide visibility, early detection of complications and a premium cognitive-care offering.
Teleassistance networks
A voice agent that calls after IoT and assistance alerts, understands urgency, routes escalation and keeps the conversation going when the person needs support.
Prefer a platform designed from the ground up around your operations rather than a white-label of Amigo? See the bespoke voice agent platform.
Operations
How the deployment is run over time.
The questions operators ask before they commit to running the voice layer themselves.
Updates
Platform updates are delivered on an agreed cadence with staging validation, so new behavior never lands in production without your sign-off.
SLA
Uptime, alert-delivery and support response targets are defined in the deployment agreement and monitored against your operating requirements.
Model weights versioning
CareLM weights are locked and versioned per release, so the model driving conversations is reproducible and every change is traceable.
Data path
Where audio, transcripts and derived signal live, how long they are retained and who can access them follow your policy, documented end to end.
Discuss an on-premise deployment.
Tell us about your infrastructure, resident population and data residency requirements, and we will map the deployment architecture with you.