How can a logistics provider use Outreach to find shippers?
Use Outreach to find prospective shipper businesses that fit your actual transport and storage services, then request an initial conversation. A shipper is the customer entrusting goods to a logistics provider. Finding an online seller’s contact does not establish outsourcing interest or shipment volume. Define the operation you can perform before prospecting.
The hypothetical provider serves ambient household-goods brands in Gyeonggi, South Korea, with storage, packing, and order dispatch. Volumes and reactions are illustrative, and screenshots contain demo data. This guide covers search, fields, review, offers, testing, sending, responses, and cost. Refrigerated storage and hazardous-goods handling remain outside this imaginary provider’s offer; adding them would change the qualification and operational obligations.
Outreach helps you find public business contacts, review the results, send email through your own connected account, and check sending and response records. A project contains keyword groups with their own country, region, common search words, and target count.
Which prospective shippers and locations should you target?
Start with companies selling products you can handle within your service geography. Household-goods brands are the audience here. A marketplace intermediary might hold no stock, and a logistics-directory page is not a shipper. Searching logistics alone can produce competing providers rather than potential customers.
Set South Korea and Gyeonggi in the group and try household-goods brand, household-goods online retailer, and homeware brand. A brand’s headquarters need not be its warehouse, so inspect its business role during review. Food, cosmetics, or electronics may need separate preparation and offers. Before targeting another country, establish service feasibility as well as local contact terminology. Do not extend the promise to operations you cannot perform simply to obtain a larger prospect list.
Which public contacts support an operational discussion?
Require Email for sharing a service scope and arranging a conversation. In this example, collect Phone If available and skip Instagram. A public brand inbox may handle consumer purchases rather than logistics operations; the first message should ask about the appropriate review route.
Your salesperson may use a phone number to confirm a department when appropriate, but Outreach does not automatically call and obtain shipment volumes. Active product promotion on Instagram does not establish outsourcing authority. Requiring both email and phone narrows the list to businesses with both fields. Choose around your actual approach rather than treating more requirements as more alternatives. Public contact discovery should not be described as identity verification of a named logistics decision-maker.
The current contact choices are Email, Phone, Instagram handle, and LinkedIn. Choose Skip, If available, or Required for each. Every required field must be present; a missing optional field does not prevent you from receiving a business.
Skip means that you do not purchase or receive that contact field. Each contact field actually received costs one credit.
How should you review operational fit in the results?
Check that the brand actually sells goods, identify the public product category and location, and inspect the contact purpose. For the example, household goods may fit an ambient operation. Product photos cannot establish carton dimensions, breakage risk, or storage requirements; those are questions for the conversation.
Leave monthly dispatches, daily cutoffs, return proportions, and channel-specific workflows unknown when public information does not establish them. Special-handling goods outside your service scope need exclusion or separate assessment. In an exported review file, distinguish the observed product type from unconfirmed operating conditions. Do not add forecast volume simply because a company publishes email. Review should identify businesses worth an accurate service discussion, not create unsupported capacity or revenue forecasts.
Collection results contain public business contact routes, not guaranteed personal addresses for named purchasing managers. Review the company and the contact destination before selecting recipients. A published email and authority to make a purchasing decision are separate facts.
Download to Excel produces an Excel-compatible CSV file. Fields you did not purchase remain blank. You can share the file for a colleague to review.
What should the first logistics offer contain?
Describe real storage, packing, and dispatch services and explain the conditions needed for a discussion. Without shipment characteristics, do not promise freight savings or next-day delivery. The hypothetical provider offers ambient household-goods handling and asks whether it reached the operational review contact.
Adaptable message: “Subject: Household-goods storage and dispatch for {company_name}. Hello, I’m [name] at [provider]. We provide ambient storage, order packing, and dispatch services in Gyeonggi. May I send our service scope to the person reviewing logistics operations? We would discuss product dimensions, order patterns, required tasks, and timing before confirming service and quotation conditions.” Replace bracketed details. Add only supported operating capability, not an unverified system connection or a capacity figure chosen for promotional effect.
Before sending, connect your own mailbox in Settings → Connect email and save your settings. Follow the provider-specific instructions shown there, then send a self-test to your own inbox. Use the account that will handle replies to this campaign.
Use {company_name} in the subject or body to substitute the company name. Save first and follow-up messages, inspect Preview, and use Send yourself a test first to receive a test in your own connected inbox.
Which operational promises should the self-test inspect?
Check the service scope, company name, document link, and reply route against current policy. If an ambient-only offer accidentally mentions refrigerated storage, correct it immediately. Review the received message in your own account and ensure an old brochure does not list services that are no longer available.
State realistic processing times, packing options, and returns tasks. Any claim about connecting a buyer’s order system requires actual support; this guide makes no such promise. If there is a consultation link, check that the requested product and workflow information is clear. A self-test is not a shipper submitting requirements. Message delivery and operational feasibility remain separate. Recheck selected recipients’ suitability after fixing wording rather than assuming a clean test qualifies the entire prospect list.
How should the first email and phone confirmation be handled?
Select suitable companies after checking contact requirements, and prepare a person to handle operational questions. Replies containing product or order conditions need someone who can assess real capability. Choose campaign scope around that capacity, not around how many addresses exist. An unqualified rate card should not become a fixed quotation.
Phone confirmation should follow the company’s procedure and respect refusals. An unanswered email does not justify repeating the message across other channels on the same day. Review failures before deciding what to do next; do not assume an automatic retry. A service-document click is distinct from outsourcing intent or a dispatch contract. Use the recipient’s actual request to guide the next step instead of assigning commercial meaning to a sending record.
Each sent email costs two credits. The default interval is roughly ten minutes, with adjustable and randomized timing available. Choosing a target count does not make every email leave immediately, and a sent message is not a promise of delivery or response.
Receiving a phone number costs one credit; receiving that number is not an automatic telephone sales service.
Finding a public contact does not establish permission for marketing email. Before sending, check the recipient country’s consent, advertising, sender identification, and opt-out requirements. Consult KISA guidance for Korea and the FTC guide for the United States. An advertising label alone does not authorize unsolicited contact.
How do you manage replies, quotations, and contracts separately?
Record information requests, operational discussions, quotations, and contracts as different stages. A brand asking for the service sheet has not committed any volume. During quotation review, confirm dimensions, storage needs, expected order patterns, packing, returns, and receiving and dispatch arrangements. Do not invent missing values.
An appropriate manual follow-up can reference the earlier message and ask whether it reached the logistics-review contact. Include only real changed service conditions. Clicks and replies are separate from contracts. Your business must separately maintain volume documents, quotations, agreements, service start dates, and operating records. Outreach does not imply an automatic connection to sales channels or warehouse records. If a requirement cannot be supported, state the limitation rather than promise capability to preserve the conversation.
Already sent can be filtered by Sent within the recent 7, 30, or 90 days, sending count, Clicks, and reply or no reply. Select the recipients yourself and use a separate Follow-up message. This manual workflow is not an automatically active sequence.
What should the first run and its budget include?
Prepare a service-scope document and a response owner before creating the Gyeonggi household-goods project. Thirty email fields and thirty sent messages are an arbitrary costing illustration, not a logistics benchmark or results target. Choose the real count around your ability to review products and handle consultations. Resolve unclear service boundaries first.
Include optional phone-field costs separately from email sending and do not assume the full target will be found or selected. See the service guide and B2B email examples for context. To start directly, sign up, select a serviceable region and household-goods buyer terms, set email requirements, and adapt the offer to the operations you can actually provide.
Signup includes 100 free credits, with no monthly subscription. A hypothetical 30 email fields plus 30 sent emails uses 30 + 60 = 90 credits. This calculation guarantees neither 30 matching companies nor delivery of every message.
What should you do when a product or workflow exceeds service capability?
Explain the unsupported condition. An ambient provider should not imply refrigerated goods remain suitable in its storage, and returns inspection or special packing needs a real operating procedure. Do not infer low handling costs from a small-looking product. Try other household-goods descriptions instead of adding unsupported categories to reach the target.
Changing contact requirements cannot change warehouse capability. If the brand holds no inventory, reassess the offer’s relevance. Leave missing volume figures unknown rather than inventing a quote assumption. Review information gaps after consultations to improve your questions, while keeping the buyer’s internal volumes private. Document requests do not establish an operating start date; contracts and actual service records do.
Is every online seller a suitable shipper prospect?
No. Confirm actual products and relevance to outsourced operations. A pure intermediary or a seller of goods outside your handling scope may be unsuitable. Contact information cannot establish dispatch volumes.
Can the first email contain rates? Supported indicative terms can be described accurately, but do not present a fixed quote without the product and workflow conditions. Does this workflow connect to the buyer’s order system? Contact collection and email sending do not establish such integration. Is a document request a contract? No; operations, quotations, and agreements need separate confirmation. What if a refrigerated-product inquiry arrives? This example is ambient-only, so respond within your real capability rather than automatically promising the requested service.
