Your player is one message away We make sure it arrives

Pushfy is the communication infrastructure of Brazilian iGaming. It brings SMS, RCS, voice, push notifications and the WhatsApp API together in one place, with the same balance, the same API and a unified report, plus event-triggered automation and conversational AI for player support.

Yes, and the safe way is not to migrate everything at once. The API is a token-authenticated HTTP call, so you can integrate Pushfy alongside your current provider, send a slice of your traffic and compare delivery side by side before you flip the switch.

Many start with a single type of traffic, usually OTP, because that is where the difference in delivery shows up fastest, and expand as the results prove out.

That is exactly what the architecture is for. Dedicated workers per channel consume distributed queues that prioritize critical traffic, so a campaign spike never jumps ahead of the verification codes of players trying to log in to your site.

A single API call accepts up to 100K destinations, and the engine is idempotent: neither a retry nor a repeated event produces a duplicate send.

You find out during the send, not in next week's report. Every message returns delivery confirmation (DLR) in real time, by webhook to your system and also in the dashboard.

Because the history is pre-aggregated, the dashboard responds in milliseconds even with millions of messages, so you can follow a large campaign while it is still running and act while there is still time.

The architecture was built for peaks: distributed queues per channel, priority for critical traffic and an idempotent engine, with real-time delivery confirmation so you can follow the campaign while it is still running, not in next week's report.

Formal commitments on availability, response time and coverage on peak dates are agreed case by case with enterprise accounts. Bring your operation's requirements to the conversation: it is more honest to settle this in writing than to promise everyone the same number.

No. You can run everything from the dashboard: import contacts via CSV, build campaigns with segmentation and variable-based personalization, and design automated flows without writing a line of code.

The API is there for those who want to send from their own system, with an OpenAPI specification, a Postman collection and ready-made examples in cURL, Node.js, PHP, Python and Java.

The contact base is yours. The platform records opt-in and opt-out and keeps suppression in force across every channel, with end-to-end audit trails, as the LGPD requires.

Access is controlled by role-based permissions and two-step verification, and groups running several brands have their accounts isolated from one another, with separate reports.

You decide who not to message. The platform's role is to enforce that decision across every channel and leave a trail. Opt-in and opt-out are recorded with an audit trail and, because the contact base is shared, an opt-out applies to SMS, RCS, voice, push and WhatsApp at the same time, not just to the channel where the player asked to leave.

This matters because an operation licensed under Law 14.790/2023 (Brazil's regulated betting law) is accountable for advertising and responsible gaming, and the LGPD (Law No. 13.709/2018) requires consent and transparency for personal data. When someone asks why a player received a given message, there is a record to answer with. A cheap route without this control saves cents per message and hands the entire risk back to your license.

No. Creating an account is free and the model is usage-based: you pay per message sent, at a price that varies with volume, traffic type and route.

Voice is only charged when the call is answered, and identified invalid numbers are suppressed automatically, so you are not charged for dead numbers. The status of every message is visible in the dashboard, and that is what the deliverability assessment analyzes to show how much of your volume reaches the device.