Skip to main content
Use these checks when your Woblar dashboard or studio does not behave as expected. Keep the difference between account data, browser-owned voice agents and published revisions in mind.

I keep returning to sign-in or verification

Email/password accounts need a verified address. Complete the verification email, return to Woblar and continue or sign in again. If Google sign-in does not open, check whether your browser blocked the popup.

Setup appears when I open the dashboard

Optional onboarding appears until you finish it or choose Save and skip the rest. Skipping saves entered answers. You can update them later in Profile.

My profile did not save

Wait for the saved confirmation. If Woblar shows a loading or save error, retry rather than assuming the changes persisted. The dashboard can remain usable while business-profile data is temporarily unavailable.

My voice agents are missing on another device

Voice Agent Studio libraries belong to the browser workspace. Sign in using the original browser. Signing in on another device does not sync the library. Clearing the workspace cookie loses access; exported configuration can help you keep a portable copy.

My agent changes are not visible publicly

Saving and publishing are separate. Save the draft, then publish or republish deliberately. Voice calls use the revision they started with. Widget publications freeze source versions and configuration; existing widget conversations may need New chat after republishing.

My widget does not appear or answer

Check that the widget is published, that the script came from Publish, and that the current website’s exact HTTPS origin is allowed. Include www separately if your site uses it. Check that selected knowledge is ready. Test the published assistant on an allowed website, not only in the private preview.

My test did not change an external service

Widget previews default to fixtures, and automated voice scenarios use labelled external-action fixtures. Fixtures exercise the interaction without making the external request. Live tools need the relevant configuration and approvals. For help, email Woblar with the page, visible error and steps to reproduce. Do not include passwords, API keys or private customer transcripts.