For managers and leads · in Slack & Microsoft Teams

Asked on Monday. Still chasing on Thursday.

Googling "how to nicely remind someone" means that message has been written before. Ayven writes it, sends it, and follows up until the work is confirmed done — in Slack and Teams, where the chase already lives.

Start free See her run the chase ↓
SarahSarah · Monday Hey Mike — quick check on the auth fix when you get a sec, no rush 🙂
○ softened — "just checking in" deleted twice
· Tuesday — silence. Wednesday — silence.
SarahSarah · Thursday Sorry to ping again — is the auth fix still on track for Friday?
· next move: ping harder, loop in his manager, or just do it yourself

thread staged with our recurring cast

01 · What Ayven does instead

The chase becomes process, not personal.

Ayven watches the open loops in Slack and Teams, so you see what's outstanding without having to ask. And when a reminder isn't working, the next move is not the same reminder, louder — she checks the ticket, reroutes, or escalates with context.

Mon—took the loop: auth fix · owed Friday
Wed—checked Jira first — nothing moved — asked Mike, once
Wed○Mike: "blocked on the security review"
Thu—rerouted: asked Priya to unblock, context attached

02 · The register

"Done" is a claim. She checks.

Ayven APP · Friday 3:12pm Mike pushed the fix once the review cleared. I checked the ticket myself before telling Sarah — the confirmation happened in the system, not in another DM.
!auth fix — blocked on security review
Thursday, before the fix landed: quiet past the date it was owed. The next move was not the same reminder, louder.
already tried: checked Jira — nothing moved · asked Mike, once
→ rerouted to Priya to unblock — context and history attached
Done — Jira · 15:12

done means the ticket says so

03 · It's real

The product, not a promise.

Ayven inbox showing items that require your action
the inbox where her asks wait for you — action required, nothing auto-fired
Ayven working a follow-up thread in Slack
staged example — a real ask handed to Ayven and routed

threads shown are staged with our recurring cast · screenshots are the live product

04 · The fair worry

Won't a bot just annoy them more?

Fair worry — nagging bots earned it. Ayven runs on the opposite rule: when a reminder isn't working, the next move is not the same reminder, louder.

Quiet doesn't mean louder

When someone goes quiet, Ayven changes strategy — checks the linked system herself where she can, reroutes to someone who can actually unblock, or escalates with context. She remembers what she already tried and won't repeat it, and every chase has a point where it stops pinging and reports back to you instead.

strategy changes · pinging stops

Timed by the work

A reminder bot fires at 9am because it's 9am. Ayven times each follow-up from the state of the work — repeat nudges to a person are spaced at least a day apart, and a teammate who's away gets a later check-in, not a fuller inbox.

timed by the work, not the clock

"Done" gets verified

Ayven doesn't take "done" for an answer. Work linked to a ticket closes only when the ticket actually shows the change — so the confirmation happens in the system, not in another DM to your teammate.

closed in the tracker, not in a DM

Process, not personal

Your third nudge reads as you being on someone's case. The same check-in from the team's coordinator reads as process — your teammate answers a workflow, not you, and it spends none of the goodwill you were rationing.

goodwill stays yours

The message you'd have written, sent on time.

Start free

stop drafting the nudge · she sends it, follows up, and confirms it's actually done