MauKirim use cases: rented WhatsApp numbers, notifications, OTP, and an iMessage API on the way

Teams often need to send a login code, order update, or payment notification without building WhatsApp connectivity from scratch. MauKirim positions itself as an AI WhatsApp Message Gateway with numbers prepared by MauKirim and a managed gateway option.

This article covers practical use cases, based on public pages checked on October 1, 2026. It does not claim that MauKirim is cheaper than Meta, Fonnte, or any other provider. Messaging prices depend on product, country, message type, taxes, volume, and account setup.

What MauKirim publicly describes

MauKirim's website lists these relevant capabilities:

• WhatsApp numbers supplied by MauKirim, so a team does not need to manage its own SIM card for the managed service.
• Usage-based OTP and notification messaging.
• A rented-number option with an inbox and incoming messages.
• An open-source WhatsApp gateway path.
• AI-assisted replies and conversation flows as part of its broader service positioning.

See the MauKirim WhatsApp gateway and messaging service for current product details. Prices and availability can change, so treat the live pages as the source of truth.

Use case 1: rent a WhatsApp number for an application

A rented number can separate application traffic from a founder's or support team's personal WhatsApp account. This fits products that need a dedicated sender for onboarding, order status, reminders, or customer replies.

MauKirim currently lists number rental at Rp149,000 per number per month. The public pricing page says this includes 2,000 messages, one inbox seat, and incoming messages. It also states that annual payment receives a 20% discount and that prices exclude 11% VAT.

Those are MauKirim's published terms, not a market-wide benchmark. Confirm eligibility, number availability, message limits, and current terms before purchase.

Use case 2: transactional notifications

Notifications fit events that already exist in an application:

• order confirmation
• shipping or delivery status
• appointment reminder
• payment status
• account activity

MauKirim's public pages describe notification messaging and show usage-based pricing. The homepage currently displays Rp28 per message on a reserved number and Rp60 without reservation; its pricing page may show different volume tiers. Check the current pricing table before estimating cost.

WhatsApp's own Cloud API documentation lists order confirmations, shipping updates, appointment reminders, and other transactional communication as supported business use cases. That does not mean every implementation has identical approval, template, or policy requirements. Your message design and account configuration still matter.

Use case 3: OTP and fallback delivery

OTP needs predictable delivery and a clear failure path. MauKirim describes WhatsApp OTP with reserved or non-reserved numbers, plus SMS fallback when WhatsApp delivery fails.

The homepage currently lists Rp165 per OTP with a reserved number and Rp350 per OTP without reservation. These figures describe MauKirim's displayed pricing at the time of research. They do not prove a lower total cost than Meta or another provider.

For an OTP flow, the implementation should cover:

1. Generate a short-lived, single-use code.
2. Send it through the selected channel.
3. Set an attempt limit and expiration time.
4. Avoid logging the raw code.
5. Offer fallback delivery only when policy and risk controls allow it.
6. Record delivery status without treating delivery as proof of identity.

MauKirim's service page is the place to confirm API behavior, webhook details, rate limits, and integration requirements. Public marketing pages alone do not establish those technical details.

iMessage API: coming soon, not available as a current feature

MauKirim's requested product direction includes an iMessage API coming soon. That should be treated as a roadmap statement, not a currently available API. No launch date, endpoint, pricing, supported message types, or production SLA is claimed here.

Teams choosing a provider today should plan around the currently documented WhatsApp capabilities. Revisit the MauKirim product page when an iMessage API announcement and technical documentation are published.

MauKirim and Fonnte: factual comparison

Area	MauKirim	Fonnte
Public positioning	AI WhatsApp Message Gateway with numbers prepared by MauKirim and an open-source gateway path	Fonnte describes itself as an unofficial WhatsApp API gateway in Indonesia
Number model	MauKirim publicly lists supplied numbers and rental pricing	Fonnte's public homepage describes its gateway; this article does not infer a matching number-rental model without a verified source
OTP	MauKirim publicly lists WhatsApp OTP pricing and SMS fallback	Fonnte's public homepage was not used here to claim a specific OTP product, price, or fallback behavior
Notifications	MauKirim publicly lists usage-based notification pricing	Fonnte provides WhatsApp gateway positioning; compare current API and pricing documentation directly
iMessage API	Described here as coming soon, not currently verified as live	No iMessage claim made

This is a narrow comparison. It avoids unsupported claims about cost, reliability, official WhatsApp status, verification badges, or blue ticks.

What independent documentation adds

Meta's WhatsApp Business Platform Cloud API documentation confirms that businesses can programmatically send text, rich media, and interactive messages. It also lists order updates, reminders, and one-time passwords among possible business uses, while documenting business phone numbers, templates, and analytics through related APIs.

Twilio's WhatsApp developer documentation provides an independent provider's implementation perspective for integrating WhatsApp Business Platform messaging through APIs. Its existence supports the general API integration pattern, not any claim about MauKirim's specific implementation or economics.

Fonnte's official website is included for product comparison. It labels the service an "Unofficial Whatsapp API Gateway Indonesia." That label is Fonnte's own wording; this article does not use it to judge reliability or compliance.

Practical fit

MauKirim is worth evaluating when a team wants a prepared WhatsApp number, usage-based OTP or notification messaging, and a managed inbox path. It may be a poor fit if your requirements depend on an already documented iMessage API, a specific WhatsApp account model, or enterprise guarantees that are not published on the pages reviewed here.

Before integration, ask for current API documentation, authentication and webhook behavior, delivery-status semantics, rate limits, retention policy, consent requirements, escalation support, and the complete price calculation including tax and fallback messages.

Research and author note

This article was prepared from the MauKirim website and pricing pages, Fonnte's official website, Meta's WhatsApp Business Platform documentation, and Twilio's WhatsApp developer documentation. Pages were checked on October 1, 2026. Claims about MauKirim features and prices are limited to what those public pages displayed. No performance test, delivery-rate study, legal review, or price benchmark was performed.

The author works with web content and API-focused product research. Readers should verify live documentation and commercial terms before deploying OTP or customer messaging in production.