A ← Integrations
Internal · Housecall Pro MCP
Housecall Pro Housecall Pro
Agent file

Eric

Johns Pest virtual receptionist. He talks on the phone. MCP writes and reads Housecall Pro. He only confirms a book, a move, or a note when the tool status says it actually happened.

Call Eric +1 (603) 441-3315
Records

Watch the walkthroughs

Two recordings from the live Housecall Pro integration. MCP is wired to Eric and these calls were tested against the real calendar.

Who he is

Agent details

Name

Eric

Says it on the first line. Do not swap the voice.

Shop

Johns Pest

Vancouver. 90-minute default visit.

Calendar

Sameer Khan

He books this tech. He must not say the name out loud.

Timezone

America/Vancouver

Naive times are shop-local, not UTC.

Goals

What this integration is for

Answer like a front desk

Short turns. One question at a time. No invented customers, times, or prices.

Use the real Housecall Pro calendar

Openings are Sameer’s empty gaps. A book creates a real job. A move changes a real job.

MCP is the only bridge

The model never talks to Housecall Pro itself. It calls six n8n tools. We inspect those calls in the logs workflow.

Architecture

What we actually built

  1. Caller hits +1 (603) 441-3315.
  2. Vapi answers as Eric (prompt + MiniMax voice + Deepgram Flux).
  3. Eric calls MCP tool housecall_pro_mcp.
  4. n8n trigger path hcp-voice runs one Code Tool.
  5. That tool hits Housecall Pro with Authorization: Token.
  6. JSON comes back with a status. Eric may confirm only on booked, rescheduled, or noted.
How to test

Place a call, then check the system

On the phone

  1. Dial +1 (603) 441-3315 or use Vapi Talk on assistant Eric.
  2. Speak like a customer. Do not say tool names.
  3. Give a real first and last name. First name only should not look anyone up.
  4. If he asks for an address, give street, city, and postal code.
  5. For times only, say “don’t book anything.”
  6. After bye, he should hang up.

After you hang up

  1. Housecall Pro → Schedule → View by employee → Sameer. Empty gaps are openings. A new block is a book.
  2. Timezone on that calendar must be Vancouver.
  3. HCP · MCP · Logs → Executions. Open Readable log row: tool, status, asked, returned.
  4. Vapi call → Railway-* tool rows if you need the raw MCP args.
  5. Fail if he said 11:00 and the job is 4:00 AM.
Scenarios

What we can test

Scenario You say Tools that should run Pass
Times only Don’t book. What do you have tomorrow morning? get_open_times 2–3 day+time slots. No tech name. No new job.
New visit Ants in the kitchen. Tomorrow morning if you can. find_customerget_open_timesbook_visit Status booked. Job on Sameer at that time.
Move I need to move my visit. Friday morning. lookup_visitget_open_timesmove_visit Status rescheduled. Same job, new time.
Lookup When is someone coming to my place? lookup_visit He reads the when. Calendar unchanged.
Note Note we have a dog. Use the side gate. add_customer_note Status noted. Note on the customer.
Cancel Cancel my visit. None that delete a job He takes a message. Job still there.
First name only “Adham” then wait No find yet He asks for last name before lookup.
Examples

Scripts that exercise the MCP

Availability

Hey, this is Maria Santos. Don’t book anything. What times do you have tomorrow morning?

Expect get_open_times only. Cross-check Sameer’s empty morning slots.

Book

I’ve got ants in the kitchen. Tomorrow morning if you can. Maria Santos. Use the number I’m calling from.

Give a full address if asked. Pick one of the times he offered. Then open Housecall Pro and find that job.

Move

I need to move my visit. Friday morning instead.

He should look up the visit, offer free times, then move. Confirm the when field, no tech name.

Note

Can you note we have a dog, and to use the side gate?

Logs should show add_customer_note / noted.

On the system

What each layer should show

Housecall Pro

Schedule

Schedule → Day or Week → View by employee → Sameer. Shop hours are usually Mon–Fri 8:00–5:00. A book is a 90-minute block. Times-only leaves the board empty.

MCP logs

Workflow HCP · MCP · Logs. Each run is one row: summary, tool, status, name, when, asked, returned. Voice workflow executions are only the handshake. That is expected.

Six tools

find_customer, get_open_times, book_visit, move_visit, add_customer_note, lookup_visit. Confirm only on booked / rescheduled / noted.