Set a reminder on a conversation over the API
The developer API can now put an internal reminder on a chat — a note that comes back to your own inbox at the time you pick, on the right thread.
Released 20 August 2026
If you build on our API, you can now hand a follow-up to the team that will actually do it — a reminder on the customer's own chat, timed for when it matters.
What's new
- A follow-up that lands on the right thread — set a reminder on a conversation from your CRM, your helpdesk or your own scripts: "chase the revised quote on Friday", "check the refund cleared on Monday". It comes back on that customer's chat, so whoever picks it up has the whole history in front of them.
- Nothing reaches the customer — a reminder is an internal note with a time on it. It is never sent, never charged for, and never opens a reply window. Set one on a chat that has gone quiet for a month if you like.
- It shows up the way a teammate's does — a bubble on the thread the moment it's set, and an urgent one when it falls due. Anything you already have reading internal notes picks both up with no extra work, and each one says whether a person or your system set it.
- Reschedule or cancel with the same key — move the time, change the heading, or stand it down. Cancelling clears the bubble too, so nobody is left looking at a reminder that will never fire.
- Reminders your team set stay theirs — your system can read everything on a thread, but only change what it set itself. Anyone in the console can still override an API-set reminder, exactly as they would a colleague's.
- Nothing new to issue — reminders ride the same permission as internal comments, so a key that can already add notes can set them today.
Give a reminder a heading, a note, or both, and pick a time at least fifteen minutes ahead. Manage keys under Developers in your workspace settings.