E-commerce
−38% support
Fashion retailer
Proactive WhatsApp shipping updates cut support tickets 38%; "where's my order" calls went near zero.
Omnichannel messaging
One message.
Five channels.
Wherever the customer is
awake.
WhatsApp, SMS, email, push and in-app — all five run on one infrastructure with delivery, consent and reporting built in. You reach customers on the channel they actually use, at the right moment, with provable delivery — instead of stitching together three vendors and praying.
Single-channel dependency (email-only or SMS-only) saturates fast. Omnichannel routes the right message at the right time over the right channel and lifts delivery up to 38%.
New message
Live
Siparişiniz kargoda 🚚
Target: 5 channels
#TX-48291
WhatsApp
SMS
Push
In-App
Email
5/5 delivered
1,234 / last hour
Why single-channel fails
If you rely only on email, you are reaching just 22% of your customers.
Email's average open rate is 22%. Of every 100 messages, 78 go unseen. WhatsApp lifts that to 97%, SMS to 99% — but cost explodes if used alone. 63% of your customers are active on 4+ channels; a single-channel brand is not where the customer is. Worse, your support conversations are split across 3-4 systems; context is lost and customers repeat themselves.
01
Email alone is 22%
Open rates fall yearly; spam filters tightened, inboxes crowded. "We sent it" is not "we reached them".
02
Customer on 4+ channels
A typical customer uses WhatsApp, email, SMS, Instagram DM and app push together. They don't know where to find you.
03
Fragmented context
Complaint on WhatsApp, order via email, confirmation by SMS — three systems. Nobody owns the unified customer profile.
04
Wrong time, wrong channel
Urgent shipping note via email — read 6 hours later. Marketing via SMS — annoying. Channel ↔ message fit is missing.
05
No delivery transparency
A system that says "sent" but doesn't know "delivered" is an operational risk. Bounces, opt-outs, error codes are invisible; you keep sending to the wrong person for weeks.
06
Consent chaos
For GDPR/KVKK: who opted-in to which channel? Without one source of truth, you're exposed. One opt-out must apply across all channels.
One engine — five paths
Compose once. Five channels in parallel. Watch the delivery rates live.
WhatsApp
97%
delivery rate
SMS
99%
delivery rate
In-App
100%
delivery rate
Push
84%
delivery rate
Email
71%
delivery rate
WhatsApp
09:42
Siparişiniz kargoda 🚚
Delivered
SIM-8298
SMS
09:42
Siparis #48291 kargoda. Takip: bit.ly/x
Delivered
SIM-4526
In-App
09:42
Siparişiniz yola çıktı
Delivered
SIM-8091
Push
09:42
📦 Kargonuz yolda
Delivered
SIM-9802
Email
09:42
Konu: Siparişiniz #48291 kargoda
Delivered
SIM-8478
Unified inbox
All channels
Wh
WhatsApp
Ayşe K.
2dk
When will it arrive?
Em
Email
Mehmet D.
5dk
Question about invoice…
SM
SMS
+90 532 …
8dk
YES
In
In-App
user_4821
12dk
Any color options?
Pu
Push
Zeynep A.
18dk
Notification clicked
Replies from WhatsApp, email, SMS, in-app and push land in one view — your team never tab-hops.
Routing rule
Smart channel choice — by rule, not by gut.
IF user.opened_whatsapp < 7d
THEN send via whatsapp
ELSE IF user.has_push_token
THEN send via push
ELSE sms → email // fallback chain
For each customer, the channel with the highest open probability is chosen automatically. If the primary fails, the fallback chain kicks in — the message never gets lost.
Live counter
1,234 messages last hour
•
97% WhatsApp delivered
•
42 fallbacks triggered
•
3 templates pending
•
0 send errors
Who it's for
Companies that talk to customers daily — every touch matters.
01
E-commerce
Order confirmations, shipping status, returns, cart reminders — thousands of transactional sends daily. WhatsApp shipping notes cut support load by 38%.
02
Marketplaces (two-sided)
Messaging between buyer and seller; payment, dispute, review. SMS + WhatsApp + email required.
03
Education platform
Class reminders, exam notice, assignment due, certificate delivery. Push + SMS mix lifts attendance 27%.
04
Healthcare
Appointment confirmation, reminders, results, follow-up. When the phone doesn't reach, WhatsApp saves; no-shows drop 27%.
05
Financial services
2FA, transaction alerts, fraud notices, billing. SMS for compliance, push for speed, email for documents — all three.
06
Hospitality
Reservation, check-in, room service, concierge chat. WhatsApp Business gives guests a digital reception feel.
07
B2B customer success
Account managers hybrid WhatsApp + email; account data, usage alerts, renewal chats.
08
Agencies
Agencies running omnichannel campaigns for clients; one infra serves many brands.
10 capabilities — one stack
From WhatsApp Business to email deliverability — every piece set up.
Messaging infrastructure is more than "API integration". Vendor selection, account approval, template authoring, DNS verification, opt-in flows, fallback chains, reporting — each takes specialist work. Partnerfy unifies them.
01
WhatsApp Business API setup
Meta Business verification, sender ID, template approval, interactive messages (buttons/lists), clickable CTAs, media sends.
02
SMS gateway — TR carriers
NetGSM, Verimor, Iletimerkezi (TR) + Twilio, Vonage (international). Operator-header (sender ID) registration, short vs long number decision.
03
Email deliverability infra
SPF, DKIM, DMARC records; dedicated IP warm-up; Postmark/SendGrid/SES selection; spam score monitoring; bounce handling.
04
Push notifications (iOS + Android)
FCM (Android) + APNs (iOS) one API; segment targeting, scheduled sends, deep-links, rich-media push, silent push.
05
In-app messaging
Banner, modal, tooltip, story; in-session intervention; Firebase In-App Messaging or Iterable integration.
06
Unified inbox
All-channel replies in one view; agent assignment, labels, status (open/resolved), SLA tracking.
07
Routing rules & fallback
User preference + channel availability + cost → rule engine. If primary fails, fallback chain kicks in.
08
Opt-in management
GDPR/KVKK-compliant double opt-in; per-channel consent; single opt-out propagates across all channels; audit trail.
09
Delivery analytics
Sent → delivered → opened → clicked → replied funnel; per-channel ROI; weekly automated reports.
10
Template approval workflow
Multi-language template prep, submission to Meta/carrier, rejection-reason fixes, versioning.
Process
From current-state audit to live — 6 clear steps.
-
01
Week 1 · Channel audit
Current channels, volume, open rates, cost, leak points. What's missing, what's redundant.
-
02
Week 2 · Vendor selection
WhatsApp BSP, SMS aggregator, email service, push platform — by region, price, features, and contracts.
-
03
Week 3-4 · Integrations
API keys, webhooks, CRM connection, customer ID mapping, queue + retry logic.
-
04
Week 4-5 · Template approvals
WhatsApp + SMS templates in multiple languages, submitted to Meta; fix-and-resubmit if rejected.
-
05
Week 5-6 · Routing rules
Rule engine by preference, availability, cost, season. A/B-validated with test users.
-
06
Ongoing · Monitor & tune
Delivery, open, conversion dashboard. Weekly channel review, per-channel ROI, fallback tuning.
Tools we use
Industry-standard providers — vendor-neutral, end-to-end integrated.
Twilio
MessageBird
Vonage
Infobip
WhatsApp Business API
SendGrid
Mailgun
Postmark
AWS SES
OneSignal
Pusher Beams
Iterable
Klaviyo
Intercom
NetGSM
Verimor
APNs
Firebase FCM
Client stories
Same infra. Different sectors. Same result: less support, more conversion.
Marketplace
+14% conv.
Local marketplace
Real-time SMS + WhatsApp to seller post-payment; buyer-seller match time down 14%, conversion up.
Healthcare
−27% no-show
Multi-branch clinic
WhatsApp 24-hour appointment reminders + confirm; no-show dropped 27%, call-centre load −44%.
B2B SaaS
−18% churn
API platform
Usage threshold alerts via push + email + Slack; customer briefed before renewal call, churn cut 18%.
Finance
+7pp login
Payments app
When 2FA SMS fails, WhatsApp fallback continues; login success rose from 91% to 98%.
Hotel
NPS +0.5
Boutique hotel chain
WhatsApp concierge handles room service and complaints in one thread; guest NPS 4.2 → 4.7.
FAQ
The 8 most asked questions about messaging infrastructure
There is no direct access; you go through a BSP (Business Solution Provider). Twilio, MessageBird, Vonage and 360dialog connect your Meta Business Manager. Typical timeline: Meta Business verification 2-5 days (tax ID, incorporation document needed), phone-number registration 1-3 days, first template approvals 1-3 business days. End-to-end 7-14 days is normal. Partnerfy handles everything from preparing verification documents to the registration flow; you only sign.
It depends on context. For marketing, an alphanumeric sender ID (e.g. "MYBRAND") is used; it requires KOSGEB registration and carrier approval (via Turkish iletim merkezleri) and must respect the legal-message frame. Transactional (OTP, shipping) can use the same sender ID or a long number (full international format) — long numbers enable two-way and let users reply "STOP". Short codes (5-6 digits) are reserved for premium-rate billing in Türkiye and not appropriate for marketing. Recommendation: alphanumeric sender ID + long number combo for most cases.
Work happens at three layers. (1) DNS: correctly configured SPF, DKIM, DMARC; DMARC policy tightened gradually (none → quarantine → reject). (2) Infrastructure: with a dedicated IP, a warm-up process — start low volume and ramp over the first 30 days; on shared IPs, the provider's reputation is critical. (3) Content: avoid spam-trigger words, balance image/text, one-click unsubscribe, correct "from". Postmark has the highest transactional deliverability; SendGrid/SES for high volume. Monthly spam-score and blacklist scans are part of the routine.
If misused — yes. Irrelevant push is the #1 reason users uninstall. The keys are segmentation and frequency discipline. General marketing push: max 1-2/week with segment-relevant content. Transactional push (order status, payment confirmation, security alert) is exempt — users expect it. Quiet hours (no sends 22:00-08:00), timezone alignment, deep-links (push opens the relevant screen, not the home), A/B testing are critical. Opt-out rate under 2% means your strategy is healthy; above 5% needs urgent revision.
Double opt-in is mandatory: at sign-up the user clearly sees which channel and message type they'll receive and confirms. Separate consent per channel (email opt-in does not cover WhatsApp). A single opt-out should propagate to all channels — not strictly required but best practice. For KVKK: personal-data inventory (VERBİS) in Türkiye, clarification text, explicit consent. Data retention, cross-border transfer (relevant if you use non-TR providers), right to be forgotten must be operationally implemented. Partnerfy sets up a KVKK-compliant opt-in stack; for legal text we recommend separate counsel.
No. Phased rollout is essential. First, audit current state: which channels are already in use, how do they perform, where are the gaps. Typical priority: (1) transactional email (if infra missing or deliverability low), (2) WhatsApp Business (highest open, channel customers love), (3) push (if you have an app), (4) SMS (for critical transactional), (5) in-app messaging (last, deeper integration). One channel live per quarter is realistic. Teams that launch five at once run each one half-baked — none optimised.
Yes. Messaging infra's heart is CRM integration — without it you're just a "spam sender". Pre-built connectors exist (official for HubSpot, Salesforce, Pipedrive, Zoho; Twilio Segment bridges many CRMs), for custom systems we set up a two-way sync via REST API + webhooks. The customer profile accumulates in one place: which channel they received, replied, clicked. That profile drives the next routing decision. Integration typically takes 2-4 weeks; longer if existing data needs cleaning.
Each channel prices differently. WhatsApp: per-conversation (Meta's conversation pricing — marketing, utility, service have different prices; for TR roughly 0.03-0.10 USD); when customer replies, a 24-hour service window opens. SMS: per-message; TR domestic 0.05-0.15 TL, international 0.05-0.50 USD by country. Email: monthly subscription (Postmark $10/10k, SendGrid free tier to start) — in practice the cheapest channel. Push: completely free (no FCM/APNs service fee), only infra cost. In-app: depends on platform. Typical mix: for an e-commerce with 100k MAU, total messaging bill lands in $300-1,000/month depending on send profile.
Start talking to your customer on the right channel.
A free 30-minute call to review your current channel performance; we share the highest-impact channel rollout order for your first 90 days.