Potential integration must be assessed against Joblogic’s API permissions and terms, not just a supplier’s claim that it has a connector. Public API access is not unrestricted permission for an autonomous agent to modify records.
Joblogic’s published terms require disclosure of AI integrations and constrain activity to an approved scope. They also address human review of automated record changes, with an exception involving notification of the specific workflow, its inclusion within the approved scope and customer responsibility. Credential sharing has its own consent requirements. (joblogic.com)
Before a supplier receives access, obtain:
- Confirmation of the approved integration and agency access arrangement.
- The endpoints, fields and operations it may use.
- Written clarity on when human confirmation is required.
- A demonstration of the proposed call-to-record workflow.
- Logging, incident and access-revocation procedures.
Do not interpret this research as confirmation that a named agency has permission, that a native receptionist is available on your plan, or that every proposed action is supported. Those are procurement questions to resolve with Joblogic and the implementation supplier.
Sources cited on this page
- joblogic.com ↗www.joblogic.com