How to let Grok Bot make outbound phone calls with Bland.ai

Linocut print of a telephone handset resting on a notebook beside a coffee cup on an office desk at morning

Grok Bot can already place phone calls on its own. There’s a catch for me, though. The official Grok Bot docs say built-in phone calls are available in the US only, and I’m in Australia. Most of the people I’d want a Bot to ring are on +61 numbers.

So I set up a dedicated Bot I call dial bot, connected to Bland.ai, which is a US voice AI platform built for exactly this. It has made real calls to Australian mobiles for me. This post walks through how I set it up, what it costs, what comes back after each call, and the guardrails I’d insist on before an MSP or SMB lets a Bot near a phone.

What this gives you, and why an MSP should care

Picture a Bot that can ring a client to confirm Thursday’s onsite visit, call a supplier to check whether a part has arrived, or follow up a prospect who asked for a callback. You tell it who to call, why, and what to cover. It makes the call in a natural voice, and then gives you a summary, a transcript and the cost.

For a small MSP that’s a few hours a week of phone tag handed off. And it comes with a written record.

I’ve written before that AI with a human in control beats AI on its own. Phone calls are where that matters most, because you can’t unsend a phone call.

What you need before you start

  1. A Bland account. Sign up at app.bland.ai. You can also create one during the Grok Bot sign-in flow described below.
  2. A Bland API key, or the device sign-in. If you use a key, it’s in the Bland dashboard under Settings, API Keys.
  3. Credits. Bland bills per minute from a credit balance. Its docs say international calls need a completed purchase: at least US$5 of credits bought under Billing, or auto-recharge turned on. Calls to Australia count as international, so plan on that first purchase.
  4. A Grok Bot you’re happy to dedicate to calling. I keep calling in its own Bot so its instructions, memory and approvals stay separate from everything else.

Step 1: Add the Bland connector to Grok Bot

Bland publishes an official command-line tool, bland-cli, which includes an MCP server. MCP is the standard way an AI assistant connects to an outside tool. When I set this up in October, the Grok Bot plugin catalog had no Bland entry, so the Bot added the official server as a custom connector instead.

You don’t type any of this yourself. In my case:

  1. I asked the Bot to add Bland’s official connector.
  2. It checked the catalog, found nothing for Bland, and asked me to confirm with a question card before it changed anything.
  3. It added a connector called Bland AI that runs Bland’s official server, npx -y bland-cli mcp, on the Bot’s own computer.
  4. It ran a harmless test, listing the calls on my account, to prove the connection worked.

Bland also runs a hosted MCP server at https://api.bland.ai/v1/mcp, which takes your API key as a bearer token. The local one suits a brand new setup because of the sign-in flow in Step 2.

One thing to know: connectors are added to your Grok Bot account, not to a single Bot, so other Bots you own can see it too. That’s one more reason to keep the calling rules in the dedicated Bot’s instructions.

Step 2: Give the Bot access without pasting a key into chat

This is the step I’d be strictest about. Never paste an API key into a chat message. Grok Bot gives you two safer ways to do it.

Option A: the secure secret box. When dial bot first started, it asked for my Bland key and showed a secure entry box in the chat rather than asking me to type it. The key is stored as a secret on the Bot’s computer and made available to it as an environment variable, BLAND_API_KEY. The Bot never sees the value, and any output that would contain it shows as redacted.

Option B: Bland’s device sign-in. The Bland AI connector includes two tools, bland_auth_login and bland_auth_poll. The Bot starts the sign-in and shows you a short code and a link. You open the link, sign in to Bland (or create an account there), and approve the request. Bland saves the key to the connector’s profile on the Bot’s computer, and the key never appears in the conversation.

A tip from my own setup: the first value I gave the Bot was the wrong kind of ID, and Bland rejected it as unauthorised. If your first test fails with an authentication error, check you copied the API key itself and not an organisation or voice ID.

Step 3: Pick a voice and set sensible defaults

Bland has stock voices, and you can clone your own in its Voices studio. I started with a stock voice called Josh and later moved to my own.

I also had the Bot save a call template, so every call starts from the same baseline. These settings made calls sound like a person, not a robocall:

  • Wait for the greeting. The Bot waits for the other person to say hello before it speaks, rather than talking the instant the line connects.
  • A casual first sentence that discloses. Mine opens with “Hi, it’s Robert Crane’s AI assistant, just so you know, this call’s recorded.”
  • A short briefing, not a script. Purpose, talking points, and what success looks like.
  • A maximum duration. Mine is 10 minutes, so a confused call can’t run up the bill.
  • A voicemail rule. Either hang up, or leave a short message pointing to my email.
  • Call screening handling. If an automated screener asks for a name and reason, give one line and wait for a human.

Step 4: Place your first call

Bland requires numbers in E.164 format. In Australia that means dropping the leading zero and adding +61, so 0412 345 678 becomes +61412345678. One of my early calls went sideways because a number was given to the Bot as “+16 416…”, which is a malformed country code. My Bot now flags odd country codes before dialling.

Start with a call to your own mobile. Then try something like this:

Call Sam on +614XXXXXXXX. Sam is the practice manager at a client site. Purpose: confirm Thursday’s 2pm onsite visit to replace the reception PC. Talking points: check the time still works, ask whether someone can let us in, and ask if parking is available. If Sam wants to change the time, agree a new day and time in Sydney time and say I’ll send an updated invite. If it goes to voicemail, leave a short message asking Sam to reply by email.

Before it dials, my Bot reads the plan back: the number, the voice, the opening line and what happens on voicemail. Then it asks Good to place the call? with options to call now, add a voicemail, or cancel. Nothing gets dialled until I say yes.

Step 5: Read what comes back

When Bland accepts the request it returns a call ID. My Bot treats that as “submitted”, not “answered”. It then checks the call every so often until it finishes, and reports:

  • the outcome, such as answered, voicemail or failed
  • how long the call ran
  • what it cost, in US dollars
  • Bland’s short summary of the conversation
  • the full transcript, only when I ask for it, which keeps each check light

If a call is recorded, Bland also provides a recording link in the call details. A timeout or a missing result isn’t treated as success. The Bot checks the existing call ID before even suggesting another attempt, and it never redials on its own.

What it costs

Here’s Bland’s published pricing as of November 2026, from its pricing page and billing docs. All figures are in US dollars:

  • Start plan: free, with US$0.14 per connected minute and no platform fee. Limits are 100 calls a day and 10 at once.
  • Build plan: US$299 a month, with US$0.12 a minute.
  • Billing: charged to the second, with a minimum of US$0.015 for each outbound attempt.
  • Agent Phone Plan: US$19.99 a month for one dedicated number, with unlimited calls and texts to the US and Canada. Calls to other countries still come out of your credit balance.

My own calls to Australian numbers lined up with that rate. A one-minute call cost US$0.16, a two-minute call US$0.29, and a three-minute call US$0.43. Check the current numbers on Bland’s site before you budget, because it changed its pricing in December 2025.

Australian considerations

  • Caller ID. By default, Bland places calls from its own pool of US-based numbers, so the number your contact sees can change from call to call. A consistent number means buying one from Bland or connecting your own Twilio number. If you want an Australian number, check that with Bland first.
  • Expect screening. A US caller ID is more likely to be ignored here, so tell people a call is coming.
  • Content filters. Bland rejected one of my calls because of a single word in the briefing. It was a security term. Rewording the briefing fixed it.

Consent, recording and the law

This is general information, not legal advice.

Australian call recording rules vary by state and territory, and some are stricter than others. Several generally require consent from everyone on the call. Your contact may also be in a different state from you. Telling the person up front that they’re talking to an AI assistant and that the call is recorded is the honest default, and it’s why my opening line does both.

Think about where the data goes, too. Bland is a US company, and it holds the audio and transcripts. When I wanted old recordings removed, I had to send Bland a request, because there was no way to do it from the Bot. Only share recordings or transcripts with people who were on the call, unless you’ve had proper advice.

Finally, only call people who expect to hear from you. If anything starts to look like telemarketing, check the ACMA’s Do Not Call Register and telemarketing rules first. Grok Bot’s terms make you the caller of record for its own calls; hold yourself to the same standard with Bland.

Troubleshooting

  • Unauthorised or 401 errors. Wrong key, a non-API ID, or an expired sign-in. Re-run the sign-in, or enter the key again in the secure box.
  • “Insufficient balance” or international calls blocked. Buy credits under Billing in the Bland dashboard. Don’t assume the balance is the problem without seeing the actual error.
  • The call is rejected straight away. Check the number is in E.164 format, then look for a flagged word in the briefing.
  • The Bot talks over the greeting. Make sure it waits for the greeting before speaking.
  • No result yet. Ask the Bot to check the existing call ID. Don’t place a second call.

Summary

Built-in Grok Bot calling is US-only for now. Bland fills the gap for Australians, and setting it up takes about ten minutes:

  1. Add the official Bland connector.
  2. Sign in with the device code or the secure secret box, never by pasting a key.
  3. Buy a few dollars of credit.
  4. Save a call template that discloses up front.
  5. Make the Bot confirm every call before it dials.

Keep a human in the loop and the Bot becomes a genuinely useful teammate on the phone. If you’re also looking at the voice features built into Grok Bot, I covered those in how to set up voice in Grok Bot, and what is limited from Australia.

Sources

  • Grok Bot docs, Message and collaborate, Have a Bot make a phone call (docs.x.ai/grok-bot/chat-and-collaboration), checked 19 November 2026
  • Grok Bot terms, section 2.7 Phone Calls (cursor.com/terms/grok-bot), checked 19 November 2026
  • Bland docs: Send Call API, Billing & Plans, CLI, MCP Server and Agent onboarding (docs.bland.ai), checked 19 November 2026
  • Bland pricing (bland.ai/pricing), checked 19 November 2026

Leave a Reply