You are running late.
You contact everyone separately. With SAINT, you would give one brief to tell your guests and ask the restaurant to hold the table.
You send the messages, wait on hold and check the details. These three short scenes show the work we are building SAINT to take on.
You contact everyone separately. With SAINT, you would give one brief to tell your guests and ask the restaurant to hold the table.
You find the bill and wait on hold. With SAINT, you would hand over the disputed charge and your terms, then receive the outcome.
You set an alarm and check your train. With SAINT, you would ask once for a wake-up and a departure update.
The service is in a private pilot, by invitation. The films illustrate our direction, not three verified workflows. You approve consequential actions. The map and examples below show what the pilot supports.
Pilot calls depend on provider support and your approval. Refunds and restaurant agreements are not guaranteed. The instrument and the combined wake-up and live train update remain in development.
You give SAINT one request. SAINT works out who it involves, reaches each of them on a supported line and brings the answers back to you. Anything consequential waits for your Y. Choose a situation and step through it.
“I’m twenty minutes late. Tell Jonas and Maria, and ask the restaurant to hold our table.”
These situations are illustrative, and the people in them are fictional. Solid lines are what the private pilot supports, depending on the accounts you connect and the other party answering. Restaurant agreements and insurer answers are never guaranteed. The dashed line to a personal agent is in development.
Each example shows the request, an illustrative return and what it needs. One example is still in development, and it says so.
Who is waiting for an answer from me?
Anna is waiting for your availability. The supplier needs your delivery address.
You choose which accounts SAINT may read. Checking your inbox does not send a reply. Requires a connected email account. Social inboxes are not included.
Draft a reply to Anna. Friday works for me.
Draft ready: ‘Friday works for me. Would 10:00 suit you?’ Nothing has been sent.
You review the wording and approve the send. Sending requires a separate account permission. Requires a connected email account.
Call North Insurance and ask when the claim decision is due.
North Insurance expects the review on Thursday and committed to a decision by Friday. The claim itself is still open.
You approve sharing claim number 483-221. SAINT cannot accept a fee, an alternative or a voicemail on that approval. Calls depend on the supported route and the other party answering. SAINT reports a blocker if it cannot finish.
Chase the supplier for the revised quote.
The supplier replied. The revised quote is attached for your review.
You approve the recipient and message. Accepting the quote would need your separate decision. Requires a connected email account and an identified supplier thread.
Find a time for Anna and me next week.
Anna accepted Friday at 10:00. The meeting is in your calendar.
SAINT asks if the contact is ambiguous. You approve the invitation before it is sent. Requires contacts and calendar access. SAINT cannot see another person’s private calendar without access.
Ask my research agent to compare these two proposals.
The intended return is an attributed reply you can discuss with SAINT. A reply alone would not prove that an external task was completed.
You would review the exact message before sharing it. The agent’s own host would still control its action approvals. Personal agent connections are not publicly available. Compatibility must be verified for each client.
You can check what SAINT took on, what it may do and what happened. Consequential action waits for your approval.
You say what you need by text or voice.
You decide what SAINT may share, spend or change.
It asks for missing information before starting.
It tracks supported work within the scope you approved.
SAINT comes back when the work needs a new decision.
SAINT returns the result or the reason it stopped.
A touchscreen can make every step quick. It still needs you to choose and perform each one. A secretary starts with the outcome and carries the work between the tools.
“Dinner for four near the office on Thursday. Somewhere good.”
6 phone surfaces · the work remains yours
“Dinner for four near the office on Thursday. Somewhere good.”
Booked for 19:30. Everyone confirmed. It’s in your calendar.
One continuing thread · consequential action waits for your approval
The point is not fewer taps. It is no longer being responsible for every tap.
These illustrative workflows explain delegation; they are not customer results or a list of currently available services. The service page describes the private pilot’s supported scope. The screenless instrument is still in development.
Tell us about the messages, calls or scheduling you want help with. We will explain what the pilot can support.
The pilot works by text and voice on your phone. We are developing a screenless instrument as another way to reach it. See the instrument design
