Book a plumber
bookBook a plumber from a find (business_id + find_id). Version 1 is a handoff: Tallyho records the request and returns the plumber's phone number and the questions to ask; nothing is booked until the user calls, so booked is false. Don't send the user's contact details on a handoff; they are never stored either way. Keep the booking_id and call report after the call to the plumber, and again after the job.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"business_id": "<business_id>"
},
"name": "book"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | No | Required when there is no find_id; otherwise the search's job is used. | |
| test | No | Defaults to the search's environment. | |
| channel | No | Default: the best available. Version 1 offers only handoff. | |
| contact | No | The user's details for the business. Never stored; unused on a handoff. | |
| find_id | No | The search this business came from. Required unless `job` is given. | |
| promises | No | ||
| business_id | Yes | ||
| principal_ref | No | Any stable id for the user; only a salted hash is kept. | |
| principal_name | No | On a Tallyho call: the first name the call uses ("calling for Jordan"). Spoken, never stored. Without it, "the property owner". | |
| idempotency_key | No | ||
| previous_booking_id | No | The booking this one follows, e.g. after a counter-offer. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes | ||
| call | No | ||
| booked | Yes | ||
| status | Yes | ||
| channel | Yes | ||
| handoff | Yes | ||
| billable | Yes | ||
| business | Yes | ||
| booking_id | Yes | ||
| environment | Yes | ||
| contact_used | Yes | ||
| report_after | Yes | ||
| check_after_s | No | ||
| contract_version | Yes | ||
| promises_in_scope | Yes |