Support

Questions, bug reports, data requests: support@replychrono.com. We aim to reply within two business days.

Commands

`/replychrono status`	Monitored channels and open timers
`/replychrono log`	Recent activity: timers, replies, breaches, escalations
`/replychrono watch` / `unwatch`	Start / stop monitoring the current channel
`/replychrono config`	Open the settings (SLA, business hours, alerts channel…)

Reporting a security issue

We welcome reports from security researchers and customers. Email security@replychrono.com with a description of the issue and, if possible, steps to reproduce it. We acknowledge reports within five business days, keep you informed while we investigate, and will credit you if you wish once a fix is released. Please do not access, modify or exfiltrate data belonging to other workspaces, and give us reasonable time to remediate before public disclosure. We will not pursue legal action against researchers who follow this policy in good faith. ReplyChrono does not operate a paid bug bounty program.

Quick fixes

Not getting alerts?

Open the ReplyChrono App Home: is an alerts channel set, and is the channel monitored? Is @ReplyChrono a member of the client channel (/invite @ReplyChrono)? Remember timers only run during your configured business hours.

A channel isn't monitored automatically?

Auto-monitoring needs the bot to be a member and the channel to be shared with an external organization. Run /replychrono watch inside the channel to add it explicitly. A channel you unwatched on purpose is never re-added automatically.

Trial ended?

Detection keeps running and nothing is lost — upgrading turns alerts back on instantly.