Phase 5 item 8 of the ingest plan. The customer connects their tools, presses Onboard, and Propflow reads everything it can. When the read is done, the customer answers only what we could not find or found two answers for. Target 10 to 15 minutes, 30 at most.
Mock for logic, flow and states, not polish. Company and values are made up ("Harbor Lane Homes (TEST)"). Lives on the existing Onboarding & Go Live page (/onboarding-hub), above the go-live checklist. No new page, no switch.
The whole flow on one card. 1 connect calendar and PMS, 2 pick any other apps, 3 press Onboard, 4 ingest runs as long as it needs, 5 "your onboarding is ready", 6 answer only the gaps. Each step below shows every state it can be in.
We read, we never change anything in your tools.
Logic. Onboard needs the PMS only, because that is the source ingest reads. The calendar stays on the card (and on the checklist) because Clara needs it to go live, but it does not hold up the read. Gmail and Outlook use the existing connect flows (/api/integrations/company-channels/connect). Drive, Monday and igloohome have no connect yet, so "I use this" records the app on the company (a setting) and the run's next-step for a gap names that connector. It is never a dead Connect button.
Propflow will start reading in a few minutes. You can leave this page.
Requested by Dana Ortiz, Oct 16, 2:14 PM.
Propflow is reading AppFolio, your website and your listings. This usually takes one to three hours. This page will show your questions when it is done.
Started 2:19 PM.
Propflow has been told and will start it again. You do not need to do anything.
Stopped 3:02 PM. Staff see the reason on the Interview guide.
Logic. The card reads the run request from ingest's run-requests API (queued, running, done, failed). "Done" becomes "ready" only once ingest has published the pre-fill for that run (PREFILL#<org> run number at least the run the request produced). Pressing Onboard twice never starts two reads: one open request per company. No email is promised on screen, because the email is not switched on.
7 questions need you, about 10 minutes. We filled 41 answers from your records.
Answer the 7 questionsSubject: Your Propflow onboarding is ready
Hi {first name},
We finished reading {company}'s records. We filled in {filled} answers for you, and {count} questions still need you. Most people finish in about {minutes} minutes.
{link: Answer your questions}
Thanks,
The Propflow team
Logic. The in-app card is the live notice. The email is built as a template plus a sender function behind the existing team-notice path, and nothing calls it until Gera approves the wording. When Gera approves the wording, the send is wired through sendOrHoldTeamNotice with one company setting, off by default, that Fede turns on (propflowai rule 8 for a new outbound). The in-app card needs no switch: it is part of the existing Overview.
0 of 48 go-live answers saved. 41 are ready to save from your records, 7 need you.
Every go-live answer is in. Propflow will finish setup and turn Clara on with you.
Answers saved Oct 16. You can change any of them later in Settings.
Logic. The list is only the customer's go-live questions (the hub's customer sections). Each is in exactly one group:
"Answer" and "Pick one" open the question where it already lives, scrolled to it, the same way Hand to client lands today. The time estimate is about 1.5 minutes per open question. A pre-fill never counts toward go-live until it is saved, so the bar counts saved answers only and names the ready-to-save pre-fills separately.
| Rule (Gera, 10-14) | How the mock meets it |
|---|---|
| The customer sees only go-live blockers | Screen 4 lists only the customer sections' asked questions. Non-blocking gaps stay on the staff Interview guide. |
| All pre-filled, no confirm buttons | Filled answers show the value and source. The single Save all is a save, not a per-field confirm (ADR-0059 amendment, draft commit 5018c07). |
| A default counts only if runtime uses the same value | An unsaved ingest value never counts as answered. Only Save all (a real save) moves go-live. |
| Never hide data we have | Conflicts show both values. Thin or old values show with a small flag, never dropped. |
| Logic and states first, polish last | This page. Visual polish comes after v1 is live. |
| Canonical, no switch | The card is part of the existing Overview. The only thing not live is the email, which waits on Gera's wording. |
| Customer copy is drafted, never sent | Screen 3's email is marked DRAFT and has no caller. |
propflowai Access token in Vercel (commands on #20510). Until then nobody sees the Onboard card.Use Fairhaven Residential (TEST). Type TEST in the company picker before any screenshot. Each line is one screenshot.
service:propflowai as <user id> (#20510, ingest #205).The "your onboarding is ready" email is a DRAFT for Gera (#20514). It has no sender. Do not expect an email.
PREFILL#): fable-decide fa6112057, Fable, high confidence.f267bc99d (Fable unreachable, Astra both passes): approve with changes. Applied: chips say "not connected yet"; the bar counts saved answers only; the email is marked delivery-not-built and, when wired, gets one default-off company setting Fede turns on; the PMS gates starting the read, never go-live.fbe546aad).