For users
These trees assume you've logged in to TelWeb and can navigate to the affected app. If you can't reach the app at all, jump to Login and access first.
Test calls and WebRTC
A test call is the in-browser WebRTC call you start from the Flow Designer on a Draft flow. It works only when the WebRTC feature flag is enabled on your platform.
| Symptom | Likely cause | What to check |
|---|---|---|
| Test call button is missing or disabled | WebRTC flag off, or you're not on a Draft flow | Ask your platform admin to confirm the WebRTC flag. Test calls require a Draft flow — see Draft and publish. |
| Click Test call, nothing happens, no microphone prompt | Browser blocked microphone access for the site | Check the browser's site permissions and grant microphone. In Chrome: padlock → Site settings → Microphone → Allow. |
| Microphone prompt appears, then immediate failure | Another tab or app is holding the microphone | Close other meeting/voice tabs. Restart the browser if the device is still busy. |
| Test call connects but the AI never speaks | Provider misconfiguration on the flow | Open the Provider inspector in the Flow Designer and confirm the AI provider is selected and credentials are valid. |
| Test call connects, AI speaks, but you sound choppy | Network jitter / packet loss | Try a wired connection or another Wi-Fi. If the issue is platform-wide it'll be in the operator's SigNoz monitoring. |
| Test call drops after ~30 seconds | Upstream realtime provider session timeout | Re-run; if it repeats, ask your team admin to check the provider config and the operator to check Voice operations → Troubleshooting. |
| You hear yourself echoed | AudioProc off and headset feedback loop | Use headphones. Operators can enable AudioProc (see Voice operations) for echo cancellation across all calls. |
What's a "Draft" vs "Published" call?
Test calls always hit a Draft flow on a temporary WebRTC endpoint. Real callers always hit a Published flow on a real endpoint. If a behaviour shows up only in production, ensure you're testing the same version — see Draft and publish.
Conversations and history
| Symptom | Likely cause | What to check |
|---|---|---|
| Conversation didn't appear in history | Call cut before TelPhi finished its post-call write | Wait ~30 seconds and refresh. If it's still missing, file a ticket with the rough call time and the caller number. |
| Conversation appears but no recording | RECORDING_ENABLED is false on the platform | Ask your operator. This is a platform-level setting in Voice operations. |
| Recording exists but won't play in the browser | Browser codec issue or expired signed URL | Refresh the page (signed URLs are short-lived). Try another browser. If the file itself is corrupt, file a ticket with the conversation ID. |
| Tool calls in the timeline show errors | Tool returned a non-2xx or timed out | Open the tool entry in the timeline for the error body. Tool config is in the Flow Designer's Tool inspector. |
| Speakers swapped in the transcript | Diarisation misattribution | Known limitation on some provider combinations. File a ticket if it's consistently wrong. |
Apps and the Flow Designer
| Symptom | Likely cause | What to check |
|---|---|---|
| Save is disabled | Your role is VIEWER | See Access roles. Ask your team admin for MEMBER or higher. |
| Publish is disabled | Validation errors on the flow | Each affected node will show an inspector error. Resolve every flagged node before publishing. |
| Flow Designer canvas is blank | Flow JSON is corrupt or a node type is missing on this platform | Open the Source view to inspect the JSON. If a node type isn't recognised, your platform may be on an older image. |
| AI Flow Builder panel is missing | aiFlowBuilder feature flag is off | See Feature flags. Operator can enable it. |
| Source view edits are reverted on save | The JSON failed schema validation | The form on Save will show what failed. Roll back to a known-good version via Version history. |
Login and access
| Symptom | Likely cause | What to check |
|---|---|---|
| Can't reach TelWeb at all | Wrong URL, browser cache, or network | Try an incognito window. Confirm the URL with your team admin. |
| Invite email never arrived | Email delivery problem on the platform | Ask the inviter to resend. Operators can verify email delivery via Web operations. |
| Login redirects loop | Stale cookies | Clear cookies for the TelWeb domain and try again in an incognito window. |
| MFA / SSO blocks login unexpectedly | Identity provider issue | Confirm your account state with your platform admin. |
| 403 after login on a specific page | Your role doesn't grant access | Confirm the required role on the page (look for the Role access callout) and request elevation. |