The bot does not answer, or says it is not configured.
The shared services that power the assistant are set up once at the organization level. If replies fail across the board, your administrator should confirm the connections in the config wizard are all active.
It says I do not have Cinode access.
The assistant matches your chat account to a Cinode user by email. This message means it could not find a Cinode user for your address, or your chat profile does not expose an email. Ask your administrator to confirm your Cinode account and that its email matches your Slack or Teams profile.
On Teams, the bot never responds.
The Cinode Teams app has to be uploaded and made available in your tenant by a Teams administrator, and the Microsoft sign-in in the config wizard must be completed. Until both are done, Teams has no way to route messages to the assistant.
It will not do something I asked (send an email, post to another channel, act for someone else).
That is by design. The assistant only works with Cinode data, alerts, reminders, and your own settings, and only inside the conversation you are in. It will tell you plainly when something is outside what it can do.
It stopped replying to me specifically.
To keep costs predictable, there is a per-user usage guardrail over a rolling window. If you hit it, the assistant pauses replies to you until the window resets. Normal use rarely reaches it.
It answered in the wrong language, or times look off.
Ask it to change your language or timezone, for example "reply to me in Swedish" or "set my timezone to Europe/Stockholm". Your preference sticks for future conversations.
I need an alert type that is not listed.
The catalog covers a wide range of staffing and CRM signals. If you need something else, tell Cinode Support and we will look at adding it.