find the intercom customer who still needs an answer
find the customer who answered your question yesterday and never heard back. an intercom bot can read the conversation, pick out what the customer still needs and draft the next reply in dusk.
give it your support team’s queue and the articles you trust. you decide what goes back to the customer.

what a bot can do in Intercom
read both sides before calling a conversation unanswered. an internal handoff can sit below a customer question. read the messages themselves to see whether the customer ever got an answer.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| List all teams | read | identify the team that handles the inbox you mean |
| Search conversations | read | narrow the queue to conversations your team owns |
| Get conversation | read | read the customer’s wording and the support replies in context |
| Search for articles | read | find a published help article using the customer’s phrase |
| Retrieve an article | read | read the actual instructions before drafting a reply |
| Reply to conversation | send: asks first | send the reviewed answer to the original conversation |
composio, the connection service behind dusk bot's apps, lists 138 Intercom actions (version 20261104_00, read 20 november 20264). dusk bot treats 61 as reads, 3 as sends and 74 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like reply to ticket, and waits for your Allow unless you set a daily amount.
connect Intercom
- open Connected apps in the sidebar.
- pick Intercom and sign in on Intercom's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Intercom.
- ask in plain words. reading and drafting happen freely; sending asks you first.
start with a conversation you know well. connect intercom under connected apps and give your support bot read access. tell it the team name and conversation id. ask which message reached the customer last. compare that answer with the thread before scheduling a wider review.
routines to copy
use the next shift change as the deadline. pick a routine based on what the incoming agent needs to do. each one returns its findings to your dusk chat.
waiting on support
at 9 each weekday, read open intercom conversations assigned to my support team. find the ones where the customer asked a question and nobody answered them. ignore internal notes when deciding who replied last. give me the conversation ids and questions here, oldest unanswered question first.weekday mornings · a queue ordered by how long customers have waited
promises for the next shift
every weekday at 4, read conversations our team updated today. look for a promise to get back to the customer. quote the promise, include any deadline the agent actually gave and flag whether a later reply fulfilled it. leave the handoff here.weekdays at 4 pm · open promises with the words the customer saw
answers from the help center
each tuesday at noon, find open setup questions in our team queue. search published articles for the exact step the customer is stuck on. draft an answer here with the article title. if the article skips that step, give me the gap instead. send nothing.tuesdays at noon · draft answers and questions the help center leaves open
what it asks you first
read the draft beside the customer’s latest message. an intercom reply asks before sending by default. closing and assigning a conversation are changes. keep those actions off a drafting bot’s list so the thread stays open for the next shift.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
what it cannot do
- read past the conversation action’s limit. it returns at most 500 conversation parts and offers no next page. mark unusually long threads as incomplete.
- wake on a new intercom conversation through this connection. schedule inbox reviews at the times your team picks up work.
- close a conversation with read-only access. a draft in dusk leaves the support queue alone.
when a customer is waiting right now
take an active conversation yourself. dusk fits a shift handoff or a batch of article lookups. if the customer is typing and you already have the thread open, answer in intercom. a scheduled pass adds another wait.
what it looks like
a fictional example.
before
clara wells sent a screenshot after support asked which menu was missing. an agent added an internal note about it.after the bot
waiting on support: clara sent the requested screenshot. the note discusses the menu, but nobody has answered her yet.an illustration with made-up names and numbers.
questions
does an internal note count as answering the customer?
look for a customer-facing reply. an agent can discuss the problem internally while the original question still needs an answer.
can the bot use the answer our support team already wrote?
give it the relevant help center. have it open the article and quote the step that applies. ask for a question when the customer describes a different problem.
sources
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 intercom customers still waiting for a human reply
give the next support shift a ticket handoff
see why an urgent zendesk ticket keeps changing hands
which urgent zendesk tickets still need an owner?
add new airtable rows without rewriting existing records
turn your notes into a comment on the right asana task