Ask what is broken
Voice reads the same current status snapshot used by chat, keeping active warnings separate from old alert history.
Voice AI · conversation with tools
Ophelia opens the conversation instead of waiting in dead air. Ask what needs attention, set a reminder, or talk through the problem without leaving the assistant that already knows the operating context.
Not a phone tree
The voice surface has a small, deliberate tool set. It can read a current operational snapshot and create reminders through the same store used by chat. If a tool is unavailable, it says so rather than pretending the action happened.
Voice reads the same current status snapshot used by chat, keeping active warnings separate from old alert history.
Say the task and time naturally. The parsed reminder lands in the shared reminder table and follows the same delivery guarantees.
The call carries Ophelia’s persona and approved context, while private tools remain individually scoped and authenticated.
One Ophelia
Your backup is current. One credential is nearing expiry, and the reminder about the phone plan is still open.
Remind me tomorrow at nine to send the renewal payment.
Done. Tomorrow at 9:00 a.m.—send the renewal payment.
Good. Text me if the service actually goes down.
Boundaries
Ophelia is not an emergency service. Carrier delivery and AI output can be delayed or wrong, so important actions need explicit tool confirmation and time-critical emergencies need the appropriate human or emergency channel.
A conversation cannot acquire a new permission by asking nicely. Each action surface is separately authenticated and limited.
The tool response—not the model’s confidence—decides whether Ophelia says a reminder or action succeeded.
An inbound conversation can receive a direct reply. Recurring service messages require a separate recorded enrollment and confirmation.
Availability
The web call surface, Ophelia greeting, current-status lookup, and shared reminder creation are active in the owner deployment.
Twilio calling and texting are under early-access validation while A2P review, enrollment confirmation, and carrier behavior are completed.
More calendar, task, and connected-service tools will be added only after each one can prove success or failure cleanly.