Leave room to finish the call
Set how many minutes after the meeting the prompt should run.
Use cases / Meeting follow-up
The call is over.Follow through.
After a busy day of meetings, follow-through can slip. Prompt the responsible rep to review the conversation and decide what should happen next.
Give the rep a prompt
after the conversation.
The person who ran the meeting knows what was agreed. Send an after-meeting notification to remind them to follow through while the conversation is still recent.
Keep the follow-up personal
Distro sends the configured notification. The rep decides what to say and what action to take.
A no-show needs
a different response.
Not every meeting becomes a conversation. Use separate workflows for cancellations and meetings marked as no-shows so your team can respond to what actually happened.
React to a marked no-show
Notify your team when a meeting is marked as a no-show so a rep can decide whether to reconnect.
Keep cancellation updates visible
Use cancellation events to let the relevant people know that the planned call will not take place.
Put the reminder
where it will be seen.
A follow-up process should fit the team’s working habits. Deliver prompts by email or Slack, or use a webhook to pass meeting context to another tool.
Meeting eventsDistro workflowsEmail · Slack · Webhooks
Reach the responsible person
Email the assigned rep or configured recipients, or post to a connected Slack channel.
Check that the action ran
Review workflow action logs when an expected notification does not arrive.
FAQ
Frequently asked
questions
Will Distro send a follow-up email to the buyer for us?
The workflow sends the email or notification you configure. The process described here prompts the rep; it does not generate a personalized recap or infer the next sales action.
Can we send the prompt after the meeting rather than at booking?
Yes. An after-meeting trigger supports a time offset in minutes.
Does a no-show trigger detect attendance automatically?
No automatic attendance detection is implied. The workflow can react when a meeting is marked as a no-show.
Can different outcomes use different notifications?
Yes. Configure separate workflows for supported events such as cancellation, completion, or a marked no-show.
Make follow-through
part of the routine.
Build a reminder process around completed conversations, cancellations, and missed meetings.