Call Screening
Training a virtual receptionist to screen solicitation calls
A screening routine that keeps sales pitches and scam calls away from the team without blocking legitimate vendors.

Table of contents
Write a definition of a solicitation call
A solicitation call is an unsolicited attempt to sell a product, service, or donation. It is not the same as a vendor calling about an existing order or a partner returning a message. The screening rule should describe the difference in plain language. A clear definition keeps the receptionist from guessing.
Include examples of calls that look like solicitations but are not. A supplier confirming a delivery window may sound like a sales call at first. A recruiter returning a candidate's message is not selling anything. Review the examples with the receptionist before the first shift.
Ask two questions before transferring
The first question is who the caller is and which company they represent. The second is whether the call relates to an existing order, account, or appointment. Those two answers usually separate a legitimate caller from a pitch. Ask them in a neutral tone and listen for a specific reference.
If the caller cannot name an existing relationship, offer a shared inbox or a scheduled callback instead of a transfer. Many legitimate vendors are happy to send an email. A caller who insists on speaking to the owner immediately is a warning sign. The receptionist should not argue, only follow the rule.
Give the receptionist a short refusal script
Write one or two sentences that decline a solicitation without being rude. A line such as "We are not taking sales calls on this line; you can send information to our contact email" is enough. Say it once and do not explain the company's entire purchasing process. The goal is to end the call politely.
The script should also cover a caller who keeps talking after the refusal. Offer to take a message and end the call if the pitch continues. Do not let a persistent caller consume the line. The receptionist can log the number for the owner's review.
Protect the team from scam and pressure tactics
Some calls are not sales pitches but attempts to extract information or money. Train the receptionist to recognize urgency, threats, and requests for payment or credentials. Common examples include fake invoices, fake utility notices, and callers claiming to be from a bank. The receptionist should never confirm account details to an unverified caller.
Set a rule that payment or credential requests are escalated to a named owner, not handled at the front desk. Keep a list of known scam patterns and update it when a new one appears. The receptionist should record the caller's number and the exact request. A calm record helps the owner decide whether to report the call.
Keep a log of screened calls
A simple log with the date, caller number, company, reason, and outcome makes the screening process visible. Review it weekly for patterns such as repeated calls from the same number. A sudden increase in a certain pitch may mean the company's contact details were sold or scraped. The log helps the owner decide whether to block a number.
The log should not include sensitive personal data that the receptionist does not need. Use a short reason code instead of a full transcript. Limit access to the people who review the calls. A lean log is easier to maintain and safer to store.
Route legitimate vendors to the right owner
Screening should not block a vendor who supports an active project. Give the receptionist a list of approved vendors and the person who owns each relationship. If a caller matches the list, transfer or schedule a callback with that owner. Update the list when a contract starts or ends.
For a new vendor, offer a standard intake path such as an email address or a vendor form. Tell the caller what happens next and how long a reply usually takes. Do not promise a meeting that the owner has not agreed to. A consistent path protects the owner's time and treats the vendor fairly.
Measure false blocks and missed vendors
Track calls that were screened out but later turned out to be legitimate. Ask the owner or the team to report a missed vendor during the week. A high false-block rate means the definition or the questions are too broad. A low rate with many complaints means the screen is too loose.
Review a sample of screened calls with the receptionist each month. Listen for tone as well as accuracy. A correct refusal delivered rudely still damages the business. Coach one behavior at a time, such as asking the relationship question before refusing.
Keep the screening rule visible and current
Post the definition, the two questions, and the refusal script where the receptionist can see them. Put the same content in the training folder for a backup handler. Review the rule when the company changes its purchasing process or adds a new department. An outdated rule creates inconsistent answers.
Ask the receptionist to suggest improvements after the first month. The person taking the calls often hears patterns that the owner misses. Test one change at a time and compare the log before and after. A screening process works best when the people using it can improve it.
Close the shift with a short handoff
At the end of a shift, the receptionist should note any caller who needs a callback and any number that should be blocked. A short handoff prevents the next person from repeating the same screening conversation. Include the reason and the owner for each open item. Keep the note in one place the team already uses.
The handoff should also mention any change in the approved vendor list or the owner's availability. A quick review at the start of the next shift takes less than a minute. Over time, these notes become a record of what the front desk actually handles. That record is useful when the team reviews staffing or call volume.