hello247Admin

A worker only counts as answering calls when the service is running, it holds its LiveKit port, and it has registered since the last error. A healthy machine with a dead agent reads as down here, which is the whole point of this panel.

Every server reports in once a minute. If one stops reporting it shows as "stale" — a sign to check it. Bars turn amber past 60% and red past 85%.

Every step of the chain is drawn whether or not it ran, so a run that stopped halfway shows the steps it never reached rather than ending early and looking finished. Dashed and faded means not reached; a red node is where it stopped.

The monitor runs every five minutes and records transitions only, so a quiet log means a quiet system rather than a broken monitor. Live state above is computed when this page asks, and is the one to trust if the two disagree.

Set each client's recurring amount, then charge on demand or let the monthly run collect it. Card capture is done by the client in their dashboard (eway Secure Fields) or on their behalf. Every successful charge is recorded and (when connected) posted to Xero.

A declined card opens a case here and it stays until the money arrives or the ladder runs out — day 0, day 3, day 7, day 14, counted from the first failure. Running out of ladder flags the account for you; it does not switch anything off unless DUNNING_SUSPEND is armed.

In MyEway: Payments → Token Payments → Search Customers, set Status: All, then Export/Print Report. Upload it here. The export is the only place a token's status can be read — the API returns an identical record for an active token and a disabled one — and it is also the only way to find a token this platform never recorded.

Import

eWAY has no delete for a stored card — it keeps the token's card data permanently — so retiring one here takes it out of service on our side only. The token stays chargeable on the merchant account until somebody disables it in MyEway, under Payments → Token Payments → Search Customers → Actions. Disabling cannot be undone, and the record stays at eWAY for reporting either way. Nothing on this page can do it, and nothing here can verify it except an import.

Ports are lodged by hand in the Enfonica console — they have no porting API. This is the record of where each one is up to. Every stage change emails the client contact and posts to the hello247 ops group.

By email address, not by org ID — a partner is not a customer, so there is no client account to point at. Approves them and mints a referral code. Rates default to $50/mo for 12 months, then $20/mo for the life of each active referred client. They sign in at partners.hello247.com.au with a code we email them.

Link a client (their org ID) to a partner's referral code so commissions accrue to that partner. Leave the code blank to clear an attribution that was made by mistake.

Runs automatically on the 1st of each month (accrues that month, then generates a statement per partner and emails you a summary). Use the button above to run on demand.

Needs you

Only things a person here can act on right now. A port lodged with the carrier is waiting on them and is deliberately not listed — a number that cannot be cleared by doing something is a number nobody reads.

Every email the platform sends. Editing one changes what goes out from the next send — no deploy. Revert puts the built-in default back.