FAQ
Use these answers as a quick decision guide while you configure, run, monitor, and troubleshoot RocketAiFlow.
For deeper steps, open the linked pages from each answer.
Where should I start if this is my first setup?
Start with Quickstart, then create one focused agent, connect one route or campaign, run one controlled call, and review the result before adding more complexity.
Is RocketAiFlow only for outbound campaigns?
No. RocketAiFlow is outbound-first and inbound-ready. Outbound campaigns are a primary operating model, but the same agent, prompt, function, telephony, and monitoring model also supports controlled inbound workflows.
What is the safest first pilot scope?
Use one agent, one prompt, one route or one small outbound campaign, conservative call limits, and a small contact list. A narrow pilot makes call behavior, telephony issues, prompt changes, and outcome review easier to understand.
Do I need inbound routing before testing an agent?
Not always. You can test the agent from the Phone area first, then connect the validated agent to AI Inbound Routing.
What should I review after the first call?
Open Call Records and check status, outcome, timing, transcript, recording state when enabled, and any useful review notes. This confirms whether the workflow behaved as expected.
What should I monitor during an outbound run?
Start from Pre-Provisioned Dashboards. The Dialer dashboard shows campaign state, active calls, call limits, dialing rate, total outcomes, selected-range performance, talk time, and ring time.
Why does Real-Time Agents & Trunks matter?
It separates campaign behavior from telephony readiness. If the campaign looks active but calls do not move correctly, endpoint and trunk state can show whether the issue is registration, reachability, provider behavior, or endpoint configuration.
Where do I learn what each Dialer panel means?
Use Dialer Dashboard Panels. It explains Total Outcomes, Call Outcomes, Dialing Rate, Calls Volume, Active Calls vs Limit, endpoint state, talk time, ring time, and selected time-range panels.
When should I use logs and traces?
Use Logs and Traces when a dashboard shows a symptom but you need event-level evidence, service timing, API action behavior, trace correlation, or the exact path of a workflow issue.
What is the safest way to troubleshoot?
Change one thing at a time, run one controlled test, and review one call record plus the matching dashboard, log, or trace evidence. For setup checks, use Troubleshooting.
Why is trunk configuration important so early?
Because routing and campaign symptoms can be telephony symptoms. If the trunk, provider credentials, routing, codec, or registration is wrong, inbound calls may not arrive and outbound calls may not start even when the agent and prompt are correct.
Does RocketAiFlow support every SIP provider automatically?
No. RocketAiFlow is designed for SIP and PBX environments, including Asterisk-based integration, but provider compatibility depends on deployment and configuration. Validate the provider path during setup. See Telephony Integrations.
Is RocketAiFlow cloud-only?
No. The documentation is written for practical on-premise or customer-environment deployment models as well as guided pilot setups. Use Deployment Overview to align the install path, telephony, APIs, monitoring, and operational ownership.