Can Grok Bot Make Phone Calls? Service Calls vs Android Dialing

Choose the Grok route you mean

Can Grok Bot make phone calls? The Grok Bot Terms updated October 31, 2026, section 2.7, expressly cover calls placed or received on a customer’s behalf. That establishes a documented service-call category, not access for every account or automatic answering of incoming Android SIM calls. Grok voice chat is different again. For a supported outgoing call from your handset, use a documented Android dialer route. The calling distinction and FoneClaw dialer flow below show what to check.

Grok on Android can refer to four different routes. There is the consumer Grok AI app for chat, voice and media work. There is the separate Grok Bot Android app for assigning tasks to the Bot experience and using limited supported phone apps. There is the Grok API for developers and compatible model configuration. There is also FoneClaw, where a compatible model can help with reasoning while FoneClaw performs supported Android actions through its own phone-agent tools.

The package IDs are different: the Grok AI listing uses ai.x.grok, while the Grok Bot listing uses ai.x.grok.bot. Check the installed app before following instructions intended for the other product.

Our Grok Bot and FoneClaw explainer illustrates Grok Bot’s cloud-computer path, while FoneClaw uses enabled Android tools for supported calendar, contact, settings and memo actions under actual permissions and approval settings. Current Grok Bot mobile documentation also describes limited supported phone-app access. For a phone task, review the proposed action and inspect the saved event, contact, memo or resulting setting on the device. The explainer is not a new head-to-head performance test or proof of current Bot calling rollout or universal Android SIM calling.

Understand what Grok Bot controls

The Grok AI listing describes the consumer Android app for answers, natural voice conversations, image and video generation, and picture upload. That is the app most people mean when they say they installed Grok on Android. It is useful for asking questions, speaking with Grok, analyzing images and creating media inside the Grok experience.

The separate Grok Bot app supports cloud tasks and limited phone-app access, not general phone authority. The official mobile guide lists Android 9 or newer and internet access. Under the new unified X Subscription, Grok Bot access starts with Premium and is also included in Super and Ultra; Plus excludes Bot. Eligible first-party usage, including Bot work, shares a weekly seat pool. Account-specific legacy subscriptions may remain, so check the entitlement shown for your account. Sign in through the Cursor browser flow; where the app requests it, link the Grok account, then use its linking-complete and status-refresh controls. If access is missing, check the signed-in Cursor account, eligible plan and Grok link before assuming the Android app itself is broken. For pricing, permanent account unification and merchant-specific renewal checks, use our X, Grok, and Cursor Subscription Guide: Bot Access, Costs, and Account Unification.

Bot entitlement does not establish calling availability. If no calling entry or supported call setup is available, check the actual Bot app, signed-in account, connected setup and current service information. Record the exact visible message before retrying. Granting Android contacts or call-log access cannot unlock a cloud service feature.

In your own chat with a Bot you own inside the Grok Bot app, supported Android phone-app access includes reading and creating, changing, or deleting calendar events; read-only contact lookup; current location coordinates; and alarm or timer creation. It does not work in group chats, Slack, or another owner’s shared Bot. Calendar access excludes changing or deleting repeating events and never invites people. Location provides coordinates, not an address or place name.

Keep Grok Bot open in the foreground for these phone-app actions. Actual permissions, team rules, and configured Auto Review determine access and whether approval is requested. Closing or backgrounding the app blocks phone-app access even though cloud work may continue. This limited path does not establish local SIM dialing or incoming-call answering. Android alarms and timers pass to Clock, which does not confirm that they were saved: check Clock yourself. Alarms target the next occurrence within 24 hours, timers run up to 24 hours, and the Bot cannot list, change, or cancel them.

On mobile, you can start or answer Bot tasks, review progress and handle approvals. Android system sharing into Grok Bot is currently documented for text; photos and files use separate in-app routes, not the Android share sheet. In the Bot profile, review routines and their run history, use Active to pause or resume, or delete a routine. Edit routine opens a draft request in the Bot chat; describe the change and send it. Add routine starts a new routine from the profile. Testing a routine still requires desktop.

xAI's September 28 Team Bots announcement adds a public beta for Teams and Enterprise plans with shared role context, skills, plugins, credentials and memories while personal conversations remain separate. That is a team-work capability, not evidence of Android SIM calling.

Separate outgoing and incoming calls

Voice conversation, a Bot service call, placing a call through your handset, and answering an incoming SIM call are separate results. Grok Voice Mode lets you speak with Grok. Grok Bot’s documented service-call category concerns calls on a customer’s behalf. Local handset dialing uses the phone’s calling surface, while incoming SIM handling needs specific support for a live Android call.

Section 2.7 of the official Bot phone-call terms says temporary numbers may be assigned and numbers or regions may be blocked. Recipients must have agreed to hear from the customer. Virtual-assistant disclosures must remain, calls may be recorded, and the service is not for emergencies. These conditions do not establish universal rollout, a particular calling menu, fixed prices, or guaranteed success.

When a source says Grok can talk, read it as voice interaction unless it also names a phone-call route. When a source says a bot can complete tasks, check whether the task returned a result in the Bot environment, used an available calling service, or performed a local Android action. When a developer page describes the API, read it as model access for an app or service. The API can help software reason; the Android phone still controls contacts, dialer access, microphone access, call log access and incoming-call permissions.

A practical handset outgoing-call check should identify the target before execution. The result should resolve one consenting non-emergency contact or one exact number, use a calling path the phone supports, and show the actual call state after the approved action runs. If the target is ambiguous, resolve the contact first. For incoming calls, look for specific support for answering a live Android call, not just voice chat or assistant conversation.

For the broader difference between service calling, Android dialer handoff and user-owned phone calls, AI Agent Phone Calls: MCP Calling Services vs Android Dialer Control explains the execution paths. For incoming-call surfaces such as screening, text calls and transcripts, Can AI Answer Phone Calls on Android? Screening, Text Calls, Transcripts, and FoneClaw covers the phone-platform side in more detail.

Check Grok as Android default assistant

Android default-assistant availability is a device-side question. A phone can offer one set of assistant choices while another phone offers a different set, depending on the installed app, app declarations, Android build, OEM behavior, region and account state. The reliable check happens in Android Settings on the exact device.

Open Settings and search for default apps, digital assistant or assistant app. On many phones the path is similar to Apps, Default apps, Digital assistant app. On others it may sit under Apps, Voice input, Assistant or a manufacturer-specific menu. If Grok appears, select it only when you want to test that entry point. If it does not appear, the phone is not offering that app as a default assistant choice in the current setup.

The assistant role controls invocation: what opens when you use a gesture, power button, voice trigger or assistant shortcut. It does not by itself authorize contacts, calls, notifications, accessibility actions or app control. After changing the default assistant, ask a harmless question first. Then test one bounded action and inspect what actually happened on the phone.

Also record how to change back before testing sensitive tasks. If you normally rely on Gemini, Google Assistant, Bixby or another assistant for daily phone commands, confirm the old assistant remains available in the same settings area. The goal is to learn what Grok can launch or handle on that phone while keeping your working setup recoverable.

Verify one bounded phone task

Before granting broader access or trusting a social claim, verify one bounded task. Use a known consenting non-emergency contact, keep the phone visible and avoid work-critical calls. If you want a no-call first check, ask only to identify or show the contact and explicitly say not to dial. For an actual handset call, confirm the target and authorize that call before execution.

For a Bot service call, proceed only if your account actually offers the supported route. A proposed reader check is a simple inquiry to a business that has agreed to receive the call: ask whether a specified item is available, with an explicit boundary of no booking, purchase, payment, or other commitment. Review the number, facts to communicate, inquiry, and intended authority before permitting execution. Follow the available approval controls described in Grok Bot’s approvals and privacy guidance, then inspect the actual status and returned result. This is not a performed test. If access is unavailable, stop rather than repeating requests or changing phone grants.

1. Confirm the app. Check whether you are using Grok AI, Grok Bot, a browser session, an API-powered app or FoneClaw.
2. Confirm the result. Decide whether the goal is voice conversation, a Bot service call, other remote Bot work, a supported phone-app action, handset dialing, incoming SIM answering or Android assistant invocation.
3. Check the route. Look for an official available service feature, supported Bot phone-app access, Android setting, dialer handoff or FoneClaw supported action.
4. Use one target. Choose one unambiguous consenting contact or one exact non-emergency number.
5. Inspect the result. A model answer is not proof that a call was placed. For handset dialing, inspect the dialer or call screen; for a Bot service call, inspect the actual service status and result.
6. Check a failure before retrying. Read the visible approval or failure state. Check service access and setup for Bot calls. For Bot phone-app actions, check foreground state, permissions, team rules and Auto Review; for a FoneClaw task, check the relevant permissions, model endpoint and phone state.

This check is more useful than a broad prompt such as “control my phone.” It separates the inquiry, authority, execution, and observed result without assuming that Grok Bot’s limited phone-app access includes the local dialer.

Use a Grok model inside FoneClaw

In FoneClaw, Grok can be used as a reasoning model when the user configures a compatible endpoint. A consumer Grok subscription and the Grok API developer service are separate routes, so check the provider account, API billing, base URL, key and model ID before assuming one covers the other. Consumer subscription fees do not cover Grok API usage in FoneClaw; that usage is billed separately by the API provider. For setup details, Connect an AI Model API to an Android Phone Agent in FoneClaw explains how to add and check a compatible model provider.

Our configured default model or an optional compatible model interprets the request and helps plan the next step. FoneClaw handles the Android side through supported tools, actual phone permissions, the configured approval policy and visible results. An online model may receive selected task context. This does not connect FoneClaw to a remote Grok Bot thread, and an API key does not grant an Android calling role.

FoneClaw's supported phone tools require exactly one phone number or one unique contact for dialing assistance, with explicit user approval. Resolve ambiguous matches first. Opening or prefilling the system dialer is preparation only; an open-only request must stop there. Only when you asked to place the call can available screen operations inspect the dialer and tap Call. An opened screen or tap alone does not prove connection: check the recipient and actual call state. Clearer approval and failure feedback helps identify a blocked step without claiming that every FoneClaw action uses the same prompt.

You conduct the connected conversation. We do not supply a cloud phone number, speak autonomously to the recipient, or automatically answer incoming SIM calls.

Use a clear request such as Call Jordan from my contacts. If you only want to check the contact, say Find Jordan in my contacts and show the matching contact, but do not dial. Those are different tasks: the second is a lookup and must not place a call. Grok Bot’s service-call terms do not establish automatic Android SIM incoming-call answering.

Choose the setup that matches the result

Choose by outcome. Use Grok AI when you want chat, voice conversation, media generation or image understanding inside Grok. Use Grok Bot for its cloud task experience or documented limited phone-app access when available for your account and setup; verify calling access separately if that is the task. Use the Grok API when you are configuring a developer model endpoint. Use FoneClaw when the goal is a supported Android action powered by a configured model and verified on the phone.

• Conversation: Open Grok AI and use chat or voice.
• Bot work: Use Grok Bot for task threads and review the result it returns; closing the app does not necessarily stop cloud work.
• Bot phone-app action: Use your own chat with a Bot you own, keep the app open in the foreground, and check permissions, team rules, Auto Review and the actual app result.
• Bot service call: Confirm actual access, a consenting recipient, the inquiry boundary, configured authority, and the service result.
• Default assistant: Check Android Settings and test the assistant entry point on the exact phone.
• No-call contact check: Ask to identify or show one contact and explicitly prohibit dialing.
• Handset outgoing call: Use one resolved consenting contact or exact number, confirm the target, authorize the call and observe the call state.
• Incoming SIM call: Look for documented Android incoming-call support before expecting automatic answering.
• FoneClaw route: Choose a supported Android action, use the configured default or compatible model, and verify the result.

The practical answer is not one universal Grok claim. Grok can be a conversation app, a Bot with cloud work and limited phone-app access, or a model provider. FoneClaw can use a configured model to assist supported Android actions, including approved local dialing with the conversation left to you. Choose the execution route that matches your intended result and verify it there.