3. What does “books directly into our diary” mean when two callers want the same slot?

Draft answer framing: A booking should be treated as confirmed only after the authoritative job system accepts a valid appointment—not merely because the agent says it has booked one.

Why it matters: Joblogic’s API terms distinguish predefined approved operations from unconstrained autonomous actions, and specify conditions for automated record changes. Buyers therefore need both operational proof and permission for the exact workflow. (joblogic.com)

Put this question to the expert:

“Demonstrate a real booking, then repeat it with a simultaneous caller, a duplicate customer and a failed API response. What does the customer hear in each case?”

A strong answer should cover these proposed controls:

• One authoritative diary and a clear distinction between a request, provisional hold and confirmed appointment.
• Validation of service area, job duration, engineer competence, travel allowance, contract priority and access arrangements.
• A method for preventing duplicate jobs when an integration retries.
• No verbal confirmation before a successful write-back; an honest fallback when confirmation is unavailable.
• A reconciliation queue for partial failures and an audit trail linking call, customer, job and appointment.

Evidence to request: Test-system records showing the actual write, conflict handling, retry outcome and customer communication.

Follow-up: “Which actions have you deliberately withheld from the AI, even though the API makes them possible?”

Expert quote: ____________________