Skip to content

[Feature New API] Bulk Message API Should Allow Unique Messages per Recipient #159

Description

@Arbaz-Dispo

🌟 Describe the Feature

We know that a bulk message API is already under development and appreciate that, but it would be a huge improvement if it could also support sending unique/personalized message content to multiple recipients within a single API request.

🚀 Justification

In many cases, sending the same message to all recipients isn’t enough. We need to send different, tailored content per recipient while still benefiting from the efficiency of a bulk API. Without this, we’re forced to either compromise on personalization or make hundreds of separate API calls.

📝 Suggestions

No response

Product Area

conversations

📋 Use Case

  • Deliver personalized messages at scale without losing the benefits of bulk processing
  • Launch campaigns where each user gets unique dynamic content in a single API call
  • Avoid making 100+ individual requests for 100 personalized messages

🚨 Why Should This Be Prioritized?

  1. Fewer requests means reduced overall latency, making large scale campaigns faster and more reliable
  2. Optimizing for bulk + personalization together would lower infrastructure costs both for developers and the platform itself

🧠 Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    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