[object Object]

Core Features

Channels (public, private, organization-wide), direct messages, voice/video calls (PrimeTime broadcasts up to 10,000 viewers), file sharing, and threaded replies. Channels support pinned messages, scheduled messages, and message reactions. The Personal Channel is each user’s private space for notes, drafts, and self-DMs — useful as a scratchpad. Cliq supports thread-first conversations as of the 2026 update; threads now persist as first-class objects with their own permalinks.

Bots

Build custom bots via Deluge to respond to messages, query data, and trigger workflows. The bot framework supports message handlers, slash commands, mentions, and scheduled posts. A common pattern is the standup bot — at 9am every weekday it asks each team member three questions and posts the responses to the team channel.

// Bot message handler — respond to "/leadcount" command
response = Map();
crm_response = invokeurl
[
    url: "https://www.zohoapis.com/crm/v3/Leads/search?criteria=(Created_Time:greater_equal:" + zoho.currentdate.toString("yyyy-MM-dd") + "T00:00:00+00:00)"
    type: GET
    headers: {"Authorization": "Zoho-oauthtoken " + token}
];
count = crm_response.get("info").get("count");
response.put("text", "Today's new leads: " + count);
return response;

Commands

Slash commands invoke actions — /ticket creates a Desk ticket, /lead creates a CRM lead, /poll opens a poll dialog, /remind schedules a reminder. Custom commands extend Cliq into your ops; build one for any frequent action your team takes from chat. The command builder is no-code for simple commands, Deluge-backed for anything dynamic.

Integrations

Native integration with Zoho apps: CRM notifications (deal won, lead assigned), Desk alerts (ticket priority high), Projects updates (milestone hit), Books (invoice paid), Bookings (new appointment) all post to designated channels. External integrations cover GitHub (PR opened, build failed), Jira (issue created), Google Drive (file shared), and Zapier-via-Flow for the long tail. Webhook channels accept POST payloads from any system that can sign a request.

Bot Patterns That Work

Standup bots, on-call paging (route P1 alerts to the rotation), CRM watch (post when a deal over $100k changes stage), and approval bots (manager replies “approve” or “reject” in thread to act on a request). The anti-pattern: notification floods. A channel that fires 200 messages a day gets muted by everyone within a week, so filter ruthlessly at the source.

vs Slack/Teams

Cheaper as part of Zoho One — effectively zero marginal cost if you’re already on the bundle. Native Zoho integration depth is unmatched (CRM, Desk, Books, Projects all flow without middleware). Ecosystem is smaller than Slack’s — niche third-party integrations (e.g. specific dev tools, niche CRMs) often don’t exist. Teams wins for Microsoft 365 shops on calendar and meeting integration. Pick by ecosystem fit: Zoho-heavy → Cliq, Microsoft-heavy → Teams, dev-heavy with diverse tools → Slack.

What to do this week

Build one slash command for your most frequent CRM action (e.g. /lead to create a lead from chat), configure CRM notifications for deals over a meaningful threshold, and audit your channels for notification volume — mute or filter anything firing more than 50 times a day.

[object Object]
Share