Disposition Behaviours
Twenty-six behaviours, each a name with a body of code behind it, seeded once at platform level so the word carries the same meaning in every workspace. Binding one to a wrap-up code is how the paperwork files itself.
Wrap-up codes, the behaviour each carries, and what runs
a body, behind a switch- code
- label
- category
- behaviour
- colour
- none
- log_voicemail
- retry_hint
- alert_low_quality
- flag_invalid_number
- flag_wrong_party
- set_dnc
- activity_not_interested
- activity_interested
- mark_qualified
- mark_unqualified
- create_callback
- create_task
- activity_left_message
- create_meeting
- mark_won
- activity_quote
- activity_payment
- activity_competitor
- activity_objection
- log_transfer
- activity_escalation
- tag_language
- activity_nurture
- tag_spam
- support_ticket
Product figures from the platform’s own defaults - not customer averages
How it works.
A behaviour is a row, not a script
Twenty-six are seeded at platform level on fixed identifiers and copied down into every workspace, so the same name means the same thing wherever you look. The catalogue itself is flat. Twenty system codes arrive already attached to one behaviour apiece, and it is those codes that carry the six categories.
Saving the call photographs the behaviour onto it
Five values are copied onto the call itself as they stood at that instant: the code itself, the label it wore, which category it sat under, its colour, and the handler key naming the behaviour attached to it. Renaming any of it afterwards leaves what was already saved untouched.
Anything other than no-automation is handed to a background job
Saving the wrap-up queues work carrying the workspace, the call, the record, the agent and the behaviour name. Running it behind the call rather than in front of the rep is why a slow follow-up never holds up the next conversation.
Each name has a body of its own
The job matches the name and does the work behind it. Do-not-call sets both do-not-call marks on the record, callback opens a callback row, task raises one against the owner, qualification moves the lead, tagging writes the tag, and the note behaviours file their own activity line.
Two moments in every run.
Every run passes through the same seven. Disposition Behaviours is the lit ones, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- Catalogue
- Twenty-six behaviours, seeded flat with a name and a sort order. The six categories belong to the twenty system codes that point into them
- What they do
- Set do-not-call, book a callback, raise a task, mark qualified, write a tag, or file the note. No-automation is the one that deliberately does nothing
- Bound one to one
- A code carries a single behaviour, which is why the catalogue is a flat list rather than a tree of them
- Timing
- Enqueued as the wrap-up commits, and run on the platform's ordinary background runner rather than inside the request that saved the call
- Names accepted
- The seeded twenty-six, validated on the way in, so a code cannot be bound to a name nothing implements
- Recorded either way
- The photograph on the call is written alongside whatever the behaviour does, so wrap-up reporting never waits on the follow-up finishing
- Where it is defined
- Platform level. A workspace chooses which codes are live, not what a behaviour does
- Not the same as
- This is the phone's wrap-up. Routing a cadence on its own call step is Branch Logic
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and webhooks that act without being asked.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Enrol a lead once and the sequence carries them: sends, waits, branches and exits, with a ledger that makes a duplicate send structurally impossible.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Six event types a CRM rule fires from: stage change, field update, new record, reassignment, schedule and inactivity, agreed in four places at once.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See disposition behaviours on your own floor.
Thirty minutes, your numbers and your data. We will set disposition behaviours up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included