Live Support Chat & Login Fixes

This week we focused on making it easier to get help and squashing several login-related issues that were tripping up real users.

Live Support Chat

You can now reach us directly from within Jules. We've added a live chat widget across the site, so if something isn't working or you just have a question, you can talk to a real person without leaving the page.

Login and Onboarding Fixes

We tackled a handful of issues that were causing friction during sign-up and login:

• Google login no longer loops back to onboarding — If you already had a Jules account and signed in with Google, you were being sent back through onboarding just because you hadn't added a phone number yet. Now, only brand-new users see the onboarding flow. Existing users go straight to their dashboard.
• Safari session timeouts resolved — Some users on Safari were hitting a cryptic error during sign-up caused by a browser lock manager conflict. We switched the onboarding page to a stateless session to avoid this entirely, and added clearer error messages if something still goes wrong.
• Clicking the logo no longer logs you out — In the app, tapping the Jules logo was pointing to the marketing homepage, which effectively signed you out. It now takes you to your dashboard instead.
• Integrations stay connected — Your linked services like Todoist now persist properly across login sessions, including through Google and magic link sign-ins.
• Duplicate phone numbers handled gracefully — If you try to verify a number that's already in use, Jules now tells you clearly rather than failing with a generic error.

Smoother Onboarding Finish

Once you complete onboarding, the "Go to dashboard" button is now front and center as the primary action, with the test call option available as a secondary choice. Small change, but it makes the next step obvious.

What This Means for You

These are the kinds of fixes you probably won't notice — because that's the point. Signing up, logging in, and staying connected should just work. If you were one of the users who ran into any of these issues, they're now resolved.