Team chat that knows every deal.

Inchat is the team chat built into veli(Q CRM, so conversations sit next to the deals, tickets and people they are about. It has public and private channels, direct and group messages, threads, reactions, polls, canvases, pins, file sharing, scheduled messages, reminders, custom status and do-not-disturb, plus slash commands such as /poll, /remind, /summarize and /genie. More about Inchat.

Every deal, account, contact and ticket can have its own room, opened with a Discuss button. A room follows the record's own permissions: if someone loses access to the deal, they lose the room, its files and its search results immediately. Membership alone is never enough.

Paste a link to a deal, account, contact, ticket, quote or invoice and it appears as a live card that keeps showing the current stage, amount and status. Calls, meetings, notes, stage changes and SLA alerts logged on the record are echoed into the room as timeline posts, and any chat message can be logged back onto the record as a note.

Yes. A rep posts an approve or reject card to a channel they choose, such as a deal desk. An admin other than the requester decides, and the decision is stamped on the quote and logged on the deal. Approvals are advisory today: a pending or rejected request does not block sending the quote.

Ask Genie in any conversation with @Genie or /genie. It answers as you, with the same permissions, and in a deal room it also has the deal as context. It can summarize a channel or thread (visible only to you), translate or explain a message, and brief you on what you missed. In deal rooms it can suggest changes to the amount or close date from the conversation, with the evidence, and a teammate applies each one under their own permissions. Nothing changes silently.

Admins choose who can create channels and who can use @channel and @here, how long messages stay editable, and whether people can delete their own. Channels can be announcement-only. Messages can be scanned for API keys, private keys and card numbers, then redacted or blocked. Retention can be set from 30 days to 7 years. There is an admin audit log (message contents are never recorded in it), chat analytics, flagged-message review and a full export.

Yes. Incoming webhooks post into a channel, public-channel messages can fire an outgoing webhook event, and the API can read and write public channels with scoped keys. Automations can post to a team channel, and can also be triggered by a message with a keyword, a reaction or someone joining a record room. Private channels, direct messages and record rooms never leave the workspace through these routes.

There are no voice or video calls, no external guests or shared channels with other companies, and no native mobile push notifications. Desktop browser notifications are available and opt-in.