Start with the actual state of the proposal
AI can follow up automatically under agreed contact rules, routing technical questions to the team before resuming the conversation.
A sent proposal is not a finished conversation. But a generic automated reminder is not meaningful follow-up either. Before contacting someone, check what was proposed, when it was sent, who attended the visit and whether questions remain unanswered. A flooring project with substrate concerns needs a different response from a window replacement waiting on a date.
Assign an owner to each proposal. They should know whether to answer a technical question, confirm availability, wait for an agreed decision or end contact. Without that context, follow-up repeats messages or asks for a decision before the customer has the information they need.
Choose timing based on commitments, not a blind rule
No interval works for every project. If you agreed to reply after a visit, honour that. If the customer said they would decide after speaking with someone else, record it before writing again. Complex work may need more time than a minor installation, but the team and the customer’s expectations should determine the schedule.
A contextual message might read: “Hello. We sent the proposal for flooring in the living room and hallway. We still need to clarify preparation of the existing substrate. Would you like us to confirm this before proceeding?” It is a specific, useful question, not pressure to close. Adapt the language and facts to the actual job.
Resolve doubts before asking for a decision
Questions about materials, compatibility, timing or price need an owner. Route technical issues to someone who can validate the solution; do not ask an automated response to invent specifications. On commercial questions, clarify what is included. Any change of price or terms requires a human decision.
Keep the question and answer with the proposal so the next contact does not start from scratch. If the customer needs time, note when it is appropriate to return. If they decline or ask not to be contacted again, stop. Clear stop rules protect the relationship and save work with no value.
Measure the process without promising results
Count proposals with an owner, appropriate follow-ups made, replies that clarified a question and decisions recorded. If your business tracks accepted proposals, compare against your starting point without assuming a tool caused any change.
Look at effort too: how long does it take to determine a proposal’s state and prepare a suitable message? A useful process leaves a clear history, an assigned next step and room for sales judgement. The goal is a relevant conversation, not a higher message count.
Review what happens before follow-up
Periodically choose a small sample of proposals and check whether each has an owner, an open question and a recorded next action. Separate those awaiting technical validation from those simply awaiting a customer decision. This review shows whether the problem lies in later contact or in the information sent with the proposal.
If several customers raise the same concern, improving the original quote may be more useful than sending more messages. Share patterns with the people who make visits and prepare proposals. Effective follow-up also depends on a clear handoff at earlier stages.