Quotation follow-up, designed as a complete customer workflow.

A quotation has been sent but the customer has not accepted, declined or asked a question. This guide shows how to follow up on open quotations without sounding repetitive while keeping the customer record, responsible team and next decision visible.

Quotation follow-up, designed as a complete customer workflow.

What quotation follow-up needs to solve

A quotation has been sent but the customer has not accepted, declined or asked a question. The useful outcome is not another automated message. It is a controlled process that can follow up on open quotations without sounding repetitive, show what happened and give the next owner enough context to act.

  • Trigger: A quotation has been sent but the customer has not accepted, declined or asked a question.
  • Decision: Choose the right follow-up time from deal value, customer intent and quotation validity.
  • Intended action: Send a concise reminder, surface the quotation context and assign meaningful replies.

Design the operating decision before the automation

Choose the right follow-up time from deal value, customer intent and quotation validity. Document the required evidence, the owner of the decision and the states that end or pause the workflow before adding triggers or messages.

  • Name the source of truth for customer identity and business state
  • Define one accountable owner and a visible fallback
  • Store the event or conversation that explains every state change

Carry out the next action with context attached

Send a concise reminder, surface the quotation context and assign meaningful replies. DripTell should carry the source event, customer record, previous messages and ownership into the same operating view so the team can continue without reconstruction.

  • Use structured fields for decisions and the transcript for supporting context
  • Pause conflicting follow-up when the customer or a teammate replies
  • Keep external-system identifiers for updates, retries and reconciliation

Put the failure boundary in writing

Stop the sequence immediately when the customer responds or the quotation expires. Define invalid data, restricted topics, duplicate events, timeouts and the point where a person must review the case.

  • Show the customer when a person has taken over
  • Make irreversible actions require stronger evidence or approval
  • Provide an observable recovery queue instead of silent failure

Confirm the final workflow against your current operating policy and channel permissions.

Measure the customer outcome, not only the message

The primary operating signal for quotation follow-up is open quotations moved to a clear next state. Review it with response quality, exceptions, customer effort and downstream business state rather than treating delivery as success.

  • Primary measure: Open quotations moved to a clear next state
  • Quality check: conversations that required correction or repeated information
  • Control check: exceptions that bypassed the intended owner or guardrail

Questions teams ask before they connect the workflow.

What should be defined before implementing quotation follow-up?

Define the trigger, customer identity, decision evidence, accountable owner, allowed action, stopping conditions, failure path and the measure that represents a useful outcome.

Can quotation follow-up be fully automated?

Stop the sequence immediately when the customer responds or the quotation expires. Automation should stay within an approved and observable boundary, with human review for uncertainty, exceptions and irreversible decisions.

How should a team measure quotation follow-up?

Start with open quotations moved to a clear next state, then review customer effort, correction rate, exceptions and the downstream state that proves the process actually moved forward.

Map quotation follow-up around your real customer journey.

Bring the current rules, messages, system events and exception cases. DripTell will map the workflow with visible ownership and recovery.