Your cabinet, step by step

Your email signs you into the platform. It does not create or modify a mobile HailMe user. One account can own several workspaces and projects.

Workspaces and projects

A workspace holds the team and a shared TEST balance. A project represents an application. Each project has separate TEST and LIVE keys, provider settings, budgets and notification history. Owner accounts can create projects and manage settings. Developer access is read-only in the cabinet.

Choose the environment first

TEST uses simulated billing and normally simulated delivery. A separately approved owner-only provider pilot is labelled in the channel settings. LIVE is for separately approved provider routes. Opening LIVE or saving a provider credential does not activate sending. A server can have real delivery enabled while an individual project or channel remains closed.

Overview

Follow the three steps: choose options, connect your backend, then check results. Open the spending link to manage the workspace wallet and project budgets. The project ID identifies the integration; it is not a secret or a service key.

Options and channels

The capability cards separate three questions: is the feature implemented, is this project connected, and can this environment send? Lifecycle badges distinguish **Available**, **In development** and **Planned**. Available is a product capability, not a grant to send. Connected means a provider configuration has been selected or a scoped connection exists. LIVE via platform is shown only when the current HailMe runtime and project admission agree. Limits still apply. Unknown or inaccessible status is shown explicitly rather than inferred from a saved credential.

**Show settings** controls visibility only. Save the selection to share it with the project team in this environment. Hiding SMS, push or OTP settings does not stop an existing integration. Use **Refresh channel status** after changing a connection; the displayed check time identifies the last read. An error reading a status is not evidence that the channel is disconnected.

Telegram bot notifications and Telegram Gateway phone OTP are separate services. The HailMe phone integration can keep SMS active while general Verify is paused. At zero Gateway balance its explicitly enabled Telegram control is limited to the free owner phone; it does not switch all mobile users to Telegram. Existing mobile clients continue to use SMS by default. Email OTP for this cabinet is also separate from application email notifications.

Stored credentials are write-only. Leaving a replacement field blank keeps the saved credential. Provider validation, route approval, environment activation and budgets remain independent. To stop delivery, an operator closes admission and reconciles accepted work; a visibility checkbox does not perform this action.

Notification journal

Use channel, source and period filters, then inspect an individual notification and its attempts. API, cabinet and Geo notifications share this journal. TEST CSV exports apply the same filters and keep destinations masked. ACCEPTED means provider acceptance; a delivery receipt is separate evidence. It does not prove a person read a message. UNKNOWN means reconciliation is needed, never an invitation to send again.

Usage and costs

Usage shows notification counts, limits and settled or reserved TEST costs by day and channel. Filter before downloading CSV. Verify has its own costs under Verify. Shared balance, top-ups, subscription samples, invoices and project budgets are under workspace Billing. Provider BYOC charges belong to your provider account and are separate from platform fees.

Affiliated projects normally pay zero platform fees. The platform owner can override the rule per organization, project or feature. Price snapshots of existing operations do not change retroactively. Zero platform fees do not bypass limits or make third-party delivery free.

Verify and Geo

Verify currently supports synthetic TEST SMS/email/Telegram challenges: five-minute expiry, five checks and two resends. Its FAKE inbox is separate from the platform sign-in email and mobile HailMe phone login. Geo is a synthetic laboratory for trips, stops and approach events. It does not track a real device.

API and SDK

Create a least-privilege service key and put it in your backend's secret store. Do not put it in a mobile app, browser, URL or screenshot. Read the quickstart before using the key. A once-visible secret cannot be displayed again. Webhook signing secrets and Maven reader credentials are different credentials.

Manual commercial onboarding

Contact Max for LIVE access, an SDK reader token, a pilot, pricing or an invoice. TEST access is not a paid subscription or automatic commercial approval.