These work for every product, not just voice agents. diagnose reads the records of a call or message on your account and explains what happened; ask answers questions about Plivo in plain English. To read the documentation itself from the terminal, see Read the docs from your terminal.
Diagnose a call or message
Give the CLI a call or message UUID and it explains what happened: whose side failed (your server, Plivo, the carrier), the timeline, and what to do next. It reads Plivo’s call and message records and carrier reports for you.
Commands
Examples
A typical answer for a failed inbound call:
Use -o json to receive the analysis as a stream of events. Answers usually take about a minute (allow 30 to 120 seconds) and are written by the AI assistant, so read them as an explanation rather than parsing them as a fixed schema; only calls and messages on your own account can be diagnosed.
Ask a question
Ask Plivo’s AI assistant a question without leaving the terminal. The assistant searches the Plivo documentation, reads the relevant pages, and streams an answer with source links.
Command: plivo ask "<question>"
Flags
-i, --interactive: start a chat session that keeps context between turns (/reset, /help, /exit). Use -o table when input is piped.-o json: emit the answer as one JSON event per line (start, tool_call, tool_output, token, final), for scripts and agents.
Examples
ask and diagnose share a rate limit per account. If you see RATE_LIMITED, wait for the retry interval shown in the error.
plivo support
List the support escalations raised from your account through the assistant. Requires a browser login (plivo login), because escalations are scoped to the person who raised them. 
