Guides

How to connect Grok Bot to your support inbox and let new customer messages wake it up

Connect Grok Bot to your support inbox as a custom MCP connector, set its rules with 5 questions, and let a webhook wake it when a customer writes, instead of a schedule that spends usage on empty runs.

Deskwoot Team13 min read
Contents
  1. Before you start
  2. How custom connectors work in Grok
  3. Step 1: Add Deskwoot as a custom connector
  4. Step 2: Answer the 5 setup questions
  5. Step 3: Let new work wake Grok
  6. Step 4: Let Fynn hand live chats to Grok
  7. Test it before a customer does
  8. Starting from X with @bot
  9. What it costs
  10. What Deskwoot cannot control
  11. Try it with one test conversation

A customer writes at 9:02 to ask where her parcel is, and the Grok Bot you connected to your inbox does not notice. A routine that checks every few minutes would catch her, but most of its runs find nothing and still spend usage.

This guide connects Grok Bot to Deskwoot, sets its rules with 5 questions and lets a webhook wake Grok only when there is work.

Before you start

  • A Grok Bot of your own, plus the Grok Bot app on a computer. You need the computer once, to copy the routine's webhook address, because the phone app does not show it yet (a known gap on Grok Bot's forum).
  • A Deskwoot workspace on Startup, Business or Enterprise, or in the 7 day trial.
  • The workspace owner to do the setup. When an administrator or a member connects Grok, it stays inactive until the owner approves it.
  • Ideally a Grok Bot that does support and nothing else, on a company account. The section on what Deskwoot cannot control explains why.

How custom connectors work in Grok

A custom connector gives Grok a service that is not in its catalog, through the Model Context Protocol (MCP). It only works while Grok is running: Grok calls the server's tools, and the server cannot start Grok.

The Grok side of this guide works the same for other MCP servers.

In Grok chat

For Grok chat on grok.com, xAI's connector docs describe these steps:

  1. Open Connectors.
  2. Click New Connector, then Custom.
  3. Enter the server's address and finish its sign in.

Grok then discovers the tools the server offers. The server must be reachable on the public internet.

On Grok Business and Enterprise, a team admin has to add the connector in the xAI console before members can use it (connector management).

In Grok Bot

Grok Bot has no form for this. You ask the bot in its chat to add the MCP server, and it confirms the details and sets it up, as an answer on Grok Bot's forum explains.

The server has to be public here too, because the bot runs in the cloud.

API key or OAuth

How the server signs Grok in matters. Some servers want an API key pasted into Grok.

Deskwoot uses OAuth: Grok opens Deskwoot's own sign in page, you approve the connection there with your password, and there is no key to copy. If you stop the agent later in Deskwoot, it loses its sign in at once.

Step 1: Add Deskwoot as a custom connector

  1. In Deskwoot, open AI teammates and choose Connect an AI agent. The first time, an administrator accepts the data processing agreement for AI agents. Pick Grok Bot as the platform.
  2. In Grok Bot's chat, ask it to add Deskwoot as a custom MCP server: Add this MCP server: https://deskwoot.com/api/mcp. Grok confirms the details and opens Deskwoot's sign in.
  3. Sign in with your Deskwoot login if the page asks for it, and pick the workspace Grok should work in.
  4. Make your choices on the consent page, tick the statement, enter your password (plus your authenticator code if your workspace uses one) and click Connect.

For a first setup we recommend these choices:

  • "As its own AI teammate (recommended)". Grok gets its own name in your team, and customers see that name on its replies.
  • "Only drafts" for what Grok may send. "Replies on everyday topics" and "All replies" can come later, once you trust the drafts.
  • Your inboxes, with "Reads every conversation in its inboxes" left off. Grok then reads only its own work: conversations assigned or handed to it or its team, and those where someone mentions it.
  • "Look up orders and propose refunds" left off too. Even when it is on, a person makes each refund.

The choice of what Grok may send and both switches appear only if you are already signed in to Deskwoot in that browser. If you sign in on the consent page instead, Grok starts on drafts only, reads only its own work, and refunds, cancellations and other money actions stay off. An administrator can change that later on Grok's page under AI teammates.

Step 2: Answer the 5 setup questions

Once Grok is connected, Deskwoot shows a sentence to copy into Grok's chat:

Use the Deskwoot connector: call onboarding_start and go through the onboarding with me.

Grok then asks 5 questions, one at a time, with options to tap or room for your own words:

  1. How much should I take on? (Only sort conversations and leave notes, also prepare replies as drafts, or also answer customers myself.)
  2. Which other topics should wait for a person? (Billing, legal questions and complaints, account security and data protection wait from the start.)
  3. Which tone should I write in?
  4. Who takes over when I escalate a conversation?
  5. What must I never promise?

How to answer them

Pick "Also prepare replies as drafts" as the first job, even if Grok should answer customers later. Every draft you fix shows a gap in its instructions before a customer sees it.

Under the topics that wait for a person, add the ones where a wrong answer costs money, such as shipping times, returns or discounts.

For escalations, name the person who really owns those cases, because "the whole team" often means nobody.

Approve the rules

From your answers Grok proposes its rules. They wait on Grok's page under AI teammates until a person approves them, and until then Grok writes drafts only, whatever you picked on the consent page.

You can also skip the questions and click "Go live with these rules" to start with the standard rules.

Step 3: Let new work wake Grok

Connected and onboarded, Grok still does nothing until something starts it. Grok Bot runs unattended work through routines.

According to xAI's routines docs, a routine starts on a schedule, on an event from apps like Slack or GitHub, from an email or from a webhook.

Why a schedule costs more

A schedule is the obvious choice and the expensive one. The same docs say "Routine schedules must be at least five minutes apart", which still means 288 runs a day.

They also say each run spends usage and warn that a short interval can use a week of usage in a day. Most of those runs would find an empty queue.

Routine every 10 minutesWebhook routine
Runs on a day with no new work1440
When Grok starts on a handed over chatat the next run, up to 10 minutes laterwhen Deskwoot sends the wake

Set up the webhook routine

When the questions are done, write this to Grok:

Use the Deskwoot connector: call whoami and set up the Deskwoot routine with a webhook trigger.

Grok creates the routine with an instruction Deskwoot hands it (work the waiting conversations one at a time, then stop), so you write none yourself. Then copy the routine's address and key:

  1. Open Grok Bot on your computer, click the bot's name at the top, then Details.
  2. Under Routines, click the Deskwoot routine and find its Webhook section.
  3. Copy "POST to" and "Key". Skip "Header", which is the key again with "Authorization: Bearer" in front.
  4. In Deskwoot, paste both in the last step of Connect an AI agent, or later on Grok's page under AI teammates, at "Wake Grok Bot instantly".

What wakes Grok

From then on Deskwoot wakes Grok when:

  • Fynn or a person hands it a conversation, or one of its teams gets one
  • a customer writes in a conversation Grok works on
  • someone mentions Grok in a private note
  • one of Grok's replies did not reach the customer

The wake carries only the conversation's id and none of the customer's text. Grok reads the conversation through the connector, under the same read rules as before.

Deskwoot also sends one wake at a time, so a customer who sends 4 short messages in a row starts one run.

If a wake fails

Grok's page in Deskwoot shows whether the last wake worked. If it failed, check that:

  • the routine is switched on in Grok
  • the address and key match the routine's Webhook view
  • Deskwoot is still one of Grok's connectors

xAI also notes that Grok Bot "may ask whether to keep routines running after a long period away and pause them if there is no response". So after a holiday, look at the routine first.

If you would rather skip the webhook, a routine every 10 minutes with the same instruction works too, only slower.

Step 4: Let Fynn hand live chats to Grok

Fynn, the AI agent built into Deskwoot, answers live chat the moment a customer writes. Grok works more like a colleague who picks up what is handed to it.

When Fynn's knowledge runs out or only a teammate can act, Fynn hands the conversation on. The inbox's bot setting "The bot hands conversations to" decides where it goes: your team, or Grok.

Grok gets a handed over conversation only while it is present and allowed in that inbox; otherwise your team gets it. A customer who asks for a person always goes to a person.

Since Grok only takes a live chat after a handover, a customer never gets answers from 2 bots at once. Fynn's side is in Setting up the Deskwoot AI bot (Fynn).

Test it before a customer does

  1. From a private account, write to your own live chat or support address and ask something your help center does not cover, or assign the conversation to Grok yourself.
  2. Watch the wake status on Grok's page: Deskwoot woke Grok, then the last wake worked.
  3. Open the conversation. On drafts only, Grok's reply waits in the "Waiting for approval" folder with Approve, Edit and Reject.

xAI's own advice for routines is to "require approval for sending", and that is how we would run the first days.

A draft nobody decides on reminds your administrators after 4 hours and expires after 24. Then the conversation goes to your team. When the drafts rarely need edits, raise Grok's level on its page.

Starting from X with @bot

You can also tag @bot in a post on X and ask it to add Deskwoot as an MCP server for your support. Your main Grok Bot takes the post as a task, and according to xAI's @bot docs, the work and its results stay in that Bot's conversation in the Grok Bot app. You finish Deskwoot's sign in there, as in step 1. Tag @bot, not @grok: a post that tags @grok is not processed.

New to Deskwoot? Choose Create account on the sign in page, and your workspace starts with the 7 day trial. The sign in page does not take the data processing agreement itself. Open Deskwoot in your own browser, accept it in the first step of Connect an AI agent under AI teammates, then reload the sign in page or ask Grok to connect again.

When you sign in or create your account on that page, the connection starts with drafts only and reads only its own work. An administrator can change that later under AI teammates.

Countries where tagging does not work yet

xAI's @bot docs say tagging is not yet available for X accounts based in Australia, the United Kingdom, the European Union, Iceland, Liechtenstein or Norway.

X goes by the country on record for your account, and an account with only a region or no country on record is left out for now too. In those countries you start the same way in the Grok Bot app.

What it costs

Deskwoot charges no monthly fee for Grok or any other AI agent you connect over MCP. Each conversation in which Grok's reply reaches the customer counts as 1 AI conversation per window (72 hours for an email or a ticket, 12 quiet hours for a chat), from the same allowance as Fynn and Copilot and on top of them:

  • 50 AI conversations a month included on Startup, then $0.07 for each further one
  • 100 a month included on Business, then $0.05 for each further one
  • 300 a month included on Enterprise, then $0.03 for each further one

Further AI conversations are paid from your prepaid AI balance. Grok's other work in a conversation, such as a note, a label or a draft for a person, counts 0.5: a draft of Grok's that a person approves counts 0.5, and a later reply of Grok in the same window adds the other 0.5. Grok and your other agents together count at most 1 per window, and next to Fynn they add at most 0.5, so when Fynn answers and hands over to Grok, which replies, the window counts 1.5. Reading conversations never counts, and neither does a message a person writes and sends.

You can connect as many AI agents as you want on Startup, Business and Enterprise, and in the 7 day trial. When the AI conversations are used up and your prepaid balance cannot pay for another, a reply from Grok that would still add to the count waits as a draft for a person. The free Hacker plan has no AI agents. The pricing page has the full plans.

The Grok side of the bill

Each conversation window in which Grok's reply reaches the customer uses 1 of your Deskwoot AI conversations, or 0.5 when Grok only worked in it, such as a draft a person approved, on top of what Fynn uses there, as described above. The conversations it works also count toward your plan's monthly conversation limit.

Grok Bot itself is billed separately, by xAI, X or Cursor depending on the plan that gives you access (xAI's Grok Bot FAQ). With a webhook routine, its usage goes to runs that have work in them.

What Deskwoot cannot control

Where the data goes

Everything Grok reads in Deskwoot leaves Deskwoot. It goes to xAI, to Cursor and to any tool Grok passes it to. xAI's security and privacy docs say Grok Bot uses Cursor authentication and account data settings.

Deskwoot hosts your workspace data in the EU and never uses it to train AI models. Whether xAI or Cursor does depends on their terms and your account's settings.

Your company needs its own agreement for that data with whoever provides your Grok Bot.

Instructions hidden in customer messages

Inside Deskwoot, customer messages reach Grok marked as untrusted, and risky replies wait for a person whatever Grok was told.

What Deskwoot cannot stop is Grok following instructions hidden in a customer message when it acts outside Deskwoot, through other connectors such as Gmail or Slack. So run support on a Grok Bot of its own, and keep your support mailbox out of its connectors.

The rules every AI teammate follows are in letting an AI agent take real actions without losing control. Grok's daily work in a team is in our Grok Bot launch post, and the setup for other MCP clients in Connect an AI agent with the MCP server.

Try it with one test conversation

Set up this way, Grok starts only when a conversation needs it, and its replies wait for a person until you raise its level. Its usage goes to runs that have work in them.

You paste no API key and write no routine instruction. You can check the result yourself: the wake status sits on Grok's page, and the draft for your test message waits in "Waiting for approval".

To run that test, sign up at deskwoot.com/signup, open AI teammates, choose Connect an AI agent and pick Grok Bot.

Every new workspace gets 7 days of Enterprise without a card, for up to 30 seats including yours, and Grok works in the trial too.

When the trial ends, you pick a paid plan or keep working on the free Hacker plan with 1 seat. That plan has no AI agents, so Grok then needs a paid plan.

Also available in:DeutschEspañolFrançaisPortuguês (Brasil)

QUESTIONS

Frequently asked questions

How do I add a custom MCP connector to Grok?

In Grok chat on grok.com, open Connectors, click New Connector, then Custom, enter the server's address and finish its sign in, according to xAI's docs; on Grok Business and Enterprise a team admin adds the connector first. Grok Bot has no form for this: you ask the bot in its chat to add the MCP server, and it confirms the details and sets it up. Either way the server must be reachable on the public internet.

Do I need an API key to connect Grok Bot to Deskwoot?

No. You ask Grok Bot to add https://deskwoot.com/api/mcp as a custom MCP server, and Grok opens Deskwoot's sign in. There you choose what Grok may do and confirm with your password, so there is no token to copy.

Can a webhook trigger a Grok Bot routine?

Yes. Ask the Bot to add a webhook trigger, then open the routine in the Grok Bot desktop app and copy its "POST to" address and its key. A POST to that address with the key as a bearer token starts a run, and a 200 response means the run started.

How often can a Grok Bot routine run on a schedule?

xAI's docs say routine schedules must be at least 5 minutes apart. Each run spends usage, so short intervals add up: every 5 minutes is 288 runs a day, and on a quiet day most of them find nothing. A webhook routine runs only when something calls it.

Why does my Grok Bot webhook routine not start?

Grok Bot's help says any response other than 200 means no run started, and points to a paused routine or an outdated key. Grok Bot may also pause routines after a long period away if nobody answers its question. In Deskwoot, Grok's page shows when the last wake failed and what to check.

What does it cost to connect Grok Bot to Deskwoot?

Deskwoot charges no monthly fee for a connected AI agent, and you can connect as many as you want. Each conversation in which Grok's reply reaches the customer counts as 1 AI conversation, once per window (72 hours for an email or a ticket, 12 quiet hours for a chat) and on top of Fynn, adding at most 0.5 next to him. Grok's other work, such as a note or a draft that a person approves, counts 0.5 until a later reply of Grok in the same window adds the other 0.5. Plans include 50 (Startup), 100 (Business) or 300 (Enterprise) a month, and each further one costs $0.07, $0.05 or $0.03 from your prepaid AI balance. Grok Bot itself is billed separately, by xAI, X or Cursor depending on the plan that gives you access.

Blog

Browse all articles

Done reading?
Try it with your team.

Start free trialBring your channels into one inbox and let Fynn answer the routine questions. Free for 7 days, no credit card.

Deskwoot interactive demo