Roles in this page
Throughout this page, manager roles means Admin, Sales Admin, Ops Manager, and Client Coordinator (the roles grouped under Branch Management). Sales Member is a non-manager role with a more limited scope. Where behavior differs between managers and Sales Members, it’s called out explicitly.Lead activity statuses
A lead activity has exactly two statuses: Draft and Published. New activities start as Draft. There is no separate “cancelled” or “completed” status. Cancelling an activity means deleting it (see Deleting an activity). The status drives everything downstream — conversion and notifications all depend on whether the activity is Draft or Published.Who can create, view, edit, and delete activities
- Manager roles can view, edit, and delete any activity within their organization and branches.
- Sales Members can view and edit activities that are assigned to them, within their organization and branches. Deleting is narrower — a Sales Member can only delete an activity they created that is still assigned to them (see Deleting an activity).
- Creating activities is available to manager roles and Sales Members.
- A user with no branch or no organization assigned has no access to lead activities.
Self-assignment for Sales Members
A Sales Member can only assign a lead activity to themselves. If a Sales Member tries to assign an activity to someone else, the save is rejected with a message that they can only create or assign lead activities for themselves. Manager roles can assign an activity to any eligible user, or leave it unassigned. Leaving an activity with nobody assigned is a manager-only choice — a Sales Member must keep it assigned to themselves.Validation applied on every save
Every time a lead activity is created or edited, these rules are enforced:- The person creating the activity is recorded as its creator.
- Sales Members can only assign activities to themselves (see above).
- The assigned user must belong to the selected branch. If not, the save is rejected with “Assigned user does not belong to this branch.” An unassigned activity has no assigned user, so this check is skipped.
- The lead must belong to the same organization as the activity. If not, the save is rejected with “Lead does not belong to this organization.”
- The end time cannot be before the start time.
Required information on an activity
A lead activity requires:- An organization and a branch (set automatically for scoping)
- A creator (recorded automatically)
- A lead
- A single assigned user — or nobody, since manager roles can leave an activity unassigned
- A start time and end time
- A status (Draft or Published)
- A “client confirmed” indicator (defaults to off)
- A “hot lead” indicator (defaults to off)
- A “flexible client” indicator (defaults to off)
Scheduling a site visit
The schedule-activity form requires:- A lead
- An assigned user (manager roles may instead leave it unassigned)
- A date, start time, and end time
- An address
- A project name
- The “client confirmed”, “hot lead”, and “flexible client” indicators
Saving a draft
When an activity is saved as a Draft, two things can happen in the background (neither blocks the save):- A “not yet published” reminder is scheduled to prompt you to publish the activity later, if the activity is new, was not already a draft, or its start time changed.
- A client notification. If the “notify client” setting is on, an “Appointment scheduled” email is sent to the lead’s contact (and any additional client emails).
Moving a published activity back to draft (unpublishing)
Saving an already-published activity as a Draft unpublishes it, which drops the lead out of the closing ratio just like deleting the activity would. So this follows the same rule as deleting:- Manager roles can move any published activity back to draft.
- Sales Members can only move a published activity back to draft if they created it and it is still assigned to themselves. Otherwise the save is rejected with “You can only move lead activities you created that are assigned to yourself back to draft.”
Draft visibility
Read and list views can either include or exclude drafts.- Published-only views (such as the calendar) exclude drafts, so unpublished site visits don’t leak into them.
- When editing or deleting an activity, drafts are intentionally included so the activity can be found.
Publishing converts the lead
Publishing a lead activity is what converts the lead into a client and project.- When you create an activity already set to Published, it converts.
- When you edit a Draft activity and change it to Published, it converts.
- Re-saving an activity that is already Published does not re-trigger conversion.
What conversion does
When an activity is published, the system does the following, in order:- Saves the entered address to the lead, then reloads the lead. If the lead no longer exists, or it has no contact, conversion stops with an error.
- Finds or creates a client matching the lead’s contact (first name, last name, email, phone), reusing the lead’s existing contact so duplicates aren’t created. A newly created client records the publishing user as its creator.
- Converts the contact from a lead contact into a client contact.
- Finds or creates a property from the entered address (including city, state, and postal code if provided).
- Finds or creates a project linked to the lead, client, property, branch, organization, and the entered project name.
Publish and time-change notifications
After an activity is published, notifications are sent in the background based on the active notification settings:- If “notify the assigned team” is on, the assigned user gets a “lead activity published” notification with a link to the activity on the calendar.
- If “notify client” is on, the lead’s contact gets an “Appointment scheduled” notification (plus any additional emails).
Idempotency — no duplicate clients or projects
Re-publishing, or publishing a second activity for the same lead, will not create duplicate clients or projects:- The conversion looks for an existing project for the lead first and reuses it if found.
- It searches for an existing client by email and phone and reuses a match, reusing the lead’s existing contact.
- Re-saving an already-published activity skips conversion entirely.
”Converted to client” on the lead page
The lead detail page detects whether a lead has been converted by checking for a project linked to that lead within the organization. If one exists, the page surfaces a banner or quick-jump to the converted client and project. The lead page only attempts to surface client information if the viewer has permission to read clients.Return behavior after publishing
When a publish converts a lead, the save reports the newly created client and project so the app can jump you straight to the new project. Because publishing and conversion succeed or fail together (see Publishing converts the lead), a successful publish of an unconverted lead always means the client and project exist.Address is saved even without publishing
If a save is not a publish (for example, saving a draft), the entered address is still saved to the lead. On a publish, the address is saved as part of the conversion instead, so it isn’t written twice. Either way, the lead’s address stays in sync.Recognition for scheduling activities
When a new lead activity is created (not on edits), the system evaluates recognition unlocks tied to scheduling activities (such as the Warm Handoff recognition) for the user who created it. Recognition evaluation runs in the background; if it fails, it’s logged and never affects the activity save.Deleting (cancelling) an activity
- Manager roles can delete any in-scope activity.
- Sales Members can only delete an activity they created that is still assigned to themselves. If someone else scheduled the activity for them, or they created it but it has since been reassigned to someone else, the delete is rejected with “You can only delete lead activities you created that are assigned to yourself.” An unassigned activity can only be deleted by a manager role.