A morning in support: one Intercom thread, a draft, and a person
By Team Two · Last updated September 23, 2026 · 2 min read
This is an example, not a customer story, and not a measured result. The company is fictional. The tools are the ones Team Two actually ships.
It is 8:12. A conversation is waiting in Intercom. The customer writes: "The pallet left your warehouse on Tuesday. Tracking still says label created. We need it before Friday's install."
Nobody on the support desk is in yet. The agent watching Intercom is.
What this agent is allowed to touch
- Intercom: read the conversation, search contacts, search help-center articles.
- The knowledge base: shipping policy, the page that says when a delayed pallet is rebooked, and the line that says a refund of freight needs a person.
- Slack: post a summary into #support-queue.
It does not have a tool that talks to the carrier. It cannot invent a tracking event. If the help center does not say it, the draft does not say it.
What it does before anyone sits down
It opens the Intercom thread and reads the earlier messages, so it does not ask the customer for an order number they already gave. It searches the help center for the delayed-shipment article and pulls that passage in with the source title.
The draft it leaves is short. It restates the Tuesday ship date, quotes the policy on rebooking, and says a person will confirm the Friday install before noon. It adds an internal note on the conversation: policy matched, carrier status not available in Intercom, needs a human before send.
Then it posts the same summary in #support-queue and @-mentions the morning lead. The customer still sees nothing new.
Where the person comes in
A reply to a customer is not sent on its own. The morning lead reads the draft, checks the carrier site herself, edits one sentence, and approves the send. If the thread had been angry, or about a charge, the same note would have marked it for takeover instead of a draft.
How a message is routed in the first place is the longer walkthrough in From a messy Slack thread to an agent team. Who may read the conversation is in Who is in control.
Frequently asked questions
Does the agent close the Intercom conversation?+
Only if you gave it that action and a person is still in the loop for the reply. In this example it notes and drafts. It does not close.
Can it answer at 3 a.m.?+
It can prepare the draft and the queue post overnight. The customer-facing send still waits for approval.
