This article helps you fix problems with the Cinode Chat Agent in Slack or Microsoft Teams. Find the message you see, or the symptom, in the sections below. Some fixes are for you as a user, and some are for your Cinode administrator. For setup steps, see Chat Agent: Admin setup.

This message means the Chat Agent has no working Cinode connection. Ask your Cinode administrator to open the Chat Agent in Cinode Flows and finish or reconnect the Cinode step in the configuration wizard.

On Microsoft Teams, the Chat Agent never responds until two steps are complete. A Teams administrator must upload the Cinode Teams app and make it available in your tenant, and an administrator must finish the Microsoft sign-in in the configuration wizard. Until both are done, Teams has no way to route messages to your Cinode account, even when the integration looks deployed. See Chat Agent: Admin setup.

In a thread it has joined, the Chat Agent stays quiet when a message looks off-topic, is only an emoji, or is aimed at other people. It also never changes data from a message that does not answer its own last reply. To make sure it responds, mention it again, for example "@Cinode what is the status of the Northwind project?"

The Chat Agent handles one question at a time in a thread and queues up to 10 more. If more than 10 are waiting, the oldest are dropped. A queued message that is not picked up within 11 minutes expires, and the Chat Agent tells you. Send the message again.

This message means Slack or Teams refused to let the Chat Agent post or join the conversation. In Slack this is usually a missing app permission. Ask the administrator of your Slack workspace to reinstall or re-approve the Cinode app. In Teams, ask your Teams administrator to check that the app is allowed and installed for that team or chat.

This message means Slack or Teams rejected what the Chat Agent tried to post. Try again, or rephrase your request. If it keeps happening, contact Cinode Support with the time and the channel.

These messages mean Slack or Microsoft Teams is throttling the Chat Agent or is temporarily unavailable. Wait a few minutes and ask again. If it continues for an hour or more, check the status page of your chat platform.

These messages mean a temporary problem, such as heavy load or a network error. Try again in a minute. If the same question fails repeatedly, rephrase it or make it smaller, and contact Cinode Support with the time of the failure.

The Chat Agent matches you to Cinode through the email address on your Slack or Teams account. This message means the chat platform did not give it an email. In Slack, the Cinode app needs permission to read email addresses, so ask your Slack administrator to re-approve the app. In Teams, the app must be allowed to see user email addresses.

This message means no active Cinode user has the same email address as your chat account. Ask your Cinode administrator to check three things: your Cinode user exists, it is active and not disconnected, and its email address is identical to the one on your Slack or Teams profile. Upper and lower case do not matter. Candidates and subcontractors do not have access.

The Chat Agent shows data for your Cinode permission level, teams and customers, and some data is never returned at all. This includes date of birth, phone, home address and employment dates, and utilisation answers never include revenue. See Chat Agent: What you can ask and do for what each role can ask. If a manager should have access, check their permission level and managed teams and customers in Cinode. Permissions are cached for 2 minutes, so allow a short moment after a change.

The Chat Agent has a per-user usage allowance to keep costs predictable. By default it is 1,000,000 tokens per user in a 24-hour window. The window starts at your first question and the message tells you when it resets. Large lists and reports use the most. Normal use rarely reaches it. If your team needs a higher allowance, contact Cinode Support.

Some questions need more work than the Chat Agent can do in one reply. It stops and asks you to break the question into smaller ones or try a smaller part. Narrow the question by team, office, date window or customer. For something recurring, ask it to set up an alert instead.

The Chat Agent only helps with Cinode: people, roles, projects, your profile, tasks and alerts. Questions outside that, and attempts to change its instructions, get this reply. Rephrase your request in terms of Cinode data.

The reply failed an automatic safety check. Rephrase the question and ask again, with a bit more context about what you want.

That is by design. The Chat Agent works with Cinode data, alerts, reminders and your own settings, and answers only inside the conversation you are in. It cannot send email, open attachments, edit another person's profile, or handle candidates and subcontractors. To get a message in another channel, add the Chat Agent to that channel, mention it there and ask again.

This message means the change was saved in Cinode, but the reply failed afterwards. Do not repeat the request, because that could create a duplicate. Open the record in Cinode to check the result.

Ask the Chat Agent "What am I subscribed to?" to see every alert with its status. Then check these causes:

For the full list of states and what causes them, see Chat Agent: Create and manage alerts.

Each person can have up to 15 alerts by default, and paused alerts count. Delete or pause one, or ask Cinode Support to raise the limit. The Chat Agent also refuses an alert that duplicates one that already posts the same events into the same channel.

This is a known limit. The Untouched contacts alert can only be set up in a channel or a thread. Create it in a channel instead.

Teams only allows a proactive message to a person once the Cinode app is installed for them. Ask your Teams administrator to pre-install the app for users and to grant the optional User.Read.All permission. See Chat Agent: Admin setup.

The catalogue covers 26 staffing, people, task, profile and sales signals. See Chat Agent: Alert types. If you need something else, tell Cinode Support and we will look at adding it.

Ask it to pause or stop a kind of message, for example "Stop task pings" or "Not this week." You can also ask it to stop direct messages from another integration. See Chat Agent: Reminders and proactive messages.

Ask it to change your language or timezone, for example "Reply to me in Swedish" or "Set my timezone to Europe/Stockholm". Your preference is kept for future conversations. The Chat Agent speaks English and Swedish.

Pipeline Assistant delivers through the Chat Agent. See Pipeline Assistant: Troubleshooting.