Can My AI Assistant Answer the Phone? I Connected Mine and Found Out
The result, first
This morning I tested what happens when I connect my phone to Moka, my AI assistant (Muse). I wanted it to answer calls for me, like a voicemail service.
Here is what the test showed:
| Task | Result |
|---|---|
| Answer an incoming call | Not possible (Moka has no phone number of its own) |
| Listen to carrier voicemail | Not possible (that stays inside the phone company’s box) |
| Read the call log | Works (after I granted permission, it read the last 5 calls) |
| Read SMS messages | Works (6 messages from the last month or so) |
| Send an SMS | Draft only (I press send myself in my messaging app) |
| Verification codes | It can read them, but never writes them down; it passes a code only to a login screen that is waiting for it, with my approval |
| Search contacts | Works (name, organization and number) |
| Place a call | Works as an assist (it dials from my phone, on my number, and I do the talking) |
It cannot answer. But almost everything around the call — finding the number, dialing, checking who called — now runs by voice.
Why I wanted this
I was born in 1971 and live in an old house in Kurashiki, Japan. I am not a tech professional. I use Moka, an AI assistant, to help with my blog and daily work, and I keep testing what it can and cannot do.
A phone call is different from email. If nobody picks up, you never learn what the call was about. So I asked: if I connect the phone, can Moka pick up for me and handle what comes in, like a voicemail service?
Why answering does not work
Moka has no phone number of its own.
Answering means receiving, on the spot, a voice that was called to a number. With no number, there is nothing to receive the call with.
Email and calendars reach Moka through connectors. The phone is different: what connects is my smartphone itself, and what Moka can touch there is the record side of it.
What the call log gave me
At first, the call log was not readable — permission had not been granted. During the test, permission came through, and Moka read my last five calls: who called, when, and how long the call lasted.
- Nov 15 — incoming, 42 seconds
- Nov 11 — incoming, 1 minute 20 seconds
- Nov 11 — incoming, 3 seconds
- Nov 6 — outgoing, 2 minutes 56 seconds (to a local government office)
- Nov 6 — outgoing, 2 minutes 31 seconds (to a health insurance association)
Names and numbers stay out of this article. Dates and lengths are enough to show the shape: after an absence, I can now ask who called, and call back.
SMS: readable, sending stays mine
SMS messages were readable too — six from the last month or so: a car valuation offer, a payment service bill notice, login verification notices, and similar.
Sending is draft-only. Moka writes the text, and I press send in my own app. It never sends on its own. To me, that is a reassuring line, not a missing feature.
Verification codes: readable, never written down
Some of those SMS messages contained login verification codes. A Google code arriving by SMS would be the same: Moka can read it.
Its rule is firm, though. The code itself is never copied into a chat, an article, or a file. A code is a key. Writing a key’s number down in many places is how keys get lost.
A code is used in exactly one situation: a login I asked for is on screen, waiting for that code. Then, with my approval, the code goes to that screen only, and it is not stored.
Readable and writable are different things. I agree with that line.
Contacts closed the loop
Finally, I asked Moka to search my contacts for a name that appeared in the call log. It found the person, their organization, and their mobile number — and the number matched the call log.
So this flow now works end to end:
I say “call Mr. X” → Moka finds the number in my contacts → it dials from my phone → I talk.
With the phone on speaker or earphones, that is hands-free. When the app is in the background, a tap-to-call card can appear and need one tap, but the searching and dialing are no longer mine to do. I cannot touch-type, so replacing that work with a spoken name matters more than I expected.
I added calls to my morning check
The test did not end as a one-off. Every morning, Moka already checks my Gmail and reports only what matters. This morning I added one more item to that check: incoming calls from the last 24 hours. If there are no calls and no important mail, the morning stays silent.
Half of my honest reason is that this will make a good follow-up article. Whether the daily check really catches calls is now part of the record too.
The answer
Moka cannot be my voicemail. It cannot pick up, and it cannot hear what a caller wanted.
What it can be is the one who tidies up after the absence: who called, when, and how to call back — all by voice. That was this morning’s answer.
- November 18, 2026 ― Draft created (ledger No.167). English version written results-first, from the same test as the Japanese version No.166(3,851 characters)
- November 18, 2026 ― Published (with the Japanese version, after the author's approval; multilingual versions published the same way on their sites)(3,851 characters)
