find intercom customers still waiting for a human reply
a private note can make a thread look busy while the customer keeps waiting. this routine reads the public exchange in each open intercom conversation.
it brings the longest waits to your dusk chat, counting from the first customer message that still lacks a public teammate reply.

the message
paste this into a chat with your bot
weekdays at 11am and 4pm, search open intercom conversations in my support inbox. ask which inbox to use before the first run. read each conversation in scope, including its opening message. find the first public customer message since the last public human teammate reply. ignore internal notes and automated acknowledgments.
if that message is at least two clock hours old, put the conversation id, waiting-since time and a short account of the request in this chat. sort longest wait first. a second message from the same customer does not restart the clock.
never reply, close or assign conversations. if missing parts prevent a decision, name the thread and the uncertainty. stay quiet only after a complete read with nobody over the threshold.- when
- 11am and 4pm on weekdays, using elapsed clock hours for the wait
- needs
- intercom conversation search and individual conversation reads with read-only app access
what comes back
an example, not a real run
conversation 5182 · waiting since 08:24 utc · 2h 36m
louise park needs a corrected delivery address on her order. the 09:10 update was a private note. no later public teammate reply in the visible thread.make it yours
- define a reply. if your team wants automated answers to count, say which ones. a receipt acknowledgment alone rarely answers the question.
- choose your clock. the default includes overnight hours. for business hours, give the opening days, hours and time zone.
- minimise what leaves the thread. ask for just the id and wait time if the inbox handles sensitive requests.
when it goes wrong
- a new follow-up makes the wait look shorter. start with the earliest customer message after the last public human answer.
- the thread is too long to reconstruct. the conversation read returns at most 500 parts. if the start of the wait is unclear, flag it for a person.1
what counts as unanswered
read the thread from the customer’s side. a teammate can write “i’ll look into this” in a private note. that helps the next agent, but the customer still sees silence. a public teammate reply ends this routine’s timer, even when the underlying problem remains open.
if someone must respond within a fixed deadline, use a live queue for that commitment. two scheduled reviews a day leave gaps.
questions
does this include a question the customer added after a reply?
yes. that message starts a fresh wait. the earlier answer belongs to the previous exchange.
does the routine write back to customers?
the waiting list stays in your dusk chat. keep intercom read only for this job. if you later enable replies, sending asks first by default.3
sources
- composio: intercom actions, checked 20 november 2026
- dusk bot docs: routines
- dusk bot docs: connected apps
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
find the intercom customer who still needs an answer
which urgent zendesk tickets still need an owner?
give the next support shift a ticket handoff
ai email triage: let a bot sort your inbox and draft the replies
where do ai agents run when your laptop is closed?
an ai executive assistant for inbox and calendar work