The MSP Peer Group Killed the MSP Community

image

There was a time when the MSP community actually felt like a community.

People shared ideas because they had discovered something useful. They talked openly about mistakes. They swapped scripts, compared vendors, debated pricing and helped competitors solve problems simply because someone needed a hand.

There was no application process.

No carefully curated cohort.

No commitment to attend four meetings a year.

No requirement to reveal your EBITDA before anyone would tell you how they structured their service desk.

And, most importantly, there wasn’t always someone trying to monetise the conversation.

Then came the peer group.

And I would argue that, despite all the good they have done for individual MSPs, peer groups have slowly helped kill the wider MSP community.

First, let me be clear: peer groups work

This isn’t an argument that MSP peer groups are bad.

Quite the opposite.

For many MSP owners, joining a serious peer group can be one of the most valuable decisions they make.

A good group provides something that is incredibly difficult to find inside your own business: perspective.

You get to sit with people running businesses that look remarkably similar to yours and ask questions such as:

  • What are you charging?

  • How many endpoints does each technician support?

  • What does your gross margin look like?

  • How do you compensate salespeople?

  • Which vendors are actually working?

  • How are you structuring your service desk?

  • What would you do differently if you were starting again?

That information is enormously valuable.

The accountability can be even more valuable.

If you tell ten other MSP owners that you are going to fix your pricing before the next meeting, you have created a very different incentive from scribbling “review pricing” on your own to-do list.

Peer groups have helped professionalise the MSP industry.

But there has been a cost.

We put the best conversations behind closed doors

This is the fundamental problem.

As peer groups became more sophisticated, the quality of the private conversation improved while the quality of the public conversation declined.

The interesting discussions moved inside the room.

Someone discovers a brilliant way to restructure their agreements?

Peer group discussion.

Someone has real numbers showing why a particular pricing model doesn’t work?

Peer group discussion.

Someone discovers a major problem with a vendor?

Peer group discussion.

Someone develops a better way of running their service desk?

Peer group discussion.

It makes perfect sense for the people involved.

Why wouldn’t you take your most commercially valuable insights to the people you trust?

But multiply that decision across thousands of MSP owners and something important happens.

Knowledge stops circulating through the industry.

It circulates through tribes.

We replaced community with cohorts

There is an important difference between a peer group and a community.

A peer group says:

These are my people.

A community says:

These are our people.

That distinction matters.

Peer groups necessarily create boundaries. Membership has value partly because not everyone is inside.

The discussions become confidential.

The relationships become deeper.

The trust becomes stronger.

All of those things are individually positive.

Collectively, however, they fragment the industry.

Instead of one large MSP ecosystem, we increasingly have dozens or hundreds of overlapping micro-communities.

People know their peer group extremely well but may barely interact with the MSP down the road.

We have become better connected to our group, while becoming less connected to the industry.

The economics changed too

There is another uncomfortable truth.

Community became a business model.

MSP owners are valuable customers.

They buy technology. They attend conferences. They purchase consulting. They consume training. They influence other MSPs.

That makes an audience of MSP owners commercially valuable.

So naturally an ecosystem developed around helping them.

Consultants.

Coaches.

Vendors.

Events.

Masterminds.

Peer groups.

Communities.

None of that is inherently wrong. People deserve to be paid for creating value.

The problem arises when almost every useful interaction eventually encounters a commercial boundary.

The question subtly changes from:

“How can we help the MSP community?”

to:

“How can we monetise access to the MSP community?”

Those are not the same question.

We also became afraid of giving away the good stuff

Something else happened along the way.

Knowledge became intellectual property.

That spreadsheet could be part of a consulting engagement.

That process could become a course.

That presentation could become conference content.

That pricing model could be reserved for paying members.

That operational insight belongs inside the peer group.

Again, every individual decision is completely rational.

Collectively, however, they create scarcity where previously there was generosity.

Ironically, this happened at exactly the time technology should have made community easier.

We have Teams, LinkedIn, Reddit, Discord, Slack, YouTube, podcasts, webinars and endless ways to communicate.

The MSP industry has never had more communication channels.

Yet sometimes it feels as though we have less genuine conversation.

The newcomers pay the highest price

Established MSP owners may not notice the change.

They already have networks.

They know who to ring.

They belong to private groups.

They see each other at conferences.

But imagine entering the MSP industry today.

Where do you go?

Many of the industry’s best conversations are happening behind doors you don’t yet know exist.

And even if you find the door, there may be a significant price of admission.

That creates a strange ladder:

Build an MSP → become successful enough to join the right group → gain access to the knowledge that helps successful MSPs become more successful.

The people arguably most in need of community can therefore be the people least able to access its best conversations.

Vendors helped accelerate it

Vendors also discovered the power of community.

Build a partner program.

Create a user group.

Sponsor a community.

Host an event.

Fund a peer group.

Create an advisory council.

None of these things are necessarily cynical. Many produce genuine value.

But they also create gravitational fields around vendors.

People who once identified primarily as members of the MSP community increasingly become members of ecosystems.

The Microsoft MSP.

The ConnectWise MSP.

The Kaseya MSP.

The HaloPSA MSP.

The Pax8 MSP.

The Huntress MSP.

Again, those communities can be excellent.

But each additional orbit fragments the broader conversation a little further.

The irony is that MSPs desperately need a wider community

The challenges facing MSPs increasingly extend beyond individual businesses.

Cybersecurity threats don’t care which peer group you belong to.

Artificial intelligence is reshaping services for everyone.

Microsoft platform changes affect thousands of partners simultaneously.

Vendor consolidation affects the entire channel.

Regulation, cyber insurance, privacy obligations, skills shortages and changing customer expectations are industry-wide issues.

These problems require something bigger than a table of twelve MSP owners.

They require a functioning professional community.

And that community needs places where someone can say:

“We learned something important. Here it is. You don’t owe us anything.”

Perhaps peer groups didn’t kill the community

Maybe that headline is unfair.

Peer groups didn’t deliberately kill the MSP community.

They simply solved one of its biggest weaknesses.

They created trusted environments where MSP owners could have conversations that were difficult to have publicly.

The problem is that they solved it too well.

We moved trust inside the walls.

We moved insight inside the walls.

We moved vulnerability inside the walls.

And eventually much of the value moved inside the walls too.

The answer isn’t to dismantle peer groups.

It is to rebuild the commons outside them.

We need to start giving something back

If you belong to an MSP peer group, keep it.

If you have a trusted circle of MSP owners, treasure it.

If you pay for coaching and get value from it, fantastic.

But perhaps every MSP professional should also deliberately contribute something to the wider industry.

Publish the script.

Share the lesson.

Explain the mistake.

Answer the beginner’s question.

Write the blog post.

Record the video.

Challenge the vendor publicly when necessary.

Tell people what worked.

And sometimes, give away the really useful thing rather than saving it for the room.

Because a strong peer group can make twelve MSPs better.

A strong MSP community can make the whole industry better.

We became very good at building the first.

Perhaps it is time we started rebuilding the second.

What Happens to Community When Everyone Has Their Own AI Bot?

Technical professionals working individually at laptops while two colleagues talk together in the background

For many routine technical questions, asking a bot now feels quicker and more useful than posting in a forum and waiting. The answer arrives in seconds and is shaped to my exact situation. So it is worth asking a harder question. When everyone is wrapped up in their own AI assistant, what happens to the technical communities we used to lean on?

The fix nobody else sees

Picture an admin chasing a Teams policy that refuses to apply to a group of users. They ask their bot, get a PowerShell snippet, adjust it for their tenant, test it, and the problem goes away. Except the context, the dead ends and the test results now live in one private chat. Nobody else learns that the policy needed time to replicate, or that the first script would have hit the wrong users.

In the old forum model, that same question would have been public. Someone would have answered, someone else would have corrected them, and a dozen silent readers would have filed it away for later. The value was the visible reasoning, the disagreement and the record left behind.

AI assistants draw heavily on shared documentation and published knowledge. If more of the hard-won lessons stay private, I wonder what the next generation of answers, human or machine, will have to work from.

Support was only part of the point

Forums and user groups were never only help desks. Asking a question was how many of us met people, found mentors, and earned a reputation by giving good answers. A good AI answer is helpful. It does not automatically create trust, judgement or belonging, and it cannot be accountable for the advice in the way a respected peer is.

I am not arguing that people should wait longer for help to keep forums busy. I wrote earlier that AI isn’t killing human engagement, lazy humans are, and I still think the choice sits with us rather than the tool.

What brings people together now?

If quick answers stop being the main reason to show up, communities need a different reason. A few that seem worth the effort:

  • Share tested conclusions, not raw AI output. After the bot helps you fix an Entra or Intune problem, post a short, sanitised write-up of what actually worked, what failed and why. Strip out customer names, tenant details and secrets.
  • Work on real problems together. Live troubleshooting, shared labs and reviews of each other’s scripts build the kind of judgement a private chat rarely does.
  • Make human conversation deliberate. Mentoring, user groups and small peer circles have always taken effort. Now they need someone to deliberately organise them.
  • Earn attention. Bolting a chatbot onto a forum does not make it a community. People return where they find insight and people they respect.

Picture a group of MSP peers comparing what their bots suggested with what actually happened in a Microsoft 365 tenant. One fix worked, another broke sign-ins, a third needed a licence nobody mentioned. That is the conversation worth having: verified evidence, context and judgement that others can question, not more autogenerated answers. It is the kind of shared capability that lasts.

The choice in front of us

If technical communities weaken, it may not be because AI has failed. It may be because it handles enough routine questions that we have fewer practical reasons to talk to each other. That leaves the harder, more human reasons to gather, and those only survive if people choose to contribute.

So when your bot hands you the answer in thirty seconds, what will you give back to the people who might hit the same problem tomorrow?

CIA Brief 20261121

image

Security

Microsoft 365 & Windows

  • The Great Exchange Online Meltdown of November 2026
    Tony Redmond goes through the Exchange Online outage: Microsoft’s preliminary post-incident report puts EX1550543 at 23 hours and 50 minutes, with a separate incident (MO1550821) covering the knock-on effects on other Microsoft 365 services. It’s a good, clear account to share with clients who want to know what happened. It’s also a reminder to agree how you’ll communicate with clients before the next big outage.
    https://office365itpros.com/2026/11/16/exchange-online-outage-nov26/
  • Copilot at Microsoft Ignite: Expanding what’s possible with intelligence built for work
    This is the main Copilot announcement from Ignite. Home (Chat and Cowork together), Office in Copilot and Copilot Managed Runtime are now GA, Copilot Code is coming in the next few weeks, and Autopilot is starting to roll out to Frontier customers. Auto routing now picks the model and effort for each task, so expect more ‘which model is it using?’ questions from clients.
    https://www.microsoft.com/en-us/copilot/blog/2026/11/17/copilot-at-microsoft-ignite-expanding-whats-possible-with-intelligence-built-for-work/
  • Office at Ignite 2026: From apps to agentic system of work
    Office in the Copilot app is now generally available, so users can go from a chat to a Word draft or a PowerPoint deck and then hand off to the full desktop apps. Today, Pages and Workspaces aim to make Copilot more proactive and collaborative. Worth a look for anyone planning Copilot training, because where users start their work is shifting.
    https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/office-at-ignite-2026-from-apps-to-agentic-system-of-work/4572226
  • Autopilot: meet your trusted personal teammate
    Autopilot is Microsoft’s always-on personal agent. It has its own identity, memory, workspace and cloud computer, works in Teams and Outlook, and can run routines without being asked. Still early (it’s only rolling out to eligible Frontier customers with a Copilot licence), but it’s the agent with its own identity that you’ll need to govern in client tenants.
    https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/autopilot-meet-your-trusted-personal-teammate/4572611
  • The End of Starting Over: How Work IQ helps Copilot understand you and your work
    Work IQ is getting better memory and context, so Copilot remembers your preferences and picks up where you left off instead of being re-briefed every session. That should make Copilot more useful day to day. It also means clients should know what Copilot remembers and how they can manage it.
    https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/the-end-of-starting-over-how-work-iq-helps-copilot-understand-you-and-your-work/4571169
  • Copilot that understands your organization: Introducing people and org context in Work IQ
    Work IQ adds governed people and org context, so Copilot and Cowork can answer questions about teams, structure and skills from authoritative org data. Microsoft admits the answers fall short when people data is poor. Good reminder to clean up Entra profile fields like manager, department and job title before clients expect this to work.
    https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/copilot-that-understands-your-organization-introducing-people-and-org-context-in/4573356
  • MC1536065 – Microsoft 365 Copilot: Suggestions to continue in another Copilot experience
    After a chat prompt, Copilot will suggest switching to a better-suited mode such as Cowork and carry the conversation context across. It’s on the web, rolling out from mid-November 2026 for Standard and mid-December for Deferred audiences, with no admin action needed. A heads-up for helpdesk teams before users start asking why Copilot is suggesting a switch.
    https://mc.merill.net/message/MC1536065
  • MC1552389 – Microsoft 365 Copilot: Workforce Intelligence plugin available in Copilot Cowork
    A Workforce Intelligence plugin in Cowork lets leaders explore org structure and skills in plain language, respecting existing data permissions. Note the limited rollout: it’s only for tenants enrolled in Frontier, needs admin setup, and Microsoft says it isn’t for employee evaluation or performance management. Most SMB clients won’t see it yet.
    https://mc.merill.net/message/MC1552389
  • Rethinking Windows management for modern IT
    Windows Autopatch gets more control over update approvals, with quality update policies that let you choose automatic or manual approval for security, preview and out-of-band updates. Microsoft also points to hotpatch for no-restart security updates and to driver status in update decisions. Worth a look if you’re still patching client fleets by hand.
    https://techcommunity.microsoft.com/blog/windows-itpro-blog/rethinking-windows-management-for-modern-it/4572664
  • How to Update All Apps on a Windows Device with Winget
    My latest step-by-step guide to updating every app on a Windows device with winget. It covers checking winget is installed, listing and upgrading apps, silent switches, pinning apps you don’t want touched, and scheduling. A quick, free way for MSPs to close the third-party patching gap.
    https://blog.ciaops.com/2026/11/19/how-to-update-all-apps-on-a-windows-device-with-winget/
  • Microsoft Ignite 2026 Book of News
    Every key Ignite 2026 announcement in one interactive guide, grouped by topic. It’s a lot to get through, so use it as a reference rather than reading it end to end. Good for checking the detail on anything you hear about from vendors or clients this week.
    https://news.microsoft.com/events/ignite/2026/book-of-news/

Cloud & AI

  • Seven new world class models at scalable price-performance
    Microsoft AI released seven models at Ignite, including MAI Code 2, MAI Cyber 2 Flash, MAI Image 2.7, MAI Realtime 1 and Decision 1.1, all pitched on cost per task. Microsoft claims MAI Code 2 reaches 96% of Opus 5.5’s performance at 5% of the price. Those are vendor benchmarks, so test them yourself, but the cost of running agents all day keeps falling.
    https://microsoft.ai/news/microsoft-ignite-2026/
  • I ran MAI Image 2.7 through my usual espresso machine test
    My latest image model comparison, adding MAI Image 2.7 and MAI Image 2.7 Flash to my espresso machine test, with the results side by side. I also cover what Microsoft has actually published about the models and what that means for businesses already using Copilot. Useful if you’re choosing an image model for business work.
    https://blog.ciaops.com/2026/11/18/i-ran-mai-image-2-7-through-my-usual-espresso-machine-test/
  • GPT-6.2 Astra and GPT-6.2 Sol now generally available in Microsoft Foundry
    OpenAI’s GPT-6.2 Astra (reasoning) and GPT-6.2 Sol (production agents) are GA in Foundry. Microsoft says Astra gets better results with fewer output tokens at the same per-token price, so cost per task comes down. Good reminder to compare models on cost per task, not price per token.
    https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/gpt-6-2-astra-and-gpt-6-2-sol-now-generally-available-in-microsoft-foundry/4574122
  • GPT 6.2 Astra beats Sol and Opus 5.5 in my latest Cowork evaluation
    My latest Copilot Cowork model evaluation has GPT 6.2 Astra scoring 8.93, ahead of GPT 6.2 Sol on 8.78 and Opus 5.5 on 8.69. The gaps are small, and I explain what the test does and doesn’t show. Worth a look before you pick a default model for research-style work.
    https://blog.ciaops.com/2026/11/19/gpt-6-2-astra-beats-sol-and-opus-5-5-in-my-latest-cowork-evaluation/
  • Continuous improvement comes to Microsoft Foundry
    Foundry can now feed agent traces and user feedback back in, then find and test improvements and show the trade-offs in quality, speed and cost before you choose what ships. Options range from small skill tweaks to retraining model weights. Still early for most SMBs, but it’s the right model: agents that get better with use, with a person deciding what changes.
    https://azure.microsoft.com/en-us/blog/continuous-improvement-comes-to-microsoft-foundry/
  • Introducing Gemini 4 Neon
    Google’s Gemini 4 Neon is a fast frontier model aimed at software engineering, knowledge work and science tasks. It’s priced at $3 per million input tokens and $15 per million output tokens, with a 1 million token context window. Another strong option outside Microsoft’s stack, and pressure on everyone’s pricing.
    https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
  • Orchestrator: One API for reliable inference
    Perplexity’s Orchestrator puts open-weight and proprietary models behind one API that accepts OpenAI and Anthropic request formats. If a provider errors, rate-limits or times out, it retries on another deployment of the same model, such as Claude on AWS Bedrock. Worth a look if you’re building client automations and a single provider outage would break them.
    https://www.perplexity.ai/hub/blog/orchestrator-one-api-for-reliable-inference
  • Building an accounting team with Grok Bot
    SpaceXSI describes five Grok Bots that each own an accounting job end to end: provisioning, billing, billing support, cash applications and collections. A person only gets involved when something needs judgement or approval. It’s a practical model for MSPs: give each bot one well-scoped process, not a grab bag of tasks.
    https://x.ai/news/grok-bot-accounting
  • How to set up a Microsoft 365 help desk bot in Grok Bot, safely
    My latest guide to building a Microsoft 365 help desk bot in Grok Bot, with the safety rules first. It covers scope, connectors, Entra app registration, skills, routines, Teams, approvals and the extra care needed across multiple tenants. The bot takes the first pass, so your people spend their time on the problems that need judgement.
    https://blog.ciaops.com/2026/11/21/how-to-set-up-a-microsoft-365-help-desk-bot-in-grok-bot-safely/
  • How to let Grok Bot make outbound phone calls with Bland.ai
    Grok Bot’s built-in calling is US-only, so I connected a bot to Bland.ai to make outbound calls to Australian numbers. My post covers the connector, handling the API key safely, a first call, what comes back, costs, consent and troubleshooting. Worth a look if you’re outside the US and want a bot that can pick up the phone.
    https://blog.ciaops.com/2026/11/19/how-to-let-grok-bot-make-outbound-phone-calls-with-bland-ai/
  • How to set up voice in Grok Bot, and what is limited from Australia
    My latest guide to the voice features in Grok Bot: dictation, live voice chat, voice memos, phone calls and joining meetings. I’ve checked it against the official documentation and noted what’s actually limited from Australia. Spoken conversations and recorded calls need the same care as anything a bot sends in writing.
    https://blog.ciaops.com/2026/11/18/how-to-set-up-voice-in-grok-bot-and-what-is-limited-from-australia/
  • Your Grok Bot can have its own email address. Claim it carefully.
    Each Grok Bot account can claim one address at mail.grokbot.com, and plus aliases work too. My post covers how to turn it on, using it for sign-ups, and what to watch, including approval, privacy and MFA. A handy way to keep bot sign-ups out of your own inbox, if you set it up deliberately.
    https://blog.ciaops.com/2026/11/17/your-grok-bot-can-have-its-own-email-address-claim-it-carefully/
  • Grok Bot Privacy Mode: what it does, how to change it, and what that means for MSPs
    My latest look at Grok Bot Privacy Mode. It’s about model training and how model providers keep prompts, not a promise that Grok Bot keeps nothing. I cover what Cursor actually publishes, how to change the setting, and what it means if you’re working with customer Microsoft 365 data.
    https://blog.ciaops.com/2026/11/16/grok-bot-privacy-mode-what-it-does-and-how-to-change-it/
  • What MSPs should understand about Grok Bot security and customer Microsoft 365 data
    Many MSPs hesitate to point Grok Bot at a client tenant, and that’s reasonable. My post sticks to what Cursor and Microsoft actually publish about Grok Bot, Entra, Graph and partner access, and what I’ve set up in practice. If you can’t explain what a bot can reach and what happens to the data, don’t connect it to production yet.
    https://blog.ciaops.com/2026/11/15/what-msps-should-understand-about-grok-bot-security-and-customer-microsoft-365-data/
  • A Significant Increase in Digital Labor Automation
    This is from July, but it’s worth a read. The Remote Labor Index measures how often AI agents complete real paid freelance projects to a standard a client would accept, and Fable 5 reached 15.8%, roughly double Opus 4.8’s 8.3%. Still a small share of the work, but it’s climbing fast, and that’s where your clients’ process automation conversations are heading.
    https://safe.ai/blog/significant-increase-in-digital-labor-automation
  • Ignite 2026: Building the frontier ecosystem
    An edited version of Satya Nadella’s Ignite keynote, which casts Copilot as ‘the new OS for work’. He builds Microsoft’s stack around three principles: keeping human ambition at the centre, giving organisations control of their own intelligence and learning, and trust. Read it for the strategy behind the product announcements, not the detail.
    https://blogs.microsoft.com/blog/2026/11/17/ignite-2026-building-the-frontier-ecosystem/

Other

  • Annual currency adjustments to Microsoft Commercial Cloud pricing
    From 1 January 2027, Microsoft cloud prices in Australian dollars drop by about 4%, while NZD rises 10% and INR rises 15.7%. Individual SKUs may vary slightly because of rounding. Good news for Aussie MSPs and clients, so factor it into renewals and quotes that cross into January.
    https://news.microsoft.com/source/2026/11/10/annual-currency-adjustments-to-microsoft-commercial-cloud-pricing/
  • New partner benefits announced at Microsoft Ignite
    Microsoft has added more discounted AI licences to all partner benefits packages at no extra cost, and launched a new Partner Success Advanced package. Packages start at $350 a year for Partner Launch. Worth checking what’s now included, because it’s the cheapest way to run Copilot and AI internally as ‘Customer Zero’.
    https://partner.microsoft.com/en-US/partnership/partner-benefits-packages-benefits
  • Leading Frontier Transformation together at Microsoft Ignite 2026
    Nicole Dezen’s Ignite partner post covers new investment in the Microsoft AI Cloud Partner Program and pushes partners to adopt AI internally first. Microsoft’s study claims partners with high AI maturity earn 67% more partner revenue per dollar of Microsoft AI revenue. Mostly a direction-setting read, but it tells you where incentives are heading.
    https://partner.microsoft.com/en-US/blog/article/microsoft-ignite-2026
  • Anthropic starts trading on Wall Street
    Anthropic is now listed on the Nasdaq as ANT, opening at US$111.50 a share against an IPO price of US$83, which valued it at about US$1.5 trillion. Its S-1 shows US$16.3 billion of revenue in the first half of the year. Claude models sit inside Copilot, so a well-funded, public Anthropic is good for the vendors MSPs depend on.
    https://www.theverge.com/ai-artificial-intelligence/1035384/anthropic-ipo-trading-nasdaq

After hours

GTA 6’s Billion-Dollar HYpe Machine – https://www.youtube.com/watch?v=_19PHik8_Jg

Editorial

If you found this valuable, the I’d appreciate a ‘like’ or perhaps a donation at https://ko-fi.com/ciaops. This helps me know that people enjoy what I have created and provides resources to allow me to create more content. If you have any feedback or suggestions around this, I’m all ears. You can also find me via email director@ciaops.com and on X (Twitter) at https://www.twitter.com/directorcia.

If you want to be part of a dedicated Microsoft Cloud community with information and interactions daily, then consider becoming a CIAOPS Patron – www.ciaopspatron.com.

Watch out for the next CIA Brief next week

How to set up a Microsoft 365 help desk bot in Grok Bot, safely

Low-poly faceted mountain valley at dusk with a small glowing lighthouse on a distant ridge

Most small businesses I work with have the same help desk problem. The same dozen questions arrive every week: Outlook will not sync, Teams will not sign in, a shared mailbox has gone missing, where do I find this setting. A person has to read each one, find the answer, and reply. A Microsoft 365 help desk bot will not replace that person. It can take the first pass, so the person spends time on the problems that need judgement.

I run a Help desk bot in Grok Bot that can start remote support through AnyDesk from the shared Linux computer. It sits alongside a PowerShell bot post that runs my scripts, a Teams bot, and read-only security monitor bots for individual tenants. This guide is how I would set one up from scratch, with the safety rules first. I have checked the Grok Bot steps against Cursor’s published Grok Bot documentation and the Microsoft claims against Microsoft Learn. Where I could not confirm a screen or a setting, I describe it generally rather than guess.

1. Decide what the bot is for

Write the scope down before you create anything. A help desk bot that tries to do everything ends up with access to everything.

A sensible first scope is this:

  • Answer “how do I” questions from official Microsoft documentation, with a link.
  • Triage a request: ask the questions you would ask, and summarise the likely cause.
  • Run read-only checks, such as service health or a user’s licence and sign-in status, and report what it found.
  • Draft replies and ticket notes for a person to send.
  • Hand over to a human, with the details collected, when the fix needs a change.

And what it does not do at the start: reset passwords, change licences, edit mail flow, delete anything, or touch a production setting. You can move a task across that line later, one task at a time, once you trust the result.

2. Create the bot and give it a job

In the Grok Bot app, choose New Bot (the + button at the top of the sidebar) or press Cmd/Ctrl+N, then type a name and choose Create. Cursor’s documentation says to use your first message to give the Bot its job, its sources and its approval boundaries, and to ask it to remember them. I follow that. A first message along these lines works, using a fictional business:

You are the Help desk bot for Contoso Pty Ltd, a small business using Microsoft 365. Your job is first-line triage for Outlook, Teams, OneDrive, SharePoint and sign-in problems. Use Microsoft Learn first, and link the page you used. Stay read-only. Draft replies for me and never send anything to a user without my approval. Never ask a user for a password or a one-time code. If a fix needs a change to the tenant, stop, summarise the request, and ask me. Remember these rules.

Cursor’s documentation says a personal Bot keeps lasting rules in its memory, and that a Team Bot still has a description its owner or a Manager edits under About in the Bot’s details. The app’s own settings map also lists description among the per-agent settings, reached from the Bot’s name in the chat header. So I tell the bot in chat, ask it to remember, and check where the description lives in my own version of the app.

Personal bot or Team Bot?

If more than one person will use the help desk bot, a Team Bot is the better fit. Cursor says Team Bots need a Team or Enterprise plan and at least one other person on your team. You create one from the + menu, tell it its job, and follow its setup, which asks for plugins, secrets, skills and files. Until you publish it, it is a Draft that only you can see. Teammates then find it under Browse Team Bots, or you share it with the people you choose. The owner and Managers change the Bot; each person’s chat with it stays private.

There is one catch. A Team Bot uses the apps and secrets its owner added, and Cursor warns to add only what everyone you share it with may use. A shared connector lets anyone who talks to the bot act through that one account, changes included, and Cursor says to share only an account that holds nothing sensitive. That sentence matters more than any other in this guide.

3. Connect the right connectors, with the least access

Open Connect apps from the sidebar, find the app, add it, and complete the sign-in when asked. Check it appears under Installed. Cursor says a connected app can do only what the account you authorise can already do in that service, and the connection is account-wide, so every Bot you run can use it. For a help desk, the useful set is small. I use Microsoft Learn for documentation search (I wrote up connecting Microsoft Learn), plus Teams, Outlook, OneDrive and SharePoint where the help desk genuinely needs them, and a Microsoft Graph connector for read-only tenant checks.

A Graph admin connector is not in every catalog. Grok Bot lets you add a custom connector (a remote HTTPS server URL, optional headers and an OAuth client ID, or a command), and your team admin’s connector policy can block it. If your Microsoft 365 account sees a message that your organisation’s admin needs to approve the app, that is the Microsoft 365 admin approving Grok Bot, and retrying the sign-in does not help. Send them the approval link the page shows.

Entra app registration: delegated first, read-only first

If your connector uses an app registration in Microsoft Entra, create it deliberately. Microsoft Learn’s steps are to sign in to the Microsoft Entra admin center, go to App registrations, choose New registration, give it a name, choose the supported account types, register it, and record the Application (client) ID. After that the decisions that matter are the permissions.

Microsoft’s guidance on Graph permissions is to apply least privilege and request the fewest permissions the app needs. It describes two access scenarios. With delegated access the app calls Graph on behalf of a signed-in user, so it is limited to that user’s scope. With application access the app calls Graph with its own identity and no signed-in user, and Microsoft says application permissions carry the most privacy risk. So I start with delegated, read-only permissions. I move to application permissions only when unattended work needs it, and then only the read permissions that the check needs.

Never give the bot Global Administrator

Microsoft recommends fewer than five Global Administrators, with all of them protected by multifactor authentication, and two cloud-only emergency access accounts. A help desk bot is not one of the five. Be careful with Helpdesk Administrator too. Microsoft marks it a privileged role: it can change passwords and invalidate refresh tokens, and Microsoft warns that changing a user’s password can mean assuming that user’s identity, including owners of app registrations. That is exactly the sort of action I want a human to approve, so I do not give the bot that role.

If administrators have to sign in anywhere in this chain, a Conditional Access policy that requires multifactor authentication for administrators is the baseline. Microsoft’s steps say to set the policy to Report-only first, review the results, then turn it on. Note Microsoft’s warning that Conditional Access policies are not enforced for administrative-unit-scoped or custom roles, so check which roles your accounts use.

4. Give it knowledge it can cite

Microsoft Learn is the main source. I tell the bot to answer from Learn first and link the page, because a link lets the technician check the answer in seconds. For your own procedures, put the documents where the bot can read them, and for scripts point it at a repository. My scripts live at https://github.com/directorcia/Office365, and the PowerShell bot post explains how I keep script work in one bot, read-only unless I say otherwise.

Do not treat the bot’s memory as the source of truth. Cursor says to keep changing facts in the source system and ask the Bot to cite or reopen current data for consequential decisions. For a help desk, that means licence counts, policy settings and service status are looked up each time, not remembered.

5. Turn repeat fixes into skills

Cursor’s guidance is to start with a one-time task, make it reliable, save the method as a skill, and only then automate it. A good skill states when to use it, the inputs and access it needs, the sequence of work, how to validate the result, what to return, and what needs approval. Ask for it in chat. For example:

Save what we just did as a skill called “Outlook not syncing triage.” Include the questions to ask the user, the read-only checks to run, the Microsoft Learn pages to cite, the format of the summary, and the rule that any change to a mailbox needs my approval.

The ones I would build first are an Outlook sync triage, a Teams sign-in triage, and a “password reset request” skill that does not reset anything. It collects who is asking, confirms the request through a second channel and hands it to a person. Private skills are one library shared across your Bots, and on a team you can publish a skill so teammates can use it.

6. Remote support needs a human in the loop

Because your Bots share a cloud computer with a browser, filesystem and terminal, a bot can start a remote support tool there. Mine can start AnyDesk from the shared Linux computer. I would treat that as a step that needs a person’s approval every time, not something to automate. Cursor’s documentation says passwords and one-time codes should never go in ordinary chat. A bot should use a login saved in Vault, or a Secure Form, and hand you the computer for steps it cannot do itself, such as single sign-on or an approval on another device.

7. Routines for daily checks

A routine runs a saved instruction on a schedule or when something happens. Ask the bot that should own the job, in plain words, and confirm the owning bot, the schedule and time zone, the input source, the expected result, the approval boundary and what to do when the source is missing. Schedules use the timezone in Settings, under Bot. A new routine waits for its next time, and you can use Test to try it, remembering that a test does real work.

For a help desk I keep it modest:

  • A weekday morning check at a sensible hour that reads service health and open requests, and posts a short summary to me. It does not contact anyone.
  • A routine that starts when mail arrives at the bot’s own address, limited to the senders you name, that reads the request and drafts a triage note.

Each run spends usage, so a broad trigger on a busy mailbox is expensive. Cursor says to define a narrow matching rule and avoid listeners such as every new message. Email from a routine or an incoming message also waits as a draft until you press Send, which is the behaviour I want.

8. How people reach it

Microsoft Teams

This takes two administrators. Cursor’s Microsoft Teams documentation says a Cursor team admin who is also a Microsoft Teams Administrator or Global Administrator turns Teams on, once, for the organisation. The organisation has to allow custom apps in Teams. The bot’s owner or a Manager then connects it, and a Teams admin reviews and publishes it. Setup can take minutes and up to about an hour, and the app shows when the bot is ready. People should wait for ready before adding it to a 1:1 chat. In a channel the bot only receives messages that really @mention it, picked from Teams’ mention list, and it answers in the thread. Everyone who chats with it needs a Teams licence in that organisation, and guest accounts cannot add it.

The approval grants delegated Microsoft Graph permissions only. Cursor says the bot holds no application permissions in the organisation, and asks for no organisation-wide access to mail, calendars, files or Teams messages.

Email

A bot can also take requests by email. You can claim one address at mail.grokbot.com, such as contoso-desk@mail.grokbot.com (a made-up example). I covered the limits in claiming a Grok Bot email address. It is one address per account, you cannot rename or delete it, and all your Bots can use it in your own chats and routines. Plus aliases such as contoso-desk+vip@mail.grokbot.com land in the same inbox. Anyone can write to an alias, so keep a sender filter on any routine that should act only for certain senders.

9. Approvals and safety

Cursor’s Auto Review checks each action your Bot is about to take, and when one needs your OK you see an approval card showing the operation and its inputs. You can Allow once, Always allow, or Deny. Be careful with Always allow on anything that changes a tenant. Custom Rules let you add narrow Ask first rules, such as “ask first before sending any external email”. If both an Allow and an Ask first rule match, Ask first wins. Auto Review is on by default, and the Auto-review switch is in Settings, General, under Bot.

Two points are easy to miss. Auto Review treats text from an email or a web page as not being your request, which is a defence against someone emailing your help desk bot instructions. That reduces the risk but Cursor says it should complement least privilege, not replace it. And cards raised by a routine or other background work expire after 30 minutes, so an unattended routine cannot sit there with a standing approval.

My short list of rules for a help desk bot:

  • Draft first. A person sends anything that goes to a user.
  • Read-only by default. Changes need approval in the bot’s own chat, never relayed from another bot.
  • No passwords or one-time codes in chat, ever.
  • No Global Administrator, and no standing Helpdesk Administrator.
  • Pause or delete routines and revoke connectors when a project ends.

10. If you are an MSP with many tenants

This is where I am most cautious. My tenant monitor bots are read-only security monitors, one per tenant, built from the Microsoft 365 security monitor template. It is tempting to treat one bot per customer as a security boundary. Cursor says it is not: all your Bots share one cloud computer, so files, browser sessions and command-line credentials on it are available across your whole roster, and Cursor says not to use separate Bots as a security boundary. Connected apps are also account-wide. I covered the wider picture in Grok Bot security and customer Microsoft 365 data.

So the separation has to come from the Microsoft side. Use a separate, least-privilege identity per tenant, so a bot that is compromised or confused can only see the one customer it was given. For partner access, Microsoft says granular delegated admin privileges (GDAP) give partners least-privileged, time-bound access that customers explicitly grant, in place of the Global Administrator role. Use that model for any human or tool that works across customers. I would not give one shared account across tenants to a Team Bot that your whole team can talk to.

What to be aware of

  • I have not verified every Grok Bot screen. Where I name a menu, it comes from Cursor’s documentation or the UI map; anything else I have described generally.
  • A bot’s answer is only as good as its source. Make it cite the Learn page, and check anything that changes a tenant yourself.
  • Routines spend usage. Review them regularly.
  • Microsoft changes roles and consent screens often. Check the linked Learn pages before you rely on a permission name.
  • Voice and phone calling are separate topics. See my voice setup post if the help desk will take calls.

Start small

Create the bot, give it Microsoft Learn and nothing else, and let it draft replies for a week. Add one read-only check. Save the first skill. Only then add a routine, and only then think about Teams. If a help desk bot never needs more access than that, it is still saving you time, and nobody has handed an AI a master key.

Sources

Why Benchmarking Matters When AI Improves Itself

Two analysts comparing performance results side by side

One of the most exciting things about AI right now is that it can improve its own work. You can ask it to review a prompt and make it better, refine an agent’s instructions, tighten a workflow or rewrite a skill, then do it again, and again. That loop of AI improving AI is powerful. But there’s a catch that I see many people miss: if you don’t benchmark, you have no idea whether all that improving is actually making things better.

Improvement, drift or regression?

Every time AI changes a prompt or an agent, it will usually tell you the new version is better. It sounds confident. It may even be right. But a change can also be drift, where the output just becomes different rather than better, or a regression, where something that used to work quietly breaks. When the AI is making changes over and over, those small shifts compound. After ten rounds you can end up somewhere very different from where you started, without anyone ever deciding that was where you wanted to go.

Without a fixed point to measure against, every version just feels like the latest version. That’s not good enough when the output is going to customers, or running inside a client’s tenant.

Start with a baseline

Before you let AI improve anything, capture how the current version performs. That’s your baseline. It doesn’t need to be perfect, it just needs to be fixed and written down, so every future version is compared against the same thing rather than against a memory or a feeling.

Build a golden test set

A golden test set is a collection of real inputs where you already know what a good answer looks like. For an MSP that might be a set of typical help desk tickets, a handful of tricky security questions, or sample documents an agent needs to summarise. Keep it the same across versions. If you change the tests every time, you’re not benchmarking, you’re just trying things.

Include the awkward cases too. The edge cases are usually where a so-called improvement falls over first.

Measure what matters

Decide up front what better means for this job. Typically I’d look at:

  • Accuracy: does it get the right answer on the golden set?
  • Time: is it faster, or has it become slower and chattier?
  • Cost: is it using more tokens, more steps or more expensive models to get there?
  • Consistency: does it give the same quality answer when you run it more than once?

A new version that’s slightly more accurate but twice as slow and expensive may not be an improvement at all for your business. You only see that trade-off if you measure it.

Compare versions side by side

Run the old and new versions against the same tests and put the results next to each other. Version every prompt, agent and skill so you always know exactly what changed between runs. This turns arguments about whether something feels better into a simple look at the numbers you collected.

Keep a human in the loop

Numbers don’t catch everything. Tone, judgement and whether an answer is actually useful to a real person still need someone to review it. Have a human look over a sample of results before a new version goes live, especially for anything customer-facing or security-related.

Always keep a way back

Never overwrite the previous version. Keep it so you can roll back the moment something goes wrong. Recursive self-improvement is only safe when every step is reversible.

The bottom line

AI improving AI is a fantastic accelerator, but speed without measurement is just moving faster in an unknown direction. Set a baseline, build a golden test set, measure accuracy, time and cost, compare versions, keep a human reviewing and always keep the old version handy. Do that, and you’ll know your AI is genuinely getting better rather than just getting different.

How to Automatically Block External Meeting Bots in Microsoft Teams

IT administrator configuring Teams meeting protection

External AI note-takers and meeting bots are turning up in more and more Teams meetings, often invited by someone outside your organisation and often without anyone really thinking about where that recording or transcript ends up. Microsoft has been steadily adding controls for this, and the latest one is a Teams meeting policy option that automatically blocks identified external meeting bots from joining. Here’s what it does and exactly how I’d roll it out.

What’s changing

This is covered in Message Center post MC1459141 (Roadmap ID 566201). Today, Teams can already detect external bots, mark them in the lobby and require the organiser to admit them. The new option goes one step further: when it is enabled, identified external meeting bots are simply prevented from joining meetings governed by that policy.

The key points from Microsoft are:

  • It’s a new option in the existing Manage bots meeting protection settings in Teams meeting policies.
  • It is off by default. Nothing changes unless an administrator turns it on.
  • It can be assigned to specific users or groups through normal meeting policy assignment.
  • Existing bot detection and visibility for organisers and administrators stays the same.
  • Targeted Release started mid-September 2026 and was due to complete by late September. General Availability began in early October 2026 and is now expected to complete by the end of November 2026 (timeline updated 3 November).

For background, Microsoft Learn’s Manage external bots and their access to meetings page explains how detection works, using infrastructural and behavioural signals during the join process. Detection isn’t perfect, so a bot that isn’t identified can still get in, and occasionally a human may be misclassified.

Before you start

  • You need the Teams Administrator or Global Administrator role.
  • The option may not appear yet if the rollout hasn’t reached your tenant. If you don’t see it, check back later rather than hunting for a workaround.
  • I haven’t confirmed the exact wording of the new toggle across tenants, so look for the option to automatically block identified external meeting bots inside the Manage bots section rather than expecting a specific label.
  • Remember this may block note-taker and recording bots that some of your people rely on. That’s why piloting matters.

Step-by-step: enable auto-block

  1. Sign in to the Teams admin center at https://admin.teams.microsoft.com.
  2. Go to Settings & policies, then Meeting policies.
  3. Choose where to apply it. For a pilot (recommended), select Add to create a new policy, such as Pilot – Block meeting bots. To apply it to everyone, open Global (Org-wide default).
  4. Scroll to the Manage bots section.
  5. Turn on the option to automatically block identified external meeting bots.
  6. Select Save.
  7. If you created a pilot policy, assign it to the pilot users or a group. You don’t need to assign the Global policy, as it already applies to everyone without another policy.
  8. Wait a few hours for the policy to apply. Changes to meeting policies aren’t instant.
  9. Test it. Schedule a meeting as a pilot user and have an external bot try to join. It should be blocked rather than sitting in the lobby waiting for approval.

Doing it with PowerShell

If you prefer scripting, the Set-CsTeamsMeetingPolicy documentation lists an ExternalBotAccessMode parameter with three values: AllowAllBots, RequireApprovalWhenDetected (the default) and BlockDetectedBots. Using the Microsoft Teams PowerShell module:

Connect-MicrosoftTeams
New-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots"
Set-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" -ExternalBotAccessMode BlockDetectedBots
Grant-CsTeamsMeetingPolicy -Identity "user@yourdomain.com" -PolicyName "Pilot-BlockBots"
Get-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" | Select-Object Identity, ExternalBotAccessMode

As always, test the cmdlets in your own tenant first, as parameter availability can lag the rollout.

Microsoft’s recommendations

Microsoft suggests the following if you plan to enable automatic blocking:

  • Review your organisation’s use of meeting bots and automated meeting applications.
  • Evaluate the feature with a pilot group before broader deployment.
  • Review existing Teams meeting policies and decide which users or groups should receive the policy.
  • Update internal documentation and help desk guidance.
  • Communicate the change to meeting organisers and users who rely on automated meeting bots.

My take

For most businesses I work with, this is a sensible control to have, but it’s not one to flip on for the whole tenant on day one. Find out who is actually using external note-takers, pilot it with a group that isn’t, then widen it once you know what breaks. Pair it with a clear position on which AI meeting tools are approved, because blocking the unapproved ones works best when people know what they should be using instead.

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

GPT 6.2 Astra beats Sol and Opus 5.5 in my latest Cowork evaluation

Three marbled-ink circular swirls in indigo, vermilion and gold on cream, in the suminagashi style

On 13 November I called a winner in Copilot Cowork: Opus 5.5 edges Fable 5.2. That head-to-head was Opus 5.5 at 8.9 against Fable 5.2 at 8.6. I said then that I had not re-run Astra, so it was not a new overall series winner, and that I would test the next model when it turned up.

The next round is in. I have now put two new GPT 6.2 reports through the same kind of evaluation, alongside the Opus 5.5 report from September. The full evaluation is here on GitHub. The winner is not Opus 5.5 this time.

What was compared

The evaluation assessed three reports, all responding to the same underlying prompt: is the traditional MSP and TSP business model becoming obsolete between 2029 and 2036? The three documents are:

  • Document A: the GPT 6.2 Astra report from Cowork, dated 18 November 2026, written as an Australian owner and investor decision report for CIAOPS.
  • Document B: the Opus 5.5 report from Cowork, dated 23 September 2026, a strategic research report for MSP owners, Microsoft partners, boards and private equity investors.
  • Document C: the GPT 6.2 Sol report from Cowork, dated 18 November 2026, a board and investment briefing for CIAOPS.

Scoring uses four weighted criteria: Argument 35%, Evidence 25%, Detail 20% and Presentation 20%. The evaluation is relative and substance-focused.

The result

RankDocumentOverallArgumentEvidenceDetailPresentation
1A: Astra / GPT 6.28.939.29.08.58.8
2C: Sol / GPT 6.28.789.08.98.78.5
3B: Opus 5.58.698.58.79.28.5

Document A, the GPT 6.2 Astra report, comes first. The evaluation calls it the tightest on epistemic discipline, with a fully reconciled decision model and the most practical capital gates for an owner or investor audience. The Sol report is a very close second. Opus 5.5 is third, but it still wins on Detail, 9.2 against 8.5 and 8.7, because it has the broadest coverage of market, security and history.

The evaluation says A and C are both clearly ahead of B on the two heaviest criteria, Argument and Evidence. Its stated reason is that Opus 5.5 was more assertive on magnitude and probability claims than its evidence strictly supports, including the 30 to 60 per cent labour-removal figure. It also says the earlier research cut-off meant Opus 5.5 missed some later November Microsoft detail that A and C used.

Where Astra and Sol differ

The gap between first and second is small. According to the evaluation, A is tighter on capital gates, inference language and the executive reading path. C is stronger on cash-trough quantification, pricing-headroom sensitivity and residual multi-vendor service, and uses a larger reference firm. The file notes that C’s title says the traditional model is becoming obsolete, while its body concludes it remains viable. It lists that as the only notable polish issue, and says C would pass A with a title that matches the body and tighter tranche limits.

How this compares with 13 November

In Opus 5.5 edges Fable 5.2, Opus 5.5 beat Fable 5.2 on evidence (9.2 against 8.3) and detail (9.3 against 8.4), while Fable 5.2 was the more polished read. The same pattern shows up again here. Opus 5.5 is still the most detailed report and still loses points for how tightly it handles claims. What has changed is the competition: two GPT 6.2 reports, Astra and Sol, are now ahead of it on overall score.

A few cautions. This is a different evaluation from the one in the 13 November post, so the Opus 5.5 score of 8.69 here should not be set against the 8.9 there as if it were a drop. Fable 5.2 was not part of this evaluation, so I cannot tell you where it would land among these three. The file does not include credit costs, so there is no price comparison here. And this is one prompt on one topic, so it is a data point, not a verdict on every task.

I have not checked which of these models are available, or in which Microsoft 365 Copilot surfaces, for your tenant. This post says nothing about availability. Check Microsoft’s official documentation for that.

What it means for choosing models in Copilot

For an MSP, I think the useful lesson is about what you are choosing for. The evaluation rewarded the reports that were careful about what they could and could not claim, and that turned analysis into reversible, bounded decisions. That is the same quality I want in a client-facing report. A longer, broader report lost to tighter ones on the criteria that carried the most weight.

So I would not pick a model on the scoreboard alone. Run your own representative prompt, such as a client QBR, a security review summary or a pricing paper. Then judge the outputs on argument and evidence first and detail second. If you need breadth, Opus 5.5 still earned the best Detail score here. If you need something a board or an owner can act on, the GPT 6.2 reports did better in this test.

Model names matter here: Astra and Sol are both GPT 6.2, and Opus 5.5 is a different model again. Keep a record of exactly which model produced each output when you compare, because they change quickly and the winner changes with them.

As soon as the next model shows up in Cowork, I will run it through the same test.