How Clara reaches people — the one screen, in every state

Phase 2 of the onboarding wizard, drawn so lanes B and C build the same thing. The admin never picks an email address here: staff already chose it on the customer page, and this screen only shows the result. The one question the admin answers is who books tours. Flip the chips to see every state the screen has.

Staff chose (customer page)

Modules bought

Calendar

PropFlow.ai

How Clara reaches people

Here's the email your prospects will see. Then tell us who books tours.

Your leasing email

FromClara at Northgate <northgate@propflowai.co> ToSam Rivera SubjectRe: Tour this Saturday?

Hi Sam, Saturday at 11 works. I've held the 2-bed on the third floor for you.

Reply here if plans change and I'll find another time.

— Clara, Northgate leasing

This address is ready. Replies come straight back to Clara.

Want a different address? PropFlow can change this for you.

Who books tours?

I do Tours land on my calendar.

A shared calendar Tours land on the company's calendar. On Microsoft, the shared calendar comes with the shared mailbox: connect that above, or we’ll set it up with you.

My leasing team does Each teammate connects their own calendar when they sign in. Nothing to do now.

You can connect a calendar any time from Settings.

This screen is skippedA maintenance-only company goes from Review straight to Add your team. Nothing about email or tours is asked.

What is fixed, and what is free

Fixed. The admin makes one choice here, who books tours. The email is shown, not chosen: staff pick owner and scope on the customer page, and after go-live only PropFlow can change it. The card is one card whose From line, signature and caption follow that choice; the body never changes. A maintenance-only company never sees this screen. The vendor buttons start the connection in one click; there is no "pick a vendor, then press Connect" second step. Continue always works: continuing without connecting is the skip.

Free. Exact spacing, icons and the arsenal components used. The example company, people and addresses on this page are made up; the real screen reads the company name and address off the company row and renders nothing it does not know (hot rule 1).

Every state of the email card

Staff chose	From line	Caption under the card	Line after the card
Not chosen yet	Clara at <company> <a PropFlow address for your company>	We'll confirm this address with you before Clara sends anything.	Want your own address instead? Tell us and we'll set it up.
PropFlow address · company	Clara at <company> <company@propflowai.co>	This address is ready. Replies come straight back to Clara.	Want a different address? PropFlow can change this for you.
PropFlow address · per building	Clara at <building> <building@propflowai.co>	Each building gets its own address, named after the building.	Want a different address? PropFlow can change this for you.
Their own inbox · company	Clara <the company's leasing inbox>	Clara writes from your own leasing inbox. Your IT admin approves the connection once.	"Connect it now" with the two vendor buttons, then: Or leave it: we'll walk your IT admin through it.
Their own inbox · per building	Clara <that building's leasing inbox>	Each building's own leasing inbox. Your IT admin approves each one once.	"Connect it now" with the two vendor buttons, then: Or leave it: we'll walk your IT admin through it.

The PropFlow-provided address does not exist in the product yet for either scope; the card describes it in words until it is minted. Never render an invented address.

Where each choice goes

I do → the vendor button starts the admin's own calendar connect (the existing "Your calendar" screen's flow). Back from the vendor, the option shows Connected and Continue moves on.
A shared calendar → Google only for now, which is calendar-only by construction. On Microsoft the company rung is mailbox + calendar in one consent, and a calendar-only company grant would break token refresh (the refresh code has two scope lanes, keyed on whether the row is a person's), so the row offers no Microsoft button and says so (settled in #8947). If the shared mailbox was connected on Microsoft, its calendar came with it and this row shows Connected. A calendar-only Microsoft company lane is a named follow-up, not part of this work. For a per-building company the copy says "one per building" and the connect is per building, on the property settings page, later.
My leasing team does → nothing now. Each leasing agent gets the connect-your-calendar screen at first sign-in, which already exists.
Continue → Add your team. The offer stamp is written when this screen renders, so a finished admin is never asked again.

For the builders

Lane B (B2): the email card, its five states, the line under it, and the Finish copy. Reads Organization.emailSetup; owner and scope drive the From line and captions above.
Lane C (C2): the "who books tours" section lives on this screen, not a separate route. It routes to the two existing connect flows and to Add your team. C3 then retires the standalone calendar step.
Lane C (C1): the maintenance-only branch removes this whole screen from the wizard.
The screen is the existing channels step, renamed. Old addresses keep redirecting with their query strings.
The mailbox vendor buttons stay only for the two "own inbox" states, and only until that inbox is connected. For a PropFlow address, or when nothing is chosen yet, no mailbox buttons render.

Companion pages: Onboarding Flow Map, chapter 4 · Calendar & Onboarding handoff.