A Cleaner First Run: Onboarding & Text Setup Fixes

Setting up a new workspace starts with pointing us at your website, and until now a site we couldn't reach could trap you in a loop. If the first scan failed — an expired deployment returning a 404, say — every refresh quietly resubmitted the same unreachable address, spending scan credits on an attempt that was never going to succeed and eventually surfacing a vague error. Now a failed attempt is remembered as failed. You come back to the address form with a clear "we couldn't reach that site" note, free to correct a typo or try a different domain, and a scan only runs when you ask for one.

The second fix is about text messaging, which has been available to everyone for a few weeks now. The setup checklist hadn't caught up: it still described iMessage and SMS as something you had to request, so customers who chose texting as their channel were told the feature didn't exist yet — and filing a request closed the item out, making the real setup flow disappear from the checklist entirely. Texting now shows up where it belongs, as a Connect step, and the card takes you straight into the phone-number setup dialog instead of a dead end. Once your number is bound, the step clears itself. If texting isn't live for your account, the request option behaves exactly as before.

We followed that through the rest of the app so the story stays consistent. Connection status for text messaging is now read the same way everywhere, which means an iMessage connect card in a conversation transcript correctly shows as connected, and the app recognises the channel as newly connected right after you finish setup — no more mixed signals between your home view and your conversations.

Together these changes make the first ten minutes behave the way you'd expect: a scan that fails tells you so, a shipped channel offers to connect, and what you've already connected reads as connected wherever you look.