Better FlowFuse expert guidance from Website chat to App.

[dimitrieh]

Epic

https://github.com/FlowFuse/product/issues/2

Description

As a: Visitor coming to the FlowFuse website that interacts with the FlowFuse expert

I want to: be better guided/convinced to bring the discussion into the app

**So that:**so that it is clear to me what will happen and why it would matter to me (what upsides it brings)

For us it will lead to better conversion.

---

Proposal

TODO: We need a holistic user journey that makes sense.

Context

Quick alignment question: with self-signups closed, how should the FF Expert guide new vs existing users? Right now the chat leads to sign-in without a clear next step for someone without an account — and the CTA says “Continue chat in app,” but for new users the app can’t actually continue the chat yet.

Agreed right now is a bit rudimentary.

CTA says “Continue chat in app,” but for new users the app can’t actually continue the chat yet.

What would you suggest for the flow of:

1. User gets to FlowFuse.com
2. Triggers FlowFuse Expert
3. Should be triggered to bring chat into FlowFuse (right now button + default login/sign up screen)

One option is still to add a “Get started” path on the sign-in screen (ref: #4404 (comment)). That said, for this specific journey, it might make more sense for the chat to ask upfront whether the user already has an account and then set the CTA accordingly (e.g. Sign in vs /get-started), so the promise matches what happens next.

This is an idea. Though login flows are finicky, where we do not want to stray too far from expectation.

Here is a sequence diagram of the flow (as user journey charts for mermaid script is not that good yet).

sequenceDiagram
    actor Visitor
    participant Website as FlowFuse.com
    participant Expert as FlowFuse Expert
    participant Auth as Login/Signup
    participant App as FlowFuse App

    Visitor->>Website: Visit FlowFuse.com
    Website->>Visitor: Show quick prompts
    Visitor->>Website: Click quick prompt
    Website->>Expert: Activate Expert
    Expert->>Visitor: Chat conversation
    Visitor->>Expert: Continue chatting
    Expert->>Visitor: Show "Bring chat to app" button
    Visitor->>Auth: Click bring to app
    
    alt Existing User
        Visitor->>Auth: Click sign in
        Auth->>Visitor: Request credentials
        Visitor->>Auth: Enter credentials
        Auth->>App: Authenticate
        App->>Visitor: Open chat in app
    else New User
        Visitor->>Auth: Click sign up
        Auth->>Visitor: Request account details
        Visitor->>Auth: Create account
        Auth->>App: Create user
        App->>Visitor: Show onboarding
        Visitor->>App: Complete onboarding
        App->>Visitor: Present chat
    end

Loading

I think the parts we need to look at individually are:

Acceptance Criteria

• criteria 1
• criteria 2
• criteria 3
• ...

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[dimitrieh]

@Yndira-E See #4010 (comment). Would love your thoughts here