Connect
Integrate via API or start from the dashboard.
Business communication platform
Send messages every day
Send messages every day
Pushfy guarantees delivery SMS, RCS, WhatsApp and voice in one API
Order confirmation, access code, payment reminder, delivery status. The right channel for each message, with a record that it arrived.
Talk to the people who run the platform. No long form.
- Better delivery
- APIs
- Enterprise
- LGPD
- Support
Proprietary infrastructure
Our own platform, operated in Brazil.
Four integrated channels
SMS, RCS, WhatsApp and voice in one account.
API and dashboard
Your devs integrate via API. Your operations team sends from the dashboard.
Human support
Directly with the Brazil-based team that knows your account.
01 Where things usually get stuck
The problem isn't the message. It's the path.
You already know what you need to communicate. The friction is in the infrastructure around it.
01 with Pushfy
Four channels, one account
SMS, RCS, WhatsApp and voice in the same dashboard and under the same contract.
one contract, one report02 with Pushfy
One API, with people alongside
Open documentation and our team working with you during the integration.
goes live on schedule03 with Pushfy
People, not ticket numbers
Human support straight from the Brazil-based team that knows your account.
same-day response04 with Pushfy
Status for every message
From send to delivery, in the dashboard and back in your system via webhook.
end-to-end evidence02 Channels
Pick the right channel for each message
OTP, order confirmations and urgent notices don't call for the same channel. Here the choice is about strategy, not contracts.
PUSHFYidentified sender
Your access code is
481 209. Valid for 5 minutes. Do not share it.Order #48219 confirmed. Expected delivery on Thursday.
delivered in 2s
Pushfy verified brand
Your order is out for delivery
Arriving today between 2 and 4 PM. Track it in real time or pick another time.
Track orderReschedule delivery
Pushfy business account
Your appointment is tomorrow at 2 PM with Dr. Helena.
ConfirmReschedule
Confirm
read at 08:05
incoming call
Pushfy
Your bill is coming due
Illustrative screens showing the format of each channel.
| Message type | Recommended channel | Why |
|---|---|---|
| Access code (OTP) | SMS | Doesn't depend on an app, internet or sign-up. |
| Order confirmation | WhatsApp RCS | Holds details and images, and lets the customer reply. |
| Delivery update | SMS WhatsApp | Read right away, with a tracking link. |
| Payment reminder | WhatsApp SMS | Has to be read before the due date and let the customer pay on the spot. |
| Critical notice or overdue payment | Voice SMS | A call reaches people who don't read messages. |
| Campaign with image and button | RCS | Brand identified on the device, with an action button. |
03 PushAgent
The AI that answers and knows when it should not
An orchestrator decides on every incoming message: rules first, AI next, a human when it matters. Pick a scenario and see which layer handled it.
PushAgentyour brand's assistant
online
Where is my order 48219?
It went out for delivery today at 8:12 AM and arrives by 6 PM. Want to track it in real time?
Yes
All set: pushfy.com/rastreio/48219
decision trail
rule
AI
human
Questions with a straightforward answer don't use AI. Lower cost per conversation and zero variation in the answer.
PushAgentyour brand's assistant
online
Can I change the delivery address before it ships?
Yes, you can, as long as the order hasn't left the distribution center. Confirm the new ZIP code and I'll update it for you.
04538-133
Address updated. Delivery is still expected Thursday, same time window.
decision trail
rule
AI · knowledge base
human
The answer comes from your policy and your content, not from a model's generic knowledge.
PushAgentyour brand's assistant
online
I was charged twice on my August bill
This needs a check against your contract. I'm passing you to someone on the team now, with the whole conversation attached.
Hi, this is Marina from billing. I can already see both August charges, no need to repeat anything.
decision trail
rule
AI
human · with history
Without a basis for the answer, the AI doesn't take chances. It hands off in real time and the customer doesn't have to ask again.
Explainable Customer Intelligence
example of one contact
Churn risk
18
Propensity
72
Engagement
64
Risk / fraud
9
Each score runs from 0 to 100 and comes with the reason. The safeguard is automatic: a customer flagged as at risk is never added to a spend-incentive flow.
04 Use cases
What your company sends every day
The same problem across industries: reach the right person, at the right time, on the channel where they respond.
E-commerce and retail
Every stage has a message that saves a support contact.
- Order confirmation: right after payment.
- Delivery update: without the customer opening the site.
- Abandoned cart: with a direct link to checkout.
- Customer win-back: people who haven't bought in months.
- Satisfaction surveys and NPS: on the channel where people respond.
Sample message
Your order #48219 is out for delivery and arrives today by 6 PM. Track it: pushfy.com/rastreio
Did everything arrive OK? Reply with a score from 0 to 10 for your shopping experience.
WhatsAppSMSRCS
Fintech, lending and collections
It has to arrive before the due date and prove that it arrived.
- Payment reminder: before it becomes overdue.
- Collections and bill copies: with a link to pay or negotiate.
- Payment confirmation: cuts the "did it go through?" contact.
- Authentication and OTP: login, transactions and account changes.
- Account activity alerts: the notice people expect right away.
Sample message
Your bill of R$ 348.90 is due tomorrow (09/12). Pay via the link: pushfy.com/fatura
Your verification code is 481 209. It is valid for 5 minutes and should not be shared.
SMSWhatsAppVoice
Healthcare and clinics
Every confirmation is a slot that doesn't sit empty.
- Appointment confirmation: with replies on the same channel.
- Reminders and preparation: the day before, plus exam instructions.
- Rescheduling: when the patient can't make it.
- Follow-up and continuity: the next stage of treatment.
- Satisfaction survey: right after the visit.
Sample message
Your appointment is tomorrow at 2 PM with Dr. Helena. Reply 1 to confirm or 2 to reschedule.
Reminder: Thursday's exam requires 8 hours of fasting.
WhatsAppSMSVoice
Education
Students and parents in one place, from the calendar to tuition.
- Enrollment confirmation: and the next steps.
- Notices and announcements: exams and last-minute changes.
- Tuition billing: reminders and bill copies.
- Communication with parents: attendance, incidents, meetings.
- Re-enrollment: the window that decides the semester.
Sample message
Enrollment confirmed. Classes start on February 5 and your materials arrive by email by Friday.
September's tuition is due in 3 days. Bill copy: pushfy.com/boleto
WhatsAppSMSRCS
Logistics and delivery
Every update sent is a call your support team doesn't get.
- Tracking code: as soon as the order ships.
- Delivery window: when someone needs to be there.
- Failed attempt: reschedule before the parcel goes back.
- Delivery confirmation: with a record.
- Operational alerts: for drivers and field teams.
Sample message
Your delivery arrives today between 2 and 4 PM. If you prefer another time, reply to this message.
We tried to deliver and no one was there. Pick a new date: pushfy.com/entrega
SMSWhatsAppVoice
SaaS and technology
Messaging as part of the product, straight from the API.
- OTP and two-step verification: sign-up, login and transactions.
- Account recovery: without relying on email.
- System alerts: incidents, limits, plan expiration.
- Product notifications: what users need to see outside the app.
- Onboarding: the first days, where churn is decided.
Sample message
Your access code is 730 914. Do not share it with anyone. Our team will never ask for this code.
We detected a login on a new device. If it wasn't you, revoke access from the dashboard.
SMSWhatsAppRCS
05 How it works
From event to delivery status
The path is always the same. Only the incoming event and the outgoing channel change.
Set the rule
Which event triggers which message, on which channel and with which fallback.
Send
Real-time transactional or scheduled campaign, personalized per recipient.
Track
Status for every message, callbacks via webhook and history in the dashboard.
Sending architecture
A message's journey
EventOrder paid, invoice issued, appointment booked.
DecisionThe rule sets channel, content and timing.
ChannelSMS, RCS, WhatsApp or voice, with fallback.
PersonThe message arrives and the reply comes back on the same channel.
ResultStatus logged and returned to your system.
06 Why Pushfy
A vendor in your operation's time zone
Every platform delivers messages. The difference shows on the day something needs fixing.
Human support, from the team in Brazil
You talk to people who know the platform and your account, via WhatsApp, phone or email.
Why it mattersFailures cost hours. The time it takes to reach someone sets the size of the loss.
Technology and operations in Brazil
Proprietary infrastructure, a team in Brazil, contracts and billing in the format your finance team already uses.
Why it mattersSame time zone means meetings at the same hour and fixes on the same day.
Four channels, one contract
All four channels in one account, with the same dashboard and the same team.
Why it mattersEvery vendor you drop is one less integration and one less point of failure.
An API built for fast integration
Sending, status and webhooks, with open documentation and support from the team during integration.
Why it mattersThe cost of switching platforms is in the weeks of integration, not the monthly fee.
End-to-end traceability
Native status for every message, from send to delivery, in the dashboard and via webhook.
Why it mattersAudits, customer disputes and campaign analysis all ask for the same thing: evidence.
Commercial flexibility and scale
A proposal built on your real volume and the channels you'll use.
Why it mattersVolume isn't linear. Black Friday and month-end concentrate sending, and the contract has to keep up.
07 API and integration
Integrate via API, operate from the dashboard
Your tech team sends from application events and gets callbacks via webhook. Marketing and operations keep working in the dashboard.
- Sending via APIOne call per message or in bulk. The channel goes in the request.
- Status and webhookAutomatic callback on every status change.
- Dashboard for the operations teamSending, scheduling and reports, no code.
- Controlled accessCredentials for your account and a separate test environment.
# Sends the confirmation when the order is paid
curl -X POST https://api.pushfy.com/v1/messages \
-H "Authorization: Bearer $PUSHFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"to": "+5511999999999",
"channel": "whatsapp",
"fallback": "sms",
"template": "pedido_confirmado",
"variables": {
"pedido": "48219",
"previsao": "Thursday"
}
}'// Callback sent to your URL on every status change
{
"message_id": "msg_8f21c4a7",
"to": "+5511999999999",
"channel": "whatsapp",
"status": "delivered",
"timestamp": "2026-09-11T09:41:04-03:00",
"reference": "pedido-48219"
}// The same send from your application
const res = await fetch("https://api.pushfy.com/v1/messages", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.PUSHFY_TOKEN}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
to: cliente.telefone,
channel: "sms",
text: `Your access code is ${codigo}.`
})
});Illustrative example. The full reference for endpoints, parameters and statuses is in the documentation.
08 Scale and operations
Built for peak day
Month-end close, seasonal campaigns, incidents. The platform and the team keep up with the peak.
High volume
Large-scale campaigns and continuous transactional traffic in the same account.
- Bulk and scheduled sending
- Real-time transactional flow
- Capacity sized with the sales team
Dashboard and reports
What went out and what arrived, by campaign and by period.
- Status for every message
- Searchable history
- Consolidated view across channels
Ongoing support
A team that knows your account and shows up at critical moments.
- Help setting up your operation
- Review of channels and sending rules
- Direct contact during peaks
Sending dashboard
illustrative example
Volume by channel
SMS
WhatsApp
RCS
Voice
channel mix in the account
Message lifecycle
- Sent
- Delivered
- Read
- Webhook
09 Compliance
Scale with control over who receives what
Sending at volume only holds up when you record who asked not to receive messages and can prove what was sent. The platform provides the tools for that control.
LGPD (Brazil's General Data Protection Law) compliance also depends on your company's policies and legal bases. Pushfy provides the tools and helps with setup; the legal assessment belongs to the data controller.
Opt-outUnsubscribes recorded and honored in later sends.
Communication controlWho receives what, on which channel and at what time.
Operational traceabilityWhat was sent, to whom and with what status.
Consent managementSupport for the rules that apply to your type of communication.
10 Frequently asked questions
Before the first conversation
SMS, RCS, WhatsApp Business API and voice in the same account, the same API and the same dashboard.
Yes: sending, status lookups and callbacks via webhook. If you'd rather not write code, you can operate from the dashboard. Documentation at portal.pushfy.com/docs.
Yes. Integration starts from the events your system already generates: order confirmed, invoice issued, appointment booked.
If your tech team is busy, you can start from the dashboard and integrate later.
Yes, on proprietary infrastructure. Capacity is sized with the sales team, based on your volume and sending profile.
Yes, it's one of the most common uses. It usually runs over SMS, which doesn't depend on an installed app or internet access.
The platform records unsubscribe requests and honors them in later sends. The rules are defined together with your operation.
Yes, and that's the most common setup: WhatsApp to confirm, SMS to notify and authenticate, voice for urgent matters, with SMS as fallback.
Human, directly with the Brazil-based team that runs the platform, with commercial and operational follow-up on your account.
The proposal is based on the channels you'll use and your estimated volume. The first step is a conversation with the sales team.
Next step
Tell us which message your company needs to deliver
In one conversation, the team reviews the channels, the integration path and the commercial model for your volume. No commitment.
- Support from the team in Brazil
- Talk to the people who run the platform
- Channel and integration review