Transport company website development should separate two tasks: a customer's freight quote request and an enquiry from a carrier offering capacity. Give each task its own call to action, relevant form fields and person responsible for the reply. Visitors can then provide the details for their situation, and your team can continue the conversation without first working out who the message is for.
If your company serves only one of these groups, the structure can be simpler. When planning website development, start by describing how you arrange work. A carrier operating its own vehicles and a business connecting shippers with carriers may need different pages.
How does a visitor choose the right route?
A customer arranging transport wants to check whether you handle their freight and cover the required route. A carrier wants to introduce its available equipment and discuss working together. A general contact button can lead to either conversation, but it gives the visitor little guidance about what to prepare.
The homepage can offer separate choices such as “Request a freight quote” and “Become a carrier partner”. Add a short explanation of who each option is for. On a service page, keep the quote request close to the service information and make carrier details accessible through the navigation.
Use a separate route for job applications if you recruit drivers. A partnership with a carrier business and an application for employment have different requirements and review processes.
What belongs on freight service pages?
For each service, explain the freight you accept, your service area and the information needed for an assessment. Include limitations that affect whether you can take the request. A vehicle photograph cannot tell a visitor whether you handle a single pallet, a full load or freight with special requirements.
Separate services when customers have different questions about them. For temperature-controlled freight, for example, the customer needs somewhere to specify the required range. Unusual dimensions call for details of size and loading conditions. Your operations team should confirm which information is needed immediately and which can follow in a conversation.
Connect the service page to the relevant form. If the customer has already chosen a service, that selection can carry into the enquiry while remaining editable. When pricing requires a review of scope and availability, label the action clearly as a quote request.
How did we separate the audiences on Cargo Shark?
Our Cargo Shark project has separate routes for customers and carriers. Its public quote request page includes fields for freight type, weight in pounds, load type, pickup date, pickup location and delivery location. Required and optional fields are identified.
The carrier page asks for a company introduction, MC number and contact details. It explains that capacity, routes and next steps will be discussed with the team. Sending an introduction does not complete carrier approval or confirm a load.
This example comes from a business operating in the US market. For your website, choose the information according to your service area and partner review process. Work through those requirements with your team before adopting another company's form.
Which details should the first enquiry collect?
For every field, ask the person handling enquiries whether they can give a useful first reply without it. Collect enough information to understand the request, with a way for customers to indicate what they do not yet know. Always show the unit for dimensions and weight.
The following fictional example is a planning aid. It is not a copy of Cargo Shark's form or a record of a real shipment. You can copy it into your brief and replace the examples with the information your team requires.
Scroll the table sideways to see all columns.
| Decision | Customer requesting transport | Carrier proposing a partnership |
|---|---|---|
| Purpose | A quote to move four pallets. | A conversation about working together on particular routes. |
| Initial information | Belgrade to Niš; approximately 800 kg; pickup date to be agreed. | Available equipment type, operating area and expected availability. |
| Details to check next | Pallet dimensions, site access and loading conditions. | Company details and documents required by the partner review process. |
| Who receives it | The person assessing transport requests. | The person responsible for carrier relationships. |
| What submission confirms | Receipt of a request for assessment; the rate and date are confirmed later. | Receipt of the company introduction; partnership terms are reviewed later. |
For each row in your specification, add the field name, whether it is required and who uses the answer. Identify documents collected at a later stage. First contact does not have to cover the whole partner approval process.
What happens after an enquiry arrives?
Agree where each enquiry goes and who takes over when the responsible person is absent. The received message should clearly show the selected service and all the answers. If both forms use the same inbox, the subject line and enquiry category can help staff assign the message.
The website should confirm successful receipt only after the system accepts the request. If something fails, explain what the visitor can do next and preserve their entries where possible. State a response time only when the team can meet that commitment.
If enquiries need to enter a CRM or transport management system, check that product's available functions before planning an API integration. Agree which fields move between systems, how duplicates are prevented and who handles failed transfers. Shipment tracking and customer accounts need a separate web application scope when they are part of the proposed solution.
Who keeps services and content up to date?
Someone in the company needs to approve changes to service areas, contact information and published conditions. Agree CMS fields for the content you regularly change and access for the person editing it. Use a real update, such as revising a service description, as the first task to try.
Our guide to editing website content with a CMS describes the Cargo Shark blog workflow. For your website, decide who can save a draft, who checks its accuracy and who publishes it. Updating copy and changing a form's rules may require different access.
What should you test before launch?
Follow both tasks on a phone and a computer, starting from the homepage and ending at the relevant form. Ask someone who was not involved in the design to find the customer route, then the carrier route. Record where they need an explanation.
- Check that the selected service carries into the form correctly and remains editable.
- Leave a required field empty and check that the error explains what is missing.
- Arrange a clearly labelled test enquiry, then check its contents and receipt by the intended person.
- Check repeated clicks on the submit button and what happens when the server reports an error.
- Use the form with a keyboard and check that its fields have understandable labels.
Measure customer quote requests separately from carrier introductions. A button click or form submission does not establish that work has been booked. Staff can later identify which enquiries fit the company's offer, so content decisions also reflect enquiry quality.
What should you send for a website estimate?
Prepare a list of services and operating areas, the details needed for each enquiry type and the person who handles them. Include one anonymised message that currently takes several exchanges to clarify. It often shows what the form should ask more clearly than a general request for an advanced form.
In your website estimate request, also say whether you need to edit content yourself or connect the site to existing software. That scope lets us propose a page structure and work through the forms your business needs.