Disposition Behaviors
Twenty-six things a wrap-up code can do besides sit in a report. Attach one, and the do-not-call mark, the callback, the task and the tag happen because the rep picked the code, not because they remembered to.
Wrap-up codes, the behaviour each carries, and what runs
a body, behind a switch- code
- label
- category
- behaviour
- color
- 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.
The same word means the same thing on every floor
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 catalog itself is flat. Twenty system codes arrive already attached to one behavior apiece, and it is those codes that carry the six categories.
What the code meant that day is frozen onto the call
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 color, and the handler key naming the behavior attached to it. Renaming any of it afterward leaves what was already saved untouched.
The follow-up runs behind the rep, not in front of them
Saving the wrap-up queues work carrying the workspace, the call, the record, the agent and the behavior 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.
What each name actually does
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 behaviors file their own activity line.
Two moments in every run.
Every run passes through the same seven. Disposition Behaviors 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- Catalog
- Twenty-six behaviors, 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 behavior, which is why the catalog 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 behavior 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 behavior 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 outside triggers that act without being asked.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
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 behaviors on your own floor.
Thirty minutes, your numbers and your data. We will set disposition behaviors up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included