Dashboard#
The dashboard presents the current runtime, phone numbers, calls, transcripts, messages, routing and browser-phone state.
Before you start#
- Both services running and able to reach each other.
- A production dashboard username and password when accessed remotely.
- An HTTPS browser origin for production use.
Sign in and inspect service state#
- Open the configured dashboard URL.
- Sign in with the operator credentials.
- Check the overview and runtime status before changing routing.
- Use the number view to confirm each Telnyx number's intended role.
- Use calls and messages to inspect recent activity and delivery state.
Treat transcripts and caller metadata as sensitive. Grant dashboard access only to the operator, use a unique password, and log out on shared devices.
Verify#
Open a recent call and confirm its lifecycle, duration and transcript are consistent with the provider event. Send a permitted test SMS and confirm both the dashboard status and Telnyx delivery record. If they disagree, preserve the event identifiers before troubleshooting.
If it does not work#
| Symptom | Check | Recovery |
|---|---|---|
| Sign-in fails | Whether the failure is credentials or the service | See Dashboard login or data fails |
| A call shows a lifecycle the provider disagrees with | The provider event against the dashboard record | Preserve both event identifiers before retrying anything — a retry can overwrite the evidence |
| A test SMS shows as sent but never arrives | The Telnyx delivery record rather than the dashboard status | The two disagreeing is the finding; record it |
| Transcripts are missing on completed calls | Whether transcription was enabled for that number | Enabling it later does not backfill earlier calls |