Work With Us

Start with a slot-first booking request, or drop back to a callback-first path if that’s easier.

This is the live partner landing page for filce.uk. It keeps the appointment-led flow up front, preserves a lighter callback alternative, and sends every submit into the server-side intake endpoint so the lead is tracked in the project-owned intake log without depending on the mail client. If the optional external mirror fails, the form now surfaces a visible operator note instead of dropping the lead silently.

What happens next

  1. Pick the route — slot-first if you want to book a time, callback-first if you want a lighter start.
  2. Fill the form — short, visible fields only, with optional notes and photo filenames carried through.
  3. Submit the request — the button posts to the intake endpoint, stores a tracking reference in the project intake log, and surfaces a warning only if the optional external mirror fails.
  4. Confirm the next step — reply with the slot or callback window that works best.

If you’d rather email directly, use contact@filce.uk.

Seller disclosure experiment

Show the fee, payout, hold, and dispute summary before seller setup.

This block surfaces the compact risk summary before the live form so the next step is framed as an informed choice, not a surprise.

Continue to seller setup See full seller terms

Live landing page

Lean slot-first lead flow, with callback-first fallback.

This is the live version of the form component: the appointment-led route stays first, the fallback stays obvious, and every submit posts to a server-side intake endpoint so the lead is captured without depending on the user's mail client.

  • Slot-first path asks for the booking details before deeper qualification.
  • Callback-first path keeps time-of-day preference instead of forcing a full calendar choice.
  • Optional notes and photo filenames are carried through the intake endpoint for follow-up.

Primary slot-first booking

Book the slot first, qualify after.

This path keeps the appointment choice visible early and avoids a long questionnaire before the visitor gets a time.

  1. Service needed
  2. Postcode
  3. Date
  4. Time slot
  5. Name
  6. Phone
  7. Email
  8. Brief issue details
  9. Optional notes / upload

Fallback callback-first

Request a callback, then offer a slot.

This is the lighter fallback for people who do not want to choose a date and time immediately.

  1. Service needed
  2. Postcode
  3. Preferred time of day
  4. Name
  5. Phone
  6. Email
  7. Brief issue details
  8. Optional notes / upload

Slot-first live form

Booking first, not questionnaire first.

The submitted draft is stored in the project intake log with the key booking details pre-filled.

Primary path
1
Service needed required
Damp proofing, timber treatment, mould investigation, or a mixed issue.
2
Postcode required
Used to route the lead to the right local team.
3
Date required
A near-term choice, not a blank calendar.
4
Time slot required
Three visible choices — no empty calendar UX.
5
Name required
The person to contact once the slot is held.
6
Phone required
Main callback channel if the slot needs a quick reschedule.
7
Email required
Used for confirmation and follow-up notes.
8
Brief issue details after slot
Short context only: where the issue is, what you noticed, and when it started.
9
Optional notes / upload only if needed
Notes stay optional. If photos are selected, the filenames are included in the email body.

The submit button posts to the server-side intake endpoint and stores the lead in project-owned intake log instead of opening a mail draft. If the optional external mirror fails, the form shows a visible status note instead of dropping the lead silently.

Fallback live form

Callback-first as the lighter alternative.

This version uses a time-of-day preference and sends the request to the same durable intake storage.

Fallback path
1
Service needed required
Same service taxonomy as the slot-first version.
2
Postcode required
Used to route the callback to the right local team.
3
Preferred time of day required
Morning / afternoon / evening is the lightest fallback.
4
Name required
Who should we call back?
5
Phone required
The callback number comes before the deeper detail.
6
Email required
Used for the request summary and next steps.
7
Brief issue details after request
Enough to help the team prepare before calling back.
8
Optional notes / upload only if needed
Notes stay optional. If photos are selected, the filenames are included in the email body.

The submit button posts to the server-side intake endpoint and stores the lead in project-owned intake log instead of opening a mail draft. If the optional external mirror fails, the form shows a visible status note instead of dropping the lead silently.