Connect channels on monday service AI

Who can use this feature
gray-cloud.svgAvailable on monday service

Channels are the pathways through which incoming requests reach your Tickets board. Each channel you connect brings requests in from a different source, whether email, a form submission, a portal chat, or Microsoft Teams, and turns them into tickets your team can act on.

 

Available channel types

monday service supports the following channel types. Each one connects to a Tickets board and routes incoming requests into the Unassigned tickets group on that board.

  • Service Inbox: a built-in monday service email address created and managed directly in the platform
  • Gmail: turns incoming emails from a Gmail inbox into tickets
  • Outlook: turns incoming emails from an Outlook inbox into tickets
  • Outlook shared mailbox: turns emails sent to a shared address (such as hr@company.com) into tickets. Available on Enterprise plans.
  • Portal AI chat: creates a customer portal with AI chat so Service AI agents can handle requests automatically
  • Microsoft Teams: lets team members submit and track requests directly from Teams. Available on Enterprise plans.
  • Ticket form: turns form submissions into tickets on your Tickets board

Setup steps for each channel type are below.

 

Add a channel

Channels are managed from the Channels tab in the left pane of monday service AI. From this tab, you can view all connected channels, search and filter the list by channel type or owner, and see each channel's connected Tickets board, owner, and status.

The Channels tab listing connected channels with their Tickets board, owner, and status

 

To add a channel, select Add a channel from the top right of the Channels tab and choose a channel type. Follow the on-screen steps to complete the connection. Once connected, the channel appears in the list and begins routing incoming requests to the selected Tickets board.

The Add a channel menu showing the available channel types

 

You can also connect a channel directly from a Tickets board by selecting Channels at the top right of the board, then selecting Add channel:

The Channels button at the top right of a Tickets board with the Add channel option

 

How to create a Service Inbox

Create a unique email address that is managed directly in monday service. Each email sent to it creates a ticket on your Tickets board.

1Select Add a channel and choose Service Inbox.

2Customize the channel name and the email address (before the "@"). Select Connect channel.

The Service Inbox form with the channel name and email address fields

 

Note: Currently, you can't customize the second-level email domain (after the @).

 

3Review the confirmation, which shows a preview of your new email domain.

The confirmation screen with a preview of the new Service Inbox email address

 

The number of connected channels now appears at the top of your board. You can connect other channels to add more than one way to receive tickets.

Note: To help keep your mailbox focused on actionable requests, monday service automatically filters out certain auto-reply emails. Incoming emails that include the Auto-Submit header with the values auto-generated or auto-replied are excluded and won't appear as new incoming emails. This filtering applies to email channels.

 

How to connect an existing email

Gmail or Outlook turns each incoming email to the connected inbox into a ticket.

1Select Add a channel and choose Gmail or Outlook.

2Follow the steps on your screen to connect your email inbox.

The on-screen steps for connecting an email inbox

 

Note: When the connected email resets its password, the channel is disconnected and tickets stop entering the Tickets board.

 

When you reply to a ticket from a connected Outlook inbox, the email composer may warn that the reply may not be sent because the selected inbox isn't part of the original conversation. This can happen when the requester's original email went to a distribution list. Your mailbox may belong to that list, but because it isn't listed directly in the thread's email headers, the email composer can't confirm it as part of the conversation.

The email composer warning about the selected inbox not being part of the conversation

 

The warning is a caution. You can still send the reply, but confirm that the selected From inbox is the correct mailbox for the conversation first.

Note: If your account also uses monday CRM and applies the Never log feature to specific team members there, emails from those team members may not create tickets on your Tickets board, even though the email channel is connected and working for everyone else. If you notice this pattern, contact our support team.

 

How to connect an Outlook shared mailbox

Who can use this feature
gray-lightning.svgAvailable on Enterprise plan
Note: A shared mailbox is a specific Microsoft 365 mailbox type where sign-in is blocked by default. Access is granted to licensed users through Full Access, Send As, and/or Send on Behalf permissions. If your team's setup is a Microsoft 365 group, a distribution list, or a mail-enabled security group, it isn't a true shared mailbox and this feature won't apply. Check with your Microsoft 365 admin before connecting.

 

If your team manages requests through a shared address, such as hr@company.com or it@company.com, you can connect a Microsoft 365 shared mailbox as a channel. Every new email sent to the shared address creates a ticket, and agent replies are sent from the shared mailbox address.

1Select Add a channel and choose Outlook shared mailbox.

2In the Connect Outlook shared mailbox window, enter the shared mailbox email address and select Connect channel.

3Sign in with an Outlook account that has access to the shared mailbox. Once the connection succeeds, you see a confirmation message, and the shared mailbox appears in your connected channels list.

Note: The Outlook account you sign in with must have access to the shared mailbox. Your Microsoft 365 plan also needs to include a Business license or higher. Outlook shared mailboxes hosted on-premises aren't supported.

 

To keep in mind when connecting a shared mailbox

If you see an Email address is already in use error, the Outlook login is already connected to monday.com through another Outlook connection on your account, so the shared mailbox connection can't be completed.

The Email address is already in use error message

 

Note: You can only have one Outlook connection active at a time. If that Outlook login is already connected, disconnect the existing connection (or use a different login) before connecting the shared mailbox.

 

To disconnect the existing Outlook connection, open the Autopilot hub, select Connections, and find the Outlook connection under My connections:

The Autopilot hub Connections page with the Outlook connection under My connections

 

Remove the connection, then connect the shared mailbox again.

If you see an Approval required screen during sign-in, your Microsoft organization requires an admin to approve the connection. Ask your Outlook admin to approve the request, then try connecting again.

 

Connecting multiple shared mailboxes

To connect several shared mailboxes, combine multiple team members and multiple Outlook logins. Each team member can connect one mailbox per Outlook login, and the same Outlook login can be reused across several team members, as long as that login has delegated access to each mailbox. The number of mailboxes you can connect is your number of team members multiplied by your number of Outlook logins with delegated access.

For example, 13 team members combined with 5 Outlook logins can connect up to 65 shared mailboxes, without a separate license for every mailbox and without one admin needing delegated access to all of them.

 

How to connect Portal AI chat

Note: Adding Portal AI chat as a channel creates a new portal, which only Enterprise accounts can do. On other plans, you can activate AI chat from your account's main portal instead.

 

Portal AI chat lets you create a customer portal where requesters get help from your Service AI agents in a chat, and tickets are created automatically as the conversation happens.

1Select Add a channel and choose Portal AI chat.

2Set a portal name, URL, workspace, and Tickets board.

The Portal AI chat form with portal name, URL, workspace, and Tickets board

 

AI chat doesn't work in the portal until your Service AI agents team is active for that workspace. You can create the portal first and activate the team later. To set up AI chat, see Set up knowledge and channels for monday service AI.

 

How to connect Microsoft Teams

Who can use this feature
gray-lightning.svgAvailable on Enterprise plan

With the Microsoft Teams integration, employees can submit, track, and reply to service requests directly from Microsoft Teams. Every update is reflected in real time inside monday service.

Select Add a channel and choose Microsoft Teams. For full setup and deployment steps, see monday service Microsoft Teams integration.

How to connect a Ticket form

A Ticket form can be set up as a channel on your Tickets board to receive incoming tickets. You can send the form to requesters inside and outside your organization, and it gives you a structured way to collect all the details a ticket needs.

1Select Add a channel and choose Ticket form.

2Name the form and select the Tickets board where form submissions create tickets.

The Ticket form setup with the form name and Tickets board

 

Once the channel is connected, you can open the form's edit, design, and settings tabs. Build out your WorkForm explains how to set up a Ticket form that meets your needs.

Previewing a form while editing it

 

Pre-filling form fields makes submitting faster and more personal. With the Account pre-fill option, the email field fills in automatically when a submitter is logged into their monday.com account or the Customer Portal. For requesters who use the Customer Portal, whether name pre-fill is also available depends on how their portal account was created:

How portal account creation affects name pre-fill
  • Self-signup via an approved domain: the requester enters their name during signup, so both name and email are captured.
  • Invited via email in the Users tab: the requester enters their name during signup, so both name and email are captured.
  • Automatically created via SSO sign-in, without SCIM provisioning: only email is captured, with no name.
  • Automatically created via SCIM provisioning: both name and email sync from your identity provider. If these requesters sign in with email and password instead of SSO, they need to reset their password first, since they never set one.

 

Note: The Account pre-fill option is only available to Enterprise accounts.

 

To enable email pre-fill, open your form's edit page and select the email question's settings. Turn on Pre-fill value, select Account as the source, and select Email as the field. You can also hide this question from submitters.

The email question settings with Pre-fill value turned on, Account as the source, and Email as the field

 

To send your form, select Share form in the right corner of the screen. Select the arrow beside the Copy link button to expand the sharing options: email, WhatsApp, an embed link, or a QR code. Every submitted form becomes a ticket on your Tickets board.

The Share form screen with the sharing options

 

Edit a channel

To edit a channel, select the edit icon on its row in the Channels tab. You can update the channel name, the connected Tickets board, and the email address.

The edit options for a channel

 

Who can edit channels

On the Channels tab, anyone can view existing channel connections and create a new connection, whether the workspace is open or closed. However, only the team member who created a connection can edit that specific connection.

This means workspace type does not affect who can view or create channel connections. Editing permissions stay with the original creator of each connection.

 

How requests flow through channels

Each incoming email or form submission creates a new ticket in the Unassigned tickets group on the connected Tickets board. When a team member replies to the ticket, the reply goes back through the same channel the request came in from. All replies are maintained within a single thread, which you can find on the Ticket Overview page of the ticket. For more on how the Tickets board works, see Managing tickets with monday service.

A ticket thread on the Ticket Overview page

 

If a requester or team member sends a new email instead of replying to the thread, it doesn't appear in the ticket. A new email from a requester becomes a new ticket, even if it relates to an open one.

Note: When you send an email on the Ticket Overview page, you can upload files up to 15MB. The limit applies to both the From computer and From file column options.

 

Which data will come from the channels?

Depending on the channel, different data fills into your board automatically from an incoming ticket.

Existing email or Service Inbox

For an existing email or a Service Inbox, the board pulls data into these fields:

  • Item name: taken from the email subject
  • Description: taken from the body of the email
  • Customer name: the sender's name
  • Email: the sender's email address
Note: An email can only be connected to one Tickets board at a time. Connecting it to a new board automatically disconnects it from the previous board.

 

Ticket form

With a Ticket form, you can customize which details a requester fills in and make questions mandatory or optional. The answers go into the matching columns on your board.

 

Channels and Service AI agents

Each channel is connected to a Tickets board and linked to a workspace. Once a channel is connected to a board inside a team's workspace, that team's agents can work on requests from that channel, including email channels. If there is no matching agent, the request is routed to a human. To create a team, see Get started with monday service AI agents.

Note: If you need the same AI setup across boards in different workspaces, you currently need to recreate the team in each relevant workspace.

 

Channel health

Channel health helps you understand whether each support channel is actively receiving and processing requests. Each channel displays a status label that reflects its operational state, along with a specific action to take when attention is needed.

The status indicator appears in two places:

  • The Channels tab, which is the main channel settings page
The status indicator on the Channels tab

 

  • The Manage your channels view within a specific Tickets board, accessed via the Channels button at the top of your board:
The status indicator in the Manage your channels view on a Tickets board

 

Channel statuses

Every channel displays one of the following statuses. The table below describes what each one means and when you're likely to see it:

Status What it means Example
Connected The channel is healthy The integration is active and tickets are flowing
Setup required The channel needs attention The channel is not linked to any board
Connection broken The connection is broken An OAuth token expired or the connection owner left the company
Access revoked Shared mailbox access was removed An Outlook shared mailbox's delegated access was revoked

 

Examples of channel status labels

 

Common issues and suggested fixes

The table below covers the most common reasons a channel's status changes and what to do in each case. The right action depends on the channel type and the cause of the issue:

Issue Affected channels Status shown What to do
Channel is not linked to any board All email channels Setup required Connect the channel to a board
The board this channel was connected to was deleted or archived All email channels Setup required Connect the channel to an active board
OAuth token expired or access was revoked Gmail, Outlook Connection broken Reconnect the channel
OAuth token expired or access was revoked Service Inbox Connection broken Delete the connection
Connection owner's account was deactivated or deleted All email channels Connection broken Delete the connection, then reconnect under an active user
Shared mailbox delegated access was revoked Outlook shared mailbox Access revoked Delete the connection, then reconnect under an account with mailbox access
Status check failed temporarily All email channels Status unknown Try again later

 

When the connection owner is no longer active

When the owner of a channel connection has been deactivated or deleted from the account, the channel shows Connection broken. Selecting the status opens a prompt with the message: "The user who connected this channel no longer has access to it, so it isn't creating tickets."

The only available action is Delete connection. After deleting, an active team member needs to reconnect the channel manually.

The Connection broken prompt with the Delete connection action

 

Who can do what

Permissions for channel health actions vary by role. The table below shows what each role can do:

Role See status Reconnect Delete connection Connect to board
Channel owner ✓ ✓ ✓ ✓
Account admin ✓ ✓ ✓ ✗
Board owner ✓ ✗ ✗ ✗
Other users ✓ (if they can see the channel) ✗ ✗ ✗

 

How status refreshes

Status updates may take up to 90 seconds to reflect after a change is made. After resolving an issue, wait a moment and reload the page to see the updated status.

 

FAQs

How do I add a channel in monday service?

Select Add a channel from the Channels tab in the left navigation, choose a channel type, and follow the on-screen setup steps.

Can I connect more than one channel to a Tickets board?

Yes. Multiple channels can be connected to the same Tickets board. Each one routes incoming requests into the Unassigned tickets group.

What does "Setup required" mean for my channel?

The channel is not linked to an active Tickets board. Connect it to a board to start receiving tickets.

What should I do if a channel shows "Connection broken"?

The fix depends on the cause. For Gmail and Outlook, reconnect the channel. For Service Inbox or channels whose owner is no longer active, delete the connection and reconnect under an active user.

Why does my channel still show an old status after I fixed the issue?

Status updates can take up to 90 seconds to refresh. Wait a moment and reload the page.

If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.

Last modified on

Still have questions?
We can help.

Chat support

Get in touch with our support team through our chat for any questions, concerns, or inquiries.

Community forum

Learn, share ideas and connect with other monday.com customers.

Expert help

Hire a monday.com expert to optimize your workflows.

Is this article helpful?
Help us improve our articles.