Let's Unlock Your Business. Book your Free Strategy Call
Free Consultation

Contractor Growth and Business Systems: A Guide to Outbound Cold Calling

Roofing contractor reviewing an outbound cold calling plan at a desk with a laptop and phoneOutbound cold calling can help a contractor start conversations with potential customers or business partners, but only when it fits a clear process. Without a defined audience, useful reason to call, and consistent follow-up, calls can consume time without creating a dependable next step. This guide lays out a practical system that roofing, solar, and other growing contractors can adapt to their goals.

Request a Free Strategy Call

What does outbound cold calling mean for a contractor?

Outbound cold calling is the practice of placing an initial call to a person or organization that has not recently requested that specific conversation. In a contractor business, the purpose may vary. A team might be looking to introduce a service to a commercial property contact, make a business-to-business connection, follow up on a permitted list of prospects, or invite a qualified person to discuss a need. These are different objectives, and they should not be blended into one vague campaign.

A useful calling process is more than a list and a dialer. It connects a business goal to a defined group of contacts, a truthful opening, a respectful conversation, a documented result, and an appropriate next step. The caller needs to know what they may say, what they should ask, when to stop, and where to record the outcome. The person who receives the call should understand who is calling and why.

Cold calling is also only one possible way to begin a business conversation. It may complement referrals, inbound inquiries, relationship building, or other outreach. It is not a substitute for delivering good work, managing customer communication, or having a service offer that is clear enough to explain. Before building a calling routine, decide whether a call is genuinely the right first contact for the audience and objective.

Why put a process around calls?

When outreach depends on memory, the same prospect may be called twice by different people, a requested callback may be forgotten, or a useful conversation may never reach the person responsible for the next step. A process reduces these avoidable gaps. It helps an owner see how the team is using its time and whether the outreach is producing conversations that deserve further attention.

Process does not mean making callers sound scripted or turning every discussion into a sales pitch. It means setting a few dependable standards: the purpose of the call, the information the caller can rely on, the questions worth asking, how to respond when someone is not interested, and how to record the result. Those standards let a caller be natural while keeping the work consistent.

For a lean contractor, the process can also make ownership clear. The owner may decide which types of organizations are appropriate to contact, while a caller handles preparation and first conversations. A coordinator or salesperson may then receive qualified follow-ups. If the business cannot identify who owns that handoff, increasing call volume is unlikely to solve the underlying problem.

What should the business decide before making calls?

Start with a short written brief. It should describe the business reason for calling and set boundaries for the work. This is not a large marketing plan. It is a practical reference that keeps the caller and the person receiving the handoff aligned.

Keep the brief current. If the offer, target audience, or next step changes, update the material before the caller uses it again. Outdated notes can lead to confusing explanations or promises the business has not approved.

How do you define the right prospect?

“Anyone who might need our services” is not a workable audience definition. It gives callers no way to prioritize or make a relevant opening. Define a prospect using a small number of observable characteristics related to the objective. For example, a contractor considering business-to-business outreach might define a target by organization type, role, region, and a documented reason the conversation could be relevant. The right criteria depend on the offer; avoid adding details simply because they are easy to collect.

Separate a good-fit prospect from a confirmed opportunity. A list entry may match the broad audience but still have no present need, no decision-making role, or no interest in a conversation. A first call can help determine whether a sensible next step exists. It should not be treated as proof that the contact is ready to buy.

Also decide what makes a contact ineligible for further outreach. Possible reasons include a prior request not to be contacted, a wrong number, a duplicate record, or a mismatch with the intended audience. The caller should have a clear way to record these outcomes and a clear instruction not to keep retrying a contact when the process says to stop.

Keep the first test group small enough to review carefully. A limited, well-understood group makes it easier to spot bad records, confusing language, and unproductive assumptions. If the list is broad or the results are unclear, refine the criteria before expanding the activity.

What should a caller know before dialing?

Preparation should be brief, relevant, and based on information the business can stand behind. The caller needs enough context to avoid sounding generic, but not a long research dossier for every number. Confirm that the record belongs in the intended audience, check for previous contact history, and identify the approved opening and next step.

Do not encourage callers to invent personal familiarity or imply a referral that did not happen. A call can be direct and personable without pretending that the caller knows the recipient. If the business has a legitimate, relevant reason for reaching out, state it plainly. If it does not, reconsider whether the call should be made.

How can you build a useful call opening?

A good opening is short enough to say naturally and complete enough to orient the person. It can identify the caller and business, explain the reason for the contact in plain language, and ask whether the person is open to a brief conversation. The opening should not hide the commercial purpose or make the recipient work to figure out what is being offered.

For example, a caller might say: “Hello, this is [name] with [business]. I’m calling because we work with [plain description of the relevant audience or need]. I wanted to ask whether [specific, appropriate topic] is something you handle. Is now an inconvenient time?” This is a framework, not a line to repeat mechanically. Replace every bracketed detail with an accurate, approved description.

Keep the opening focused on one reason. Avoid stacking multiple services, claims, and questions into the first breath. If the recipient says it is a bad time, acknowledge that and follow the approved process for asking whether another time is appropriate. If they say no, accept the answer without arguing. Respectful exits are part of a professional process.

Listen for the response rather than rushing into the next paragraph. A caller who gives the person room to answer can learn whether the contact is relevant, whether someone else is the right person, or whether there is no reason to continue. That is more useful than reciting a long pitch before learning anything about the situation.

What questions help qualify a conversation?

Questions should clarify fit and next steps, not collect information for its own sake. Use a short, consistent set that follows naturally from the opening. The caller might ask whether the person handles the relevant area, whether the issue is something the organization is considering, or whether a follow-up with a particular colleague would be more useful. Ask one question at a time and let the contact answer.

Choose questions that the business can act on. If nobody will use a detail to decide what happens next, it probably does not belong in the first conversation. Avoid turning an introductory call into a full discovery interview. Detailed scoping belongs with the appropriately qualified person and should happen only when the contact wants to continue.

Write down what counts as a qualified follow-up before calls begin. The definition could include a relevant organization, a contact who has a role in the topic, a stated need or interest, and permission to take a specific next step. The definition should not depend solely on a caller’s impression that the conversation “felt good.”

There is no need to force every call into a sales opportunity. A clear “not a fit,” “not interested,” or “wrong contact” can be a useful result if it is recorded accurately and handled according to the business’s contact rules. Good records help the team distinguish a genuine opportunity from activity that merely produced a response.

How should you handle common responses?

Prepare brief response guidance for the situations callers are likely to encounter. The aim is not to defeat objections. It is to answer honestly, clarify what the person means when appropriate, and make it easy to end or continue the conversation by mutual choice.

Review the language with the people who will take the next step. A caller should not promise a price, service scope, schedule, result, or capability that another team has not confirmed. If the same unanswered question comes up repeatedly, route it to the owner to resolve and update the approved guidance.

What should happen after a call?

Every attempt needs a clear disposition. A short result label makes the activity understandable to the next person and helps the business see where the process is getting stuck. Labels should describe what happened, not the caller’s judgment of the person. Keep the set concise enough that callers can use it consistently.

A practical starting set may include: no answer; left an approved message; connected, no interest; wrong contact or number; requested information; requested callback; possible fit, follow-up needed; qualified next step agreed; and do-not-contact request. Customize labels to the campaign, and explain when each one applies. Do not use “qualified” as a catch-all for anyone who answered the phone.

Record the date, contact, outcome, key points the person volunteered, and the exact next action where appropriate. If a follow-up is due, assign an owner and date. If no further action is appropriate, record that too. Good notes are factual and brief. They should help someone continue a conversation without requiring the recipient to repeat everything.

Use the company’s chosen CRM or another approved recordkeeping system as the source of truth. Do not leave the only record in a caller’s personal notebook, text thread, or memory. If the business uses a CRM, decide which fields are required and how to handle duplicates before the campaign starts. Review the range of operational support services when considering how call work fits alongside other contractor workflows.

How do you plan follow-up without becoming a nuisance?

Follow-up should be based on what the recipient said and what the business has approved, not on an automatic assumption that every unanswered call deserves another attempt. Set a contact policy before outreach begins. The policy should describe how to handle no answers, requested callbacks, requested information, and explicit declines, along with how to record any instruction to stop.

Make any planned cadence realistic for the team and appropriate to the context. Decide how many attempts are allowed, how much time should pass between them, which channels are permitted, and who monitors repeated activity. A high number of touches is not a goal by itself. If the contact asked for one specific callback, follow that request rather than placing a series of uninvited attempts.

When a person requests information, send only the material agreed on and make the message useful. Identify the sender, connect it to the conversation, and avoid implying that the recipient committed to a meeting or purchase when they did not. If a next conversation is agreed, confirm who will contact whom and what the discussion is expected to cover.

Keep contact preferences visible to anyone who might reach out. When outreach crosses channels, make sure that separate team members do not unknowingly contact the same person with conflicting messages. A coordinated, measured process protects the recipient’s time and the contractor’s reputation.

How can a contractor keep the conversation natural?

Scripts are most useful as guardrails. They should help a caller explain the purpose, ask essential questions, and respond accurately. They should not require the caller to read every sentence regardless of what the other person says. Provide a short opening, a few optional prompts, approved answers to common questions, and clear rules for ending the call or escalating an issue.

Train callers to pause after asking a question, listen for the answer, and reflect the relevant point before moving on. A simple acknowledgement can make a conversation feel more human than an elaborate line. Encourage plain language and short sentences. Remove jargon, exaggerated promises, and phrases that sound as if they came from a generic script rather than the business.

Practice with realistic situations before live outreach. Include a contact who is curious, one who is busy, one who asks a question the caller cannot answer, and one who declines. Practice the handoff as well as the opening. A caller should know how to summarize the discussion to the next person without adding assumptions or omitting the recipient’s request.

Listen to a sample of calls or review notes according to the company’s policies and applicable requirements. Use the review to coach specific behaviors: accurate introductions, respectful listening, truthful descriptions, clear next steps, and complete records. Do not judge quality by the number of words spoken or how forcefully the caller pushes for a meeting.

Who should own each part of the process?

Small teams often share responsibilities, but every task still needs an owner. A simple responsibility map avoids the situation where everyone assumes someone else is maintaining the list or responding to an interested contact.

One person may hold several roles, especially in a small business. The important point is to assign each responsibility explicitly and provide enough time and access to complete it. If the caller cannot see prior contact history or cannot enter notes, the process design—not just caller performance—needs attention.

Contractors can map these steps to the way they already manage customer communication, scheduling, and CRM upkeep. The same discipline used for coordinating roofing jobs and schedules can help clarify who owns a call handoff, what information must travel with it, and when a task is complete.

What should you measure?

Choose a few measures that help answer operational questions. Activity counts can show whether a planned work block happened, but they do not establish that outreach is useful. Pair activity with measures of data quality, conversation outcomes, and completion of agreed follow-up. Define each measure before collecting it so the team does not change its interpretation from week to week.

Interpret the measures together. A large volume of dials with weak records may point to a data or workflow problem. A low number of qualified follow-ups may mean the audience, message, offer, or timing needs review. A high number of positive conversations is not automatically a good result if the next step is unclear or the team does not complete it.

Set a review interval that is practical for the team. In a short pilot, a weekly check may reveal early issues; a larger or slower-moving effort may need a different rhythm. Compare like with like and note changes to the list, script, staffing, or offer. Do not treat a small or inconsistent sample as proof of a reliable outcome.

How can you run a manageable pilot?

A pilot is a controlled way to find operational problems before making outreach a larger routine. It does not need complex software. It does need a defined period or work block, a bounded prospect group, an approved opening, a recordkeeping method, and someone responsible for reviewing what happens.

  1. Write the brief. Document the objective, audience, offer, next step, and boundaries in language the caller can use.
  2. Check the contact records. Remove obvious duplicates, confirm the information available, and make contact-status instructions visible.
  3. Prepare the call guide. Include a natural opening, a few qualification questions, approved answers, and clear ways to close or escalate.
  4. Test the handoff. Walk through what happens when someone requests a callback or shows interest. Verify that the receiving person can see the notes and knows what to do.
  5. Make a limited set of calls. Keep the scope small enough that the team can inspect the outcomes and correct errors.
  6. Review and adjust. Look for recurring list problems, unclear language, missing information, and overdue follow-ups. Change one or two things at a time where possible.
  7. Decide whether to continue. Continue only when the audience, process, workload, and next-step ownership are clear enough to support it.

Do not expand just because the first day produced a few encouraging conversations. Look for repeatable execution: callers can follow the process, records are reliable, follow-up is completed, and the activity remains appropriate for the business. If the pilot reveals a weak list or an unclear offer, resolve that before increasing effort.

What does a complete call workflow look like in practice?

Consider a contractor that wants to introduce a defined service to a narrow group of business contacts. The goal is not to call every organization in a region. The owner first writes down what kind of organization is relevant, which role is most likely to handle the topic, what the business is prepared to explain, and what counts as a useful next step. The list owner checks each record for duplicates and prior contact instructions. The caller then reviews a small batch rather than relying on a large, unfiltered spreadsheet.

Before a call, the caller confirms the record and chooses one reason for reaching out. During the conversation, they identify themselves, explain that reason, ask whether the topic belongs to the person, and listen. If the contact is not the right person, the caller may ask whether they are comfortable suggesting a role or department. If the contact has no interest, the caller ends politely and records the outcome. If the contact asks for a later conversation, the caller confirms a practical time or next action rather than promising an unspecified callback.

Immediately after the call, the caller records the result using the agreed disposition. A requested follow-up gets an owner, due date, and a brief factual note about what was requested. A wrong number or do-not-contact request updates the record so it does not return to the active list. A question outside the caller’s knowledge goes to the named owner rather than being answered by guesswork. At the end of the work block, the owner can review not only how many calls were placed, but whether each result has a clear destination.

This sequence exposes weak links early. Perhaps the chosen contact role is rarely correct, or the offer takes too long to explain. Maybe the caller records outcomes but the follow-up owner does not see the queue. Each is a different problem and calls for a different fix. Adjusting the list will not repair a handoff, and adding more script language will not solve missing records. Inspect the stage where work stops, then change that stage and retest it.

How should you prepare and maintain a calling list?

A calling list is an operating record, not just a set of numbers. Each row should have enough information to support a relevant, responsible attempt and enough status detail to prevent conflicting outreach. The exact fields depend on the business and its systems, but a practical baseline includes the organization or contact name, number, source or reason for inclusion, assigned owner, prior contact status, last attempt date, disposition, and next action when one exists.

Before a list enters a calling block, perform a quick quality pass. Remove duplicate records or choose one canonical record and preserve useful history. Check that a number is present and associated with the intended organization. Flag records with unclear source or audience fit for review instead of encouraging the caller to fill gaps through assumptions. Make opt-out or no-contact status conspicuous; it should not be buried in free-form notes that a caller may overlook.

After activity begins, maintain the list in manageable batches. A list owner can review a portion for duplicates, missing details, and inconsistent status labels at a set interval. If callers discover repeated problems, record the type of defect: wrong role, disconnected line, duplicate, incomplete organization information, or out-of-scope contact. A pattern suggests a sourcing or cleanup issue, while isolated errors may simply need individual correction.

Establish rules for who may edit core fields and how changes are documented. If multiple people can add prospects, agree on the minimum details required before a record becomes callable. If records are imported from a spreadsheet, test a small sample first and confirm that fields map correctly. Do not let a bulk import overwrite contact preferences or erase history. A controlled list makes outreach easier to coordinate and helps the team explain why a particular person was contacted.

How can you schedule calling work around contractor operations?

Calling has to fit alongside estimates, job coordination, customer updates, and urgent field questions. A schedule that assumes uninterrupted blocks all day may be unrealistic for an owner or coordinator who is also responsible for active projects. Start by identifying who can make calls, how much protected time is practical, and who will cover incoming work during that period. The purpose is to create a repeatable routine, not to force a rigid calendar that will be abandoned after the first disruption.

Separate preparation, calling, and follow-up tasks where useful. For example, a team might clean a small batch of records before a call block, place calls during the reserved period, and then spend a short closing block entering dispositions and assigning requested actions. If follow-up is left until an undefined later time, even a productive conversation can lose momentum. The final minutes of the block should be reserved for complete records, not merely for making one more attempt.

Use a visible queue to distinguish work that is due now from work that is waiting on someone else. A callback requested for a specific time is different from an unanswered first attempt. Information requested by a contact may have a different owner from an internal question that needs approval. Clear status labels prevent the caller from treating every record as equally urgent and help a manager notice when a commitment is at risk of being missed.

Protect some flexibility. A contractor’s operating day can change when a customer issue or project need arises. When a call block is interrupted, the team should know how to pause safely: save the record, leave the queue in a known state, and reschedule unfinished callbacks. Do not leave a contact marked as completed when the agreed action remains open. Small, honest status updates are more useful than an ambitious calendar that hides incomplete work.

How can you review call quality and coach callers?

Quality review should test whether the process is clear and respectful, not whether every call follows identical wording. Decide in advance what a reviewer will look for. A simple review may check that the caller introduced themselves accurately, gave a truthful reason for the call, asked a relevant question, listened to the answer, respected a decline, avoided unapproved claims, and recorded the outcome correctly. Use the same standards across the team so feedback does not depend on a reviewer’s personal style.

Review both the conversation and the record when the company’s policies and applicable requirements allow it. A call may sound smooth but still end with no owner for the promised next step. Conversely, a short or awkward conversation may be handled well if the caller recognizes a mismatch, ends courteously, and records the result correctly. Looking at the record alone can miss tone and listening; evaluating a conversation alone can miss whether the workflow was completed.

Give feedback tied to an observable action. Instead of saying “be more persuasive,” a reviewer might note that the caller introduced three services before asking whether the contact handled the topic. A specific adjustment could be to use one concise reason and pause for an answer. If a caller repeatedly receives a question they cannot answer, determine whether the call guide needs an approved response or whether the audience expects a different role. Do not make the caller responsible for filling a gap that belongs to the business.

Keep a change log for the call guide. Record what changed, why it changed, who approved it, and when callers should begin using it. This prevents one person from coaching an old opening while another distributes a new one. A brief practice session after a meaningful change can confirm that callers understand the revised language and know which parts remain flexible.

How do you decide whether to continue, change, or stop?

A pilot review should end in a decision, not just a report of activity. Continue when the intended audience remains appropriate, callers can follow the process, records are reliable, and the team can complete the next steps it agrees to. Continuing does not require every call to produce an opportunity. It does require that the effort can be managed and that the results are useful enough to justify the work.

Change the process when evidence points to a specific obstacle. If many records are outside the target audience, tighten list criteria. If contacts repeatedly misunderstand the offer, simplify the explanation and verify that it is accurate. If people respond but no one follows through, repair ownership and task visibility before calling more. If the call block repeatedly interrupts essential operations, reconsider who should handle the work or when it should occur.

Pause or stop when the team cannot honor contact preferences, answer basic questions responsibly, or assign follow-up. Also pause if the campaign’s reason for contacting people is no longer clear or the list cannot be maintained accurately. Stopping a poorly controlled routine is a useful management choice. It prevents the business from scaling a workflow that is confusing for callers and recipients alike.

When reviewing results, compare similar groups and periods. If the audience, script, call time, list source, and caller all change together, it becomes difficult to know what caused a difference. Keep notes on meaningful changes and avoid drawing firm conclusions from a few conversations. A practical review asks what the team learned, what specific change it will make, who owns that change, and when the next check will happen.

What commonly goes wrong?

The audience is too broad. Callers cannot explain why they chose a contact, and conversations sound interchangeable. Tighten the criteria and give the caller a relevant, truthful reason for reaching out.

The script explains too much. The opening becomes a monologue, leaving little room for the other person to respond. Reduce it to an introduction, a concise reason, and one appropriate question.

The offer is unclear. Callers describe different services or imply that unrelated work is automatically included. Create a short, approved service explanation and direct detailed scope questions to the right person.

The notes are incomplete. The next person cannot tell what was discussed or what the recipient asked for. Use clear dispositions, a few useful fields, and an assigned next action.

Follow-up has no owner. A promising conversation sits in a queue while each team member expects someone else to act. Assign the owner and due date before the record leaves the caller’s hands.

Activity is mistaken for progress. The team tracks dials but not relevance, handoffs, or completion. Add a small number of quality measures and review the full path from attempt to next step.

Callers are asked to improvise beyond their role. They guess about pricing, technical matters, or outcomes to keep a conversation moving. Give them an approved way to say they will check, and make sure someone is responsible for answering.

Too many systems are used. Notes end up in personal files, inboxes, and disconnected spreadsheets. Choose a source of truth, document how it is used, and make sure the people who own follow-up can access it.

How do compliance and contact preferences fit in?

Calling rules can depend on the type of call, who is being contacted, how the number was obtained, the technology used, and where the recipient is located. A contractor should not assume that one informal rule covers every campaign. Before making calls, determine which federal, state, and other requirements apply to the specific outreach, and get qualified guidance when needed.

At the operational level, use contact information responsibly, maintain accurate records, honor requests to stop, and make sure callers know the approved boundaries. Review the campaign’s calling methods and scripts before launch. If the business changes its list source, call technology, audience, or message, reassess the process rather than assuming the original review still applies. This section is practical risk awareness, not legal advice.

Do not let a caller decide on their own that a person’s request can be ignored because the record looks valuable. Provide a clear internal path for documenting contact preferences and make that information available to the people making calls. Respectful, well-controlled outreach is part of protecting customer trust.

When might a contractor need operational support?

Some owners can manage a small outreach test themselves. Others already have a clear objective but struggle to keep records updated, make calls consistently, or complete handoffs while also managing estimates, jobs, and customer communication. The gap may be a defined task, a missing workflow, or insufficient time. Identify which problem exists before deciding what kind of support would help.

Routine virtual-assistant support and specialized business services are not automatically the same engagement. A business should clarify what work it wants covered, what decisions stay with its own team, what systems the person will use, and how completed work will be reviewed. Unlocked Business Solutions describes operational support for contractor workflows and separately lists cold calling services. A conversation can help determine whether the described service is relevant to a particular need; it should not be treated as a promise of a specific outcome or scope.

If a contractor is evaluating staffing support more broadly, it can review the company’s published process and prepare questions about discovery, role definition, selection, interviews, and onboarding. Ask how a proposed arrangement would handle the actual task, access, records, oversight, and handoffs. Confirm what is included rather than assuming every service follows the same staffing model.

How do cold calls fit with the wider contractor system?

Outbound calls work best when they connect to the systems around them. A prospect record should have a clear home. A call outcome should lead to an assigned task. A requested callback should appear where the owner will see it. If an interested contact is passed to a salesperson or coordinator, that person should receive enough context to continue without restarting the conversation.

Map the workflow from beginning to end: how a contact is selected, who makes the call, what information is captured, where the record is updated, who takes the next step, and how the team closes or pauses the record. Mark each handoff. For every handoff, state what information must be included, who accepts responsibility, and how completion is recorded.

Also decide how outreach relates to other communication. A call should not collide with a separate email or another team member’s follow-up. When several channels are used, define which system records contact history and how the team checks it before acting. Consistency makes it easier to provide a coherent experience and to understand what happened.

Finally, keep the process proportionate. A growing contractor does not need a complicated sales operation just to test a handful of calls. Start with the minimum reliable workflow, add structure when a real need appears, and document changes so the process does not depend on one person remembering every exception.

What is a practical checklist before launch?

If several items are missing, pause and resolve the process gaps before expanding call activity. A smaller, well-managed effort is easier to learn from than a large list handled inconsistently.

Discuss Your Contractor Support Needs

Frequently Asked Questions

Is outbound cold calling right for every contractor?

No. Its fit depends on the business goal, audience, offer, available contact information, team capacity, and applicable requirements. Consider other ways to reach the audience if a call would be irrelevant or if the business cannot handle a resulting conversation.

How long should an outbound call script be?

Keep the opening concise and use the rest as a guide, not a speech. Include only the information needed to introduce the caller, explain the reason for the call, ask a relevant question, and agree on a next step or end the conversation politely.

What should a contractor record after a call?

Record the attempt, contact, factual outcome, useful points the person shared, any contact preference, and the next action with an owner and due date when follow-up is appropriate. Use a consistent system and avoid speculative or unnecessary notes.

How often should a team follow up?

There is no single cadence that fits every situation. Set a reasonable policy for the campaign, follow any specific request from the contact, and honor instructions not to call again. Make sure repeated attempts are coordinated across the team and channels.

Can outbound calls be handled by an outside support provider?

That depends on the provider’s described services and the contractor’s needs. Confirm the scope, responsibilities, systems, approved language, oversight, and handoff process before proceeding. Do not assume that outbound calling is included in every operational-support arrangement.

Build a calling process your team can maintain

Outbound cold calling is easier to manage when the goal, audience, message, records, and next step all fit together. Start with a clear brief, test a limited process, review real outcomes, and improve the parts that create friction. For contractors, the most useful system is one that supports relevant conversations while protecting the time of both the caller and the person being contacted.

Leave a Reply

Your email address will not be published. Required fields are marked *