Context
We use the Cloud Chat API to proactively send messages via WhatsApp templates. In part of our templates, the header is a document (PDF, for example), which we pass via the header_attachment parameter with a signed S3 URL.
problem
The file reaches the recipient under the name “Untitled” on WhatsApp, regardless of the actual file name or the URL passed. We didn't find any parameters available today that allow us to control the displayed name.
What do we expect
We would like to be able to define the name that the recipient sees when receiving the document - for example, Proposta_Comercial_Abril.pdf - to be:
  1. Automatically deriving the name from the file referenced in the URL, or
  2. Accepting an explicit parameter in the API call (e.g. header_attachment_filename) that allows us to define the name freely.
Why does it matter
Documents with the name “Untitled” convey an unprofessional image to our end customers. Filename control is essential for use cases such as submitting proposals, contracts, and custom reports.
·