Skip to content

/send/carousel splits message into two bubbles (Text + Cards) instead of sending one unified message #69

@asoftdb

Description

@asoftdb

Welcome!

  • Yes, I have searched for similar issues on GitHub and found none.

What did you do?

Currently, when sending a carousel message using the /send/carousel endpoint with a top-level "body" and "footer", the Evolution Go server splits the payload and sends it as two separate messages on WhatsApp:

First bubble: A standard text message containing main text and footer.
Second bubble: The actual interactive cards carousel.
This creates a disconnected user experience. WhatsApp’s native interactive protocol supports binding the main body text, footer, and the sliding carousel cards together inside one single interactive message bubble.

What did you expect?

The recipient should receive only one single interactive message bubble where the body text ("Special offers from Royalty Tours 🌸") and footer text ("Click below to see details") reside directly above the sliding cards within the same bubble.

What did you observe instead of what you expected?

Instead of splitting the payload into a separate sendTextMessage call and a sendCarousel call, the Go handler should compile the top-level body and footer directly into the interactive message payload as the main interactive text header/body, so that the WhatsApp client renders everything together in one single bubble.

Screenshots/Videos

No response

Which version are you using?

0.7.1

What is your environment?

Docker

If applicable, paste the log output

No response

Additional Notes

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions