Farrier New-Client Intake Form: What to Ask Before You Accept the Appointment

Overview

A new-client farrier request is different from a routine rebooking.

Before accepting a mobile visit, the business may need to know where the horse is, how many horses are involved, what service is being requested and whether the location fits the current round.

The intake form should collect enough information to make that decision without becoming a horse medical record.

The minimum useful intake

A practical request can start with:

That is usually enough for an initial scheduling decision.

Treat these as intake-design fields, not as a claim that every OneStudio form configuration exposes every field type. Use only the fields and controls actually supported in the project, and adapt the request flow if a detail must be collected another way.

• client name;
• phone number;
• email address;
• barn, yard or property location;
• requested service;
• number of horses;
• preferred days or time windows;
• short free-text note;
• consent to be contacted about the request.

Ask for location early

For a mobile farrier, geography is operationally important.

Useful location fields might include:

Do not promise that the system calculates route efficiency, mileage or travel fees automatically.

• postcode or ZIP code;
• town or locality;
• barn or yard name;
• street address if needed for the visit;
• simple access note.

Use service choices that match the website

The intake form should use the same labels as the public service pages.

For example:

Avoid an enormous list of technical variations unless they are genuinely useful for scheduling.

• routine trim;
• front shoes;
• full set;
• reset;
• other / needs discussion.

Horse count matters more than a long horse profile

A first request may need the number of horses because visit length can change materially.

That does not mean the website needs to collect a detailed horse record.

Keep the first step proportionate.

Avoid unnecessary clinical data

A public lead form is not the right place to collect broad health histories.

Do not ask for fields such as:

unless the business has a specific, lawful, secure and genuinely necessary workflow outside the basic website request process.

The public intake can ask the client to describe the service need in ordinary language without asking the website to diagnose it.

• diagnoses;
• medications;
• veterinary reports;
• detailed pathology;
• X-rays;
• medical history;

Separate request submission from appointment acceptance

The confirmation after a new-client form should be explicit.

Good language can say that:

That is safer and clearer than displaying a final appointment confirmation when manual review is still required.

• the request has been received;
• the business will review location and availability;
• the appointment is not confirmed until the farrier accepts it;
• the client will receive the next step.

Use direct booking for the clients who fit it

The same website can support a different route for predictable, repeat visits.

Where a farrier can define a real service duration and available times, OneStudio can expose open slots through online booking.

That creates a useful split:

new client → request and review

eligible returning client → real available booking slot

The exact implementation depends on the project and the farrier's scheduling model.

Keep intake data useful inside the client workflow

OneStudio's public product pages confirm ordinary client records, contact details, interaction history and related bookings.

A sensible intake process should preserve the basics needed to continue the relationship without pretending the CRM is a horse-specific practice-management system.

Add form friction only when it reduces real admin

Every extra field lowers completion.

Before adding a question, ask:

Will this answer change whether I accept, schedule or prepare for the visit?

If not, remove it.

A practical intake flow

1. Contact details.
2. Location.
3. Service.
4. Horse count.
5. Preferred timing.
6. Short note.
7. Submit request.
8. Manual review.
9. Confirm or propose another next step.

What the intake form should not become

Do not turn it into:

• a veterinary questionnaire;
• a diagnostic tool;
• a route optimizer;
• a shoe inventory request;
• a specialist horse-record database;
• a guaranteed estimate engine.

Make the first request easier to review

A short, focused intake form can reduce phone tag while keeping the business in control of a mobile schedule.

Explore OneStudio features and pricing.