Create an engagement
Service, stage, lead and team — and where the title comes from on its own.
Opening one
Pick the client
An organisation or an individual client. If the service catalogue has not been built yet, you are sent to the catalogue page rather than to an empty picker.
Pick the service
The service decides what the default stages are. A retired service does not appear in the picker.
Leave the title blank, or write one
Left blank, the title derives from the live service name — so renaming the service later reflows into it. A title you typed is never touched.
Set value and expected close
Both optional and both editable later. These two fields are what make pipeline value reporting possible at all.
The lead and the team
Whoever creates the engagement is its lead. The lead can change and other people can join the team, but the system will not let the last lead be removed.
Writing to an engagement — a note, a document, a stage move — requires team membership. Reading does not: engagements are readable firm-wide.
The workspace owner is the exception and can manage an engagement they do not lead.
The description is one line in the lead's own words
The description field is where the lead says, in their own sentence, what this engagement is about. Empty is the normal state and breaks nothing.
That same sentence is what shows on the Pulse card — so if you want a colleague to understand the situation without opening the engagement, write it here.
Read this next
- Pipeline & opportunitiesPipeline stagesA human picks the stage, the outcome is derived, and the history only appends.
- Service catalogueWhat the catalogue isTwo levels: line and service. And why it ships empty.
- Pipeline & opportunitiesValue and expected closeThe two fields that make pipeline value reporting possible.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.