Submit a transport requestShip my horse

Usecase

Horse transport requests: every lead in one place

Move.horse collects horse transport requests from Facebook and directly from clients on the portal, and displays them to transporters in a single feed. Only relevant requests get through, the feed can be filtered in several ways, and each request's route can be analyzed and merged with your scheduled trips. Available in the web app and the mobile app.

Why this matters

For most horse transporters, finding clients means patrolling Facebook groups. Requests appear in dozens of communities, in different countries and languages, mixed in with sales posts and general discussion. Other leads arrive through the website or by phone — and every channel has to be checked separately, several times a day. Miss a post by a few hours, and another carrier has already answered it.

Even the leads you do find are mostly noise. A request from the wrong region, a route you don't cover, or more horses than your lorry can take is a lead you never could have served. Sorting the relevant few from the irrelevant many is manual work that competes with driving, quoting, and caring for the horses on board. And relevance goes deeper than geography: the most profitable request is often the one that fits a trip you've already scheduled — and no Facebook feed will tell you that.

Move.horse gathers transport requests in one place and shows you only the ones that match your business. It collects requests created by clients on the portal and discovers fresh ones on social media, then checks them against your capacity, base country, and operating countries. Flexible filters narrow the feed further — by distance from your base, around custom locations, or specifically to requests that can be merged with your scheduled trips. The result is a single feed of workable leads in the web app and the mobile app, instead of a day spent scrolling.

How to use it

Horse transport requests: every lead in one place

Requests reach your dashboard from two sources: internal ones, created by clients on the move.horse platform, and external ones, discovered on social media within the last few days. A request appears only if it matches your business profile — the number of horses is within your maximum capacity, one country on the route is your base country, and the other is on your list of operating countries (for the US, Canada, and Australia, state and province filters apply too). In the mobile app, you open the feed with the "Open requests" button on your dashboard, where Facebook requests carry a blue "F" icon and move.horse requests an orange "M".

The matching logic is adjustable. Tap the "Matching" button to set up three filters: by base location (your whole country, or a set distance from your base), by scheduled trips (requests that can be merged with trips in your Scheduler, or that sit within a distance of your trip stops), and by custom places (any address with a radius around it). That last one is useful when you know you'll be somewhere anyway — say, returning from a competition with empty stalls.

Working a request depends on its source. For a Facebook request, the "Open link" button (or "Open post" on the web) takes you to the original post so you can contact the author directly. For a move.horse request, the "Message" button (or "Send offer or question" on the web) opens a chat with the client right in the app. Before committing, you can preview the route on Google Maps, or tap "Analyze" to get a Route analyzer report — including whether the route can be merged with one of your scheduled trips. Requests that don't interest you are removed with "Skip", and if a post was already deleted or recognized incorrectly — detection is AI-based, so occasional errors happen — the "Report" button flags it for review. The feed stays clean, and every lead you see is one you could actually take.

Managing requests in the browser

Managing requests with the mobile app

Frequently asked questions

Where do the transport requests on move.horse come from?

From two sources: internal requests created by clients directly on the move.horse platform, and external requests discovered on social media such as Facebook. Internal requests include all active ones; external requests are from the last few days, so the feed stays fresh.

Why don't I see every request on the platform?

Because requests are matched to your business profile first. A request appears only if the number of horses fits your maximum capacity, one country on the route is your base country, and the other is on your operating list — with state and province filters for the US, Canada, and Australia.

Can I filter requests to match my scheduled trips?

Yes. The "By scheduled trips" filter shows requests that can be merged with trips in your Scheduler, either by country or within a set distance from your trip stops. There are also filters by base location and by custom places with a radius.

How do I contact the client behind a request?

For a move.horse request, use the "Message" button in the app or "Send offer or question" on the web to chat with the client directly. For a Facebook request, use "Open link" or "Open post" to reach the original post and reply there.

Do you charge any commitons from orders completed with your service?

No. We charge a small fee to process every request. But as some credits are included even in a Free plan, you can process 10-20 requests per month for free.

Other usecases