Configuring Post-Call Actions

Last updated: October 26, 2026

Post Call Actions decide what happens once a Marketing Agent conversation ends and Docket has analyzed it.

Use them to alert the right team while the conversation is still fresh, and to send what Docket learned into Salesforce, HubSpot, Marketo, or Dynamics 365.

Before you configure post-call actions

  • 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.

How to open Post Call Actions in Docket

  1. Log in to app.docketai.com.

  2. Open Marketing Agent Configuration.

  3. Select the agent you want to configure.

  4. Open the Analysis and Actions tab.

  5. Find Post Call Actions.

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

What should trigger a post-call 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.

How to configure post-call alerts

The conditions below are summarised here. For the full setup, including delivery channels and testing, see Setting Up Post-Call 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.

How to use analysis fields in your actions

Actions are only as good as the fields behind them. Creating Post-Call Analysis Fields covers how to define those 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.

How to test a post-call action

  1. Save the action or alert configuration.

  2. Run a controlled conversation that clearly meets one configured condition.

  3. End the conversation and wait for post-call processing to finish.

  4. Confirm the expected alert or CRM update occurs once.

  5. Run a negative test that should not trigger the action.

  6. Review the destination and captured values before enabling the workflow for production traffic.

Best practices for post-call actions

  • 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 post-call actions

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.

Frequently asked questions

When does a post-call action run?

At the end of the conversation. Docket completes the post-call analysis first, then runs the actions and writes to any connected systems.

Do I need to enable object writes for an action to do anything?

Yes for CRM actions. If Docket does not have write access to the relevant Lead, Contact, or Opportunity object, the action runs but nothing is written.

Does Docket read from my CRM during the conversation or after it?

Both, for different things. Docket reads during the conversation to route meeting bookings. Everything else happens after the conversation ends.

Can I send leads to one system and activity to another?

No. Disabling a provider's Lead or Contact write also stops Docket using that provider as an activity logger.

Related Articles