openclaw - 💡(How to fix) Fix voice-call: completed inbound calls persist transcript but do not notify Telegram/user [1 comments, 2 participants]

Summary

Completed inbound voice calls are recorded in voice-calls/calls.jsonl, but no visible notification/summary is delivered to the user over Telegram or the originating/main session.

This appears to be the same product gap described in #29164 (voice-call: add postCall hook to notify originating session with transcript summary), but #29164 is locked and closed. Reproduced on the current local release below.

Environment

• OpenClaw: 2026.5.4
• OS: macOS 26.4.1 arm64
• Provider: Twilio
• Mode: realtime voice via OpenAI
• Telegram channel: enabled and independently able to send messages

openclaw voicecall setup --json passes:

• plugin enabled
• provider configured: twilio
• provider credentials/config complete
• public webhook configured
• realtime voice enabled

Reproduction

1. Configure plugins.entries.voice-call with Twilio, inbound calls, and realtime mode.
2. Place an inbound call to the OpenClaw/Twilio number.
3. Complete a short conversation.
4. Inspect /Users/<user>/.openclaw/voice-calls/calls.jsonl.
5. Observe the completed call record contains transcript and state: completed.
6. Observe no Telegram message, originating session message, main session message, or post-call summary is delivered to the user.

Observed local evidence

Two successful inbound calls were made:

• Call from the user's own phone completed with 7 transcript lines and explicit spoken request to summarize the call into Telegram.
• Call from another caller completed with 7 transcript lines including a scheduling request.

Both calls were present in calls.jsonl with provider call ids and transcripts. Neither produced a Telegram notification. openclaw voicecall status --json showed no active calls after completion, which is expected; the missing part is post-call delivery.

Expected behavior

A completed call with a transcript should produce one of:

1. A visible delivered summary to the originating session/user.
2. A configured post-call delivery to Telegram/other channel.
3. A visible delivery failure if notification cannot be delivered.

Silent persistence to calls.jsonl is not enough for phone-secretary/scheduling use cases.

Suggested fixes

Any of these would address the gap:

• plugins.entries.voice-call.config.postCall.notifySession: true
• postCall.delivery / postCall.channel / postCall.to for explicit channel delivery
• first-class internal hook event such as voice-call:completed carrying the call record/transcript
• plugin-side sessions_send / message delivery using the stored CallRecord sessionKey

Local workaround used

A temporary external scanner reads calls.jsonl, dedupes completed transcript-bearing calls by providerCallId, and sends summaries via openclaw message send --channel telegram. This works operationally but is brittle because it lives outside the plugin lifecycle and may break on storage/schema/CLI changes.