Workflows for what you build.

Puts a phase invoice in front of the client the day it's issued and closes the loop when payment lands.

1. Invoice issuedSent when a new invoice is issued, with the amount in the text.
2. Due-date reminderSent before a payment is due, with the amount in the text.
3. Payment receivedSent when a payment arrives, with the amount in the text.

Keeps the client and site contact aligned on when the architect is on site, and recovers missed visits.

1. Visit bookedSent when a booking is confirmed.
2. Visit tomorrowSent the day before the appointment.
3. Visit in 1 hourSent about an hour before the appointment.
4. Visit movedSent when an appointment is rescheduled.
5. We missed the visitSent after a missed appointment.

Runs an RFI or submittal review as a tracked thread so a waiting question never stalls a phase.

1. RFI loggedSent when a support request is logged.
2. Routed to your PMSent when a ticket is routed to a specific agent.
3. Reply postedSent when an agent replies to the ticket.
4. RFI closedSent when a ticket is marked resolved or closed.

Reminds staff and subconsultants of a deliverable due date and escalates to the principal if nobody acknowledges.

1. Deliverable dueSent to remind a team member of an upcoming task or deliverable deadline.
2. Deadline at riskClaim-required alert; escalates server-side if nobody claims it.

Proves phone ownership when a client or subconsultant is invited into the project portal, and covers later sign-ins.

1. Portal signup codeSent when a user verifies their phone at signup.
2. Portal login codeSent when a user logs in with SMS as a second factor. SMS is still commonly used for primary 2FA, but it is less secure than authenticator apps that use temporary one time passwords (TOTP) or passkeys. Consider using one of them instead.