Is Marcus a real person?

No. Marcus is an AI employee, not a person. He is labelled AI employee, not a person on the page. If a customer asks whether they are dealing with a human, the answer is no.

What does Marcus do after a job is booked?

Once a booking is confirmed, Marcus drafts two messages: the dispatch to the technician covering job type, address, scheduled time, customer contact, and notes; and the booking confirmation to the customer. Both drafts wait for your approval before anything sends.

Does Marcus send the dispatch and confirmation automatically?

No. Both drafts need your approval before they go anywhere. You review both messages, edit if needed, then send them yourself. Calendar sync, two-way SMS confirmation, and Jobber integration are planned for a later phase and are not live.

Will Marcus tell a customer their appointment is confirmed before you have approved it?

No. Marcus will not commit a slot or tell a customer a time is confirmed if the booking has not been approved by you. The confirmation draft is held until you approve it.

Does Marcus work with Jobber or other field-service software?

Not yet. Jobber integration, calendar sync, and two-way SMS are planned for a later phase. Right now Marcus produces the two draft messages — dispatch and confirmation — and you send them from your existing tools.

What does Marcus cost?

The hosted and managed option is $79 per month. If you bring your own API key, the one-time fee is $797. Custom integrations are quoted on request.

Marcus

Scheduler / Dispatcher Ops Team

Nothing sends without your approval — every dispatch holds until you say yes

Job booked. I draft the dispatch to your tech and the confirmation to your customer. You approve before either one sends.

Hire me

Marcus chains off Michelle. She takes the call and books the job. I pick it up from there — the dispatch goes to the tech, the confirmation goes to the customer. Together the handoff takes about 90 seconds of your time.

Hi. I am Marcus. Tell me what was booked — job type, date and time, customer name, tech name — and I draft two things: the dispatch message the technician needs to move, and the confirmation the customer expects to receive.

Right now I draft. You approve. Calendar sync and Jobber integration are Phase 2 — I will say so plainly. Give me a real booking below.

Tell me what was just booked. I will draft the dispatch and the confirmation.

One free draft. No account. Give me the booking details — job, date, customer, tech. This is live AI, not a canned example.

Describe what was just booked

0 / 1200 characters

Draft by Marcus — pending your approval

These are drafts only. Nothing has been sent. Review both messages, edit if needed, then send them yourself. The tech gets the dispatch; the customer gets the confirmation.

Ready to add Marcus to your ops stack?

Template hosted from $79/mo — or bring your own API key for a one-time fee.

Hire me — $79/mo Bring my own API key — $797

What I do. What I will not do. What I handle. What I escalate.

What I do

I take a confirmed booking and produce two drafts: the dispatch message the technician needs to move on the job, and the confirmation the customer expects to receive.

The dispatch covers job type, address, scheduled time, customer contact, and any notes from the booking. The confirmation is professional and brief — what was booked, when, what to expect next.

I flag anything that was missing from the input. I do not invent addresses, phone numbers, or job details you did not give me.

What I will NOT do

I will not send anything. Both drafts need your approval first. That is not a Phase 2 feature — it is the design.

I will not invent details. No made-up addresses, phone numbers, or job specifics. If you did not give me the information, I flag it.

I will not commit a slot or tell the customer a time is confirmed if the booking has not actually been approved by you.

I will not represent myself as a person. If a customer asks whether they are dealing with a human, the answer is no.

Calendar sync, two-way SMS confirmation, and Jobber integration are Phase 2 — not live yet. Right now the stack is: Marcus drafts, you send.

What I handle

Dispatch messages for the assigned technician — job type, location, time, customer contact, notes
Customer booking confirmations — what was booked, when, what to expect
Flagging any missing information before the drafts go to you
Any job Michelle has already captured — I pick up exactly where she left off

What I escalate to you

Any booking where critical details are missing and the draft would be incomplete without them
Any situation where the tech availability or time slot has not been confirmed — I do not guess at a schedule
Any customer communication that goes beyond a standard confirmation (disputes, special requests, scope changes)

Ready to put me on your ops stack? See hiring options

Hire me.

I draft the dispatch and the confirmation the moment a job is booked. You approve. Then they go.

The average field-service no-show costs $200–$400 in wasted drive time. One confirmation that actually goes out covers a year of the $79/mo plan.

Template hosted

Start today, no custom setup required.

Hosted and managed. Immediate access. No infrastructure setup.

Template hosted:
$79 / month start here

Bring your own API key (one-time):
$797

When you are ready for Jobber integration and calendar sync, that is the custom version — Phase 2.

Secure checkout via Stripe. Cancel any time from the customer portal.

Bring your own API key

Own the setup. Pay once.

One-time fee. You supply the OpenAI API key. We set it up. No monthly subscription to us — you pay OpenAI directly for usage.

BYO API key (one-time):
$797

Custom with Jobber / calendar integration (Phase 2):
Quoted on request

Hire me — $797 one-time

Questions first? Email hello@ai-field-guide.com

Drafts only — nothing sends without your approval No invented details — if I don't have it, I flag it Chains off Michelle — no handoff gap