How to design sales follow-up around inquiry status

A useful follow-up workflow tells a small service team which inquiry needs attention, what the customer has already said and when to stop. AI can summarize a conversation or prepare a relevant draft. The CRM, calendar and permission records should determine whether another message is appropriate.

Start with the inquiry states below. The example is a workflow design you can adapt. For the wider system, read our AI revenue systems guide.

For implementation scope, see AI revenue systems and follow-up automation. This article explains the triggers, timing decisions and stopping rules a team should prepare.

Design around changes in the customer's situation

A fixed sequence should not continue after a state change. A customer who has booked should not receive an “Are you still interested?” sales message because the CRM and calendar disagree.

Agree timing with the team that answers

Choose intervals that fit the service, the customer's stated preference, applicable communication rules and the team's ability to respond. An urgent repair request and a considered renovation estimate need different handling. There is no universal number of touches that is appropriate for every business.

Keep one accountable owner for each open inquiry. Outside staffed hours, an acknowledgment should describe the actual next step without inventing a response commitment. When a customer replies, pause scheduled messages until the new information has been handled.

Write messages that resolve a decision

An example for an incomplete request is: “Thanks for the details. Which service address should we check for availability?” This asks for a fact required by the workflow. An estimate follow-up might offer to clarify scope or arrange a conversation with the person who prepared it.

Use only verified information. Do not imply limited availability, a discount or an expiring quote unless the underlying record supports it. Avoid exposing sensitive service details in ordinary message previews. The relevant business reviewer should approve language for legal or healthcare inquiries.

Respect the rules of each channel

Receiving an inquiry is not a reason to contact someone through every available channel. Record their permissions and preferences and apply withdrawals across the connected workflow. For WhatsApp, the Business Messaging Policy governs permission, templates and escalation. Our WhatsApp implementation guide explains the operating checks.

Before adding SMS, email or calls, review the current provider rules and applicable requirements for the intended messages and markets. Keep that review specific to the planned use rather than assuming one channel's permission covers another.

Test the sequence's stopping rules

Try a reply just before a scheduled send, a booking made outside the messaging flow, a cancellation and a staff takeover. Each should produce the correct state and suppress messages that no longer fit. Then disconnect the CRM and check that the system does not continue using stale information.

The CRM integration guide explains how to handle duplicate and delayed events. Review qualification rules before automating follow-up for an inquiry your business may not accept.

How AI sales agents handle first touches and multi-touch sequences

The first touch is where AI earns its place. It replies within minutes, at any hour, answers the question the customer asked and requests the one missing detail. People rarely manage that during a busy day.

Later touches should come from the inquiry's state, not from a fixed calendar. An AI agent reads the latest reply, updates the CRM and picks the next step from the table above. That might be a reminder about an unanswered question, an offer of new availability or a handover to the estimator. If the customer has replied by SMS, the next touch goes by SMS. If they asked for a call, a person gets a task instead of the customer getting another message.

Example: follow-up for a construction company

A remodeling contractor receives inquiries through its website, Google Business Profile messages and phone calls. The AI acknowledges each one, asks for the address, project type and preferred timing, and books the site visit into the estimator's calendar. After the estimate goes out, it checks in when the customer has had time to read it and offers a call with the estimator to discuss scope. It stops when the customer accepts, declines or asks to pause.

The sales team structure stays simple: the AI handles first touches, scheduling and routine check-ins, while estimators own site visits, pricing and the conversations that decide the job. This is an example design to adapt.

Measure completed work and unwanted contact

Track open inquiries without an owner, time to a useful response, booked appointments, completed jobs, opt-outs and staff corrections. Keep sent and delivered messages separate from conversations and bookings. A higher send count does not demonstrate a better customer experience.

Compare equivalent inquiry cohorts and allow time for outcomes to mature. Record changes in advertising, pricing and capacity alongside the automation launch. Those changes can affect results too.

Can Luminous build this around our current tools?

Our AI revenue systems service starts with the existing CRM, booking process and operating rules. Bring a few anonymized inquiry journeys to Discuss Your Project. We can identify a bounded workflow, its dependencies and the checks required before launch.