[GH-ISSUE #118] WhatsApp connectivity to send codes #66

New issue

Closed

opened 2026-05-07 00:18:35 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:18:35 +02:00

Owner

Originally created by @stefan-f-punkt on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/glenndehaan/unifi-voucher-site/issues/118

Originally assigned to: @glenndehaan on GitHub.

The feature

Is there a possibility to link the WhatsApp API to send the code directly per Whatsapp to the user?
Or to link Whatsapp Web? https://faq.whatsapp.com/5913398998672934/?locale=de_DE

Originally created by @stefan-f-punkt on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/glenndehaan/unifi-voucher-site/issues/118 Originally assigned to: @glenndehaan on GitHub. ### The feature Is there a possibility to link the WhatsApp API to send the code directly per Whatsapp to the user? Or to link Whatsapp Web? https://faq.whatsapp.com/5913398998672934/?locale=de_DE

BreizhHardware

2026-05-07 00:18:35 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@glenndehaan commented on GitHub (Jan 13, 2026):

Hi @stefan-f-punkt,

I might need some more context to what we are trying to solve here.
In the current version it's already possible to copy the code from a voucher.
And this api, or more a weblink only accepts text as an input (not even styling).

So it would require the user to first enter a phone number in a wizard within this app. Then opens whatsapp or whatsapp web. To then hit send.

This seems overkill to me, since it would be faster to click the copy button, open whatsapp web, paste the code and hit send.
I would get it if I was able to embed things like the scan to connect (even tho you would not be able to use it). But maybe i'm missing some context here?

Kind regards,
Glenn de Haan

@glenndehaan commented on GitHub (Jan 13, 2026): Hi @stefan-f-punkt, I might need some more context to what we are trying to solve here. In the current version it's already possible to copy the code from a voucher. And this api, or more a weblink only accepts text as an input (not even styling). So it would require the user to first enter a phone number in a wizard within this app. Then opens whatsapp or whatsapp web. To then hit send. This seems overkill to me, since it would be faster to click the copy button, open whatsapp web, paste the code and hit send. I would get it if I was able to embed things like the scan to connect (even tho you would not be able to use it). But maybe i'm missing some context here? Kind regards, Glenn de Haan

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@stefan-f-punkt commented on GitHub (Jan 13, 2026):

Copy paste works, indeed.
What I am looking for is a "send button" similar to the email button in the overview.
The Email address needs to be entered manually, also the WhatsApp number.
In my opinion it would reduce the effort and bring more usability to the UI.

Best regards
Stefan

@stefan-f-punkt commented on GitHub (Jan 13, 2026): Copy paste works, indeed. What I am looking for is a "send button" similar to the email button in the overview. The Email address needs to be entered manually, also the WhatsApp number. In my opinion it would reduce the effort and bring more usability to the UI. Best regards Stefan

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@glenndehaan commented on GitHub (Jan 13, 2026):

I get your point. But there are 2 mayor differences between mail and this proposal. The app provides both the template and an SMTP implementation. Therefore no external tools are required for it to operate (email client). My point was if you still need WhatsApp Web then what problem are we solving/automating here.

If the user has not properly configured WhatsApp Web, or the browser does not recognize the url the whole thing fails. Where as in the email system is configured server side once, and stays the same for all users. For WhatsApp we need to rely on users getting this to work.

And thats where I don't see the improvement, the same could be said for other implementation. Lets say users would utilize Telegram or Signal. It's still up to the user to send the message in the end.

@glenndehaan commented on GitHub (Jan 13, 2026): I get your point. But there are 2 mayor differences between mail and this proposal. The app provides both the template and an SMTP implementation. Therefore no external tools are required for it to operate (email client). My point was if you still need WhatsApp Web then what problem are we solving/automating here. If the user has not properly configured WhatsApp Web, or the browser does not recognize the url the whole thing fails. Where as in the email system is configured server side once, and stays the same for all users. For WhatsApp we need to rely on users getting this to work. And thats where I don't see the improvement, the same could be said for other implementation. Lets say users would utilize Telegram or Signal. It's still up to the user to send the message in the end.

BreizhHardware referenced this issue

2026-05-07 00:18:57 +02:00

[PR #66] [MERGED] New Crowdin updates #107