A quotation has been sent, but nobody is clearly responsible for the next contact. One salesperson assumes a colleague followed up while the customer has already replied through another channel. A scheduled message alone cannot solve this: the system needs to know the current state of the opportunity.
Following one quotation through its changing circumstances reveals a better design. The aim is to make the next contact appropriate, with enough context for the person responsible to act.
Before sending: define what is being followed up
An opportunity can contain several quotation versions as the customer changes the scope or requested items. Keep the opportunity separate from each document version, and identify which version is current.
The follow-up record needs the customer or organisation, contact person, owner, document version, sending channel and next agreed contact date. Do not force the same interval onto every opportunity. If the customer has arranged an internal discussion, the agreed date should take priority over a default reminder cycle.
Define “sent” carefully. Generating a file, submitting a message to a provider and receiving delivery confirmation are different events. Do not imply the customer has read the quotation when the available evidence only confirms that someone pressed Send.
At the agreed time: give the owner context
A notification saying “remember to follow up” leaves the salesperson to reconstruct the conversation. Opening the task should show the latest scope, outstanding questions and the outcome of the previous contact.
An illustrative internal reminder might read:
The customer-facing message should be separate. During the initial rollout, present it as a draft for the owner to review. It can refer to the unresolved question and offer relevant information, but it should not invent a discount or promise a delivery date that an authorised person has not confirmed.
Immediately before contact: check what changed
Suppose the system prepares a message in the morning and the customer replies before the scheduled send. Acting on the earlier snapshot would make the follow-up sound disconnected from the conversation. Recheck the relevant state close to sending.
Confirm that the opportunity remains open, the referenced quotation is current, there is no unhandled customer reply and another employee has not already taken the task. If a check fails or cannot be completed, hold the action for review rather than interpreting uncertainty as permission to continue.
Duplicate prevention should relate to a specific follow-up task and event. After a connection failure, the system needs to distinguish an actual failed send from a successful send whose confirmation has not arrived. Blindly retrying can produce a second customer message.
A change in circumstances must change the pending task
| Latest event | Expected effect on the follow-up |
|---|---|
| Customer replies | Hold the earlier message and route the reply to the owner |
| A revised quotation is issued | Cancel tasks tied to the obsolete version and create the appropriate next action |
| Customer requests a later conversation | Update the agreed date and record the reason |
| Ownership changes | Transfer the context and open tasks to the new owner |
| Opportunity closes or contact stops | Cancel messages still waiting to be sent |
An expired quotation is not necessarily a lost opportunity. The customer may still be interested but need an updated offer. Route that situation to the responsible person; the system should not renew terms or confirm an old price on its own.
Provide a straightforward way to record replies received outside the connected channels. Otherwise, the system will continue treating a customer as silent even though an employee has already spoken to them.
Test conflicting events, not just the happy path
Useful test cases include a reply arriving just before a message is due, two employees opening the same task, a quotation changing after a reminder is created, and a provider taking too long to confirm the sending result.
Each case needs an observable outcome: no duplicate contact, no reference to an obsolete document, a visible reason for a held task, and a way for the owner to continue without erasing the history. Begin with internal reminders and human-reviewed drafts. That exposes exceptions before automatic sending is enabled for cases the team has explicitly approved.
The work list should distinguish tasks that are due, tasks waiting for the customer, tasks requiring an internal response and delivery problems. A single “pending follow-up” queue hides these different needs and makes it difficult for a manager to help.
Success means the owner can explain who is expected to act, what is outstanding and why another contact is appropriate. Track missed agreed dates, duplicate messages and the completeness of next actions alongside sales outcomes. A higher message count, by itself, does not demonstrate better follow-up.
If customer conversations remain separate in LINE, see how to connect LINE OA to a CRM so quotations, ownership and conversation context refer to the same customer.
Give every quotation a clear next step
Talvyn Labs connects sales tools with quotation follow-up workflows, including ownership, reminders and stop conditions when a customer's situation changes. Share your current process and where follow-ups get missed so we can scope a system your team can oversee and take over.
Discuss sales follow-ups