Documentation

Agent handoff

Business and above. Create the task, not just the message.

Agent handoff closes the loop. When a rule fires, SIGNLD issues a task into the system where the work is tracked, with the finding and a link to the sourced Brief attached.

Supported target categories

Category	Example task
HR	Open a staffing review when overtime crosses a threshold at a location
CRM	Create a task on the account when spend drops more than 20 percent
PSA	Raise a project review when realised rate falls below plan
ITSM	Open an incident when a data source stops reporting

Set one up

1
Confirm the plan
Agent handoff is available on Business and above, which also includes the read and write API plus webhooks.
2
Authorise the target system
Handoff uses a scoped write credential for the target system only. Source connections used for reading stay read-only.
3
Pick the rule and the task template
Choose the rule, then map the task type, queue or owner, and priority.
4
Map the fields
Map entity, finding, figures, and the Brief link into the task fields so the assignee has context.
5
Add a duplicate guard
Set a window that prevents a second task for the same entity while the first is open.
6
Run a test handoff
Fire once against a test queue, confirm the task lands correctly, then enable it.

Safety boundary

SIGNLD reads from your systems of record read-only. A handoff writes only into the target work system you explicitly authorise, and only the task fields you mapped.

Agent handoff FAQ

Does agent handoff let SIGNLD change my source data?

No. Data connections remain read-only. Handoff creates a task in a work system you authorise separately, using a scoped credential.

Which plans include agent handoff?

Business and above. Growth workspaces can notify with action triggers instead.

Can a person approve before a task is created?

Yes. A handoff can be set to propose the task for confirmation rather than issuing it automatically.