Test a messenger conversation reaching the agent inbox

Failure modes in this flow

The test spans both sides of the conversation, which is the only way to prove delivery rather than acceptance.

• The message sends - with a conversation id of CNV-41820.
• The attachment lands - confirmed and previewed inline in the thread.
• The thread is right - both messages attributed to the sender.
• The inbox has it - the conversation listed and the transcript carrying the text and the attachment.

The inbox assertion is the one that matters. Everything before it happens inside the widget, which is the party that would also be wrong if the message were lost.

Writing the objective

The attachment is asserted twice: as a confirmation and as an inline preview, so a file that uploads without rendering is distinguishable from one that failed outright.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/intercom-clone-app/messenger?reset=true
max_steps: 45
tags: [intercom, support, messaging]
---

# Intercomm 31.1: Messenger conversation start

Catalog objective: open the messenger and start a conversation with an attachment.
Key assertion: the message is sent and visible in the inbox.

## Start the conversation
Type "The export keeps failing on large reports" into the messenger box, click "Send", and verify a green banner says the message was sent and conversation "CNV-41820" is now in the inbox.

## Attach a file
Click "Attach error-screenshot.png" and verify a green banner reads "error-screenshot.png attached to the conversation." and an inline image preview appears in the thread.

## Verify the thread
Verify the thread shows a message from "Sam Rivera" reading "The export keeps failing on large reports" and a second from "Sam Rivera" reading "Attached error-screenshot.png".

## Verify it is visible in the agent inbox
Go to https://my-testing-repo-main.vercel.app/intercom-clone-app/inbox and verify the conversation list has a "Sam Rivera" row for "CNV-41820", and the detail panel transcript contains "The export keeps failing on large reports" and an attachment marked "error-screenshot.png".

The transcript assertion in the inbox includes the attachment by filename, since an agent who cannot see the screenshot asks the customer to send it again.

The assertions in detail

A message, an attachment, the thread, and the inbox.

Asserting the sender name on each message catches a thread that renders the customer messages as agent replies, which is confusing for both parties.

Running it locally

kane-cli testmd run tests/intercom/messenger-conversation_test.md

Add an oversized attachment, since a clear refusal is better than a silent failure that leaves the customer thinking the file arrived.

File handling in chat is a common gap. File handling in Kane CLI covers it, and evidence based QA covers keeping proof of a delivery test.