If the current Messages composer has no attachment picker, do not rely on the attachment-limit text beneath it as a file-upload control. Selecting or dropping a local file elsewhere on the page is not a confirmed upload.
Use Documents to upload the supporting file to the correct company, or use the specific document request the team provided. Complete that upload and wait for its success result.
Return to the conversation and identify the filename, company, and the question it supports. This lets the team connect the file with the discussion without a temporary external sharing link.
Existing message attachments can still appear as downloadable chips in older or team messages. That does not mean the current customer composer exposes an attachment action. If the team needs the file delivered through a particular request, follow that route rather than uploading a duplicate to an unrelated location. A local path pasted into the message is not a shared file the team can open.
Was this article helpful?
Tell us whether this answered the question you came with.