WORKSPACE
Welcome
Contact phone (optional)
PLATFORM OWNER
Affiliation & platform fees
Affiliated projects default to waived platform fees for all features. You can charge standard fees for the whole project or selected features at your discretion.
Saving a rule does not send notifications, activate a feature or move money. External provider costs remain separate. Existing charges and reservations keep their original prices. Budgets, country restrictions and safety limits still apply.
Showing the first 500 projects.
How fee rules are resolved
Priority: project feature → project rule → organization feature → organization rule → affiliation default. Project rules override organization rules. Standard amounts currently exist only as TEST samples. Rules never change accepted price snapshots or provider invoices.
Fee change history
No manual changes yet.
Your workspaces
Each workspace has its own team and shared balance. Open one to manage its projects.
ORGANIZATION
Your projects
No projects yet.
ORGANIZATION BILLING
Subscription, balance & invoices
Test amounts are shared across this organization's projects. They do not pay for LIVE delivery or your mobile HailMe subscription. Zeta and DGI are not connected; these documents are not CFE.
For a real pilot, activation or invoice, contact Max.
Loading billing…
SUBSCRIPTION
Sample terms for testing. No automatic renewal or approved LIVE offer.
TEST BALANCE
Reserved: · Test delivery charges: .
Test delivery billing
Funds are reserved before a TEST/FAKE job is admitted. FAKE acceptance charges the snapshot price once. Failed or expired jobs release it. UNKNOWN keeps the reserve pending review. These rates are test fixtures, not a LIVE offer.
Create a project in your organization to try a billed test notification.
Project budgets · TEST/FAKE
Calendar days and months in UTC. Committed cost = accepted jobs admitted in the period plus all pending reserves, including older UNKNOWN jobs. Blank means unlimited; zero pauses new sends. Lowering a limit never cancels admitted jobs. Clear project budgets before disabling test usage billing.
Delivery reservations & charges
No billed test notifications yet.
Reservation events
Test invoices
Latest 100. No fiscal documents or real payment confirmations.
No invoices yet.
Balance history
Latest 100 credits and debits. Amounts are stored in integer cents.
No balance movements yet.
PROJECT
SMS country restrictions
·
START HERE
Your project at a glance
Choose your channels, connect your backend and follow every notification from request to result.
Sending environment
TEST and LIVE keep separate keys and provider settings. Selecting LIVE does not activate it.
Spending & limits
Notification expenses are in Usage. Verify has its own cost summary. Both use the TEST wallet and project budgets.
Manage balance & budgetsHow does HailMe Platform work?
Your backend requests a notification. The platform checks the project, environment, template, permissions and limits, then queues one operation. A provider handles delivery. The journal records the result. Replaying the same request with the same key does not create a second operation within the retention period.
OTP verification checks a code. Your backend still owns user accounts, sessions and access decisions.
Read the cabinet guideMessage templates
Create SMS, push and Telegram TEST messages here. Your backend sends a template ID, recipient language and parameters. Published content is immutable: publish a new versioned ID for each change.
Preview values must be fictional. This editor never sends a message. Phone OTP and HailMe mobile payloads use their separate protected protocols.
First 200 templates shown.
Exact preview
SMS segments include the signature. This preview uses STANDARD_V1; provider-specific segmentation and the current TEST price are fixed during admission, before balance reservation. No real invoice or payment is created.
Use in your backend or SDK
Options & channels
Check an option to show its setup. Uncheck it to hide the settings for this project and environment.
These switches customize your workspace. They do not activate or stop delivery, erase credentials, change permissions, cancel jobs or remove budgets. Configure a channel and review its delivery status separately.
SMS configurations
Twilio settings belong to this application and the selected TEST or LIVE environment. Auth Tokens are encrypted and write-only. Saving or selecting a configuration does not activate delivery. TEST sends remain simulated.
The save result is unconfirmed. Refresh and inspect the configuration/version before editing again. Tokens are never recovered or resent automatically.
Push configurations
Credentials are encrypted and write-only. LOCAL_ONLY validates the file and declared project/key format; provider permissions, package/bundle ownership and device delivery still need operator verification. Stored configuration is separate from operator-approved delivery. TEST is simulated.
The save result is unconfirmed. Refresh and inspect the configuration/version before editing again. Credentials are never recovered or resent automatically.
Email notifications
Application email is being prepared. Account sign-in email already runs inside the platform through its separate system sender. No customer email transport is enabled by this option.
Read the email and OTP rollout planWhatsApp · preparation
Not connected · no messages can be sent
- Use your own Meta Business portfolio, WhatsApp Business Account and sending number.
- Prepare approved templates, including Authentication templates for OTP, and recipient consent.
- Connect scoped credentials and signed webhook processing when the adapter is available.
Provider IDs, credentials and live activation are not collected here yet. This checklist is preparation, not a working connection.
Connection requirementsTelegram
Real Telegram delivery is in preparation. The isolated TEST laboratory is available to project owners when its stage feature flag is enabled. No real bot token or chat ID is collected here.
Read the Telegram integration guideYour own Telegram bot · BYOC
Outgoing messages require operator activation. Default delivery is blocked. A scoped owner pilot can permit one real Telegram message, as shown below. Billing is simulated in TEST; no real payment is enabled. The FAKE laboratory below is separate.
2 · Verify identity and webhook
First verify the bot, then register this platform's webhook. Another service's callback is never overwritten. Registration retains pending updates and does not send a message.
3 · Consent and recipient binding
Use fictional application references for acceptance. A phone or username cannot substitute for an opted-in private chat. Your backend must authenticate the account before confirming its reference. No message-sending button is enabled here.
One message to the owner
Pacing: up to 20 messages per bot/second and one per private chat/second; Telegram cooldowns can be longer. An uncertain provider response requires review and is never blindly retried. These are safety ceilings, not an activated sending quota.
BYOC setup and API guideSimulation only · No bot is created or contacted. Use fictional test: references and fake: chats. These steps simulate private /start, account confirmation, queue delivery and TEST billing.
Linked TEST recipients
Signal · research
Unavailable · technical feasibility review required
A supported business/bot integration has not been established. No account linking, gateway, number registration or third-party bridge is started by this option. Signal will stay outside customer delivery until a supportable route is accepted.
Research boundariesHailMe Verify
One-time codes with expiry, attempt limits and per-project fees. Currently TEST/FAKE with synthetic recipients.
Open VerifyGeo notifications
Build a synthetic trip, load stops and simulate proximity. No real location is collected.
Open Geo laboratoryWebhook destination
The signing-key result is unconfirmed. Refresh to inspect the active key ID. The secret cannot be recovered; rotate explicitly again only after checking the current configuration.
Save this signing secret now
Install it on your receiver before verification. It disappears on hide, refresh, sign out or navigation and cannot be read again.
Webhook diagnostics
Notification journal
ACCEPTED means provider acceptance. SMS delivery receipts are separate provider reports, not proof of a person reading. FCM/APNs acceptance does not confirm handset delivery. LOCAL_TEST receipts are simulations. UNKNOWN requires reconciliation and is never retried automatically.
CSV includes all matching retained notifications at export time, up to 5,000 rows. Narrow the period or filters for larger journals. TEST/FAKE only; destinations stay masked. No message bodies or credentials.
Notification detail
Attempt journal
Provider receipt evidence
Usage & notification costs
CSV uses the displayed period and costs, in USD with two decimal places. TEST/FAKE funds only.
Costs by creation day in UTC. The first and last day cover only the selected hours. Released funds return to the test balance; they are not expenses.
| Day | Charged | Reserved | Released | Notifications |
|---|
| Channel | Charged | Reserved | Released | Notifications |
|---|
SMS segments
Additional admission limits
SMS route policies
Operations count once when admitted; attempts count when started during this period, including retries. FAKE attempts are simulations. The original caps are lifetime operation counters. Additional limits may reset daily or monthly in UTC. Segment reservations use a calculation of the admitted text, once per operation. Provider-reported segments are separate facts; LOCAL_TEST reports are simulations. Started attempts do not prove a network request or a bill. TEST costs use recorded notification prices, not the number of provider attempts. Subscription fees and top-ups belong to organization Billing.
HailMe Verify · TEST laboratory
Reserve a sample success fee when creating a verification. One successful check settles it once; expiry, cancellation or five failed checks release it. No SMS or email is sent. This service does not sign anyone into HailMe.
Sample standard fee: USD 0.05 per unique successful verification. Affiliation and VERIFY overrides apply at creation. FAKE delivery cost is zero; this is not a live provider quote. TTL 5 minutes, five checks, two resends with a 30-second cooldown. Resend keeps the original expiry and check limit.
Manage TEST balance and budgetsVerify charges use the same test wallet and project budgets as notifications. The costs below cover Verify; notification Usage and its CSV cover SMS/push notifications.
Geo TEST laboratory
Bulk-load stops, simulate an approach and inspect the budget reservation and charge. This page never reads a device location or contacts a real phone. No actual courier is tracked.
Each confirmed stop creates one FAKE SMS using the current sandbox rate and project budget. Stops are processed in order. Trips expire after one hour. Cancelling stops new admissions; jobs already admitted continue. FAKE acceptance does not prove handset delivery.
Connect with API or SDK
Your backend calls the platform. Mobile applications use your authenticated backend; service keys stay on the server.
First TEST API notification
This sandbox template uses FAKE delivery. No SMS is sent and no provider credentials are used. Your saved BYOC configuration is checked locally; provider access and LIVE delivery need separate approval.
Create a TEST service key with notifications:write, notifications:read, templates:read and usage:read below. Use it only on your backend. Keep service keys out of browsers and mobile apps.
For sample expenses, open Billing, add test funds, activate the sample subscription and enable test usage billing. This records simulated HailMe fees only. Your provider account is billed separately for real BYOC traffic.
The fictional +12025550131 recipient is for FAKE development only. Reuse the same idempotency key and identical payload after an uncertain response. Check the returned notification ID in this project's journal and Usage.
Service keys
No service keys in this environment.
The creation result is unconfirmed. Check the list and revoke any unread key before creating another. The secret cannot be recovered.
Save this secret now
This secret disappears when you leave, refresh, sign out or close this panel. It cannot be displayed again.
Your account is ready. Your workspace will appear here. Reload to check access.
Need LIVE access, SDK access or an invoice? Contact Max
Commercial onboarding and invoices are handled personally for now. This form prepares an email in your mail app; nothing is sent automatically.
Loading your account…