What is MessageHop?
MessageHop connects the Organization, Brand, Project, and Registered App that requested a message to durable API acceptance, provider attempts, delivery evidence, cost state, and support. Those states remain distinct so an accepted request is never presented as confirmed delivery.
Which channels are available?
SMS, WhatsApp, and email are represented in the platform. Actual sending availability is account-specific and depends on provider activation, destination rules, sender identity, template approval, consent, and project readiness. The console should be treated as the source for your enabled configuration.
How do I get started?
Sign in and verify your email, create the legal Organization and first Brand, create a Project, then register the Web, iOS, Android, server, or other approved app that owns the integration. Start in test mode and complete the production-readiness requirements shown for the account.
How do I integrate?
General sending originates from a trusted customer backend. Create a server registration, issue its scoped show-once credential, store it in a server-side secret manager, and call the versioned REST API with an idempotency key. Never embed a long-lived sending credential in browser, iOS, or Android code.
What does a successful API response mean?
A 202 Accepted response means MessageHop durably accepted the request for asynchronous processing. It does not mean the provider accepted or delivered the message. Use the returned message identifier to follow queued, provider, delivery, failure, and stale outcomes.
How does pricing work?
Where commercial sending is active, MessageHop records provider cost, the approved versioned service markup, applicable tax, currency, and rounding basis in integer minor units. Costs can remain provisional until reconciliation. Public rate cards are not listed because no undated rate should become a promise; confirm the current commercial basis for your account.
How do budgets and balances work?
The Organization is the billing owner. Project budgets and limits are controls, not separate wallets. Available, reserved, posted, provisional, and final states are kept distinct, while immutable ledger events remain authoritative over a mutable balance projection.
What can I manage in the Customer Console?
Depending on account permission and readiness, customers can manage organizations, brands, projects, registered apps, credentials, message history, usage and billing views, budgets, team members, help content, support tickets, ticket attachments, and live support conversations.
Why are there separate Customer, Staff, and Admin consoles?
They are different trust zones. The Customer Console is tenant self-service; the Staff Console supports bounded day-to-day operations; the Admin Console controls sensitive platform, provider, pricing, finance, tenant, and security workflows. Access to one does not imply access to another.
How is data protected?
Organization is the tenant boundary. Server endpoints resolve identity and ownership rather than trusting caller-supplied roles or organization IDs. Privileged changes are authenticated, authorized, and audited; sensitive sessions can require recent sign-in and TOTP. Read the security model.
Why was a credential or production action refused?
Protected actions can require an active app, sufficient scoped permission, recent sign-in, a verified second factor, current organization state, and account readiness. Fail-closed behavior is intentional when the platform cannot verify those conditions.
How do I get help?
Use Help in the Customer Console for product guidance and open a ticket for account-specific investigation. Include safe references such as organization, project, app, and message IDs. Do not paste credentials, OTPs, full message bodies, or unnecessary personal data. For access or pre-sales questions, email hello@msghop.com.
What is not a current public promise?
Universal country or provider coverage, public fixed rates, delivery-time guarantees, unlimited throughput, compliance certification, self-service funding, customer webhooks, and public SDK availability are not implied by this website. Account configuration and dated product evidence take precedence.