Start with the agreement
A useful follow-up responds to a specific need: a question, time to consider an offer or a request to speak later. A bare “call back” quickly loses context.
Record what actually happened. No answer, a conversation and a request to call later are different outcomes. A manual entry is a user report, not a verified telephony event.
One action, one responsible record
Link the action to its customer, purpose, owner and due date. If no date was agreed, keep it explicitly undated instead of defaulting to midnight today.
The assignee must have appropriate customer access. A task assignment does not grant that access.
- Use an actionable title.
- Keep the necessary context in the description.
- Use the agreed date and timezone.
- Change the status when the action is performed.
An illustrative follow-up
Fictional example: Alex wants to discuss the proposal internally and asks for a call on Tuesday. The salesperson records that agreement and creates one task for the agreed day.
After performing the task, record the result. Create another action deliberately if needed. Completing a task does not automatically confirm a meeting, sent offer or purchase.
Review the next actions each day
Review overdue tasks, today’s actions and customers without a next step. Read the context before moving a due date. Rescheduling should not obscure an earlier commitment.
Use the existing Ermission tasks and customer history. Check for a confirmed save. Resolve uncertain results before retrying to avoid a duplicate action.
Sources and product scope
Prepared with AI assistance and checked against the current implementation and cited sources. Product availability may change; check the linked scope.