iMessage voice memos
Send a voice memo to an existing iMessage chat. The supported connection presents it as a voice message in the conversation.
Send voice memos in an iMessage conversation, and audio attachments where the connected channel supports them. Keep voice content in the messaging workflow your app already uses.
iMessage voice memos require an authorized device-lab connection.
Send a voice memo to an existing iMessage chat. The supported connection presents it as a voice message in the conversation.
Provide a supported audio URL or an uploaded attachment ID for the voice memo. Your application creates or selects the recording.
Share audio attachments on channels that support them. Accepted formats, size limits and voice-note presentation depend on the connection.
Voice memos follow the project's connection permissions, recipient opt-outs and message-delivery rules.
On an eligible Twilio-backed number, configure a forwarding destination for incoming calls. TidyMessages validates the inbound call and forwards it to that number. This is separate from sending voice messages, and requires an active, ready connection and an authorized forwarding setting.
Discuss your connectionUse an authorized, active phone-number connection with inbound voice support.
Choose the E.164 phone number that should receive incoming calls.
A verified incoming call is forwarded to the configured destination. Without a destination, it receives a busy response.
A voice memo is a recorded audio message sent within a chat. Inbound call forwarding routes a live incoming phone call to a configured destination. They are separate capabilities with separate connection requirements.
Your application supplies the recording. Audio generation and transcription belong to your application's chosen services, rather than the voice-memo sending capability described here.
The phone-number capability described here is inbound call forwarding. It does not provide a general outbound calling or real-time voice-agent API.