Choose the smallest useful brief
Begin with the service requested, the location, the preferred timing and a callback number. Add only the details that help your team decide the next step. For a hypothetical cleaning enquiry, the type of property and approximate size may be useful; a long inventory of every room may not be needed before a callback. Ask staff which missing details usually cause another phone call and prioritise those. Avoid turning the conversation into a full technical survey when the team will need to inspect the work or ask specialist questions later.
Screen service fit with clear boundaries
Write an approved list of services and areas covered, along with known exclusions. If an enquiry is clearly outside those boundaries, say so politely before collecting a long brief. If it is uncertain, mark it for staff review rather than guessing. Distinguish where the caller lives from where the work is needed. A caller may be arranging a service for another property. Do not claim a local office or technician presence simply because you accept enquiries from an area. Use the actual service coverage approved by the business.
Handle the price question honestly
If approved pricing information exists, specify precisely when it applies and which conditions must be stated. Otherwise explain that the team needs to review the request before quoting. A useful response is: "I can collect the details so the team can discuss a quote with you." Do not fabricate a starting price to keep the caller interested. Avoid implying that a requested budget has been accepted. Store the budget as something the caller said, and leave commercial decisions with the authorised person who can assess the work.
Separate urgency from a promise
Ask when the caller would ideally like the work done. Record that preference without promising a booking or response time your team cannot meet. If the business has a defined priority process, use its approved categories and destinations. For ordinary time-sensitive enquiries, a date and a short explanation are more useful than an unqualified "urgent" label. A request for tomorrow should be marked as a requested date. The receptionist should explain whether availability can be checked during the call or must be confirmed by staff afterwards.
Request attachments through an approved route
Some enquiries are easier to assess with a photograph or document, but a phone conversation cannot inspect material that has not been received. Offer the business-approved contact route when appropriate and explain what to include. Do not say an attachment arrived just because a link was offered. Associate received material with the original enquiry where the workflow supports it. Avoid asking callers to send unnecessary personal documents. Staff should be able to see whether images are pending, received or reviewed so they do not repeatedly ask for the same information.
Make the handoff useful to the quoting team
End with a concise recap of the requested service, location, timing and next step. The internal message should distinguish caller statements, unanswered questions and any commitment actually made. Assign the enquiry to a queue with an owner and track its eventual outcome, including unsuitable, awaiting details, quoted and accepted. Those states reveal where enquiries stall without treating every phone message as a sale. Review lost or delayed requests for missing information before adding more intake questions. A shorter script with the right fields can be more useful than a detailed form nobody completes.