We use BotSailor Telegram flows with an external PHP/MySQL ordering system.
Each order summary needs a unique reference. When the customer clicks “Confirm order,” our PHP webhook must receive the reference associated with that exact message, including clicks on older summaries.
Currently, we receive chat_id, subscriber information, postbackid and user_input_data, but no per-message summary reference.
Please support dynamic callback_data per Telegram message and forward it to outgoing webhooks, while BotSailor continues managing the Telegram webhook.
Acceptance example: send summaries A and B to the same chat, then click A, B and A. Our endpoint must receive references A, B and A, respectively.