Grok Bot for companies

    Grok Bot in the company: Team Bots with clear approvals.

    Team Bots take work in the Teams channel, hand it on among themselves and wait for a person's approval. We introduce Grok Bot with a pilot in one department.

    For management, IT and business teams in Swiss companies who want to trial Grok Bot and keep data and approvals under control.

    • Team Bots
    • Microsoft Teams
    • Slack
    • Single sign-on
    • Audit log
    • Routines

    Team Bots at work.

    Choose a flow and play it, from the request to a person's approval.

    Sales back office9.02 am

    The Bots' screens

    • Saleswaiting
    • Customer sheetwaiting
    • Draftwaiting
    • Reviewwaiting

    History

    1. Your team · 9.02 am

      A colleague posts the customer request in the Teams channel and names the Team Bot: 40 units, delivery in January.

    Step 1 / 6

    Schematic view of an example scene. It shows how the Bots work together, not the interface of the Grok Bot app.

    Where Team Bots take work off your teams.

    Each scene shows the Bots, their handoffs and the point where a person approves.

    01

    A morning in the back office

    At nine a colleague posts the customer request in the Teams channel. The Team Bot confirms and hands out the work: one Bot compiles the customer sheet from CRM and storage, one writes the quote in your template, one compares it with price list and discount rules and reports the one deviation. At eleven the sales manager reads both, calls the customer and approves. He sends it himself.

    02

    What we set up with you

    Grok Bot signs into your tools and computes on the vendor's computers in the US. So we settle data and rights first and create the Bots afterwards:

    • Plan and enablementOn Enterprise an admin enables Grok Bot for everyone or for chosen groups; Team plans include it for every member.Result: you know before buying who can use it.
    • Sign-inSingle sign-on through Microsoft Entra, on Enterprise with SCIM for joiners and leavers.Result: whoever leaves the company also loses access to the Bots.
    • Data rulesWhich data classes may go to a service in the US, as a policy for staff.Result: personal data and secrets stay out, and everyone knows why.
    • Team BotsRoles, channels in Microsoft Teams or Slack, files and access per Bot.Result: a Bot gets only what everyone who works with it may see.
    • Approvals and evidenceRules for automatic review, plus audit log and action recording on Enterprise.Result: you can look up who triggered what.
    • Network and secretsTeam Secrets and setup scripts, if wanted access to your own network via Tailscale, which you operate yourself.Result: internal systems are reachable without facing the internet.
    • PilotOne department, two flows, measured on real cases from recent weeks.Result: you decide on the rollout with your own numbers.
    03

    What to clarify first

    Which data may leave Switzerland? Grok Bot offers no data residency in Switzerland or the EU; that belongs on the table before the pilot, with data protection and management. We also need one person from the business side who knows the flow, one from IT for access, and three real cases to measure against.

    04

    How you measure the pilot

    We measure the pilot on your cases: how long the flow took before, how long with the Bots, how many drafts passed approval without correction and where a Bot had to wait for a person. In the audit log we show you every action. Then you decide whether and where to continue.

    Grok Bot for your company

    Leave your details, we get in touch.

    Tell us in two sentences which work your Bots should take over. We get in touch, settle data, access and plan and propose a pilot in one department.

    mail@cnext.ch

    No commitment. We reply in person.

    Sound familiar? Tell us where you stand today.

    Contact

    News on Grok Bot for companies.

    As of: 21 November 2026

    • Since 3 September 2026

      Available to companies.

      The launch waitlist is gone. On Enterprise an admin enables Grok Bot for everyone or for chosen groups.

      Source: SpaceXAI: Grok Bot for enterprise
    • Since 28 September 2026

      Team Bots for whole teams.

      One Bot a team uses together, with a private chat per person. On the Team and Enterprise plans.

      Source: SpaceXAI: Team Bots
    • 11 November 2026

      Grok Bot 1.0.

      Team Bots work in Slack and Microsoft Teams, Bots join video calls and take part in the chat.

      Source: SpaceXAI: Grok Bot 1.0

    What companies ask before the pilot.

    Can we use Grok Bot as a Swiss company?

    Grok Bot has been available to companies since 3 September 2026, without a waitlist. SpaceXAI publishes no country list; whether it is enabled for your account we settle with you and the vendor before the pilot. As of 21 November 2026.

    Where is our data processed?

    In the US. The only data residency programme keeps processing and storage in the US exclusively; there is no option for Switzerland or the EU. For data that must stay in the country we show you agents that run in your tenant or on your own hardware.

    Does Grok Bot work with Microsoft 365?

    Team Bots work in Microsoft Teams once an admin turns on the connection and approves each Bot in the Teams admin centre; sign-in runs through Microsoft Entra. What works with Outlook and SharePoint in your environment we check in the pilot; where a connector is missing we connect through an MCP server of your own.

    Are the Bots separated from each other?

    Between people yes: each person has a dedicated, isolated computer. One person's Bots share that computer with its files and logins; the vendor itself says separate Bots are not a security boundary. A Team Bot has a computer of its own, and whatever it is given is open to everyone who uses it.

    What does Grok Bot cost for a team?

    Team seats cost the same as the individual Premium, Super and Ultra plans per the announcement of 12 October 2026; Enterprise on request from the vendor. The licence runs directly there. We quote our effort for the pilot after the first conversation.

    What if a Bot makes a mistake?

    That is why the flows end with a person. In the pilot, quotes, emails to customers and orders go out only after approval, and every action is in the log. Where a mistake would be costly the Bot stays with preparing.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.