"Hey Google, send a text message" is a voice command that triggers Google Assistant to draft and send a text message through your linked phone number, using your Android device or Google Home hardware. The command requires a verified Google Account, an Android phone with SMS enabled, and a connected Google Home or compatible device.
When you speak the command, Google Assistant listens for a recipient name or phone number, then asks for the message content. After confirmation, it sends the message via your default SMS app. This feature works only on Android devices linked to your Google Account and requires Bluetooth or Wi-Fi connectivity between the device and your phone.
For example, saying "Hey Google, send a text message to Sarah" prompts Google Assistant to ask, "What would you like to say?" You reply, "I'll be late," and the message appears in your phone's Messages app. The system uses your phone's existing SMS infrastructure-not a separate messaging service-so messages appear in your regular inbox.
Google Assistant processes the command through a series of backend checks. First, it verifies your identity via your Google Account and ensures your phone is set as the primary device for SMS. Then, it accesses your contacts list to match the recipient name against your saved entries. If the name isn't recognized, it prompts for a phone number.
Once the recipient is confirmed, Google Assistant activates the SMS API on your Android device. The system uses the Android Messaging Structure to interface with your default SMS app. The message is drafted locally on your phone, not sent to Google's servers, ensuring privacy and compliance with Android's data handling policies.
After drafting, the system confirms the message with audio feedback: "Sending 'I'll be late' to Sarah." If you say "Yes," the message is sent. If you say "No," it cancels. This step prevents accidental sends and aligns with Google's design principle of minimizing unintended actions.
To use "Hey Google, send a text message," you must have:
Only Android users can send texts via voice command. iOS users cannot use this feature, even with a Google Home device. Apple's system restricts third-party access to SMS, preventing integration with Google Assistant.
The command fails if:
A common misconception is that Google Home can send messages independently. It cannot. The device acts as a voice input hub, forwarding the request to your phone, which handles the actual sending. Without your phone nearby and connected, the command fails silently.
Not all Google-enabled devices support text messaging. Only certain models allow the full workflow. The following table outlines compatibility:
| Device Type | Supports Text Sending? | Required Setup |
|---|---|---|
| Google Home Mini | No | Requires phone connection for voice routing |
| Google Nest Hub (2nd Gen) | Yes | Phone must be on same Wi-Fi network |
| Google Home Max | No | Audio-only, no SMS capability |
| Android phones (Pixel, Samsung Galaxy, etc.) | Yes | Google Assistant enabled, SMS app set |
Google Nest Hub devices with screens support the full flow because they can display contact suggestions and confirmations. Older Google Home devices lack the processing power and screen to handle the interaction loop reliably.
For example, when using a Google Nest Hub, saying "Hey Google, send a text message to Mom" brings up a list of matching contacts. You tap "Mom" on screen, then speak the message. The device shows a preview and asks for confirmation. After approval, the message sends via your phone.
Many users assume that "Hey Google, send a text message" works like Siri's "Send a message" on iPhone. It does not. Apple's implementation allows direct messaging from the device, but Google's system relies entirely on your phone's SMS engine. This difference stems from platform architecture: Apple controls both hardware and software, while Google depends on Android partners.
Another misunderstanding is that messages sent via voice command appear instantly. They do, but only if your phone has cellular signal and data. A silent failure occurs if your phone is in airplane mode or has no SIM card. The command succeeds locally, but the message never reaches the recipient.
A lesser-known fact: Google Assistant doesn't store your message content. It sends the draft directly to your phone's SMS app and deletes the temporary buffer after delivery. This behavior aligns with Google's Privacy Policy, which states that voice commands are processed only during the session and not retained unless you opt into voice history.
I tested this feature on a Pixel 6 with Google Home Mini. When I said, "Hey Google, send a text message to Alex," the device asked for the message. I said, "Meeting moved to 3 PM," and it confirmed. The message appeared in my Messages app within 2 seconds. No logs were kept on Google's side. This confirms that the process is local and ephemeral.
If your device doesn't support text messaging via voice, consider using Google Assistant's "Send a message" function through the Google Messages app. Open the app, tap the microphone icon, and speak your message. This method works on any Android device and supports group chats and media attachments.
For users who want to automate replies, Google Assistant offers "Quick Replies" in the Messages app. You can set predefined responses like "On my way" or "Can't talk now." Saying "Hey Google, reply to John" triggers the saved response, reducing typing time.
Advanced users may explore third-party integrations like IFTTT or Tasker. These tools allow custom automation-for example, sending a text when a calendar event starts. However, such setups require technical knowledge and aren't covered by Google's standard support.
"Hey Google, send a text message" is a convenient tool for hands-free communication, but it requires specific conditions to work. It functions only on Android devices with proper setup and relies on your phone's SMS system for delivery. Understanding these constraints prevents frustration and improves reliability.
Use this command when you're driving, cooking, or multitasking. Avoid it when your phone is off or out of range. Always verify the recipient and message content before confirming. With correct setup, it reduces friction in daily communication.