Configuring channels in Zoho Desk connects your support team to customers across email, social media, chat, and phone — all routed into a single ticketing workspace. Here is what you need to know to get each channel type set up correctly.
Why this matters
Every inbound support request arrives through a channel, and without proper configuration those requests either never reach your agents or land in the wrong department. Getting channels right means tickets are automatically assigned, SLAs start ticking from the correct moment, and no customer message falls through the cracks. This is one of the first things our team at Beam Help — independent expert support for Zoho, not official Zoho support — tackles during any Desk onboarding engagement.
Step-by-step
Step 1. Confirm you have the correct OAuth permissions in place before touching any channel settings. Zoho Desk requires the Desk.settings.ALL scope (or at minimum Desk.settings.READ, Desk.settings.WRITE, Desk.settings.CREATE, Desk.settings.UPDATE, and Desk.settings.DELETE) to read and modify channel configuration. If your integration or API connection is missing these scopes, every save attempt will be rejected silently or with a generic auth error. [2]
Step 2. Navigate to your Zoho Desk admin panel. Channels in Desk are configured at the department level, so before you open any channel settings you must know which department the channel will belong to. Each channel configuration is tied to a specific department, and you will need to supply that department identifier when making any programmatic changes. [1]
Step 3. Choose the channel type you want to configure. Zoho Desk supports the following channel types: email, twitter, facebook, chat, and phone. Each type has its own set of configuration options that you pass as part of the channel setup. [1]
Step 4. For each channel, supply the three required pieces of information: the channel type (one of the values listed in Step 3), the department the channel belongs to, and the config object containing channel-specific settings such as the email address for an email channel or the page ID for a Facebook channel. All three parameters are mandatory — omitting any one of them will cause the configuration call to fail. [1]
Step 5. If you are configuring channels via the Zoho Desk API or an automation layer, note that channel configuration operations carry a medium risk classification. This means changes are not instantaneous or reversible without a follow-up action — treat each configuration change as a deliberate, reviewed operation rather than a quick toggle. [1]
Step 6. After saving a channel configuration, verify the result by navigating directly to your Zoho Desk portal. The base URL for your Desk instance follows the pattern https://desk.zoho.{dc}/agent/{portal}, where {dc} is your data centre region (for example com, eu, or in) and {portal} is your portal name. Tickets flowing in through the newly configured channel will appear under the relevant department's ticket list. [3]
Step 7. If you are also connecting Zoho Desk to a broader integration that includes Zoho CRM, make sure your combined OAuth scope string includes both the CRM scopes and the full set of Desk scopes. These are typically concatenated with a comma separator. Missing Desk scopes in a combined-scope setup is a common reason channel settings appear to save but do not persist. [2]
Common pitfalls
- Missing department assignment. The
departmentparameter is required for every channel type. Attempting to configure a channel without specifying a department will result in an error, even if every other field is correctly populated. [1]
- Insufficient OAuth scopes. Read-only scopes such as
Desk.settings.READalone are not enough to create or update a channel. You need write-level access (Desk.settings.WRITEorDesk.settings.ALL) for any configuration change to succeed. [2]
- Wrong data centre in your portal URL. If your Desk instance is hosted in the EU or India region, the base URL uses
desk.zoho.euordesk.zoho.inrespectively, notdesk.zoho.com. Using the wrong domain when verifying your setup will simply return a "portal not found" error that has nothing to do with your channel configuration itself. [3]
- Medium-risk operations queued for approval. In environments where write operations above a certain risk threshold require human approval before execution, channel configuration changes may be held in a "planned" state rather than applied immediately. Check your admin actions queue if a change does not appear to take effect right away. [4]
What to check
- Confirm that
Desk.settings.ALL(or the equivalent granular write scopes) is present in your active OAuth token before attempting any channel save. [2] - After configuration, send a test message through the newly added channel and verify the resulting ticket appears in the correct department's queue. [1]
- Double-check your Desk portal URL uses the right data centre suffix for your account region so that any direct navigation links resolve correctly. [3]