CLI Help Desk Playbook

CLI Help Desk Playbook

Use this script to guide customers using moby in production.

Scope

• Customer has a Mobayilo account.
• Customer wants to call from terminal with moby.
• Support goal is to get customer from login to successful call.

Standard support flow

1) Confirm prerequisites

Ask customer to confirm:

• moby is installed and runnable (moby --help).
• They have a valid CLI token.
• They are on production by default (no --host needed).

If moby is not installed yet:

curl -fsSL https://mobycli.mobayilo.com/install.sh | sh

Then ask customer to update binary first:

moby self-update
moby --version

2) Login and verify auth

Ask customer to run:

moby auth login
moby auth status --json

Expected: "authenticated": true

Fallback if browser/device login is blocked:

moby auth login --api-token <YOUR_CLI_TOKEN>

3) Confirm account balance

moby balance --json

If balance_cents is 0, customer must top up before caller ID verification or calling.

4) Verify caller ID (mandatory for CLI calling)

Request code:

moby caller-id request <PHONE_NUMBER> [--country <ISO>]

CLI prompts immediately for SMS code after request. Manual fallback:

moby caller-id confirm <SMS_CODE>

Phone format rule:

• Caller ID request accepts local or international input.
• If user enters a local number, include --country <ISO> (for example JP, US).
• confirm reuses the most recent request reference saved locally.

5) Place call

Place call directly:

moby call <DESTINATION> [--country <ISO_OR_NAME>]

Destination format rule:

• Destination can be E.164 or local format.
• For local format, pass --country <ISO_OR_NAME> (example: JP or Japan).
• moby call defaults to desktop audio mode and auto-starts local agent when needed.
• Use --callback only for legacy phone callback.

6) Top up if needed

moby topup 5

Note:

• Stripe payment opens automatically in browser by default (--no-open disables auto-open).
• Minimum top-up is $5.00 (some account types may require more).

Fast error triage

• authentication token required
  • Action: run moby auth login ... again or pass --token.
• new version available notice
  • Action: run moby self-update and retry command.
• invalid_token / expired_token / revoked_token
  • Action: issue a new CLI token and re-login.
• positive_balance_required
  • Action: top up account and retry.
• missing_caller_id
  • Action: complete caller ID request + confirm flow.
• invalid_destination
  • Action: retry with valid number; if local format, add --country.
• invalid_amount
  • Action: increase top-up amount to minimum allowed.

How customer gets manual CLI token

Manual token path is fallback only.

1. Customer signs in to Mobayilo web app.
2. Go to Settings -> CLI access.
3. Create token (scope + expiry).
4. Copy token once and run:

moby auth login --api-token <YOUR_CLI_TOKEN>

Copy-paste response template for support

Please run these commands in order:
1) moby self-update
2) moby auth login
3) moby auth status --json
4) moby balance --json
5) moby caller-id request <NATIONAL_NUMBER> --country <ISO>
6) (enter SMS code in prompt, or run: moby caller-id confirm <SMS_CODE>)
7) moby call <DESTINATION> [--country <ISO_OR_NAME>]

If browser login is blocked, use:
moby auth login --api-token <YOUR_CLI_TOKEN>

If balance is zero, run:
moby topup 5

Escalate when

• Customer receives repeated 5xx API errors.
• SMS code never arrives after repeated retries.
• Caller ID confirm keeps failing with valid code.
• Account appears authenticated but data is inconsistent across status and balance.