For developers
Send order updates, booking confirmations or service alerts from your backend. Integrate once, keep provider secrets on the server and investigate attempts through API status, webhooks and the journal.
HAILME PLATFORM · FOR PRODUCT TEAMS
Your app sends the event. We handle the notification workflow.
SMS, push, message templates, delivery history and spending controls behind one backend integration. Bring your provider accounts, test without contacting recipients and agree the scope of your LIVE pilot.
Built from a working product: HailMe already uses the platform for production SMS, push and phone sign-in codes. Its user accounts and sessions stay in the application.
Build the product. Keep delivery under control.
For teams adding transactional messages to an app or service. Start in TEST; agree countries, providers and limits before LIVE.
Keep your provider relationships
BYOC means Bring Your Own Credentials: connect your Twilio, FCM and APNs settings per project. Provider charges stay separate from platform fees.
Separate each product and environment
Manage several projects under one account, with team access, scoped API keys and separate TEST and LIVE configuration.
Understand every notification
Use one journal for API, cabinet and Geo events. Filter by channel, source and date, inspect attempts and export CSV.
Test costs before opening delivery
In TEST, follow reservations and charges, set daily and monthly project budgets, and check that exhausted budgets stop new requests.
Integrate with a documented API
Use HTTP/OpenAPI, read-only Swagger and a signed JVM SDK for evaluation. Idempotency keys preserve one operation across retries; signed webhooks bring delivery updates back to your backend. Service keys stay on your server.
Try OTP and proximity workflows
Evaluate customer Verify and Geo workflows in TEST/FAKE: code checks, expiry, limits, simulated trips and proximity events. HailMe’s own live phone OTP is a separately admitted first-party integration.
Useful across engineering and product work
For product managers
Prepare versioned, localized message templates with previews. Evaluate the notification journey, inspect outcomes and export usage and costs without digging through provider dashboards.
For teams with several products
Keep projects, access, provider settings and budgets separate. Rehearse the integration in TEST before agreeing countries, recipients, quotas and a controlled LIVE launch.
From first request to an agreed pilot
Define your scenario
Tell me your countries, channels and expected volume. Initial BYOC pilots focus on Uruguay and Argentina.
Prove it in TEST
Create a project, connect your backend and use FAKE delivery to verify results, retries, costs and limits without contacting recipients.
Agree the LIVE launch
Review provider setup, recipients, quotas and rollback together. LIVE access is enabled for the agreed scope after acceptance.
What you can evaluate today
PILOT · SMS & PUSH
Production delivery is in use by HailMe. External integrations start with individual onboarding and an agreed BYOC pilot.
TEST/FAKE · CUSTOMER VERIFY & GEO
Customer OTP and proximity workflows can be evaluated with synthetic recipients and trips. General commercial Verify LIVE and production courier tracking are not open.
IN PREPARATION · NEW CHANNELS
Telegram has a TEST lab and BYOC adapter; general production outbound remains closed. WhatsApp and RCS have TEST/protocol work, with real customer delivery pending activation. General email is in preparation; Signal is research.
See the interface before connecting
Template Studio is shown with synthetic TEST content. The API reference is public and read-only. Open either screenshot for a closer look.
SEPARATE SERVICE · ASSISTED ONBOARDING
Get communications connected for your project
Get help with account and sender registration, provider setup and integration with HailMe Platform. We agree the work around your countries, channels and volumes.
Accounts and channels
Help registering and configuring WhatsApp Business, a Telegram bot and an SMS provider. Preparation of sender ID registration requests where required.
Setup for your product
Platform integration, templates, webhooks and limits. Accounts and numbers are registered in your name where possible; setup access is agreed separately.
Scenario acceptance
Integration checks in TEST and an agreed launch scope. Account and sender approval remains with the provider; real delivery requires separate LIVE admission for the channel.
Three separate cost items
Assisted onboarding
A one-time service with its own agreed price. Scope and cost are confirmed before setup starts.
Platform fees
Platform use is billed separately under the agreed terms and limits.
Provider charges
Messages, numbers and sender registration follow your chosen providers’ terms, separate from onboarding and Platform fees.
Plan your integration with me
Assisted onboarding, Platform fees and provider charges are priced separately. Pilot terms, countries and volume limits are agreed individually. Invoicing is arranged directly; there is no automatic card charge on this site.
Talk directly with Max at Dymnoff Software Labs about your integration or an invoice.