Messages, attachments, read acknowledgements and delivery evidence
Send manual replies and supported media, page through message history, protect downloads and understand linked-device read and delivery evidence.
Guides in this workflow
Select the exact setup, Inbox, verification, automation, portal, audit or troubleshooting action you need.
Send a text reply
Write up to 10,000 characters and send it through the selected linked-device account.
Send an attachment with a message
Select a supported file, optionally add text, verify the configured size limit and send once.
Send an attachment without text
Attach a supported file and send it when the media itself is the complete response.
Understand empty-message validation
Know that a request with neither text nor a valid attachment is rejected.
Understand the 10,000-character reply limit
Keep manual reply text within the HTML and server validation limit.
Configure the maximum attachment size
Set a limit from 1 to 32 MB in Settings and verify larger uploads are rejected.
Understand MIME validation
Know that the server inspects file content rather than trusting only the browser filename or extension.
Understand supported attachment categories
Use only media types accepted by the module allowlist, including supported image, audio, video, PDF, text and office-document formats.
Understand secure attachment storage
Know that stored media uses randomised names and is served through an authorised controller rather than a public guessed path.
Download an Inbox attachment
Open the message and select its media link; the controller checks account View access, path containment and file existence.
Understand download response protections
Know that protected downloads send a safe filename, Content-Disposition and X-Content-Type-Options: nosniff.
Troubleshoot a missing attachment
Confirm the message has a media path, the file remains inside the managed upload directory and the current staff can view the account.
Read inbound and outbound directions
Use message direction and sender attribution to distinguish customer messages, staff replies and automated system messages.
Understand internal staff attribution
Know that outbound CRM messages retain the responsible staff or system actor for operational evidence.
Understand WhatsApp message-ID deduplication
Know that repeated connector events with the same WhatsApp message ID do not create duplicate CRM messages.
Understand message delivery acknowledgements
Read stored acknowledgement/state information supplied by the linked-device connector without treating it as a contractual delivery guarantee.
Mark an unread conversation as read
Open the conversation and allow Britixo to call WhatsApp sendSeen before setting the CRM unread count to zero.
Understand mark-read idempotency
Know that a conversation already at zero unread can be opened again without creating an incorrect negative or duplicate state.
Troubleshoot a read acknowledgement failure
Keep the CRM unread count when the linked-device read operation fails, repair the account if needed and retry.
Load up to 200 messages
Understand that a conversation request returns a bounded page to protect the browser and server.
Load older message pages
Use the before-message cursor to retrieve an earlier page without duplicating the messages already shown.
Understand profile-photo URL storage
When enabled, store only the current WhatsApp profile-photo URL and expect it to expire or change.