Configuring Post-Call Actions

Last updated: August 10, 2026

Use Post Call Actions to define what should happen automatically after a Marketing Agent conversation ends.

Actions help turn conversation outcomes into follow-up workflows, alerts, and downstream updates.

Before You Start

You need access to app.docketai.com.
You need an existing Marketing Agent.
Configure any post-call analysis fields that your actions depend on.
Connect Slack, Microsoft Teams, or CRM integrations before using actions that depend on those systems.

Open Post Call Actions

Log in to app.docketai.com.
Open Marketing Agent Configuration.
Select the agent you want to configure.
Open the Analysis and Actions tab.
Find Post Call Actions.

The section explains that actions can trigger automatically after each agent conversation.

Decide What Should Trigger an Action

Start by defining the outcome that should cause follow-up.

Common trigger signals include:

A conversation lasts longer than a target duration.
The visitor's company is identified.
A new lead is created.
A known contact engages.
A custom criterion is met.
A meeting is booked.

Use specific criteria so actions do not fire for low-value or unrelated conversations.

Configure Alerts

The same Analysis and Actions tab includes Post Call Alerts, which send an alert when selected conditions are met.

Available alert conditions may include:

Condition	Use when
Call Duration	Long conversations should notify a team member.
Visitor's Company is Identified	Company identification should trigger review or follow-up.
New Lead Created	New CRM leads should be routed quickly.
Known Contact Engaged	Existing leads or contacts should be reviewed by the owner.
Custom Criteria	A custom conversation signal should trigger an alert.
Meeting Booked	Booked meetings should notify the team.

Alert delivery options shown in the tab include Slack and Microsoft Teams. Complete the relevant integration before relying on either channel.

Connect Actions to Analysis Fields

Post-call actions are most useful when they use structured analysis fields.

For example:

Use a Qualification Status field to alert sales only when a visitor is qualified.
Use a Product Interest field to route conversations by product area.
Use a Buying Timeline field to prioritize urgent follow-up.
Use Meeting Booked to notify the team when a conversation converts.

Review the analysis output before building actions around it.

Verify the Follow-Up Action

Save the action or alert configuration.
Run a controlled conversation that clearly meets one configured condition.
End the conversation and wait for post-call processing to finish.
Confirm the expected alert or CRM update occurs once.
Run a negative test that should not trigger the action.
Review the destination and captured values before enabling the workflow for production traffic.

Best Practices

Start with one or two high-value actions.
Use clear criteria so alerts stay useful.
Test actions with preview or controlled conversations before relying on them.
Keep alert recipients focused on the team that owns the follow-up.
Review noisy alerts and tighten the trigger criteria.

Troubleshooting

Issue	What to check
Action did not run	Confirm the conversation met the configured trigger criteria.
Alert did not send	Confirm the delivery integration is connected and enabled.
Too many alerts are firing	Make the trigger criteria more specific.
Wrong team received the alert	Review the selected destination channel or team.
CRM-dependent action failed	Confirm the CRM integration and field mapping are ready.