One owner at a time
A shared address keeps work accessible when someone changes roles or takes time away. Add a claiming process or assignment rule so each inquiry has one person responsible for the next action.
That person may ask others for help while remaining accountable for the next step. If ownership changes, record the transfer and its purpose. Avoid using several individual inboxes as competing sources of status.
Write an action someone can finish
Write the action as a task: request site access after agreement, confirm installation dimensions or prepare a discovery agenda. Add a due date when timing matters and say what counts as completion. A label such as follow up leaves the next person to reconstruct the work.
A status can summarize the stage, such as awaiting customer information. The next action explains what happens within that stage. Keeping both prevents a pipeline from becoming a collection of labels with no operational direction.
Review the draft and record the send
An AI response workspace can help assemble the inquiry context and prepare a first draft. Staff should be able to inspect and change the message, particularly where it discusses scope, price, timing or promises. The original customer request should remain available.
Separate saved drafts from sent messages. Record the sending result and the channel used. A draft being generated does not mean the customer has heard from the business, and a send attempt does not establish a reply or a qualified opportunity.
Requests that need attention
Create a regular view of unassigned requests, overdue next actions and failed deliveries. Use this view to find and assign work that needs attention. A short review can assign the missing owner or resolve the blocked step.
Decide what happens when the normal owner is unavailable. The substitute should have access to the relevant record and know what they can decide. Support requests and billing issues may need separate handling from new sales inquiries.
- Unassigned: choose an owner.
- Waiting internally: name the decision needed.
- Waiting on the customer: record the requested information.
- Delivery failed: use an approved retry or alternative channel.
Response and ongoing outreach
An inquiry establishes a reason to respond to that request. It does not automatically subscribe the person to ongoing campaigns. Maintain the appropriate preferences and suppression rules in the system used for outreach, and do not infer permission from a lead score.
Review a few completed and stalled inquiries with the team. Check whether the record explains what happened and whether another authorized person could continue the work. Improve the process where it breaks down before adding more automatic follow-up. The next person should be able to open the record and continue the work.
