Owner check: booking link, delivery confirmation and thank-you step

Live test, in order:

  1. n8n: set the webhook to respond using a Respond to Webhook node. It returns JSON {"ok":true} with status 200 and the header Access-Control-Allow-Origin set to this site's exact origin (scheme + host, no trailing slash).
  2. Create a 20-minute event in Cal.com or Calendly. Set notifications to julien@relaycairn.com.
  3. Paste the https:// link into BOOKING_URL at the top of the script at the bottom of this file, then republish.
  4. Reopen this page at /#booking-check on your phone. Tap every button listed above. Each should open your calendar in a new tab.
  5. Make one test booking. Confirm the notification arrives at julien@relaycairn.com.
  6. Submit the form once with the message "TEST - ignore". The "Received" panel must appear only after n8n answers 2xx with {"ok":true}, and the lead must arrive in n8n. Hidden site value is automation.
  7. Failure test: turn off your network (or temporarily deactivate the n8n workflow) and submit again. The red error message must appear, the form must stay filled in, and "Received" must not show.
  8. Delete the test booking and the test leads.

This panel shows only when the address ends in #booking-check. Visitors never see it.

Relaycairn Request a scoping call

AI operations for freight brokerages & 3PLs

Your reps shouldn't be the copy-paste layer between the inbox and the TMS.

For owner-operated brokerages doing roughly $1M-$20M in revenue, we design and build the back-office workflows that quietly eat your team's day.

  • Reps retyping rate-request emails into the TMS, one lane at a time.
  • Carrier packets and expired COIs chased by hand, usually after a load is already booked.
  • Invoice and POD reconciliation that runs behind and delays the cash you've already earned.

Done-for-you engagements, $5k-$25k depending on scope. AI drafts are reviewed by your people before anything goes out.

Where the hours go

Four repetitive workflows. One or two usually hurt most.

Brokerage work is email-heavy and exception-heavy. Most of the drag sits in four places. We look at all four in the audit, then build the one or two that fit your operation.

1

Inbound quote-request triage and draft replies

The manual pattern
Shipper emails land in a shared inbox. A rep reads each, pulls out origin, destination, equipment, dates and weight, retypes it into the TMS or a rate sheet, then writes the reply.
What gets automated
Sorting requests from noise, extracting lane details into a structured summary, and drafting a reply for the rep to edit.
Human step
A rep confirms the details and the rate before any quote is sent.
2

Carrier onboarding document collection and expiry reminders

The manual pattern
Packets, W-9s, authority and insurance documents come in piecemeal. Someone tracks what's missing in a spreadsheet and chases COIs as they expire.
What gets automated
A checklist per carrier, follow-up drafts for missing items, document field extraction, and expiry reminders ahead of the date.
Human step
Your compliance owner approves a carrier. Nothing is auto-approved on the AI's say-so.
3

Load-status check-call and update automation

The manual pattern
Reps call or text for status, then email the customer an update. It repeats for every load, several times a day.
What gets automated
Scheduled status requests, parsing replies into a consistent update, and drafting customer messages. Late or silent loads get flagged for a person.
Human step
Exceptions go to a rep. Whether routine updates send automatically is your decision, load type by load type.
4

Invoice and POD matching with exception flags

The manual pattern
PODs arrive by email or portal. Someone matches each to a load, checks rates against the confirmation, and builds the invoice, so cash waits on the slowest step.
What gets automated
Matching PODs to loads, comparing paperwork against load data, and listing mismatches, missing PODs and accessorial questions in one queue.
Human step
Someone on your team approves invoices before they go out or post to accounting.
Illustrative example only, not a result or a promise: if a rep spends 4 minutes retyping each of 30 rate requests a day, that is about 2 hours of typing a day for that one task. Your numbers will differ. We'll measure yours in the audit rather than assume ours.

Sample walkthrough

One workflow, start to finish: a rate-request email becomes a reviewed draft.

This shows workflow 1 from the list above, step by step, so you can see where the AI stops and your rep takes over. Every name, lane and detail below is made up for illustration.

Mock dataFabricated example. Not a client, not a real shipper, not a measured result. The company, contact and lane do not exist. No rate is shown because the AI never sets one: the rep enters it.
Step 1 · Input

1Email arrives in the shared inbox

From: dispatch@example-shipper.test
To: quotes@your-brokerage.test
Subject: Truck needed Dallas to Atlanta

Hi, can you quote a load from
Dallas TX to Atlanta GA? About 38,000 lbs
of boxed goods, 22 pallets. Need it picked
up Thursday morning, delivered by Friday
if possible. Let me know.

Thanks,
Sam (Example Shipper Co.)
Step 2 · AI extraction

2Details pulled into a structured summary

OriginDallas, TX found
DestinationAtlanta, GA found
Weight / pallets~38,000 lbs, 22 pallets found
EquipmentNot stated flag
Pickup window"Thursday morning", no address or time flag
Delivery"by Friday if possible" flag: firm or flexible?
Rateleft blank for rep

Anything missing or ambiguous is flagged instead of guessed.

Step 3 · AI draft (not sent)

3Reply drafted for the rep to edit

Hi Sam,

Thanks for reaching out. To quote
Dallas, TX to Atlanta, GA, can you
confirm:

- Equipment: dry van or something else?
- Pickup address and time window on
  Thursday
- Whether Friday delivery is firm

Rate: [REP ENTERS RATE]

Best,
[REP NAME]
Step 4 · Human review

4A rep checks, edits and approves

Try it. This is a demo with no real data. Nothing is sent anywhere.

Status: Draft, waiting for human review. Not sent.
Request a 20-minute scoping call

In a real engagement we build this against your own redacted samples, your TMS fields and your approval rules, then test it in review mode before it touches live mail.

How an engagement works

Audit, scoped build, handoff.

Fixed scope, written down before building starts. Timeline depends on scope and on how quickly we get sample emails, exports and access.

Audit

  • Walk through your inbox, TMS exports and current process.
  • Review real (redacted if you prefer) samples of each workflow.
  • Pick the workflow or workflows worth building first.
  • You get a written scope, price and list of what we need from you.

Scoped build

  • Built around your stack and your rules.
  • Tested on your own samples in review mode first.
  • Approval steps built in wherever a wrong output would cost you.
  • Exceptions are flagged for a person, not guessed at.

Handoff

  • Written documentation of how each workflow runs.
  • Walkthrough for you and the people who use it.
  • Clear instructions to pause or switch off any automation.
  • You decide afterward whether to extend the scope.
Typical price bands (set after the audit, not a quote)
ScopeBandWhat moves the price
One focused workflowabout $5k-$10kNumber of document or email types, how clean your data is, and the approval rules.
Two or three connected workflowsabout $10k-$18kHow the workflows share data and the tools involved.
Full four-workflow systemabout $18k-$25kStack complexity, volume, exceptions and training needs.

Bands show how scope drives price. Your quote depends on your stack, volume and process. We don't promise savings or a specific payback period.

Which workflow first?

Four quick questions. A suggested starting point.

Pick the answer closest to your week. Your result carries into the form below so the scoping call starts in the right place. It's a conversation starter, not a diagnosis.

1. Which sentence sounds most like your week?
2. If you got a few hours back each week, where would they come from?
3. What's the most visible problem right now?
4. What does the owner end up personally fixing?

FAQ

Questions owners ask first.

What data and access do you need?

Only what the scoped workflow needs: typically a shared mailbox or a set of sample emails, TMS exports or reports, and sometimes read access to accounting data. We prefer exports and limited-permission accounts to full admin logins, and we agree on this in writing during the audit. Accounts stay yours, and access can be revoked at handoff or any time before.

If you'd rather start with redacted samples, we can do the audit that way.

Does a human approve what the AI produces?

Yes. AI drafts are reviewed by people. Quote replies, carrier approvals and invoices go through an approval step by default, as in the mock walkthrough above. If you later want certain low-risk messages to send automatically, such as a routine status update, that's a rule you set explicitly and can turn off.

AI can misread a document or an email. That is why anything unclear is flagged for a person.

Do I stay in control as the owner?

Yes. You decide which workflows get built, what needs approval, and what stays manual. Each workflow comes with plain-language documentation and a way to pause it. You aren't locked into ongoing work, and you can extend scope later or run it yourselves.

What tools do you work with?

We work with email, TMS exports and reports, Google Workspace or Microsoft 365, and QuickBooks. Exactly how each connects is scoped per your stack. We don't claim a pre-built integration for every TMS. During the audit we confirm what's feasible with yours (API, export, email or a manual step) before you commit.

Will this replace my TMS or my people?

No. It sits around your TMS and inbox to cut retyping, chasing and matching. Your team keeps the judgment calls and the relationships.

Can you guarantee savings or a payback period?

No. Results depend on your volume, data quality and how your team uses the workflows. We measure your current process in the audit so you can judge the likely value yourself. We don't offer guarantees or share made-up ROI figures.

Next step

Tell us where it hurts. We'll tell you if we can help.

The short form takes about two minutes. It tells us your size, your TMS and your biggest bottleneck, so a 20-minute scoping call is useful rather than generic.

Request a 20-minute scoping call

Send the form and we'll reply with times for a 20-minute call.

Prefer email? Write to julien@relaycairn.com with your company, TMS and monthly load volume.

We use your details only to reply about this request. See our privacy policy. Don't include confidential shipper or carrier data in this form.