Unable to refresh the dashboard. Showing the last received data. Controls will become available when the connection returns.
Recent activity could not be saved or restored. Check the app’s storage permissions. Current activity remains visible for this process.
VOICE OPERATIONS
Line overview
A little visibility. A lot of peace of mind.
Active calls
Follow calls as they happen.
Connection checklist
Saved configuration, not a connectivity test.
Recent activity
The latest events from your voice line.
Activity retains the latest 1,000 events across restarts. Call minutes, texts, and estimated cost for this month and for the life of the line are stored separately and do not shrink when that activity rolls off. The month is Central time and starts over on the 1st. Estimates are not provider billing. Active calls end if the app restarts.
MONITOR
Call activity
Call events, verification results, and callback proposals.
Activity stream
Latest 150 events shown. Export includes all retained events.
Callback tickets are proposals. Approval happens in the PIM’s Email / Action Approval screen.
CONFIGURE
Line settings
Make the line work the way your team does.
CONNECT
Service connections
Set up the services behind your voice line.
Test saved connections
Read-only checks. Save connection settings before running a test.
Phone routing setup
Complete these steps with your administrator.
- Attach your Twilio number to an Elastic SIP trunk with origination
sip:{number}@sip.voice.x.ai;transport=tls. - Register the number with xAI using the repository’s
--register-numbercommand. Save the returned webhook secret above. - Set the xAI webhook URL to
Loading…. - Add your staff caller IDs in Line settings, then complete a staff smoke test.
Pausing rejects incoming calls at this bridge; it does not release the Twilio number or stop provider subscription charges. The repository’s --kill-switch command removes xAI number registration.
VERIFY
Test lab
Exercise the bridge with synthetic orders and simulated calls.
Run a sample call
Verify a synthetic order and retrieve its status.
Caller admitted→Order verified→Status returned
Uses the saved caller list and current mock fault. No phone call, audio, or paid service is involved.
Simulate a PIM issue
Check the response when an upstream service fails.
PROTECT & PLAN
Operating controls
Set your call allowance and when the line is available.
FOLLOW THROUGH
Callbacks & alerts
See what needs a person’s attention.
Failure alerts
Loading delivery settings…
Callback requests
Submitted means received by PIM for human approval. An uncertain result must be checked in PIM before any manual resubmission.
Requests are never automatically retried. Reviewed entries older than 30 days are removed when new requests arrive; unresolved requests remain. Request details can contain private contact information.
RECOVER & MANAGE
Recovery & team
Recover a known configuration and give each operator their own login.
Settings history
The last 20 versions. Restoring creates a new version and also restores saved service credentials.
Recovery backup
Includes saved settings, operators, callback history, usage, activity and encryption keys.
Pause the line and finish active calls first. This ZIP contains keys capable of reading private data and credentials. Store it in a restricted, encrypted location. Follow the restore instructions in DEPLOY-AZURE.md with the app stopped.
Individual operators
Operators can manage the line. Administrators can also manage accounts and download backups.
Your password
Changing it signs you out on every device.