The minimum team is an operations owner, an integration owner and a risk approver, with named frontline fallback. One person may cover several roles, but responsibilities should remain explicit.
| Contact | Ask them for | Evidence or decision you need |
|---|---|---|
| Operations sponsor: owner, COO or contact-centre director | The business problem, permitted scope and stop authority | Signed pilot charter |
| Reception, dispatch or patient-access supervisor | Real exceptions, booking rules and recovery work | Approved workflow and exception register |
| Finance or commercial owner | Attributable costs and alternatives | Baseline economics and investment ceiling |
| Telephone administrator or carrier support | Routing, forwarding, SIP, transfers and recovery options | Tested routing diagram and rollback procedure |
| CRM, dispatch or practice-management administrator | API access, supported objects, permissions and test environment | Access approval and integration specification |
| Platform solutions engineer or support team | Current limits, billing, data controls and failure behaviour | Written configuration and commercial answers |
| Security and privacy leads | Data flows, access, retention, subprocessors and incident response | Risk assessment and approved controls |
| US counsel familiar with calling and privacy rules | Workflow-specific legal analysis | Approved calling, recording and disclosure policy |
| Clinical owner, where relevant | Administrative boundaries and urgent-call handling | Approved escalation instructions; no autonomous clinical judgement |
| Human fallback provider | Coverage, acceptance procedure and callback ownership | Staffed handoff agreement and service runbook |
If you hire a contractor, assess more than prompting. Give candidates a practical exercise: connect a sandbox booking tool, simulate an ambiguous timeout, prevent a duplicate booking and demonstrate failed-transfer recovery.
An employer-published Hatch integration-engineer listing includes production integration work, pre-launch testing and post-launch monitoring. That is useful evidence of the breadth of implementation work, but one job advertisement is not a labour-market or salary benchmark. (jobs.ashbyhq.com)
What should your first integration enquiry say?
Use this buyer-written template:
We are evaluating an inbound voice pilot for one workflow and one location. Please confirm our account’s supported read and write operations, authentication method, permission scopes, test-environment access, rate limits, transaction identifiers and error behaviour. We need to distinguish a pending request from a confirmed booking, verify the final record, prevent duplicate submissions and reverse routing without changing our public number. Please identify any additional charges, contractual restrictions and production-access approvals.
Send it to both the business-system owner and the voice-platform contact. Require them to agree on where each responsibility sits.