Frequently asked questions

What does InRoots read?

Messages in the rooms you assign to it, direct messages with the bot, reactions on standups, presence from your chat server, and the integrations you connect. It does not read your screen, your email, your files or your source code, and there is no agent on any laptop.

Does it decide anything about people on its own?

Routine things, within rules you set: a short leave request that fits the guardrails, a nudge, a routing. The neural engine can automate some of those with a confidence and a reason, but strikes are never issued autonomously, retention signals never act, and pay decisions stay human. Every automatic action is logged and reversible.

Can employees see their own data?

Yes. Their scorecard with the full pillar breakdown, their goal and what it is measured against, their leave, their report, their objectives, and the same drift signals about themselves. Type /pulse me in chat at any time. Admin-only signals such as the integrity pattern label are not shown to peers.

Is the score an AI guess?

No. It is deterministic arithmetic over recorded signals, with public weights and a line-by-line breakdown. The AI parses free text, writes summaries, rewords recommendations and answers questions. Turn the AI off entirely and the score still works.

Can it run with no internet, and what if the AI provider is down?

Yes. Self-host the chat server, set the provider to a local Ollama, refresh the local IP database on the host, leave spoken replies off, and enable no cloud integrations. There is no telemetry.

When a provider is down, calls fail over through your configured chain automatically, a failsafe job switches the active provider every fifteen minutes if needed, and non-essential features degrade to keyword paths. Nobody gets a strike because a classifier was unavailable.

How do we handle part-timers, night shifts and other countries?

Per-person weekly hours and working days, per-team holiday calendars generated offline, a late threshold learned from each person’s own history, a late-finish rule relative to each person’s own median, and per-team overrides for almost every setting.

What about lost messages and mistakes?

If the bot cannot decrypt a message it tells the sender to re-send. A nightly sweep records every event that never made it in, and on a day with a recorded gap the missed-sign-off deduction is zero.

Managers correct a day from the employee’s attendance detail: edit the sign-in, the sign-off or the credited hours, with a 90-second undo and an audit row. Strikes can be forgiven from the employee card. Long days wait in a review queue with the day’s evidence beside them.

Which chat channels are supported, and where do I get help?

Matrix natively, including K9 Chat, with encrypted direct messages; Slack and Microsoft Teams through their own APIs; WhatsApp for outbound on-call and ticket reach. The check-in format and /pulse me are the same everywhere.

Every dashboard page has a Help entry with searchable articles and feature guides. The API explorer is inside the product for admins. For anything else, write to support@inroots.ai.